-
Posts
671 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Rick Sanchez
-
-
This is the board that I was looking at getting for my Node 304.
It's concerning that you're having these issues
Sent from my Pixel 6 using Tapatalk -
My Xeon setup uses 120w in use and idle! I wish I could drop its usage massively!
Can this help?
-
I'm thinking of buying this case at a later date for a super low powered backup NAS.
Are you using this case yet?
-
Try Discord, you'll get more active help!
I
-
Quote
2022-01-16T23:02:16.831862Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88376, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.831869Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88377, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.831876Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88378, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.831883Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88379, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.831893Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x8837a, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.831903Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x8837b, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.831912Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x8837c, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.831926Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x8837d, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.831936Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x8837e, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.831945Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x8837f, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.831953Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88380, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.831961Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88381, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.831967Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88382, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.831975Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88383, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.831982Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88384, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.831989Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88385, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.831996Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88386, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.832003Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88387, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.832011Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88388, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.832018Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88389, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.832027Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x8838a, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.832037Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x8838b, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.832046Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x8838c, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.832053Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x8838d, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.832061Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x8838e, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.832068Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x8838f, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.832076Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88390, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.832083Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88391, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.832089Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88392, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.832097Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88393, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.832104Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88394, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.832111Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88395, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.832119Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88396, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.832126Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88397, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.832133Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88398, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.832140Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88399, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.832149Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x8839a, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.832160Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x8839b, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.832168Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x8839c, 0x0,1) failed: Device or resource busyHas anyone got a solution to my problems?
Thanks for your help!
-
IOMMU Groups Attached...
.thumb.png.7ab554d8ed007da048379521fa273a02.png)
.thumb.png.1fad5ffe34dc31952fa885ac8da1ca5e.png)
-
This is what loads on screen since my reboot:
Sent from my TA-1012 using Tapatalk
-
Hi everyone,
I am loosing the will to live with UnRAID VMs as I have run out of ideas!
Created a new Windows 11 VM and everything worked fine, until I needed to reboot and now I cannot get it to boot at all!
What am I doing wrong?
VM XML:
Quote<?xml version='1.0' encoding='UTF-8'?>
<domain type='kvm' id='1'>
<name>Windows 11</name>
<uuid>fd34370c-6e4f-cd0b-55a1-2fa823b2ff7e</uuid>
<metadata>
<vmtemplate xmlns="unraid" name="Windows 11" icon="windows.png" os="windowstpm"/>
</metadata>
<memory unit='KiB'>8388608</memory>
<currentMemory unit='KiB'>8388608</currentMemory>
<memoryBacking>
<nosharepages/>
</memoryBacking>
<vcpu placement='static'>8</vcpu>
<cputune>
<vcpupin vcpu='0' cpuset='4'/>
<vcpupin vcpu='1' cpuset='12'/>
<vcpupin vcpu='2' cpuset='5'/>
<vcpupin vcpu='3' cpuset='13'/>
<vcpupin vcpu='4' cpuset='6'/>
<vcpupin vcpu='5' cpuset='14'/>
<vcpupin vcpu='6' cpuset='7'/>
<vcpupin vcpu='7' cpuset='15'/>
</cputune>
<resource>
<partition>/machine</partition>
</resource>
<os>
<type arch='x86_64' machine='pc-q35-6.1'>hvm</type>
<loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi-tpm.fd</loader>
<nvram>/etc/libvirt/qemu/nvram/fd34370c-6e4f-cd0b-55a1-2fa823b2ff7e_VARS-pure-efi-tpm.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' check='none' migratable='on'>
<topology sockets='1' dies='1' cores='4' threads='2'/>
<cache mode='passthrough'/>
</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='qcow2' cache='writeback'/>
<source file='/mnt/user/domains/Windows 11/vdisk1.img' index='3'/>
<backingStore/>
<target dev='hdc' bus='virtio'/>
<boot order='1'/>
<alias name='virtio-disk2'/>
<address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/>
</disk>
<disk type='file' device='cdrom'>
<driver name='qemu' type='raw'/>
<source file='/mnt/user/isos/Windows/Win11_English_x64v1.iso' index='2'/>
<backingStore/>
<target dev='hda' bus='sata'/>
<readonly/>
<boot order='2'/>
<alias name='sata0-0-0'/>
<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.208-1.iso' index='1'/>
<backingStore/>
<target dev='hdb' bus='sata'/>
<readonly/>
<alias name='sata0-0-1'/>
<address type='drive' controller='0' bus='0' target='0' unit='1'/>
</disk>
<controller type='pci' index='0' model='pcie-root'>
<alias name='pcie.0'/>
</controller>
<controller type='pci' index='1' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='1' port='0x8'/>
<alias name='pci.1'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0' multifunction='on'/>
</controller>
<controller type='pci' index='2' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='2' port='0x9'/>
<alias name='pci.2'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
</controller>
<controller type='pci' index='3' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='3' port='0xa'/>
<alias name='pci.3'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/>
</controller>
<controller type='pci' index='4' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='4' port='0xb'/>
<alias name='pci.4'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x3'/>
</controller>
<controller type='pci' index='5' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='5' port='0xc'/>
<alias name='pci.5'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x4'/>
</controller>
<controller type='pci' index='6' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='6' port='0xd'/>
<alias name='pci.6'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x5'/>
</controller>
<controller type='pci' index='7' model='pcie-root-port'>
<model name='pcie-root-port'/>
<target chassis='7' port='0xe'/>
<alias name='pci.7'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x6'/>
</controller>
<controller type='pci' index='8' model='pcie-to-pci-bridge'>
<model name='pcie-pci-bridge'/>
<alias name='pci.8'/>
<address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
</controller>
<controller type='virtio-serial' index='0'>
<alias name='virtio-serial0'/>
<address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/>
</controller>
<controller type='sata' index='0'>
<alias name='ide'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/>
</controller>
<controller type='usb' index='0' model='ich9-ehci1'>
<alias name='usb'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/>
</controller>
<controller type='usb' index='0' model='ich9-uhci1'>
<alias name='usb'/>
<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'>
<alias name='usb'/>
<master startport='2'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/>
</controller>
<controller type='usb' index='0' model='ich9-uhci3'>
<alias name='usb'/>
<master startport='4'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/>
</controller>
<interface type='bridge'>
<mac address='52:54:00:c4:05:be'/>
<source bridge='br0'/>
<target dev='vnet0'/>
<model type='virtio-net'/>
<alias name='net0'/>
<address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/>
</interface>
<serial type='pty'>
<source path='/dev/pts/0'/>
<target type='isa-serial' port='0'>
<model name='isa-serial'/>
</target>
<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/domain-1-Windows 11/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='mouse' bus='ps2'>
<alias name='input0'/>
</input>
<input type='keyboard' bus='ps2'>
<alias name='input1'/>
</input>
<tpm model='tpm-tis'>
<backend type='emulator' version='2.0' persistent_state='yes'/>
<alias name='tpm0'/>
</tpm>
<audio id='1' type='none'/>
<hostdev mode='subsystem' type='usb' managed='no'>
<source>
<vendor id='0x046d'/>
<product id='0xc52b'/>
<address bus='1' device='2'/>
</source>
<alias name='hostdev0'/>
<address type='usb' bus='0' port='3'/>
</hostdev>
<hostdev mode='subsystem' type='pci' managed='yes'>
<driver name='vfio'/>
<source>
<address domain='0x0000' bus='0x03' slot='0x00' function='0x0'/>
</source>
<alias name='hostdev1'/>
<address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/>
</hostdev>
<hostdev mode='subsystem' type='pci' managed='yes'>
<driver name='vfio'/>
<source>
<address domain='0x0000' bus='0x03' slot='0x00' function='0x1'/>
</source>
<alias name='hostdev2'/>
<address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0'/>
</hostdev>
<hostdev mode='subsystem' type='pci' managed='yes'>
<driver name='vfio'/>
<source>
<address domain='0x0000' bus='0x00' slot='0x17' function='0x0'/>
</source>
<alias name='hostdev3'/>
<address type='pci' domain='0x0000' bus='0x08' slot='0x01' function='0x0'/>
</hostdev>
<hostdev mode='subsystem' type='usb' managed='no'>
<source>
<vendor id='0x045e'/>
<product id='0x07f8'/>
<address bus='1' device='6'/>
</source>
<alias name='hostdev4'/>
<address type='usb' bus='0' port='1'/>
</hostdev>
<hostdev mode='subsystem' type='usb' managed='no'>
<source>
<vendor id='0x046d'/>
<product id='0x0809'/>
<address bus='1' device='3'/>
</source>
<alias name='hostdev5'/>
<address type='usb' bus='0' port='2'/>
</hostdev>
<hostdev mode='subsystem' type='usb' managed='no'>
<source>
<vendor id='0x046d'/>
<product id='0xc05b'/>
<address bus='1' device='9'/>
</source>
<alias name='hostdev6'/>
<address type='usb' bus='0' port='4'/>
</hostdev>
<hostdev mode='subsystem' type='usb' managed='no'>
<source>
<vendor id='0x8087'/>
<product id='0x0029'/>
<address bus='1' device='10'/>
</source>
<alias name='hostdev7'/>
<address type='usb' bus='0' port='5'/>
</hostdev>
<memballoon model='none'/>
</devices>
<seclabel type='dynamic' model='dac' relabel='yes'>
<label>+0:+100</label>
<imagelabel>+0:+100</imagelabel>
</seclabel>
</domain>
VM Error In UnRAID:
QuoteErrorWarningSystemArrayLogin
2022-01-16T23:02:16.831862Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88376, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.831869Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88377, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.831876Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88378, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.831883Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88379, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.831893Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x8837a, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.831903Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x8837b, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.831912Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x8837c, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.831926Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x8837d, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.831936Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x8837e, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.831945Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x8837f, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.831953Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88380, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.831961Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88381, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.831967Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88382, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.831975Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88383, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.831982Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88384, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.831989Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88385, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.831996Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88386, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.832003Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88387, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.832011Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88388, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.832018Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88389, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.832027Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x8838a, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.832037Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x8838b, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.832046Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x8838c, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.832053Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x8838d, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.832061Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x8838e, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.832068Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x8838f, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.832076Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88390, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.832083Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88391, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.832089Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88392, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.832097Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88393, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.832104Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88394, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.832111Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88395, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.832119Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88396, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.832126Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88397, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.832133Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88398, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.832140Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x88399, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.832149Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x8839a, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.832160Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x8839b, 0x0,1) failed: Device or resource busy
2022-01-16T23:02:16.832168Z qemu-system-x86_64: vfio_region_write(0000:03:00.0:region0+0x8839c, 0x0,1) failed: Device or resource busySee images and diagnostics attached.
I've tried to split my IOMMU groups, by following @SpaceInvaderOne's guide, but after the reboot, they are all still grouped together?
Any ideas?
Have I selected the wrong things, causing it to crash?
-
Personally, I would use a web host, such as fusionhost.co.uk
- That's who I use.
-
Update, rebooted the server today and the loaded on screen.
Another step closer!! [emoji120]
What am I missing? Corrupt Windows OS?
Thanks for your help [emoji846]
Sent from my TA-1012 using Tapatalk -
Still can't get a picture on my monitor and I have no errors.
Any ideas?
-
@SpaceInvaderOne - Do you have any ideas that I can try?
-
So, the VM has started, but I have no picture on my monitor?
VM Log:
[quote]
ErrorWarningSystemArrayLogin
-smp 6,sockets=1,dies=1,cores=3,threads=2 \
-uuid df5c1f38-a6f0-9667-757e-0c4b4cc9c912 \
-display none \
-no-user-config \
-nodefaults \
-chardev socket,id=charmonitor,fd=31,server,nowait \
-mon chardev=charmonitor,id=monitor,mode=control \
-rtc base=localtime \
-no-hpet \
-no-shutdown \
-boot strict=on \
-device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x7.0x7 \
-device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x7 \
-device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x7.0x1 \
-device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x7.0x2 \
-device ahci,id=sata0,bus=pci.0,addr=0x3 \
-device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x4 \
-blockdev '{"driver":"file","filename":"/mnt/user/domains/Windows 10/vdisk1.img","node-name":"libvirt-3-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}' \
-blockdev '{"node-name":"libvirt-3-format","read-only":false,"cache":{"direct":false,"no-flush":false},"driver":"raw","file":"libvirt-3-storage"}' \
-device virtio-blk-pci,bus=pci.0,addr=0x5,drive=libvirt-3-format,id=virtio-disk2,bootindex=1,write-cache=on \
-blockdev '{"driver":"file","filename":"/mnt/user/isos/Windows/Window11_Insiders.iso","node-name":"libvirt-2-storage","auto-read-only":true,"discard":"unmap"}' \
-blockdev '{"node-name":"libvirt-2-format","read-only":true,"driver":"raw","file":"libvirt-2-storage"}' \
-device ide-cd,bus=sata0.0,drive=libvirt-2-format,id=sata0-0-0,bootindex=2 \
-blockdev '{"driver":"file","filename":"/mnt/user/isos/virtio-win-0.1.190-1.iso","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"}' \
-blockdev '{"node-name":"libvirt-1-format","read-only":true,"driver":"raw","file":"libvirt-1-storage"}' \
-device ide-cd,bus=ide.0,unit=1,drive=libvirt-1-format,id=ide0-0-1 \
-netdev tap,fd=33,id=hostnet0 \
-device virtio-net,netdev=hostnet0,id=net0,mac=52:54:00:9c:03:84,bus=pci.0,addr=0x2 \
-chardev pty,id=charserial0 \
-device isa-serial,chardev=charserial0,id=serial0 \
-chardev socket,id=charchannel0,fd=34,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 \
-device vfio-pci,host=0000:03:00.0,id=hostdev0,bus=pci.0,multifunction=on,addr=0x6 \
-device vfio-pci,host=0000:03:00.1,id=hostdev1,bus=pci.0,addr=0x6.0x1 \
-sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \
-msg timestamp=on
2021-12-16 17:56:27.456+0000: Domain id=6 is tainted: high-privileges
2021-12-16 17:56:27.456+0000: Domain id=6 is tainted: host-cpu
char device redirected to /dev/pts/0 (label charserial0)[/quote]
So close, but, not close enough!!
Anymore suggestions/ideas?
-
Researching this error brings me to info about a Mac VM - I've never had one...
/mnt/user/system/custom_ovmf
What am I missing, @Squid?
-
1 hour ago, Squid said:
Yes, but the devices still have to be isolated via one of the ACS override options in Settings - VM Settings
I have done as instructed and I selected both and restarted.
Now I see - attached screenshot:
And the 'Execution Error' is:
operation failed: unable to find any master var store for loader: /usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd
Thank you for your help!
-
20 minutes ago, Squid said:
It was mentioned earlier in this thread. If you're attempting to passthrough the AMD card, you've got to isolate it. Those current devices in group 1 aren't conducive to passthrough, so you'd have to use one of the ACS override settings.
The stuff before just forced the server to boot in BIOS and it wasn't clear why. I had to format the flash drive to get it to boot...
So, what did I miss? Do I just tick the box by the graphics card text? I don't understand
-
6 minutes ago, Squid said:
Did you fix this
2021-12-12 23:39:55.344+0000: 13274: error : qemuProcessReportLogError:2097 : internal error: qemu unexpectedly closed the monitor: 2021-12-12T23:39:55.300339Z qemu-system-x86_64: -device vfio-pci,host=0000:03:00.0,id=hostdev0,bus=pci.4,addr=0x0,romfile=/mnt/disk3/isos/Windows/Saphire.RX5708GB.8192.191031.rom: vfio 0000:03:00.0: group 1 is not viable Please ensure all devices within the iommu_group are bound to their vfio bus driver.By isolating (Tools - system devices) what you're attempting to passthrough from the OS?
Which ones should I enable?
IOMMU group 1?
-
[quote]Execution error
operation failed: unable to find any master var store for loader: /usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd0[/quote]
Any ideas why this still isn't working?
-
On 10/27/2021 at 2:52 AM, winklevos said:
Also interested in what everyone is using, and if the 6.9 version is better with UEFI and 3.0 USBs?
I had been running off SanDisk Cruzer Glide 3.0 16GB (SDCZ600-016G) for a few years but now my server doesn't want to post with it plugged in.
I'm going to grab a couple of different models and see what works@Rick Sanchez not sure if you found Testing to find the best USB flash drive to boot an OS like Unraid - YouTube
I bought the SanDisk Cruiser Fit 2.0 16GB
-
4 hours ago, ghost82 said:
I don't understand..did you change the boot options by enabling csm?
Does your unraid usb stick have the EFI folder?(note: EFI and not -EFI).
I would just backup the config folder in the unraid usb stick, delete all, copy new files on it, run the bootable script and allow uefi boot when asked, copy back the config folder, disable csm in the bios.
Is unraid your only os or are you booting other bare metal oses?If so, if they were installed with legacy bios you won't be able to boot them with csm disabled, until you convert the partition scheme from mbr to gpt and make the fat32 efi partition with bootloader file(s) in it.
Yes, and yes
I did a fresh install
Quote
If you have a PCIe graphics card installed and want to keep the iGPU active as well then please set:
BIOS > Advanced > Chipset Configuration > IGPU Multi-Monitor > Enabled
(you probably know that already)
This is what keeps knackering my system!
UnRAID refuses to boot when this is enabled?!
-
From AsRock
[quote]
Hello,
Could it be related to CSM?
BIOS > Boot > CSM
If CSM is enabled then the system should be able to boot from both legacy and EFI bootable devices.
If CSM is disabled then the system can boot only from EFI bootable devices. Devices without the required EFI folder/file structure will be ignored.
Please note that the integrated graphics in your CPU do not support legacy mode properly. So when using this integrated GPU (iGPU) please make sure to install the OS in UEFI/GPT mode, and boot from EFI bootable devices.
If you have a PCIe graphics card installed and want to keep the iGPU active as well then please set:
BIOS > Advanced > Chipset Configuration > IGPU Multi-Monitor > Enabled
(you probably know that already)
Thanks.
Kind regards,
ASRock Support
[/quote]
Stops UnRAID from working!
-
The third time lucky!
Hopefully, my new USBs will arrive quickly as one has a broken case!
-
What USB Drives is everyone using now?
-
5 hours ago, ghost82 said:
Did you change something in the bios??revert the changes!
I have. But still nothing.
.png.e6a7578585fffdba4ffc0e90f6a5beeb.png)
.png.0605ee6d733c1917112c51c9fa5a0172.png)
M710q Tiny 1L Backup Server
in Unraid Compulsive Design
Posted
This looks great and it's similar to what I want to do.
I currently have a node 304 case, but, might sell it for something smaller
Sent from my Pixel 6 using Tapatalk