Hey,

 

I have a problem, where everytime I start the Windows 10 VM I created the whole array stops working. The unraid web UI stops responding etc.

The powerdown script doesn't even manage to do a shutdown, it just creates the zip and after the shutdown notification nothing happens.

I can only shut the system down with the power button.

 

Can you please advise on what is going wrong here?

 

The diagnostic file is attached and I am running version 6.2.0-beta20.

 

p.s. In case you see the libvirt daemon going down, that was me trying to fix the lockup. I also tried to stop the Windows 10 VM from the commandline using virsh.

 

Hope you can help

 

Thanks,

activ 

tower-diagnostics-20160401-2055.zip

No ideas at all on how to solve this? Or did I say something wrong in my post?

Could you provide your Win10 XML?

 

I assume you previously had this working?

Or you're just now trying to install Windows 10 and cannot?

 

Hey, thanks for the reply.

 

I'm not sure what you mean by Windows 10 xml, I used the template that was in Unraid and a standard Microsoft Windows 10 image. I'm new to Unraid, but if you could point me towards the xml I'll dig it up.

 

I managed to install Windows, do the driver install and at some point after that the first crash occurred. At the time I didn't realise the Windows VM was causing the issue though. So I kind off had it working, but not for very long.

 

 

How many cores do you have assigned to the VM? If multiple, try changing it to only 1.

Which driver did you install?

Copy/paste the XML from clicking on the VM name, select edit XML. This will bring up the VM template (XML) that unRaid creates for you.

Please try the following:

 

1)  Click on your VM under the VMs tab and click Edit

2)  In the top right of the Edit VM page, turn on Advanced View

3)  Under CPU Mode, change from Host Passthrough to QEMU Emulated

4)  Apply and start your VM

 

Let me know if this works for you.

How many cores do you have assigned to the VM? If multiple, try changing it to only 1.

 

I have assigned only one. (CPU 0)

 

Which driver did you install?

Copy/paste the XML from clicking on the VM name, select edit XML. This will bring up the VM template (XML) that unRaid creates for you.

 

In stalled the drivers from the downloaded iso (for everything missing a driver in Windows)

 

The xml is here:

 

<domain type='kvm'>
  <name>Windows 10</name>
  <uuid>d9ccf481-92ab-f7be-4fca-1e090ab127a2</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='0'/>
  </cputune>
  <os>
    <type arch='x86_64' machine='pc-i440fx-2.5'>hvm</type>
    <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader>
    <nvram>/etc/libvirt/qemu/nvram/d9ccf481-92ab-f7be-4fca-1e090ab127a2_VARS-pure-efi.fd</nvram>
  </os>
  <features>
    <acpi/>
    <apic/>
    <hyperv>
      <relaxed state='on'/>
      <vapic state='on'/>
      <spinlocks state='on' retries='8191'/>
      <vendor id='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/VMS/Windows 10/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/Windows10.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.112-1.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:79:7a:e6'/>
      <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'>
      <source mode='connect'/>
      <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'/>
    <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'/>
      <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>

 

Please try the following:

 

1)  Click on your VM under the VMs tab and click Edit

2)  In the top right of the Edit VM page, turn on Advanced View

3)  Under CPU Mode, change from Host Passthrough to QEMU Emulated

4)  Apply and start your VM

 

Let me know if this works for you.

 

Okay, will try asap and let you know.

I have tried using the emulated CPU, but the result is the same.

I have tried using the emulated CPU, but the result is the same.

 

After setting the emulated CPU, make sure you check under Device Manager in Windows and look at "Processor" to make sure it says "QEMU Emulated."  Often times you will need to reboot the VM once after making the change in the VM Manager before the change actually takes affect.

The VM was shutdown when I made the change, and at this point starting the VM will have it booting but during the boot the crash occurs so I never got to the point anymore where I can see device manager.

I wanted to upload a new diagnostics file but the forum won't let me as the file is too big.