Slarti123
-
Posts
27 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Slarti123
-
-
OK, dann wäre der RAM das bottle neck und ich könnte da ein wenig nachrüsten.
Wenn ich aber auf ein Cache Share vom Client hochlade, dann ist die Phase 0 MB/s teilweise fast 1min lang, bevor es weitergeht. Das ist bei größeren Mengen schon nervig. Ist es einen Versuch wert, die Cache SSD zu tauschen oder ist das unnötig?
Übrigens: Vielen Dank für die schnellen und hilfreichen Antworten!
-
3 minutes ago, MPC561 said:
Wobei, hast Du mal gewartet ob er den Kopiervorgang nicht doch noch abschliesst?
Ja, das war auch tatsächlich so. Ging dann irgendwann weiter und hat den Vorgang erfolgreich abgeschlossen.
4 minutes ago, MPC561 said:Hmmm, dachte es geht um SMB? Und wenn dann vom einem Share auf dem Cache aufs Array und umgekehrt.
Verstehe nicht, was Du meinst. Habe mich vielleicht schlecht ausgedrückt. Habe von einem Share ("Video") eine "nicht gecachte" Datei aus dem Array kopiert auf ein anderes share ("nextdata"), das als "array only" konfiguriert ist. Dabei nur als Oberfläche den Win Explorer/SMB genutzt. Lief aber kein traffic über das Netzwerk.
-
Noch ein Nachtrag: Habe mal vom Win Client per SMB eine 13GB Datei auf das "Array only" geladen. Die ersten ca 4GB gingen mit ca 100MB/s hoch. Danach konstant bei ca. 45MB/s.
-
Quote
Du hast VMs laufen auf dem Cache und kopierst via SMB auf den Cache? Dann sieht man nicht deine Kernzuteilung. Hast Du Kerne Isoliert? Wieviel? Wieviel RAM nutzt die VM?
Ja. S. Screenshots. Nur 1 VM für HomeAssistant mit einem Kern und 4-8 GB RAM von 32GB.
Quote1.) Einen Share mal auf Array only stellen und nochmal kopieren ob es auch hakt beim kopieren darauf.
Das war interessant: Habe ein file von einem share auf das "Array only" share kopiert: 7,8 GB groß. Bis 72% eine Wahnsinnsgeschwindigkeit >1GB/s. Dann auf 0 gedroppt.
33 minutes ago, MPC561 said:2.) VMs und Docker stoppen und nochmal kopieren probieren auf den Cache.
Das hat keine Veränderung gebracht.
-
Hallo zusammen,
ich bin nicht 100% sicher, habe aber den Eindruck, dass das Phänomen erst seit dem letzten Update auftritt:
Wenn ich ein File kopiere, geht zunächst die Geschwindigkeit auf ca. 140Mb/s hoch. Nach kurzer Zeit bricht sie aber völlig ein. Geht auf 0 Mb/s, pausiert dort und schießt wieder kurz auf 140Mb/s hoch, usw.
Das passiert auch, wenn ich "lokal" kopiere: Also über einen Win Client auf dem SMB Share von einem Unterordner in den Parentfolder kopiere, ohne das Netzwerk zzu nutzen. RAM/CPU sind nie voll ausgelastet und ich nutze einen SSD Cache Drive (mit Error!). Anbei ein paar Screenshots.
Wo kann ich den anfangen, den Fehler einzukreisen?Danke!
-
Hi,
I'm using Gluetun with Surfshark and no territory restrictions.
Recently my connection speed decreased significantly.
When I restart the container, it connects to other servers. Sometimes they are faster, sometimes not.
Is there a better way to receive a new IP/server with an API call or using the command line?
Thanks!
-
Hi all,
I'm migrating my Home Assistant setup from a dedicated (but now dead) PC to a VM on Unraid.
My Unraid Server has only one physical NIC and runs several Dockers.
I have another stand alone server running OPNSense (where I manage "everything network").
My Home Assistant VM has to be on two VLANS:
- The "General" one, that is not tagged and all devices use (including all dockers)
- A "Untrusted" one (VLAN "20"), where I have some IOT devices in
On my standalone Home Assistant PC I had two physical NICs and my switch took over for tagging.
I guess, in my new setup I could create a virtual nic and tag that one?
I am really concernced to break things on my Unraid for all other dockers, etc.
So: Could someone please give an idiot-safe instruction what to do?Thank you very much!
-
Reviving this old threat as I experience the same issue.
Updated Unraid to 6.10 and now the dockers run in the subnet 172.17.0.X.My actual LAN is in 192.168.178.X
I have some docker in bridge or host mode which works, but I do have some as br0 with static IPs in the range of 192.168.178.X.
The br0s now cannot find the dockers in host or bridge mode, anymore.
Everything worked fine before and I am not very keen to change all settings in some of the clients, etc.
Any way to just bring the docker network behaviour back to how it used to be in my environment?
-
Hi all,
I've set up the Nordlynx version succesfully and also tunneling other container's traffic through it works.
But I see one odd behaviour and have no clue:
I use xteve as a container to provide a m3u file for clients. xteve runs through that VPN via "--net=container:nordlynx".
I am able to get acccess to that m3u with every app or desktop client (http://UNRAID-IP:34400/m3u/xteve.m3u).
I did add 34400 to the ports in Nordlynx and get access in the browser to the GUI.
But: When I use the exact same URL in Jellyfin to get access to the m3u, it gets no access.
Same behaviour in Plex, when adding it as a DVR (http://UNRAID-IP:34400)- it won't find xteve.
Jellyfin and Plex are running as dockers, too, but do not use the VPN.
Do I have to open Upnp or something similar, maybe?
Thanks!
-
Thank you!
Solved:
TL;DR
had to delete everything (image, container) including the "appdata" folder and re-install without error messages.
-
Thanks, everyone:
Solved.
For the record (and others):
1) Traccar:
The template createa a folder called "traccar.xml". You have to delete that and upload the linked XML file, instead (and of course, do not autostart the docker, before).For some reason, that created a container that was never ever able to start again, even though I manually copied as described.
Had to remove the container, delete the image, manually delete all data in "appdata" and then set everything up from scratch as desribed above.
2) TVH:to give you the full picture: still not sure about the initial reasons. Still, similar solution: completely delete container, image and "appdata". New, clean setup. Works now...
Thanks a lot! -
Thank you!
I get that one:
docker: Error response from daemon: Conflict. The container name "/tvheadend_neu" is already in use by container "1ee57545183880d2da1786e6a8993b32db491fbc1920a8273ef94afa6759b5d2". You have to remove (or rename) that container to be able to reuse that name.
-
Thanks for the fast reply.
My docker run shows no errors and is as follows:root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker create --name='tvheadend_neu' --net='br0' --ip='192.168.178.15' -e TZ="Europe/Berlin" -e HOST_OS="Unraid" -e 'TCP_PORT_9981'='9981' -e 'TCP_PORT_9982'='9982' -e 'RUN_OPTS'='' -e 'PUID'='99' -e 'PGID'='100' -e 'UMASK'='022' -v '/mnt/user/Media/Video/Aufnahmen/':'/recordings':'rw' -v '/mnt/user/appdata/tvheadend':'/config':'rw' --device='/dev/dri' --device='/dev/dvb' 'lscr.io/linuxserver/tvheadend' 1ee57545183880d2da1786e6a8993b32db491fbc1920a8273ef94afa6759b5d2 The command finished successfully!
What I did just see in the log is that:
Jul 3 16:29:11 Server kernel: docker0: port 5(veth78599bd) entered blocking state Jul 3 16:29:11 Server kernel: docker0: port 5(veth78599bd) entered disabled state Jul 3 16:29:11 Server kernel: device veth78599bd entered promiscuous mode Jul 3 16:29:11 Server kernel: docker0: port 5(veth78599bd) entered blocking state Jul 3 16:29:11 Server kernel: docker0: port 5(veth78599bd) entered forwarding state Jul 3 16:29:11 Server kernel: docker0: port 5(veth78599bd) entered disabled state Jul 3 16:29:11 Server kernel: docker0: port 5(veth78599bd) entered disabled state Jul 3 16:29:11 Server kernel: device veth78599bd left promiscuous mode Jul 3 16:29:11 Server kernel: docker0: port 5(veth78599bd) entered disabled state -
Hi all,
I've had a lot of dockers running succesfully.
When I installed a new one (Traccar) I experienced an "Execution Error- bad parameter".
I tried to install that as custom Br0 with own (free) IP. I did realize that in the overview the port mapping shows 0.0.0.0 instead of 192.XXX.
Anyway, I had the same error with every other "Network Type". I decided to put it aside and look at it later.
Another Docker was running smoothly. But I wanted a clean restart (TVHeadend).
It was set up as custom Br0 with 192(...)15 and worked.
I did remove it through the GUI and re-installed it as before (without any error). I did also use the same Network parameters.
Now, I see the same: I cannot run the docker ("Server Error" instead of "bad parameter"), but all mappings show 0.0.0.0 instead of the desired 192....15.
Any idea where to start?
(not even sure, if the two occurences are dependent).Thanks!
-
Hi,
I'm trying to get traccar running as a Docker.I did download the traccar.xml and put it into the folder that I selected as host path.
I do not get any error messages when applying:
Command: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker create --name='traccar2' --net='br0' --ip='192.168.178.13' -e TZ="Europe/Berlin" -e HOST_OS="Unraid" -e 'TCP_PORT_8082'='8082' -e 'TCP_PORT_5000-5150'='5000-5150' -e 'UDP_PORT_5000-5150'='5000-5150' -v '/mnt/user/appdata/traccar/logs':'/opt/traccar/logs':'rw' -v '/mnt/user/appdata/traccar/':'/opt/traccar/conf/traccar.xml':'rw' --restart always --hostname traccar 'traccar/traccar' 903a019ed9bef0cb8a80ababf42e9fd94a1eb56c51949d9bc3f9ba62ed7f6b91 The command finished successfully!When I want to start the docker, though, I receive an "Execution Error- bad parameter".
My fav would be running it as "br0", but I dod get the same error in each other scenario.
There is no conflicting IP, btw.What I did just see ion the log is that:
Jul 3 16:29:11 Server kernel: docker0: port 5(veth78599bd) entered blocking state Jul 3 16:29:11 Server kernel: docker0: port 5(veth78599bd) entered disabled state Jul 3 16:29:11 Server kernel: device veth78599bd entered promiscuous mode Jul 3 16:29:11 Server kernel: docker0: port 5(veth78599bd) entered blocking state Jul 3 16:29:11 Server kernel: docker0: port 5(veth78599bd) entered forwarding state Jul 3 16:29:11 Server kernel: docker0: port 5(veth78599bd) entered disabled state Jul 3 16:29:11 Server kernel: docker0: port 5(veth78599bd) entered disabled state Jul 3 16:29:11 Server kernel: device veth78599bd left promiscuous mode Jul 3 16:29:11 Server kernel: docker0: port 5(veth78599bd) entered disabled state
Any hint?
Thank you. -
On 1/15/2022 at 9:36 PM, YoHoNoMo said:
Ich hab's... Das Template hat die Variable RUN_OPTS und die hat wiederum den Standard-Wert "run options here", wie man hier noch sehen kann:
1.000 Dank!
Das war es auch bei mir
-
Hi,
I've set up two VMs, that I start manually, when I need them (WIN10, Ubuntu- they never run simultaneously). They use my 2nd GPU (NVidia Quadro). See configs below.
Now I've set up another VM (Home Assistant OS) without a GPU and pure VNC.
I see the following behaviour:
1) Starting one of the original VMs first, I am able to start the Home Assistant OS afterwards. But after some minutes the original VMs are crashing while the Home Assistant OS keeps running (see log below).
2) When I start the Home Assistant OS first, I'm not even able to start any of the original VMs and receive a pop up error window:
Quoteinternal error: qemu unexpectedly closed the monitor
Any Idea where to look for the issues? I am not aware of any PCIe, that they are sharing. CPUs are pinned to not conflict.
WIN10 VM
<?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>WindowsVM</name> <uuid>700c4a2f-4046-f721-fcd2-21b5367ece58</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>29884416</memory> <currentMemory unit='KiB'>13107200</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>6</vcpu> <cputune> <vcpupin vcpu='0' cpuset='1'/> <vcpupin vcpu='1' cpuset='7'/> <vcpupin vcpu='2' cpuset='3'/> <vcpupin vcpu='3' cpuset='9'/> <vcpupin vcpu='4' cpuset='5'/> <vcpupin vcpu='5' cpuset='11'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-5.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/700c4a2f-4046-f721-fcd2-21b5367ece58_VARS-pure-efi.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='3' threads='2'/> <cache mode='passthrough'/> <feature policy='require' name='topoext'/> </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/domains/WindowsVM/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/Win10_20H2_German_x64.iso'/> <target dev='hda' bus='sata'/> <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.190-1.iso'/> <target dev='hdb' bus='sata'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='pci' index='0' model='pcie-root'/> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x8'/> <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'/> <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'/> <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='0x13'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0x14'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/> </controller> <controller type='pci' index='6' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0xb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x3'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <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> <interface type='bridge'> <mac address='52:54:00:40:81:f8'/> <source bridge='br0'/> <model type='virtio-net'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' 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'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </source> <rom file='/mnt/user/isos/quadro.dump'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x04' slot='0x00' function='0x1'/> </source> <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='0x06' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046a'/> <product id='0x0023'/> </source> <address type='usb' bus='0' port='1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x413c'/> <product id='0x3012'/> </source> <address type='usb' bus='0' port='2'/> </hostdev> <memballoon model='none'/> </devices> </domain>
Home Assistant VM
<?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='1'> <name>homeassistantOS</name> <uuid>0b796e24-559c-5f55-9a90-7e3454f0b9f9</uuid> <metadata> <vmtemplate xmlns="unraid" name="Linux" icon="linux.png" os="linux"/> </metadata> <memory unit='KiB'>6815744</memory> <currentMemory unit='KiB'>2097152</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>2</vcpu> <cputune> <vcpupin vcpu='0' cpuset='4'/> <vcpupin vcpu='1' cpuset='10'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-5.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/0b796e24-559c-5f55-9a90-7e3454f0b9f9_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='1' threads='2'/> <cache mode='passthrough'/> <feature policy='require' name='topoext'/> </cpu> <clock offset='utc'> <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='file' device='disk'> <driver name='qemu' type='qcow2' cache='writeback'/> <source file='/mnt/user/domains/haos_ova-7.0.qcow2' index='1'/> <backingStore/> <target dev='hdc' bus='sata'/> <boot order='1'/> <alias name='sata0-0-2'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <controller type='sata' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <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='0x10'/> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x11'/> <alias name='pci.2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0x12'/> <alias name='pci.3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0x13'/> <alias name='pci.4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> </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='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:49:1c:78'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='virtio-net'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x01' 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-homeassistantOS/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'/> <address type='usb' bus='0' port='2'/> </input> <input type='mouse' bus='ps2'> <alias name='input1'/> </input> <input type='keyboard' bus='ps2'> <alias name='input2'/> </input> <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='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <alias name='video0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </video> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </memballoon> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain>
Log of crashed Win VM:
Quoteno-shutdown \
-boot strict=on \
-device pcie-root-port,port=0x8,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x1 \
-device pcie-root-port,port=0x9,chassis=2,id=pci.2,bus=pcie.0,addr=0x1.0x1 \
-device pcie-root-port,port=0xa,chassis=3,id=pci.3,bus=pcie.0,addr=0x1.0x2 \
-device pcie-root-port,port=0x13,chassis=4,id=pci.4,bus=pcie.0,addr=0x2.0x3 \
-device pcie-root-port,port=0x14,chassis=5,id=pci.5,bus=pcie.0,addr=0x2.0x4 \
-device pcie-root-port,port=0xb,chassis=6,id=pci.6,bus=pcie.0,addr=0x1.0x3 \
-device ich9-usb-ehci1,id=usb,bus=pcie.0,addr=0x7.0x7 \
-device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pcie.0,multifunction=on,addr=0x7 \
-device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pcie.0,addr=0x7.0x1 \
-device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pcie.0,addr=0x7.0x2 \
-device virtio-serial-pci,id=virtio-serial0,bus=pci.2,addr=0x0 \
-blockdev '{"driver":"file","filename":"/mnt/user/domains/WindowsVM/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.3,addr=0x0,drive=libvirt-3-format,id=virtio-disk2,bootindex=1,write-cache=on \
-blockdev '{"driver":"file","filename":"/mnt/user/isos/Win10_20H2_German_x64.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=ide.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.1,drive=libvirt-1-format,id=sata0-0-1 \
-netdev tap,fd=35,id=hostnet0 \
-device virtio-net,netdev=hostnet0,id=net0,mac=52:54:00:40:81:f8,bus=pci.1,addr=0x0 \
-chardev pty,id=charserial0 \
-device isa-serial,chardev=charserial0,id=serial0 \
-chardev socket,id=charchannel0,fd=37,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=3 \
-device vfio-pci,host=0000:04:00.0,id=hostdev0,bus=pci.4,addr=0x0,romfile=/mnt/user/isos/quadro.dump \
-device vfio-pci,host=0000:04:00.1,id=hostdev1,bus=pci.5,addr=0x0 \
-device vfio-pci,host=0000:06:00.0,id=hostdev2,bus=pci.6,addr=0x0 \
-device usb-host,hostbus=5,hostaddr=2,id=hostdev3,bus=usb.0,port=1 \
-device usb-host,hostbus=7,hostaddr=3,id=hostdev4,bus=usb.0,port=2 \
-sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \
-msg timestamp=on
2021-12-09 16:46:24.429+0000: Domain id=3 is tainted: high-privileges
2021-12-09 16:46:24.429+0000: Domain id=3 is tainted: host-cpu
char device redirected to /dev/pts/1 (label charserial0)
2021-12-09 16:46:32.299+0000: shutting down, reason=failed -
Thank you so much! Scanning for new hardware + power options solved it.
(GPU fixes as a bycatch
)
Amazing.
-
And here is the config of the VM
<?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>WindowsVM</name> <uuid>700c4a2f-4046-f721-fcd2-21b5367ece58</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>29884416</memory> <currentMemory unit='KiB'>13107200</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>8</vcpu> <cputune> <vcpupin vcpu='0' cpuset='1'/> <vcpupin vcpu='1' cpuset='7'/> <vcpupin vcpu='2' cpuset='3'/> <vcpupin vcpu='3' cpuset='9'/> <vcpupin vcpu='4' cpuset='4'/> <vcpupin vcpu='5' cpuset='10'/> <vcpupin vcpu='6' cpuset='5'/> <vcpupin vcpu='7' cpuset='11'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-5.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/700c4a2f-4046-f721-fcd2-21b5367ece58_VARS-pure-efi.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'/> <feature policy='require' name='topoext'/> </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/domains/WindowsVM/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/Win10_20H2_German_x64.iso'/> <target dev='hda' bus='sata'/> <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.190-1.iso'/> <target dev='hdb' bus='sata'/> <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='pcie-root'/> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x8'/> <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'/> <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'/> <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='0x13'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0x14'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <interface type='bridge'> <mac address='52:54:00:40:81:f8'/> <source bridge='br0'/> <model type='virtio-net'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' 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'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </source> <rom file='/mnt/user/isos/quadro.dump'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046a'/> <product id='0x0023'/> </source> <address type='usb' bus='0' port='1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x413c'/> <product id='0x3012'/> </source> <address type='usb' bus='0' port='2'/> </hostdev> <memballoon model='none'/> </devices> </domain>
-
Hi all,
I've installed a CLS PCIe USB 3.0 card. It is in its own IOMMU group:
IOMMU group 24: [1106:3483] 06:00.0 USB controller: VIA Technologies, Inc. VL805/806 xHCI USB 3.0 Controller (rev 01) This controller is bound to vfio, connected USB devices are not visible.PCIe ACS override is set to "both".
I do passthrough the controller for two separate VMS (not running simultaneously, just for testing).
1) UBUNTU: hot swap works, everything recognized
2) WIN 10: Whatever I connect to the ports, is not recognized by the VM. When It is supposed to work out of the box with WIN 10 without installing any drivers. Still, I downloaded the correct ones and gave it a try: The setup exits with the message, that it cannot detect the hardware.
Any ideas?
Thanks!
This is the log of the WIN VM:
-no-hpet \ -no-shutdown \ -boot strict=on \ -device pcie-root-port,port=0x8,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x1 \ -device pcie-root-port,port=0x9,chassis=2,id=pci.2,bus=pcie.0,addr=0x1.0x1 \ -device pcie-root-port,port=0xa,chassis=3,id=pci.3,bus=pcie.0,addr=0x1.0x2 \ -device pcie-root-port,port=0x13,chassis=4,id=pci.4,bus=pcie.0,addr=0x2.0x3 \ -device pcie-root-port,port=0x14,chassis=5,id=pci.5,bus=pcie.0,addr=0x2.0x4 \ -device ich9-usb-ehci1,id=usb,bus=pcie.0,addr=0x7.0x7 \ -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pcie.0,multifunction=on,addr=0x7 \ -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pcie.0,addr=0x7.0x1 \ -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pcie.0,addr=0x7.0x2 \ -device virtio-serial-pci,id=virtio-serial0,bus=pci.2,addr=0x0 \ -blockdev '{"driver":"file","filename":"/mnt/user/domains/WindowsVM/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.3,addr=0x0,drive=libvirt-3-format,id=virtio-disk2,bootindex=1,write-cache=on \ -blockdev '{"driver":"file","filename":"/mnt/user/isos/Win10_20H2_German_x64.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=ide.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.1,drive=libvirt-1-format,id=sata0-0-1 \ -netdev tap,fd=33,id=hostnet0 \ -device virtio-net,netdev=hostnet0,id=net0,mac=52:54:00:40:81:f8,bus=pci.1,addr=0x0 \ -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=3 \ -device vfio-pci,host=0000:04:00.0,id=hostdev0,bus=pci.4,addr=0x0,romfile=/mnt/user/isos/quadro.dump \ -device vfio-pci,host=0000:06:00.0,id=hostdev1,bus=pci.5,addr=0x0 \ -device usb-host,hostbus=5,hostaddr=2,id=hostdev2,bus=usb.0,port=1 \ -device usb-host,hostbus=7,hostaddr=2,id=hostdev3,bus=usb.0,port=2 \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on 2021-12-07 09:21:46.303+0000: Domain id=6 is tainted: high-privileges 2021-12-07 09:21:46.303+0000: Domain id=6 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) 2021-12-07T09:21:53.486675Z qemu-system-x86_64: vfio: Cannot reset device 0000:04:00.0, depends on group 22 which is not owned. 2021-12-07T09:21:54.506372Z qemu-system-x86_64: vfio: Cannot reset device 0000:04:00.0, depends on group 22 which is not owned. -
Thank you for your swift reply. i somehow solved it- for now.
I just started the mover manually and when it was finished, all clients had access, again.
Really strange, as my cache drive had only 120GB used (of a 1TB disk)...
-
Hi all,
I've set up Unraid 10+ days ago and it works smoothly. Not aware of any change, that I've made recently.
Today I started a longer file transfer (500GB) and left my laptop. When I came back, it had no access to the SMB, anymore.
Tried to re-connect and access was denied.
Tested the same with 2 other Win machines which had already access before: same behaviour.
What i tried so far, without success:
On the Unraid site:
Attempt #1) Just reboot
#2) full pw reset: shut off, USB on other PC and delete passwd , smbpasswd , shadow, set new passwords
#3): create new user with rw rights
On Windows site:
#1) Tried with all existing users including root
#2) username+"\"
2a) blank password
2b) correct passwordI don't know what to try now. Are there any logs that I could look into to get an idea?
Thanks!
-
Thank you both for that amazing input, was the last trigger needed. I was able to get some nice parts to build the Ryzen route. Will do that first and get used to Unraid. Could easily be, that I keep an alert active for ebay and will shoot a 19" solution with XEON, when I see a good deal. Would then turn that into the home server and use the Ryzen as VM...
But for training and familiarity I will go first with what I know
(we're having a PV module on the roof and I will take care of consumption in the next step, then).
-
Sorry for hijacking this. Did you ever succeed? I could get the same motherboard really cheap and woul start with a 2600x and GT 1030. Before burning money, I'd like to know if there is an actual working fix.
Thanks!
)
Kopiergeschwindigkeit schwankt stark//fällt auf Null
in Deutsch
Posted
Top, ganz herzlichen Dank!