December 23, 201510 yr Hey folks.. I am still new.. Learning (slowly), so be gently ;-) Win10 running in a VM for BlueIris DVR Software and Crashplan. C drive is an image on an SSD Cache Drive D drive I am (trying) passing a 2TB HD Things were working good but I was out of SATA ports so I ordered up a Dell H310. I updated the bios and tested it out on another motherboard. Once I had it working I put it into my production box and pick 4 HD's to put on it - Cache, 2TB that is being passed through to the VM and 2 other 2TB drives from the array. After making this swap the VM started randomly powering off. There is nothing logged within the Windows VM event log other then the unexpected shutdown when its booted back up again. In testing I removed the D drive 2TB disk and thing appear to be running fine. Well other then BlueIris which is recording to that disk. It still runs just does not record. I added the disk back and it starts crashing again. To remove BlueIris I shut it down and rebooted and it still crashes. Sometimes its within seconds sometimes it takes 5 minutes. Here is how I was adding the disk (taken from here: https://lime-technology.com/forum/index.php?topic=42490.msg422773#msg422773 ) <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source dev='/dev/disk/by-id/ata-ST2000DL003-9VT166_5YD2292K'/> <target dev='hda' bus='virtio'/> </disk> In searching for solutions I found another config that someone added that looks like this and tried it out and appears to be working <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='none' io='native'/> <source file='/dev/disk/by-id/ata-ST2000DL003-9VT166_5YD2292K'/> <backingStore/> <target dev='vdb' bus='virtio'/> <alias name='virtio-disk1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </disk> So all that said here are some questions I am trying to sort out... [*]Where do I find logging about the VM's so I can see what might be causing the crash? [*]A couple difference in the config from what was working to what is working any explanation as to what they do (cache and having PCI domain etc)? [*]Is there a better way I should be passing through a whole disk instead of hacking XML to which I don't claim to really understand? For giggles here is the current complete config. <domain type='kvm' id='1'> <name>WinServer</name> <uuid>564eed86-6a1b-28eb-4e9b-b0615619481e</uuid> <metadata> <vmtemplate name="Custom" icon="windows.png" os="windows"/> </metadata> <memory unit='KiB'>6291456</memory> <currentMemory unit='KiB'>6291456</currentMemory> <memoryBacking> <nosharepages/> <locked/> </memoryBacking> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='8'/> <vcpupin vcpu='1' cpuset='9'/> <vcpupin vcpu='2' cpuset='10'/> <vcpupin vcpu='3' cpuset='11'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-2.3'>hvm</type> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> </hyperv> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='4' 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/bin/qemu-system-x86_64</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/cache/VM/WinServer/vdisk1.img'/> <backingStore/> <target dev='hda' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='none' io='native'/> <source file='/dev/disk/by-id/ata-ST2000DL003-9VT166_5YD2292K'/> <backingStore/> <target dev='vdb' bus='virtio'/> <alias name='virtio-disk1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </disk> <controller type='usb' index='0'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <interface type='bridge'> <mac address='50:54:00:d9:e2:ba'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/0'/> <target port='0'/> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/0'> <source path='/dev/pts/0'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/WinServer.org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='connected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <alias name='input0'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='5900' autoport='yes' websocket='5700' listen='0.0.0.0' keymap='en-us'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='vmvga' vram='16384' heads='1'/> <alias name='video0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </memballoon> </devices> </domain> Sorry for the long post. Doing my best to provide as much detail as possible.... Things seem to be running ok right now. Just wondering if the config is optimal or is there a better way to do it. Many thanks in advance for any input, insight or name calling ;-) Mike ------ Solved ------ Turns out it was memory/motherboard causing my problems. Machine has 12GB installed. When I setup the VM initially I assigned 6GB for the VM. At some point it lost access to 2 DIMMs and provided only 8GB to the OS. Things would work fine until higher memory usage from a Docker would cause the VM to stop running. I did not experience the problem until after the H310 was installed. I am not sure if the H310 eats up some extra memory or the problem with the memory started when I installed the card. As it turns out 2 memory slots on the board are screwy. Its a P6T6 WS Revolution. Reading about the board some people were having problems with the Heatsync causing problems with these 2 memory slots. Without the heatsync screwed down the memory slots work. Once I tighten it they get funky. That combined with a couple DIMMs that are acting up took me quite a bit of time to troubleshoot and isolate. In the end I have 3 x 4GB DIMM's installed now pirated from various machine around my house. Things seem stable but I plan on replacing this as soon as possible. Thanks for reading....
December 24, 201510 yr Author Ok.. Another crash with the new config... Took a couple hours I think. I need to review the logs... How do I go about checking the Unraid logs for the KVM? Windows is not reporting any errors. Anyone able to review the overall config? Am I missing something or have something messed up? Love any help you can give! Thanks, Mike
December 30, 201510 yr Author Hey Folks. I would really appreciate any insight into this that you might have. Here are the logs from the VM's tab 2015-12-24 06:25:41.998+0000: starting up libvirt version: 1.2.18, qemu version: 2.3.0 Domain id=1 is tainted: high-privileges Domain id=1 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) 2015-12-24 23:41:59.522+0000: shutting down 2015-12-25 15:11:23.599+0000: starting up libvirt version: 1.2.18, qemu version: 2.3.0 Domain id=2 is tainted: high-privileges Domain id=2 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) 2015-12-30 15:36:38.543+0000: shutting down I need to do some further testing but it seems like it might be kicking out when CPU use in the dockers goes up. Any thoughts or ideas? Is there better logging somewhere that might help me (More likely help you help me) Many thanks! Mike **** well Just did some testing... As soon as I started transcoding in a Plex via a Docker the VM stopped running. CPU utilization spiked in UnRaid. I rebooted UnRaid and cannot reproduce the crash now. It seems to take some time.
December 30, 201510 yr Author Ok folks.. I am new. My Apologies. I have only been using UnRaid for a few weeks now and I am still learning my way around. I Found the logs and will look through them for a bit. Also attaching if anyone has time/interest to offer a hand. In more playing I think (guess really) that it maybe a memory issue. I had 6GB assigned to the VM. Looks like this machine only has 8GB available. I thought it was 16GB, but I will have a look at the physical box tonight to confirm I don't have a hardware issue to deal with. I have dropped the VM to 4GB for now and I am testing to see how BlueIris runs. I will try and drop it further if I can. Thanks for reading. Mike tower-diagnostics-20151230-1140.zip
December 30, 201510 yr Also, may not be causing your problem but others on the forum have reported this fix is required for stability in Unraid on their hardware.
December 30, 201510 yr Author Thanks CHBMB I had to do this to get the box to boot. I quickly realized my eyes are not as good as they use to be. So far stable after reducing memory on the VM. Will give it sometime though to decide as it was running a day or so before it would crash. That maybe though that it was only transcoding every few days. Mike Also, may not be causing your problem but others on the forum have reported this fix is required for stability in Unraid on their hardware.
Archived
This topic is now archived and is closed to further replies.