[Qemu-devel] Resuming a guest freezes on high resolutions

[Qemu-devel] Resuming a guest freezes on high resolutions

[Robert Annessi]

[-- Attachment #1: Type: text/plain, Size: 395 bytes --]

Hi,

when using a higher resolutions then 640x480 resuming a guest freezes (I
ran into that problem with linux, fbsd and win xp guests).
The monitor still works, but the guest doesnt respond to anything.

Workaround: use -std-vga as argument to qemu (dont emulate cirrus vga
but a standard vga card).

Is this a known bug? I couldnt find any information on that.

Regards,
Robert


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

Re: [Qemu-devel] Resuming a guest freezes on high resolutions

[Fabrice Bellard]

This is a PCI save/restore issue. I am working on it. In between you can 
boot and wait until the VGA is initialized by the guest OS and then do 
the loadvm.

Fabrice.

Robert Annessi wrote:
> Hi,
> 
> when using a higher resolutions then 640x480 resuming a guest freezes (I
> ran into that problem with linux, fbsd and win xp guests).
> The monitor still works, but the guest doesnt respond to anything.
> 
> Workaround: use -std-vga as argument to qemu (dont emulate cirrus vga
> but a standard vga card).
> 
> Is this a known bug? I couldnt find any information on that.
> 
> Regards,
> Robert
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel

Re: [Qemu-devel] Resuming a guest freezes on high resolutions

[Brad Campbell]

Fabrice Bellard wrote:
> This is a PCI save/restore issue. I am working on it. In between you can 
> boot and wait until the VGA is initialized by the guest OS and then do 
> the loadvm.

If you did this, I would have thought you were letting the guest alter the state of the disk image, 
you then loadvm a suspended guest that believes the disk image is in a different state.

Kinda like hibernating linux, loading a live cd and mounting the filesystem and then resuming linux. 
All hell will break loose as the suspended system expects the on-disk state to be exactly as it was 
left, but something has messed with it in the mean time.

I kinda did this when I hibernated winxp on my box, then wrote to an auxiliary fat32 partition I 
have here within my linux session, then later resumed winxp. Windows does not cope with something 
altering the disk underneath it at all, and all hell broke loose. It would be easier if windows let 
you unmount a partition :(

Brad
-- 
"Human beings, who are almost unique in having the ability
to learn from the experience of others, are also remarkable
for their apparent disinclination to do so." -- Douglas Adams