Not sure if this is a 6.4.0 rc2 issue but here goes...

 

I have a problem with building windows 10 vms

 

I have tried to change the display driver from the default "Microsoft Basic Display Adapter" and after choosing the RedHat display to install, the windows image reboots and doesn't install the Redhat display driver.

 

I have tried with both a 2016 windows 10 cd image build and the new 2017 creators win 10 image build and each time the same issue the image reboots without installing the driver.

 

Any ideas why that is happening and how to fix it?

 

 

The QEMU log says...

 

2017-06-14 22:15:20.154+0000: starting up libvirt version: 3.3.0, qemu version: 2.9.0, hostname: GOLIATH
LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name 'guest=003 Windows 10,debug-threads=on' -S -object 'secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-8-003 Windows 10/master-key.aes' -machine pc-i440fx-2.9,accel=kvm,usb=off,dump-guest-core=off,mem-merge=off -cpu host,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff,hv_vendor_id=none -drive file=/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd,if=pflash,format=raw,unit=0,readonly=on -drive file=/etc/libvirt/qemu/nvram/f1b2b7a1-2d0c-e009-4899-ec760f060576_VARS-pure-efi.fd,if=pflash,format=raw,unit=1 -m 8192 -realtime mlock=off -smp 4,sockets=1,cores=2,threads=2 -uuid f1b2b7a1-2d0c-e009-4899-ec760f060576 -no-user-config -nodefaults -chardev 'socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-8-003 Windows 10/monitor.sock,server,nowait' -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-hpet -no-shutdown -boot strict=on -device ich9-upci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev 'socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/domain-8-003 Windows 10/org.qemu.guest_agent.0,server,nowait' -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -device usb-tablet,id=input0,bus=usb.0,port=1 -vnc 0.0.0.0:2,websocket=5702 -k en-gb -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 -msg timestamp=on
2017-06-14 22:15:20.154+0000: Domain id=8 is tainted: high-privileges
2017-06-14 22:15:20.154+0000: Domain id=8 is tainted: host-cpu
2017-06-14T22:15:20.246878Z qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/2 (label charserial0)
ehci warning: guest updated active QH
qemu-system-x86_64: hw/display/qxl.c:416: qxl_ram_set_dirty: Assertion `offset < qxl->vga.vram_size' failed.
2017-06-14 22:21:00.274+0000: shutting down, reason=crashed

 

 

 

Edited June 23, 20179 yr by GFRoSTY

No one has any comments?

 

I created a video so you can see it happening. stuck with the default MS basic driver at the moment.

 

 

 

No one has any comments? [emoji20]
 
I created a video so you can see it happening. stuck with the default MS basic driver at the moment.
 
 
 

Can you try this on 6.3.5? Curious if this is an rc issue or not.

Sent from my SM-G930P using Tapatalk

I did copy the bz* files to the flash drive copying over the existing files and rebooting, then unraid booted into 6.3.5

 

I then created a new win10 vm however same issue, when trying to add the the qxl and qxldod driver.. 

 

I think the next thing is to clear the flash drive completely and make a new 6.3.5 install. Should I try that  Jonp?

Have you tried playing with the video XML section to see if you can fix or bypass the issue? You could adjust the vram and ram section here.

 

    <video>
      <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/>
    </video>

I did copy the bz* files to the flash drive copying over the existing files and rebooting, then unraid booted into 6.3.5
 
I then created a new win10 vm however same issue, when trying to add the the qxl and qxldod driver.. 
 
I think the next thing is to clear the flash drive completely and make a new 6.3.5 install. Should I try that  Jonp?

What version of the Virtio drivers are you trying to load?

Sent from my SM-G930P using Tapatalk

I've tried the virtio 137, 126.2 and 126 and all 3 do the same thing.

 

also tried doubling the qxl memory ram, vram. vgamen all to 131072 - still same issue

I've tried the virtio 137, 126.2 and 126 and all 3 do the same thing.
 
also tried doubling the qxl memory ram, vram. vgamen all to 131072 - still same issue

Please try lowering the amount of memory allocated to the VM (at least 1GB) and try again. Curious to see if this is a memory availability issue.

Sent from my SM-G930P using Tapatalk

ok, it was currently set to 8gb, I halved it to 4gb

 

left the ram bits all at 131072  - issue persists

 

then tried all ram bits at 65536 - issue persists

 

ok, it was currently set to 8gb, I halved it to 4gb
 
left the ram bits all at 131072  - issue persists
 
then tried all ram bits at 65536 - issue persists
 

Ok, we will look into this further. If no one else reports this issue and we cannot recreate, it may just be something odd with your system. If anyone else has had this happen, please let us know!

Side note, you don't really need the qxl drivers to operate the VM, it just improves the resolution options a bit, but even better still is setting up RDP access to windows directly, bypassing the need for a virtual graphics adapter altogether.

Sent from my SM-G930P using Tapatalk

On 2017-6-15 at 10:36 PM, GFRoSTY said:

No one has any comments?

 

I created a video so you can see it happening. stuck with the default MS basic driver at the moment.

 

 

 

1

 

Try manually installing the qxl drivers. It isn't the qxl driver, that you want its the qxldod   (QXL graphics driver for Windows 8 and later)  

Maybe it's not pulling the correct driver in on the auto search. I am using 0.1.126

 

 

 

 

If this doesn't work I see that maybe you are using an older Win 10 image. I say that because I see in your video the error on the HID Button over Interrupt driver

This was caused apparently by a typo when putting in support more recent ACPI specs. On newer 10 images I think this is fixed as I haven't seen this recently on new 10 VMS I have made. So maybe worth a try on a newer 10 if so.

 

If you want 4k resolution on qxl it needs 4 bytes per pixel for that res so we need to change the video ram to 64 meg (65536)

So edit the XML to as below

<video>
<model type='qxl' ram='131072' vram='131072' vgamem='65536' heads='1' primary='yes'/>
</video>

 

On a side note if anyone wants to fix the  HID Button over Interrupt driver issue on the older 10 builds you can with these steps.

1. Uninstall the existed driver package for this device, if can check delete button, please check it too.

2. Download the PsTools from https://technet.microsoft.com/en-us/sysinternals/pstools.aspx

3. Unzip PsTools, and locate the folder of PsTools, then input in CMD (Run as Administrator): psexec -s -i regedit.exe

4. Delete subkey ACPI0010 under HKLM\SYSTEM\DriverDataBase\DriverPackage\hiinterrupt.inf_x86_<some instance ID>\Descriptors\ACPI0010 And delete subkey "bidinterrupt.inf" under HKLM\SYSTEM\DriverDataBase\DeviceIds\ACPI\ACPI0010

5. Rescan device to see the effect.

Edited June 17, 20179 yr by gridrunner

Thanks for the comments jonp and Gridrunner.

 

So I ended up doing this..,

 

1. Fresh install of unraid 6.3.5 booted up,  added my drives and let the parity check run to completion so all data was verified2. After parity check completed, stopped array, deleted all flash files on usb and copied backup of 6.3.5 (with all my data/users/plugins etc)

3. Downloaded Windows 10 creators edition (april 2017edition) via microsofts "media creaton tool".

4. Downloaded fresh virtio 1.26.2 from with VM settings option in unraid

5. New windows 10 vm creation option, only changing size to 50G, and keyboard to UK.

6. Kicked off new windows 10 install

 

and choosing the qxldod driver IT WORKED!!!!.

 

So... I am not at a bit of a junction point...  do I now upgrade to the latest rc edition and try from step 5 and see how I go  I think I will so...  I'll do that in the next hour of so and feedback

 

 

 

 

 

 

 

Edited June 18, 20179 yr by GFRoSTY

Well,  after installing to 6.4.0.rc4 and tested my original VM it was still working.

 

I then tried a fresh install going through the creation and install process and updating the Video driver with qxldod which WORKED!!

 

So, not sure exactly what the issue was, either a dodgy Windows image as I was using one from march but getting a new download gave me an image with a date of 27th April 2017, or something else...

 

Suffice to say,  everything is working as it should for me as far as I can tell under 6.4.0rc4 edition.  

Any further issues, I will report back.

 

Thanks for the help with this.