> I disagree about bumping the memory size as a fix:
In the release notes I only mentioned changing the machine type,
however bumping the memory size does work in the qemu command line.
It's just that ...
> For many months (13.10 days) I have always been bumping the memory for
> the video, as I calculated that it should be more. Typically, I have
> this in the .xml file:
>
> And I even ran this just now:
>
> <model type='vmvga' vram='32768' heads='1'/>
>
> Question:
>
> what file or location that contains this stuff mentioned above? (so that I can look at the bigger context):
> },{\
> .driver = "VGA",\
> .property = "vgamem_mb",\
> .value = stringify(8),\
> },{\
> .driver = "vmware-svga",\
> .property = "vgamem_mb",\
> .value = stringify(8)
Hi Doug,
> I disagree about bumping the memory size as a fix:
In the release notes I only mentioned changing the machine type,
however bumping the memory size does work in the qemu command line.
It's just that ...
> For many months (13.10 days) I have always been bumping the memory for
> the video, as I calculated that it should be more. Typically, I have
> this in the .xml file:
>
> <model type='vmvga' vram='16384' heads='1'/>
Yeah, see http:// www.redhat. com/archives/ libvir- list/2014- March/msg01118. html
for why that didn't work. What you have ought to work, ideally,
but it doesn't.
> And I even ran this just now:
>
> <model type='vmvga' vram='32768' heads='1'/>
>
> Question:
>
> what file or location that contains this stuff mentioned above? (so that I can look at the bigger context):
> },{\
> .driver = "VGA",\
> .property = "vgamem_mb",\
> .value = stringify(8),\
> },{\
> .driver = "vmware-svga",\
> .property = "vgamem_mb",\
> .value = stringify(8)
hw/i386/pc_piix.c in the qemu source