Created attachment 841965 [details] Windows 7 installed but stay indefinitely on boot screen Description of problem: I've successfully installed Windows 7 x64 using Virtual Machine Manager. After finishing installation the Windows VM boot but stau indefinitely on boot screen HW configuration for Win7 VM: ACPI enabled APIC enabled Security : Dynamic Logical host CPU: 4 Current allocation: 2 Maximum allocation:2 model: Westmere No pinning Memory total host memory: 7976 MB current allocation: 4096 MB Display Spice Channel Spice : device type spicevmc, target type: virtio, target name: com.redhat.spice.0 Video: QLX Version-Release number of selected component (if applicable): all latest version released for Fedora 20 How reproducible: Steps to Reproduce: 1. Install Windows 7 2. boot Windows 7 after installation 3. Actual results: Windows 7 installed but stay indefinitely on boot screen Expected results: Windows 7 installed booting and working fine Additional info: Troubleshooted setting SELinux as permissive or disabled: no way to make it works. Changed all setting for Display (VMVGA, VGA, Cirrus,...) no way to make it works. Changed Spice in VNC: no way to make it works
started qemu daemon with my user (not default user for qemu daemon) reinstalled from scratch: same results --> Windows 7 installed but stay indefinitely on boot screen as per attachment
installed a Centos 6.5 x86_64 netinstall and all works very fine. GUI working nice with spice and all HW settings equal to the not working Windows 7.
Physical host is a Laptop on which Fedora 20 is installed is a Dell Latitude E6510 with all the latest patch. HW specs: Intel i7 4 x Physical processors 8 GByte RAM Not using the Noveau Video drivers but installed NVIDIA drivers for NVS 3100M (the installation implies disbling Nouveau and installing the NVIDIA drivers with on the fly recompilation of the NVIDIA modules)
Please provide the guest XML, sudo virsh dumpxml $vmname Does reinstalling the guest, but doing 'customize before install' followed by 'copy host CPU' make any difference?
Created attachment 850397 [details] virsh_dumpxml_vmname output xml file as requested
Manlio, it's unclear, did you try the 'copy host cpu' step and try reinstalling? Or maybe you did that the first time? Also, please provide /var/log/libvirt/qemu/$vmname.log Make sure you are running fully up to date fedora 20 and rebooted into the latest kernel.
Created attachment 851251 [details] virsh_dumpxml_vmname output xml file working VM
Created attachment 851253 [details] /var/log/libvirt/qemu/win7-2.log /var/log/libvirt/qemu/win7-2.log
now all is working in a very strange way:. -resinstalled all with a different ISO (altought I'tve used the first ISO hundereds of time) - Fedora 20 installed on VMware Workstation on Windows8. - the strange thing is that a VM inside a VM works while a VM inside a physical Fedora 20 do not. - I assume that the issue was in the ISO but I've attached all the log requested for further investigation by your side. the issue can be close for me as I cannot reproduce the error on a Physical Fedora 20 system at the moment. best regards Manlio
Thanks for the info, I will close. It may have had to do with the CPU setting, I think windows 7 doesn't like the default qemu CPU (we will be changing the default soon).
Change the default in virt-manager I mean, not qemu.