Windows 7 On A CentOS Kvm Host Pauses After The Installation Reboot.

Home » CentOS-Virt » Windows 7 On A CentOS Kvm Host Pauses After The Installation Reboot.
CentOS-Virt 2 Comments

I am using CentOS 6.5 as a kvm hypervisor with local ssd disks in raid and with glusterfs based storage for couple disk images. I have tried to install Windows 7 from ISO and it seems to pass the first stage of the installation which installs the basic files and also the first reboot. After that the installation is almost finished and the desktop should be up and running after a reboot but instead the Windows 7 machine gets paused before windows shows the windows 7 logo at the boot sequence.

I have tried to find for a record of the issue in the past but found only tiny records which I did not understood from, if it was solved or not. The kvm host has 16GB of ram and 100GB of disk space. For this specific host I have used a disk image ontop of glusterfs but the same happens ontop of glusterfs and ontop of local disks.

I have an ubuntu kvm host with less RAM and I can install windows server
2012 (which I was unable to install on the CentOS 6.5 kvm host both 2012
+ windows 8 + windows 7).

Two things:
If anyone had or has the same issue please notify me. If anyone has a solution please share it.

Thanks, Eliezer

2 thoughts on - Windows 7 On A CentOS Kvm Host Pauses After The Installation Reboot.

  • 1. Is there a CD/DVD drive associated with the VM?

    2. If so, do you have a readable optical disk in the drive when starting the Windows7 guest?

    If the answer to 1 is yes and to 2 is no and your guest configuration file shows this:

    30
    31
    3233
    34
    35

    36

    then remove the line ‘‘ and try again.

    HTH.

  • Hey James,

    I do not have any optical device associated with the VM. What I tried and worked was to update the OS and also the kernel. Since I did an update from 2.6.X base repo kernel to elrepo lt kernel and CentOS basic updates and then a reboot it was all resolved. I do not know the reason but it seems like the updated system solved the issue.

    Thanks, Eliezer