Win10 VM hangs on Reboot / Dont start with PT Audio


Recommended Posts

Hi guys,

 

I'm setting up a new machine for my dad, but I've got a few Problems :(

 

1. All Windows 10 Pro VMs hang when they reboot - after the BIOS Screen (and before windows logo) it only shows a black screen with text cursor. I've tried creating new VMs with different settings (hyper-v on/off, gpu/vnc, bios) but it doesnt seem to work. All VMs hang when Windows 10 tries to restart (even while installing)

 

2. When I try to PT Audio of the NVIDIA GT710 it hangs on Boot (at logo, loading animation hides and Host CPU Cores are at 100%)

 

Ideas anyone? Thanks very much!

 

aussenbecken-diagnostics-20170506-0922 2.zip

Link to comment
7 hours ago, NAStyBox said:

Is your cache drive full? You may need to run mover.

nope :(
 

5 hours ago, jonathanm said:

Make sure you only have one CPU core checked in the VM until everything is stable.

tried that, but even with only one Core assigned it hangs :(

Link to comment

I doubt its the SSD. But is it possible that kvm isnt fully compatible with kaby lake and/or Intel H270 chipsets yet? 

 

Or any other Idea where I can search for the problem? On my own machine (i7-6700k @ z170) everything works fine. never had problems with that one :(

 

edit: unRAID 6.3.3. runs qemu 2.7.1 but latest stable is 2.9.0 ... does anyone know if LT will update it in 6.3.4 or 6.4?

Edited by me.so.bad
Link to comment
On 5/6/2017 at 3:30 AM, me.so.bad said:

Hi guys,

 

I'm setting up a new machine for my dad, but I've got a few Problems :(

 

1. All Windows 10 Pro VMs hang when they reboot - after the BIOS Screen (and before windows logo) it only shows a black screen with text cursor. I've tried creating new VMs with different settings (hyper-v on/off, gpu/vnc, bios) but it doesnt seem to work. All VMs hang when Windows 10 tries to restart (even while installing)

 

2. When I try to PT Audio of the NVIDIA GT710 it hangs on Boot (at logo, loading animation hides and Host CPU Cores are at 100%)

 

Ideas anyone? Thanks very much!

 

aussenbecken-diagnostics-20170506-0922 2.zip

 

 

1. What guide did you follow in making the vm? If you just went at it on you own, that's probably your problem.

 

2. deal with problem 1 first.

Link to comment

This time I did it on my own, but I've created multiple VMs on my own unRAID machine before. so personally I dont think its something that easy.

Also I have tried multiple configurations (including seaBios/OMVF, different VNC/GPU, different Cores, different Hyper-V Settings... basicly different everything) and not a single VM restarted during Windows 10 installation... some of them didnt even start at all. 

 

But if your pass me over a guide I'm more then happy to try it out, maybe there is something I dont know yet.

Link to comment
3 hours ago, me.so.bad said:

This time I did it on my own, but I've created multiple VMs on my own unRAID machine before. so personally I dont think its something that easy.

Also I have tried multiple configurations (including seaBios/OMVF, different VNC/GPU, different Cores, different Hyper-V Settings... basicly different everything) and not a single VM restarted during Windows 10 installation... some of them didnt even start at all. 

 

But if your pass me over a guide I'm more then happy to try it out, maybe there is something I dont know yet.

 

I always follow along with the guide, even though I've made dozens of win10 vm's. Plus, if you follow the guide and still have problems, this lets us all know it was setup correctly, and we can eliminate some variables and isolate your problem better.

 

 

Edited by 1812
Link to comment

Ok, heres an XML generated with the video above ("minimal setup")

- it boots into windows setup

- I select E:\viostor\w10\amd64 drivers

- it copies windows pro

- it restarts ... and hangs :( 
- force stop from unRAID webUI, start again.
- setup completes (express - no cortana), I'm in Windows.
- installing all needed drivers (network, balloon, pice "simple device")

- disable fast boot (shouldnt affect reboot at all)
- restarting... and it hangs again :(

 

Screenshot of hanging VM is attached

 

<domain type='kvm'>
  <name>Windows 10 Test</name>
  <uuid>c74f8c77-0c9b-a13b-a4e1-ee1c2ad62e6e</uuid>
  <metadata>
    <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/>
  </metadata>
  <memory unit='KiB'>2097152</memory>
  <currentMemory unit='KiB'>2097152</currentMemory>
  <memoryBacking>
    <nosharepages/>
  </memoryBacking>
  <vcpu placement='static'>1</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='2'/>
  </cputune>
  <os>
    <type arch='x86_64' machine='pc-i440fx-2.7'>hvm</type>
    <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader>
    <nvram>/etc/libvirt/qemu/nvram/c74f8c77-0c9b-a13b-a4e1-ee1c2ad62e6e_VARS-pure-efi.fd</nvram>
  </os>
  <features>
    <acpi/>
    <apic/>
    <hyperv>
      <relaxed state='on'/>
      <vapic state='on'/>
      <spinlocks state='on' retries='8191'/>
      <vendor_id state='on' value='none'/>
    </hyperv>
  </features>
  <cpu mode='host-passthrough'>
    <topology sockets='1' cores='1' threads='1'/>
  </cpu>
  <clock offset='localtime'>
    <timer name='hypervclock' present='yes'/>
    <timer name='hpet' present='no'/>
  </clock>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>
  <devices>
    <emulator>/usr/local/sbin/qemu</emulator>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source file='/mnt/user/domains/Windows 10 Test/vdisk1.img'/>
      <target dev='hdc' bus='virtio'/>
      <boot order='1'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
    </disk>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/mnt/user/isos/de_windows_10_multiple_editions_version_1607_updated_jul_2016_x64_dvd_9053906.iso'/>
      <target dev='hda' bus='ide'/>
      <readonly/>
      <boot order='2'/>
      <address type='drive' controller='0' bus='0' target='0' unit='0'/>
    </disk>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/mnt/user/isos/virtio-win-0.1.126-2.iso'/>
      <target dev='hdb' bus='ide'/>
      <readonly/>
      <address type='drive' controller='0' bus='0' target='0' unit='1'/>
    </disk>
    <controller type='usb' index='0' model='ich9-ehci1'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci1'>
      <master startport='0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci2'>
      <master startport='2'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci3'>
      <master startport='4'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/>
    </controller>
    <controller type='pci' index='0' model='pci-root'/>
    <controller type='ide' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
    </controller>
    <controller type='virtio-serial' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
    </controller>
    <interface type='bridge'>
      <mac address='52:54:00:94:d3:c4'/>
      <source bridge='br0'/>
      <model type='virtio'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
    </interface>
    <serial type='pty'>
      <target port='0'/>
    </serial>
    <console type='pty'>
      <target type='serial' port='0'/>
    </console>
    <channel type='unix'>
      <target type='virtio' name='org.qemu.guest_agent.0'/>
      <address type='virtio-serial' controller='0' bus='0' port='1'/>
    </channel>
    <input type='tablet' bus='usb'>
      <address type='usb' bus='0' port='1'/>
    </input>
    <input type='mouse' bus='ps2'/>
    <input type='keyboard' bus='ps2'/>
    <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='en-us'>
      <listen type='address' address='0.0.0.0'/>
    </graphics>
    <video>
      <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
    </video>
    <memballoon model='virtio'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>
    </memballoon>
  </devices>
</domain>

 

Bildschirmfoto 2017-05-09 um 19.39.55.png

Link to comment
3 minutes ago, NAStyBox said:

I still don't know what that "loader" thing is in yours, or where it comes from. Can anyone explain?

Maybe because I have copied the XML before starting the VM the first time.

You XML is copied while the VM is running, right? but it looks more or less the same as mine..

Link to comment

Lots of "errors" in libvirt. The tainted domain is nothing to worry about and not causing the problem.

 

 

2017-05-09 14:08:15.630+0000: 4706: error : qemuStorageLimitsRefresh:11550 : cannot stat file '/mnt/user/domains/Workstation/vdisk2.img': Bad file descriptor
2017-05-09 14:08:18.362+0000: 4706: error : qemuOpenFileAs:3033 : Failed to open file '/mnt/user/domains/Workstation/vdisk1.img': No such file or directory
2017-05-09 14:08:18.362+0000: 4706: error : qemuStorageLimitsRefresh:11550 : cannot stat file '/mnt/user/domains/Workstation/vdisk1.img': Bad file descriptor
2017-05-09 14:08:18.362+0000: 4704: error : qemuOpenFileAs:3033 : Failed to open file '/mnt/user/domains/Workstation/vdisk2.img': No such file or directory
2017-05-09 14:08:18.362+0000: 4704: error : qemuStorageLimitsRefresh:11550 : cannot stat file '/mnt/user/domains/Workstation/vdisk2.img': Bad file descriptor
2017-05-09 17:33:53.661+0000: 4702: warning : qemuDomainObjTaint:3885 : Domain id=8 name='Windows 10 Test' uuid=c74f8c77-0c9b-a13b-a4e1-ee1c2ad62e6e is tainted: high-privileges
2017-05-09 17:33:53.661+0000: 4702: warning : qemuDomainObjTaint:3885 : Domain id=8 name='Windows 10 Test' uuid=c74f8c77-0c9b-a13b-a4e1-ee1c2ad62e6e is tainted: host-cpu
2017-05-09 17:33:53.743+0000: 4702: error : x86FeatureInData:780 : internal error: unknown CPU feature __kvm_hv_spinlocks
2017-05-09 17:33:53.743+0000: 4702: error : x86FeatureInData:780 : internal error: unknown CPU feature __kvm_hv_vendor_id
2017-05-09 17:40:55.669+0000: 4706: warning : qemuDomainObjTaint:3885 : Domain id=9 name='Windows 10 Test' uuid=c74f8c77-0c9b-a13b-a4e1-ee1c2ad62e6e is tainted: high-privileges
2017-05-09 17:40:55.669+0000: 4706: warning : qemuDomainObjTaint:3885 : Domain id=9 name='Windows 10 Test' uuid=c74f8c77-0c9b-a13b-a4e1-ee1c2ad62e6e is tainted: host-cpu
2017-05-09 17:40:55.750+0000: 4706: error : x86FeatureInData:780 : internal error: unknown CPU feature __kvm_hv_spinlocks
2017-05-09 17:40:55.750+0000: 4706: error : x86FeatureInData:780 : internal error: unknown CPU feature __kvm_hv_vendor_id

 

save a copy of your xml to a second location, then try changing the following changes: change machine to Q35-2.7 

 

if that doesn't work, then try

 

<hyperv>
		<relaxed state='off'/>
		<vapic state='off'/>
		<spinlocks state='off'/>
	</hyperv>

 

Was doing some reading this am. no guarantee this will work, but seem to solve some similar issues.

Edited by 1812
Link to comment
1 hour ago, me.so.bad said:

I'm pretty sure its an issue with OVMF + Win10 + my CPU/Chipset... Dang!
is there any chance to upgrade something on unRAID?

 

If you think it's an ovmf issue, then make a win 10 vm with seabios, no gpu, and only use 1 core.

 

Also, if you're on unRaid 6.3.3, then you'e on the latest.

Link to comment
  • 4 weeks later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.