Michael Malone wrote: >>> When I run [kvm-76] it using the --std-vga parameter, >>> windows boots to just before it gets to the "welcome" >>> screen and hangs. The output shows a multitude of >>> "kvm: get_dirty_pages returned -2"
[...] Glauber Costa replied: >> It's a regression introduced in last version. It should work using >> cirrus vga (can you confirm, please?) >> >> There are some quick hacks, but I'll be trying to work on a proper >> fix in the following days. Then Glauber Coster additionally replied: > This is a band aid, but proves the general idea. Can you > confirm that it fixes the problem for you ? When I use kvm-76 with -std-vga (I am booting an XP3 guest under a Linux 32-bit PAE host) I see this: kvm_create_phys_mem: File existsset_vram_mapping: cannot allocate memory: File exists set_vram_mapping failed kvm: get_dirty_pages returned -2 kvm: get_dirty_pages returned -2 kvm: get_dirty_pages returned -2 kvm: get_dirty_pages returned -2 kvm: get_dirty_pages returned -2 ...zillions of this line... When I omit -std-vga and use Cirrus VGA, it works fine. When I apply glommer's abovementioned band aid patch and use -std-vga then the problem is different, but not fixed. I no longer see the kvm_create_phys_mem error, nor the set_vram_mapping error, but the: kvm: get_dirty_pages returned -2 kvm: get_dirty_pages returned -2 kvm: get_dirty_pages returned -2 kvm: get_dirty_pages returned -2 kvm: get_dirty_pages returned -2 ...zillions of this line... still appears. kvm-75 shows none of these issues and appears to work just fine. HtH. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
