hiptoss

Members
  • Posts

    10
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

hiptoss's Achievements

Noob

Noob (1/14)

2

Reputation

  1. Thanks for the reply. I am using 6.9, so the idea is to create a separate cache pool of drives in raid0, create a share using "cache only" pointed at the new cache pool, and then share it?
  2. Is it possible to create a stripe of unassigned devices and then use the new raid device as a share target? I'd like to be able to use a higher performing share for moving data around my home lab that doesn't need to be in the redundant array.
  3. Are you sure blue iris needs that much cpu resources? Per their documentation, it seems like one or two cores on your i7 should be plenty. You will likely need to buy some more ram if you intend to use the VM as a 'daily driver' in addition to the blue iris software. If it were me, I'd buy a 16gb (2x8) ram kit for less than $70. Assign the VM 4 of the 6 cores and 24 of the 32gb ram, and you should be good to go. That leaves 2 cores and 8gb ram for unraid to manage everything in the background, and your VM should perform fine for what you're looking for.
  4. I didn't do anything to help, but I'm happy to hear you got it all sorted. Make sure to save all of your configs now I'd recommend installing the CA backup/restore app and getting all of your configs to a data drive in case you have to go through this nightmare again. Good luck!
  5. What happens to your VM when you start it now?
  6. I'm not an expert with this, but it looks like you have a couple other sata controllers available on your motherboard. I'd try plugging whichever drive you want to pass through to the VM on a separate controller so you can avoid the IOMMU grouping problem.
  7. A significant downside to using emulated CPUs is apparently that some apps and games actually check your CPU capabilities. For example, last night I tried to play NBA 2k20, and I received a popup saying basically "cpu without SSE 4.2 detected" and the game wouldn't start. Taking @Pducharme's tip, I spent a couple hours trying to figure out how to work around the QEMU issue with AMD 3000 series CPUs. In my research, I ran across a great thread on the VFIO subreddit explaining the issue, and how to work around it. The "easy" solution I used was to simply edit the qemu xml and change cpu mode to 'host-model' instead of 'host-passthrough'. It isn't perfect in that it shows my 3960x as an EPYC processor on boot, but it does allow me to use the VM for gaming. (note that there are more detailed methods listed on the reddit thread fiddling with the -amd-stibp qemu cpu argument. I wasn't able to get that to work with XML parsing errors.) The details of how I fixed this after creating a regular Windows 10 VM with host-passthrough, from the command line. My VM is called "testing1", which creates a testing1.xml in /etc/libvirt/qemu. cd /etc/libvirt/qemu virsh edit testing1 ^ will open your XML to edit (change testing1 to whatever your .xml filename is, minus the .xml extension. ie, myvm.xml = virsh edit myvm) For my config the cpu section looked like this: <cpu mode='host-passthrough' check='none'> <topology sockets='1' dies='1' cores='10' threads='2'/> <cache mode='passthrough'/> <feature policy='require' name='topoext'/> </cpu> All I had to do was change that section to look like this: <cpu mode='host-model' check='none'> <topology sockets='1' dies='1' cores='10' threads='2'/> <feature policy='require' name='topoext'/> </cpu> After saving, and then starting the VM, everything "just worked." I used it last night for a few hours, and I'm typing this post from the VM left on overnight. So far so good. I wanted to point this out in case anyone else finds themselves in my position, having no idea about the QEMU bug with the later AMD cpus. Perhaps someone can add the workarounds from that thread in a more visible post until the bug is fixed in an updated release.
  8. Thank you for the suggestion. When I try that, I get a popup saying "XML error: Non-empty feature list specified without CPU model" -- is there something else I need to add? I tried with i440fx4.2 and 5.0 EDIT: After re-creating a new VM, I'm in a functional state. I did have to still turn on acs override within unraid, even with the new options to directly pass components. After figuring that out, and using SATA on my two passthrough NVME drives to the windows VM, I'm up and running. Thank you very much for your help.
  9. I've recently upgraded to 6.9.0beta22 and I'm having VM issues I haven't seen before. It seems no matter which settings I try. I will consistently get a bluescreen on boot, prior to windows login. The bluescreen is the "kernel security check failure" screen with the little QR code. It auto reboots, tries to repair, and does this bluescreen loop until I stop the VM. I've tried various machine types, with hyper-v and without, many cores, or just one, various memory configurations, etc. I have a 3960x and 128gb of ram, in case it matters. Below is the XML of my latest attempt, as well as attached diag. In this iteration, I'm only using 8 cores, 16gb ram, passing just keyboard and mouse, and using only VNC for video. Any help would be tremendously appreciated. <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>abc</name> <uuid>5bf07f3a-c47f-f0c7-1698-9bf520dc24e1</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>16777216</memory> <currentMemory unit='KiB'>16777216</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>8</vcpu> <cputune> <vcpupin vcpu='0' cpuset='20'/> <vcpupin vcpu='1' cpuset='44'/> <vcpupin vcpu='2' cpuset='21'/> <vcpupin vcpu='3' cpuset='45'/> <vcpupin vcpu='4' cpuset='22'/> <vcpupin vcpu='5' cpuset='46'/> <vcpupin vcpu='6' cpuset='23'/> <vcpupin vcpu='7' cpuset='47'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-4.2'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/5bf07f3a-c47f-f0c7-1698-9bf520dc24e1_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none'> <topology sockets='1' dies='1' cores='4' threads='2'/> <cache mode='passthrough'/> <feature policy='require' name='topoext'/> </cpu> <clock offset='localtime'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <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='block' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source dev='/dev/disk/by-id/nvme-Samsung_SSD_970_EVO_500GB_S466NX0KC32791N'/> <target dev='hdc' bus='ide'/> <boot order='1'/> <address type='drive' controller='0' bus='1' target='0' unit='0'/> </disk> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <controller type='ide' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='pci' index='0' model='pci-root'/> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </controller> <controller type='usb' index='0' model='qemu-xhci' ports='15'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:10:46:d3'/> <source bridge='br0'/> <model type='virtio-net'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <serial type='pty'> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> </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='3'/> </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> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x04d9'/> <product id='0x1818'/> </source> <address type='usb' bus='0' port='1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x1038'/> <product id='0x1710'/> </source> <address type='usb' bus='0' port='2'/> </hostdev> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </memballoon> </devices> </domain> beastmode-diagnostics-20200623-1128.zip