Description of problem: install Window xp in kvm failed Version-Release number of selected component (if applicable): [root@dhcp-66-70-91 ~]# rpm -qa |grep qemu qemu-system-cris-0.10.4-5.fc11.i586 qemu-0.10.4-5.fc11.i586 qemu-common-0.10.4-5.fc11.i586 qemu-system-sparc-0.10.4-5.fc11.i586 qemu-system-x86-0.10.4-5.fc11.i586 qemu-system-mips-0.10.4-5.fc11.i586 qemu-kvm-0.10.4-5.fc11.i586 qemu-user-0.10.4-5.fc11.i586 qemu-system-arm-0.10.4-5.fc11.i586 qemu-system-ppc-0.10.4-5.fc11.i586 qemu-img-0.10.4-5.fc11.i586 qemu-debuginfo-0.10.4-5.fc11.i586 qemu-system-sh4-0.10.4-5.fc11.i586 qemu-kvm-tools-0.10.4-5.fc11.i586 qemu-system-m68k-0.10.4-5.fc11.i586 [root@dhcp-66-70-91 ~]# rpm -qa |grep virt virt-manager-0.7.0-5.fc11.i586 libvirt-python-0.6.2-10.fc11.i586 virt-viewer-0.0.3-4.fc11.i586 libvirt-0.6.2-10.fc11.i586 python-virtinst-0.400.3-7.fc11.noarch How reproducible: 100% Steps to Reproduce: 1.create a VM for windows xp with default settings 2.boot the VM with en_windows_xp_professional_with_service_pack_3_x86_cd_x14-80428.iso 3.during install,the "Windows XP Professional Setup"will copy files to disk.After copying finished,system will reboot automatically,but the system was shut off,start system manually,can not start up Actual results: Expected results: Additional info:
Created attachment 345557 [details] virt-manager log
Created attachment 345558 [details] xp log
(In reply to comment #0) > 3.during install,the "Windows XP Professional Setup"will copy files to > disk.After copying finished,system will reboot automatically,but the system was > shut off,start system manually,can not start up So the install completed successfully, but it failed to boot afterwards? What happens when you try and start it? Does it hang? Is there anything displayed on the console?
No, during installation,first step is to copy files to disk(after you press F8 to accept their agreements),second step is to install. when first step finished,the system should reboot and start install,but it was shut off.
Okay, just tried an XP install here - what you're seeing is a duplicate of bug #499547
*** This bug has been marked as a duplicate of bug 499547 ***