[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-discuss] Windows 10 guest on qemu 2.9

From: Sam Varshavchik
Subject: Re: [Qemu-discuss] Windows 10 guest on qemu 2.9
Date: Tue, 11 Jul 2017 17:59:56 -0400

Nerijus Baliunas writes:

On Tue, 11 Jul 2017 14:19:35 -0400 Sam Varshavchik <address@hidden> wrote:

> Has anybody successfully installed Windows 10 on qemu 2.9
> I upgraded to Fedora 26 (x86_64) going from qemu 2.7 to qemu 2.9, with a
> Windows 10 guest. Booting this guest eventually resulted in a vga resolution-
> sized screen with gray vertical bars. With no further progress, after a few
> minutes, I force-rebooted, which kicked into Windows 10 recovery, which
> failed.
> I had a recovery disk made earlier. The first recovery attempt failed, I'm
> now in a middle of a full recovery; but just wanted to know if anyone
> managed to install Windows 10, and which VM settings have worked.

I have win10 VM installed earlier, but it successfully boots on Fedora 25 with
qemu-kvm-2.9.0-1.fc25.x86_64. It is basically standard Q35 VM. Video is QXL.

My video is QXL too. The emulation is "pc-1440fx-1.4", emulating a core2duo CPU. At the time Win10 came out, IIRC that was the config that was needed to install it without bluescreening the original Win10 installer. BTW, just for the record, this is a fully-licensed, paid Win10.

I did some more investigation. What appears to be reproducibly broken is the guest VM-initiated reboot. But only the VM-initiated reboot process.

I was able to reinstall Windows 10, eventually. But, each time the installer rebooted itself, instead of rebooting it immediately goes into some kind of a "Preparing Automatic Repair" Screen that churns for a while, then bluescreens claiming an irrecoverable error.

But, if I were to force-off the VM when it does that, then start it again, it boots fine, with not a hint of anything being awry. With that, I was able to reinstall Windows 10, but this behavior remained. If I tell Windows 10 to reboot, it looks like it doesn't even do that. I don't even see the bios screen flash by. It immediately goes into the "Automatic Repair" mode which then claims that there are no restore points, and, basically, nothing can be done.

When after the original F26 qemu update booted up and landed on a gray VGA screen with corrupted vertical-gray-bar-video, I initiated a reboot from libvirt. The result was very convincing in getting me to believe that my VM was hosed. I guess I took Win10 at its word that there were no restore points, and I proceeded to reinstall from scratch, re-wiping the disk, etc. In hindsight, I was probably fine, and just had to cold-reboot. Crap.

FWIW, here's my VM config from libvirt:

OVERWRITTEN AND LOST. Changes to this xml configuration should be made using:
 virsh edit WINDOWS10
or other application using the libvirt API.

<domain type='kvm'>
 <memory unit='KiB'>2097152</memory>
 <currentMemory unit='KiB'>2097152</currentMemory>
 <vcpu placement='static'>2</vcpu>
   <type arch='x86_64' machine='pc-i440fx-1.4'>hvm</type>
     <hidden state='on'/>
 <cpu mode='custom' match='exact' check='partial'>
   <model fallback='allow'>core2duo</model>
   <feature policy='require' name='nx'/>
 <clock offset='localtime'/>
   <disk type='file' device='disk'>
     <driver name='qemu' type='raw'/>
     <source file='/var/lib/libvirt/images/WINDOWS7.img'/>
     <target dev='hda' bus='ide'/>
     <boot order='2'/>
     <address type='drive' controller='0' bus='0' target='0' unit='0'/>
   <disk type='file' device='cdrom'>
     <driver name='qemu' type='raw'/>
     <target dev='hdc' bus='ide'/>
     <address type='drive' controller='0' bus='1' target='0' unit='0'/>
   <controller type='ide' index='0'>
     <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
   <controller type='usb' index='0' model='ich9-ehci1'>
     <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x7'/>
   <controller type='usb' index='0' model='ich9-uhci1'>
     <master startport='0'/>
     <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0' 
   <controller type='usb' index='0' model='ich9-uhci2'>
     <master startport='2'/>
     <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x1'/>
   <controller type='usb' index='0' model='ich9-uhci3'>
     <master startport='4'/>
     <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x2'/>
   <controller type='pci' index='0' model='pci-root'/>
   <controller type='virtio-serial' index='0'>
     <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/>
   <interface type='network'>
     <mac address='52:54:00:0b:ef:1d'/>
     <source network='default'/>
     <model type='rtl8139'/>
     <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
   <serial type='pty'>
     <target port='0'/>
   <console type='pty'>
     <target type='serial' port='0'/>
   <channel type='spicevmc'>
     <target type='virtio' name='com.redhat.spice.0'/>
     <address type='virtio-serial' controller='0' bus='0' port='1'/>
   <input type='tablet' bus='usb'>
     <address type='usb' bus='0' port='1'/>
   <input type='mouse' bus='ps2'/>
   <input type='keyboard' bus='ps2'/>
   <graphics type='spice' autoport='yes'>
     <listen type='address'/>
   <sound model='ich6'>
     <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
     <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' 
     <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
   <memballoon model='virtio'>
     <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>

Attachment: pgpU6KP24Chla.pgp
Description: PGP signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]