-
Owel started following [DEFECT] Random Server Crash
-
Simpler / Easier PCI Device Pass Through for NON-GPUs
Fuck, it says IOMMU disabled. But virtualization on Bios is enabled... BIOS update?
-
Simpler / Easier PCI Device Pass Through for NON-GPUs
Hi Guis I wanted to pass through my tv tuner card (cine S2) But I get the following error, when I want to start up the VM: Error: unsupported configuration: host doesn't support VFIO pci passthrough. Device: root@Tower:~# lspci | grep Multi 02:00.0 Multimedia video controller: Micronas Semiconductor Holding AG nGene PCI-Express Multimedia Controller (rev 01) This is my xml <domain type='kvm'> <name>Debian</name> <uuid>ba6891bd-32cf-2236-2525-6e12bb490e9c</uuid> <memory unit='KiB'>1953125</memory> <currentMemory unit='KiB'>1953125</currentMemory> <vcpu placement='static'>3</vcpu> <os> <type arch='i686' machine='pc-i440fx-2.3'>hvm</type> <loader type='rom'>/usr/share/qemu/bios-256k.bin</loader> <boot dev='cdrom'/> </os> <features> <acpi/> <apic eoi='on'/> <pae/> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='3' threads='1'/> </cpu> <clock offset='localtime'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='yes'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/bin/qemu-system-x86_64</emulator> <disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='none'/> <source file='/mnt/cache/vm/Debian_VM/debian.qcow2'/> <target dev='vda' bus='virtio'/> <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/cache/vm/Debian_VM/debian-7.6.0-amd64-netinst.iso'/> <target dev='hdb' bus='ide'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' 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> <filesystem type='mount' accessmode='passthrough'> <source dir='/mnt/cache/'/> <target dir='cache'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </filesystem> <interface type='bridge'> <mac address='52:54:00:01:f8:a1'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </interface> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='5901' autoport='no' listen='192.168.178.11' keymap='de' sharePolicy='allow-exclusive'> <listen type='address' address='192.168.178.11'/> </graphics> <video> <model type='vga' vram='16384' heads='1'> <acceleration accel3d='yes' accel2d='yes'/> </model> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </hostdev> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </memballoon> </devices> </domain> root@Tower:~# egrep -q '^flags.*(svm|vmx)' /proc/cpuinfo && echo virtualization extensions available virtualization extensions available Hardware: AMD Athlon 5350 (Kabini) ASUS AM1M-A Unraid 6.0.1 Starting the VM without <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </hostdev> is no problem at all. How can i check if amd_iommu is enabled? Any other suggestions? BR Owel
-
unraid-tunables-tester.sh - A New Utility to Optimize unRAID md_* Tunables
I ask, because it is unclear for me, if only this script is slowed down by my application. or the parity check also? I read of scary out of memory errors. So my fear is, that when the script runs while everything else is stopped, it will come up with results , which will cause an error when the applications are running an parity starts ?! Can someone confirm that this fear is pointless?
-
unraid-tunables-tester.sh - A New Utility to Optimize unRAID md_* Tunables
Hi, I'm on v6b14 have two Dockers and two VMs running. Is it safe to run this script while these Application are running?
- Docker requests
-
[SOLVED] How to send remote command for Unraid to Sleep / Shutdown?
GET http://<UNRAID-IP>/update.htm?shutdown=apply
Owel
Members
-
Joined
-
Last visited