Bugs item #2138166, was opened at 2008-09-30 14:39 Message generated for change (Comment added) made by markit You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2138166&group_id=180599
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: qemu Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: John Rousseau (johnrrousseau) Assigned to: Nobody/Anonymous (nobody) Summary: Vista guest fails to start on kvm-76 Initial Comment: CPU: Intel(R) Core(TM)2 Duo CPU T7250 @ 2.00GHz Build: kvm-76 Host kernel: 2.6.26.3-29.fc9.x86_64 Host arch: x86_64 Guest: Windows Vista Ultimate 64-bit QEMU command: qemu-system-x86_64 -hda /home/jrr/vista-x86_64.img -m 2048M -net nic,vlan=0,macaddr=52:54:00:12:32:00 -net tap,vlan=0,ifname=tap0 -std-vga -full-screen -smp 2 I've been running this guest on this host with kvm-75 without difficulty. kvm-76, built the same way that kvm-75 was (and on the same machine), fails to start my guest. The guest window is up, but the guest fails to complete startup. Command line output is: kvm_create_phys_mem: File existsset_vram_mapping: cannot allocate memory: File exists set_vram_mapping failed kvm: get_dirty_pages returned -2 The last line repeats hundreds of times. ---------------------------------------------------------------------- Comment By: Marco Menardi (markit) Date: 2008-10-10 14:02 Message: I've the same issue with my XP-32 guests, I've Debian64 sid, Phenom 9550, kernel 2.6.26-1-amd64. Everything works like a charm with kvm-75 instead (and I've had to revert to 75, of course). Any news? Would love to have forecoming kvm77 with this blocking bug fixed. ---------------------------------------------------------------------- Comment By: John Rousseau (johnrrousseau) Date: 2008-10-03 02:06 Message: kvm-2646c5.tar.gz: Worked fine kvm-d558461.tar.gz: Failed (showed this bug) I've never used git before, but if you teach me to fish... I installed git, pulled the userspace and kernel trees, built kvm-75 and kvm-76 and got the expected results, but when I did a bisect on kvm-75 (good) and kvm-76 (bad) I kept getting sparse trees that I couldn't build. "configure" among other things was missing. What am I doing wrong? Also, what should I be syncing my kernel tree to when I am bisecting the userspace tree? Thanks. ---------------------------------------------------------------------- Comment By: Glauber de Oliveira Costa (glommer) Date: 2008-10-02 18:27 Message: Are you using git? If so, can you bisect to find out who the culprit is? If not, I've managed to archive two strategic commits you should try: http://glommer.net/kvm-2646c5.tar.gz and http://glommer.net/kvm-d558461.tar.gz please report success or failure with them thanks! ---------------------------------------------------------------------- Comment By: John Rousseau (johnrrousseau) Date: 2008-10-02 17:48 Message: I applied the patch to kvm-76 and ran into basically the same problem. The guest still hung during boot and I got the plume of kvm: get_dirty_pages returned -2 errors, but the first message "kvm_create_phys_mem: File existsset_vram_mapping: cannot allocate memory: File exists" wasn't displayed. ---------------------------------------------------------------------- Comment By: Glauber de Oliveira Costa (glommer) Date: 2008-10-02 15:01 Message: can you please test the patch at http://glommer.net/band-aid.patch ? ---------------------------------------------------------------------- Comment By: Brian Jackson (iggy_cav) Date: 2008-09-30 16:06 Message: This was reported on the mailing list. It's a problem with sdl output. Not specific to any guest. Until the problem is fixed, I'd suggest using vnc output. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2138166&group_id=180599 -- 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
