comfox
-
Posts
255 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by comfox
-
-
Was this issue ever resolved? I am now experiencing this with my newly created VM
-
Just updating everyone that has helped me on this issue so far...
Since it was a holiday weekend where I am, I decided to build a new VM from scratch using a bunch of the new features that 6.2 offered (pci stubbing, gui assinging of devices, etc, etc) as my old VM was over a year old and from the original days of KVM's on unRAID. This also allowed me to install Win 10 Anniversary Update since my old VM would error out when trying.
The newly built VM is up and running just fine and I migrated all my data off of the old VM by assigning the img as disk 2 and doing a straight copy. This VM has been running for 24 hours now and is working fine. All devices are passed through and it is performing as expected.
I know this is the most drastic option for resolving this issue but non the less it has resolved the issue. Feel free to move on from this post and enjoy your day!
Before 6.2.1, were you running 6.2.0 or an earlier version?
I was running 6.2.0 for 2 days prior to upgrading to 6.2.1. All was working fine on 6.2.0 prior to the upgrade to 6.2.1
-
Just updating everyone that has helped me on this issue so far...
Since it was a holiday weekend where I am, I decided to build a new VM from scratch using a bunch of the new features that 6.2 offered (pci stubbing, gui assinging of devices, etc, etc) as my old VM was over a year old and from the original days of KVM's on unRAID. This also allowed me to install Win 10 Anniversary Update since my old VM would error out when trying.
The newly built VM is up and running just fine and I migrated all my data off of the old VM by assigning the img as disk 2 and doing a straight copy. This VM has been running for 24 hours now and is working fine. All devices are passed through and it is performing as expected.
I know this is the most drastic option for resolving this issue but non the less it has resolved the issue. Feel free to move on from this post and enjoy your day!
-
I just tried to start up the VM again, it failed, and the output of that command has changed. This is now what it shows:
01:00.0 VGA compatible controller: NVIDIA Corporation GM204 [GeForce GTX 970] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GM204 [GeForce GTX 970] Flags: fast devsel, IRQ 11 Memory at f6000000 (32-bit, non-prefetchable) [disabled] [size=16M] Memory at e0000000 (64-bit, prefetchable) [disabled] [size=256M] Memory at f0000000 (64-bit, prefetchable) [disabled] [size=32M] I/O ports at e000 [disabled] [size=128] Expansion ROM at f7000000 [disabled] [size=512K] Capabilities: [60] Power Management version 3 Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [78] Express Legacy Endpoint, MSI 00 Capabilities: [100] Virtual Channel Capabilities: [250] Latency Tolerance Reporting Capabilities: [258] L1 PM Substates Capabilities: [128] Power Budgeting <?> Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?> Capabilities: [900] #19 Kernel driver in use: vfio-pci 01:00.1 Audio device: NVIDIA Corporation GM204 High Definition Audio Controller (rev a1) Subsystem: ASUSTeK Computer Inc. GM204 High Definition Audio Controller Flags: bus master, fast devsel, latency 0, IRQ 10 Memory at f7080000 (32-bit, non-prefetchable) [size=16K] Capabilities: [60] Power Management version 3 Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [78] Express Endpoint, MSI 00 Kernel driver in use: vfio-pci
-
My theory was incorrect (but was the most likely thing).
I don't use the PCI ACS override, but it does appear to be working if/as needed, as your groups are separated.
I'm kind of wondering if something is binding this card, preventing it to be assigned to vfio-pci.
From the terminal if you type "lspci -v" look and see if the device is binded to something.
...
Thanks. After a fresh boot up here is the output of the command for the Group 16 IOMMU
01:00.0 VGA compatible controller: NVIDIA Corporation GM204 [GeForce GTX 970] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GM204 [GeForce GTX 970] Flags: fast devsel, IRQ 11 Memory at f6000000 (32-bit, non-prefetchable) [disabled] [size=16M] Memory at e0000000 (64-bit, prefetchable) [disabled] [size=256M] Memory at f0000000 (64-bit, prefetchable) [disabled] [size=32M] I/O ports at e000 [disabled] [size=128] Expansion ROM at f7000000 [disabled] [size=512K] Capabilities: [60] Power Management version 3 Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [78] Express Legacy Endpoint, MSI 00 Capabilities: [100] Virtual Channel Capabilities: [250] Latency Tolerance Reporting Capabilities: [258] L1 PM Substates Capabilities: [128] Power Budgeting <?> Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?> Capabilities: [900] #19 01:00.1 Audio device: NVIDIA Corporation GM204 High Definition Audio Controller (rev a1) Subsystem: ASUSTeK Computer Inc. GM204 High Definition Audio Controller Flags: bus master, fast devsel, latency 0, IRQ 10 Memory at f7080000 (32-bit, non-prefetchable) [size=16K] Capabilities: [60] Power Management version 3 Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [78] Express Endpoint, MSI 00
-
Upgraded to 6.2.1 this morning and now my VM will not start. Here is the error log from the VM page.
2016-10-07 14:05:01.388+0000: starting up libvirt version: 1.3.1, qemu version: 2.5.1, hostname: Tower Domain id=1 is tainted: high-privileges Domain id=1 is tainted: custom-argv Domain id=1 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) 2016-10-07T14:05:02.215662Z qemu-system-x86_64: -device vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: error opening /dev/vfio/16: Operation not permitted 2016-10-07T14:05:02.215685Z qemu-system-x86_64: -device vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to get group 16 2016-10-07T14:05:02.215690Z qemu-system-x86_64: -device vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: Device initialization failed 2016-10-07 14:05:02.481+0000: shutting down 2016-10-07 14:07:02.947+0000: starting up libvirt version: 1.3.1, qemu version: 2.5.1, hostname: Tower Domain id=2 is tainted: high-privileges Domain id=2 is tainted: custom-argv Domain id=2 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) 2016-10-07T14:07:03.762923Z qemu-system-x86_64: -device vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: error opening /dev/vfio/16: Operation not permitted 2016-10-07T14:07:03.762947Z qemu-system-x86_64: -device vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to get group 16 2016-10-07T14:07:03.762952Z qemu-system-x86_64: -device vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: Device initialization failed 2016-10-07 14:07:04.033+0000: shutting down
I believe it is erroring out on my Video Card, but really have no idea what to change to make it work. Worked fine in all 6.2 and lower versions, and now doesn't. Odd.
I have reverted back to 6.2 and the issue remains. I will create another post in the main help section now.
Are you sure you didn't just enable ACS override where there was none before? Maybe your IOMMU groups changed layout. I had this issue when enabling ACS override on a processor with no ACS feature, where it would try to separate the video cards from the PCIe root controller they're normally grouped with.
No I have had ACS enables the entire time. Also there is no issues with IOMMU group 16. It is just the NVIDIA video and audio devices in it.
-
Can you do this as a test. Plug the device in to a USB port that is NOT passed through, essentially letting unRAID detect it. Then go in to the GUI XML edit screen and see if unRAID shows the two devices properly. If it does then just use this section to pass them through directly.
I am doing a similar thing to you, except that I do not plug my Logitech USB devices in to the passed through USB. I let unRAID pass them through directly. This has the added benefit of having more USB ports for my Windows VM.
-
Please provide the listing of your IOMMU groups, you'll find this listed in the system devices page.
It looks as if for whatever reason the device 1:00:0 is now in a group with other devices, which would give this error.
This is speculation until I see that output.
Yes of course, I thought I had put that in, guess I copied and didn't paste it. See above.
-
Hi All,
I upgraded to 6.2.1 this morning and once booted up my VM would not start. I downgraded back to 6.2 and it still won't start so creating this thread for help.
Here is the error from the VM page.
2016-10-07 14:05:01.388+0000: starting up libvirt version: 1.3.1, qemu version: 2.5.1, hostname: Tower Domain id=1 is tainted: high-privileges Domain id=1 is tainted: custom-argv Domain id=1 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) 2016-10-07T14:05:02.215662Z qemu-system-x86_64: -device vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: error opening /dev/vfio/16: Operation not permitted 2016-10-07T14:05:02.215685Z qemu-system-x86_64: -device vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to get group 16 2016-10-07T14:05:02.215690Z qemu-system-x86_64: -device vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: Device initialization failed 2016-10-07 14:05:02.481+0000: shutting down 2016-10-07 14:07:02.947+0000: starting up libvirt version: 1.3.1, qemu version: 2.5.1, hostname: Tower Domain id=2 is tainted: high-privileges Domain id=2 is tainted: custom-argv Domain id=2 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) 2016-10-07T14:07:03.762923Z qemu-system-x86_64: -device vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: error opening /dev/vfio/16: Operation not permitted 2016-10-07T14:07:03.762947Z qemu-system-x86_64: -device vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to get group 16 2016-10-07T14:07:03.762952Z qemu-system-x86_64: -device vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: Device initialization failed 2016-10-07 14:07:04.033+0000: shutting down
I believe it is erroring out on my Video Card, but really have no idea what to change to make it work. Worked fine in all 6.2 and lower versions, and now doesn't.
Here is my list of PCI Devices
00:00.0 Host bridge [0600]: Intel Corporation 4th Gen Core Processor DRAM Controller [8086:0c00] (rev 06) 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller [8086:0c01] (rev 06) 00:01.1 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x8 Controller [8086:0c05] (rev 06) 00:02.0 VGA compatible controller [0300]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) 00:03.0 Audio device [0403]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller [8086:0c0c] (rev 06) 00:14.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI [8086:8c31] (rev 05) 00:16.0 Communication controller [0780]: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 [8086:8c3a] (rev 04) 00:1a.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 [8086:8c2d] (rev 05) 00:1b.0 Audio device [0403]: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller [8086:8c20] (rev 05) 00:1c.0 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 [8086:8c10] (rev d5) 00:1c.3 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #4 [8086:8c16] (rev d5) 00:1c.5 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #6 [8086:8c1a] (rev d5) 00:1c.6 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #7 [8086:8c1c] (rev d5) 00:1c.7 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #8 [8086:8c1e] (rev d5) 00:1d.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 [8086:8c26] (rev 05) 00:1f.0 ISA bridge [0601]: Intel Corporation Z87 Express LPC Controller [8086:8c44] (rev 05) 00:1f.2 SATA controller [0106]: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] [8086:8c02] (rev 05) 00:1f.3 SMBus [0c05]: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller [8086:8c22] (rev 05) 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) 01:00.1 Audio device [0403]: NVIDIA Corporation GM204 High Definition Audio Controller [10de:0fbb] (rev a1) 02:00.0 USB controller [0c03]: Fresco Logic FL1100 USB 3.0 Host Controller [1b73:1100] (rev 10) 04:00.0 Ethernet controller [0200]: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller [1969:e091] (rev 13) 05:00.0 PCI bridge [0604]: Pericom Semiconductor PI7C9X111SL PCIe-to-PCI Reversible Bridge [12d8:e111] (rev 02) 06:04.0 RAID bus controller [0104]: Silicon Image, Inc. SiI 3124 PCI-X Serial ATA Controller [1095:3124] (rev 01) 07:00.0 Ethernet controller [0200]: Intel Corporation 82574L Gigabit Network Connection [8086:10d3] 08:00.0 SATA controller [0106]: ASMedia Technology Inc. ASM1062 Serial ATA Controller [1b21:0612] (rev 01)
Here is the IOMMU Groups
/sys/kernel/iommu_groups/0/devices/0000:00:00.0 /sys/kernel/iommu_groups/1/devices/0000:00:01.0 /sys/kernel/iommu_groups/2/devices/0000:00:01.1 /sys/kernel/iommu_groups/3/devices/0000:00:02.0 /sys/kernel/iommu_groups/4/devices/0000:00:03.0 /sys/kernel/iommu_groups/5/devices/0000:00:14.0 /sys/kernel/iommu_groups/6/devices/0000:00:16.0 /sys/kernel/iommu_groups/7/devices/0000:00:1a.0 /sys/kernel/iommu_groups/8/devices/0000:00:1b.0 /sys/kernel/iommu_groups/9/devices/0000:00:1c.0 /sys/kernel/iommu_groups/10/devices/0000:00:1c.3 /sys/kernel/iommu_groups/11/devices/0000:00:1c.5 /sys/kernel/iommu_groups/12/devices/0000:00:1c.6 /sys/kernel/iommu_groups/13/devices/0000:00:1c.7 /sys/kernel/iommu_groups/14/devices/0000:00:1d.0 /sys/kernel/iommu_groups/15/devices/0000:00:1f.0 /sys/kernel/iommu_groups/15/devices/0000:00:1f.2 /sys/kernel/iommu_groups/15/devices/0000:00:1f.3 /sys/kernel/iommu_groups/16/devices/0000:01:00.0 /sys/kernel/iommu_groups/16/devices/0000:01:00.1 /sys/kernel/iommu_groups/17/devices/0000:02:00.0 /sys/kernel/iommu_groups/18/devices/0000:04:00.0 /sys/kernel/iommu_groups/19/devices/0000:05:00.0 /sys/kernel/iommu_groups/19/devices/0000:06:04.0 /sys/kernel/iommu_groups/20/devices/0000:07:00.0 /sys/kernel/iommu_groups/21/devices/0000:08:00.0
Here is my VM XML
<domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>Win 10 Main PC</name> <uuid>e43d49b3-00c0-a740-1250-341a6f1f11a4</uuid> <description>This is the main gaming rig in the office</description> <metadata/> <memory unit='KiB'>12107200</memory> <currentMemory unit='KiB'>12107200</currentMemory> <memoryBacking> <nosharepages/> <locked/> </memoryBacking> <vcpu placement='static'>7</vcpu> <cputune> <vcpupin vcpu='0' cpuset='1'/> <vcpupin vcpu='1' cpuset='2'/> <vcpupin vcpu='2' cpuset='3'/> <vcpupin vcpu='3' cpuset='4'/> <vcpupin vcpu='4' cpuset='5'/> <vcpupin vcpu='5' cpuset='6'/> <vcpupin vcpu='6' cpuset='7'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-2.5'>hvm</type> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor id='none'/> </hyperv> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='7' 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/user/VM_HDD_Lib/Win 10 Main PC/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> <controller type='usb' index='0' model='nec-xhci'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <controller type='pci' index='0' model='pci-root'/> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:d9:23:a0'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </interface> <serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <source mode='bind'/> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x1532'/> <product id='0x011a'/> </source> </hostdev> <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x046d'/> <product id='0xc24a'/> </source> </hostdev> <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='0x06' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x2433'/> <product id='0xb200'/> </source> </hostdev> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </memballoon> </devices> <qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='ioh3420,bus=pci.0,addr=1c.0,multifunction=on,port=2,chassis=1,id=root.1'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=01:00.1,bus=root.1,addr=00.1'/> </qemu:commandline> </domain>
For some reason my unRAID will not download an Anonymous version of diagnostics (clicking the button and nothing happens) so I can't post that. I have posted my syslog though.
-
Upgraded to 6.2.1 this morning and now my VM will not start. Here is the error log from the VM page.
2016-10-07 14:05:01.388+0000: starting up libvirt version: 1.3.1, qemu version: 2.5.1, hostname: Tower Domain id=1 is tainted: high-privileges Domain id=1 is tainted: custom-argv Domain id=1 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) 2016-10-07T14:05:02.215662Z qemu-system-x86_64: -device vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: error opening /dev/vfio/16: Operation not permitted 2016-10-07T14:05:02.215685Z qemu-system-x86_64: -device vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to get group 16 2016-10-07T14:05:02.215690Z qemu-system-x86_64: -device vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: Device initialization failed 2016-10-07 14:05:02.481+0000: shutting down 2016-10-07 14:07:02.947+0000: starting up libvirt version: 1.3.1, qemu version: 2.5.1, hostname: Tower Domain id=2 is tainted: high-privileges Domain id=2 is tainted: custom-argv Domain id=2 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) 2016-10-07T14:07:03.762923Z qemu-system-x86_64: -device vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: error opening /dev/vfio/16: Operation not permitted 2016-10-07T14:07:03.762947Z qemu-system-x86_64: -device vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: vfio: failed to get group 16 2016-10-07T14:07:03.762952Z qemu-system-x86_64: -device vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: Device initialization failed 2016-10-07 14:07:04.033+0000: shutting down
I believe it is erroring out on my Video Card, but really have no idea what to change to make it work. Worked fine in all 6.2 and lower versions, and now doesn't. Odd.
I have reverted back to 6.2 and the issue remains. I will create another post in the main help section now.
-
This docker reads your metadata.db which is the Calibre database, regardless of whether Calibre is running or not. You do need to create the database with Calibre and still add books via Calibre, this is just a very lightweight way of serving the content, far lighter than Calibre running it's OPDS server.
This line should be added to the docker description
I think the readme on github makes it pretty clear tbh...
It wasn't clear to me, which is why I asked the question. I believe your answer sums up the use of this docker very very well. I will be now implementing this for sure!
-
Map /books to the location of your Calibre metadata.db
Sorry, I realized I kind of hijacked this thread.
I was actually asking hernandito in regards to the rdp-calibre setup he posted and was referring to the native content server that comes with Calibre. Oh my bad, sorry, carry on...
Although the whole point of this container is you don't need to bother running the Calibre OPDS server anymore. So the Calibre RDP container can be stopped when you're not using the webui.
I thought I understood this docker, however your line above confuses me. Do I need to use Calibre RDP along with this Docker or just use this docker for everything?
-
Host path 1 (from looking at the container Path that displays on it) is the /config folder, and would get mounted to something like /mnt/cache/appdata/calibre
Path 2 Is presumably a path to where your library is / will be stored
Thanks...I have trialed and error it and figured it out. Working on adding my library now.
-
Great, very useful your answers! Any opinions regarding whether I should go for:
Intel Xeon E3-1275 v5 @ 3.60GHz, passmark 10,256
or
Intel Core i7-6700 @ 3.40GHz, passmark 9,965
?
Leaning towards the Xeon, but not sure..
Gesendet von iPhone mit Tapatalk
The Xeon should be better suited for all the VMing you are looking to do but I don't have real word experience so it is just an educated guess.
-
Thanks! Quick questions:
- What GPU did you go for? Can't find it in your parts list.
- Any experience running both media/games and a Windows/MacOS VM simultaneously? I understand I need 4 cores for gaming, so considering a 6-8 cores CPU just in case I want to run both simultaneously (i.e. playing a game on the plasma while doing work on another monitor). On the other hand, as this won't happen often, could save some money.
On a more general note:
- i7 vs. Xeon: Any thoughts?
- How many cores, mHz, and RAM do I need for what I want to do?
Gesendet von iPhone mit Tapatalk
My bad, video card is ASUS GeForce GTX 970 Turbo. I added it to the original post
Xeon is more designed for the application that I am doing, but I got a great deal on the I7 from a private seller so went that route for the price. It also fit in the motherboard that I had so I didn't need to dish out more money on a new Mobo. If you can afford a Xeon and have the parts then have at it.
I have doing gaming and had other VM's/Dockers running. The only time I experienced and issue is before I had all my CPU pinning set up and under control. I now CPU Pin all my dockers to CPU 0 and send the remaining 7 to my VM's. Never had a performance issue again once I set that up. I also make sure that Docker app data is on the user share and the VM images are on the SSD cache shares.
You "should" have no problem running VM's simultaneously.
-
Actually, this *could* possibly be related to your other issue (which I've posted separately about). Unlikely since presumably you are getting 20% of new downloads properly, but anything's possible.Since I have upgraded to unRAID 6.2 I am having an 80%+ failure rate (Repair failed, not enough repair blocks (XXX short)) downloading nzbs now. Anyone else experiencing an issue?
BTW, what is your general Geographical location? Middle East?
I am in Canada, but testing some things. Will come back shortly with the results. I have two NZB providers, thinking on my be not working right. Testing the other right now as it seams the 20% working are all from the other provider.
EDIT - OK seems to be one provider works fine and another doesn't at all.
-
Since I have upgraded to unRAID 6.2 I am having an 80%+ failure rate (Repair failed, not enough repair blocks (XXX short)) downloading nzbs now. Anyone else experiencing an issue?
-
Hi there, I am trying to readd my Plex docker and I am receiving the following error wile trying to readd it.
Pulling image: needo/plex:latest TOTAL DATA PULLED: 0 B Command: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="PlexMediaServer" --net="host" --privileged="true" -e TZ="America/New_York" -e HOST_OS="unRAID" -v "/mnt/user/Kids Movies/":"/kidsmovies":rw -v "/mnt/user/appdata/plexmediaserver":"/config":rw -v "/mnt/user/TV Shows/":"/TV Shows":rw -v "/mnt/user/Movies/":"/Movies":rw -v "/mnt/user/Kids Shows/":"/kidsshows":rw -v "/mnt/user/Music/":"/music":rw --memory=8GB --cpuset-cpus="0" needo/plex Unable to find image 'needo/plex:latest' locally docker: Error response from daemon: Get https://registry-1.docker.io/v2/needo/plex/manifests/latest: Received unexpected HTTP status: 500 Server Error. See '/usr/bin/docker run --help'. The command failed.
-
Upgrade to 6.2 Attempt number 2.
So I encountered the same issues so far in attempt number 2 (NIC getting reassigned, Docker going hair wire, VM's not starting).
I have reconfigured the network so that is fixed.
I have rebuilt all of docker however still have an issue with my Docker Versions not acting right. Some of my dockers say "update ready", one says "up to date" and all the rest say "not available". I have clicked "update" on all of them and the issue remains. The one that says "update ready" finishes with "The command finished successfully!" however the message never goes away. The ones that say "not available" are not changing status no matter what I do.
Any advice on the docker issue?
That sounds like what several users found, lots of upgrade notices for dockers but upgrades didn't work. I believe they all found that the same fix took care of it, deleting the docker.img (through the Docker settings page), recreating it, and adding back your containers through the Community Apps Previous Apps or through My Templates(?).
Squid: made the change.
I have already done these steps twice, how many times should I be repeating them?
Any advice for my docker issues?
-
For those of you having issues with networking, Docker updates, VMs not seeing the network, etc. Please go through the following steps to see if it helps. The reason for this is that unRAID needs to have a bridge called br0 for VMs and some changes may have renamed your NICs. There are several things to do to set up the bridge and make it work.
- Go to 'Settings->Network Settings' and be sure 'Enable Bridging:' is set to yes. If you have multiple NICs that are bonded, don't set any bonding mode other than active backup for now. Setting this to other modes can cause issues. You can come back later and tune this up after you get other settings made and the system is running correctly. Don't set up any VLANs at this time. Verify IP address and default gateway settings. If the settings already look correct, make a change then set it back and click 'Apply' to re-save them.
- Go to 'Settings->VM Settings' and select br0 as the 'Default Network Bridge'.
- Edit each VM and be sure that the 'Network Bridge:' is set to br0.
When updating from 6.1 there were some significant improvements to the networking and these manual settings have to be made for the new networking to work properly.
In the older versions of unRAID, the user created and named a bridge. That no longer applies. Back in the Xen VM days we all had a bridge we called Xenbr0. That no longer works and these steps have to be made to update the bridge.
If you have multiple NICS and don't bond them, you will need to verify that eth0 is the same NIC as before. Linux may be renaming the NICs so eth0 is not the NIC you think it is. If you have multiple NICS I recommend that you bond them.
If none of this works and you are still having issues, remove all plugins and reboot. Then install plugins one at a time and see if they affect the network. Some plugins have been reported as causing network issues. The best way to do this is to remove the plugins one at a time and then use CA to restore them using the 'Previous Apps' button.
If you are still having issues, reboot in safe mode, capture diagnostics and post them here.
Thank you very much for this. This has fixed my issue with my VM. I believe a walk-though should be created for this upgrade truthfully, step by step. For complex setups (Dockers, Plugins, VMs, Large arrays, multiple NICs, etc), there are far too many things that have to be done in order to upgrade properly. Especially since I have had to edit my VM XML manually at least four times. Using the GUI to edit the xml results in severe performance degradation of the VM.
It is not as easy as pressing a button in the Gui.
The network changes from 6.1.9 to 6.2 were pretty significant. Unfortunately upgrading to 6.2 was not just a button press to upgrade.
Which part of the procedure fixed your problem?
swapping my source element in the interface part of the XML to <source bridge='br0'/>. The bridge was not setup correctly.
-
For those of you having issues with networking, Docker updates, VMs not seeing the network, etc. Please go through the following steps to see if it helps. The reason for this is that unRAID needs to have a bridge called br0 for VMs and some changes may have renamed your NICs. There are several things to do to set up the bridge and make it work.
- Go to 'Settings->Network Settings' and be sure 'Enable Bridging:' is set to yes. If you have multiple NICs that are bonded, don't set any bonding mode other than active backup for now. Setting this to other modes can cause issues. You can come back later and tune this up after you get other settings made and the system is running correctly. Don't set up any VLANs at this time. Verify IP address and default gateway settings. If the settings already look correct, make a change then set it back and click 'Apply' to re-save them.
- Go to 'Settings->VM Settings' and select br0 as the 'Default Network Bridge'.
- Edit each VM and be sure that the 'Network Bridge:' is set to br0.
When updating from 6.1 there were some significant improvements to the networking and these manual settings have to be made for the new networking to work properly.
In the older versions of unRAID, the user created and named a bridge. That no longer applies. Back in the Xen VM days we all had a bridge we called Xenbr0. That no longer works and these steps have to be made to update the bridge.
If you have multiple NICS and don't bond them, you will need to verify that eth0 is the same NIC as before. Linux may be renaming the NICs so eth0 is not the NIC you think it is. If you have multiple NICS I recommend that you bond them.
If none of this works and you are still having issues, remove all plugins and reboot. Then install plugins one at a time and see if they affect the network. Some plugins have been reported as causing network issues. The best way to do this is to remove the plugins one at a time and then use CA to restore them using the 'Previous Apps' button.
If you are still having issues, reboot in safe mode, capture diagnostics and post them here.
Thank you very much for this. This has fixed my issue with my VM. I believe a walk-though should be created for this upgrade truthfully, step by step. For complex setups (Dockers, Plugins, VMs, Large arrays, multiple NICs, etc), there are far too many things that have to be done in order to upgrade properly. Especially since I have had to edit my VM XML manually at least four times. Using the GUI to edit the xml results in severe performance degradation of the VM.
It is not as easy as pressing a button in the Gui.
-
I am trying to install your Calibre Docker, but unsure what to fill in for Host Path 1 and Host Path 2.
-
Upgrade to 6.2 Attempt number 2.
So I encountered the same issues so far in attempt number 2 (NIC getting reassigned, Docker going hair wire, VM's not starting).
I have reconfigured the network so that is fixed.
I have rebuilt all of docker however still have an issue with my Docker Versions not acting right. Some of my dockers say "update ready", one says "up to date" and all the rest say "not available". I have clicked "update" on all of them and the issue remains. The one that says "update ready" finishes with "The command finished successfully!" however the message never goes away. The ones that say "not available" are not changing status no matter what I do.
Any advice on the docker issue?
My Win 10 VM is also still pooched. It won't start, giving the error code "Cannot get interface MTU on 'xenbr0': No such device"
You need to set the VM settings to default to br0 interface, and then change your VM to br0 interface. There is no more xenbr0.
I solved the issue by the method above, but guess that this caused some sort of issue because network issues are occurring.
DNS for local computers on my network is not working. Prior to the upgrade I could rung "ping htpc" and it would work just fine, post upgrade I get the error that the host cannot be resolved.
I cannot access any shares from the Windows VM. When trying to access them an authentication box pops up asking for a username and password.
Shares do work from other PC's on the network so this definitely a VM specific issue I think.
Your network on the VM may have defaulted to Public. Check to see that it is not set to a Public network.
There's also a Windows advanced sharing setting for password protected sharing. Be sure it is not password protected.
I thought this as well and already confirmed that I am on a Private Network setting in Windows for this network. Also no password protection going on. Literally worked before the 6.2 reboot and then after coming up it does not.
-
Upgrade to 6.2 Attempt number 2.
So I encountered the same issues so far in attempt number 2 (NIC getting reassigned, Docker going hair wire, VM's not starting).
I have reconfigured the network so that is fixed.
I have rebuilt all of docker however still have an issue with my Docker Versions not acting right. Some of my dockers say "update ready", one says "up to date" and all the rest say "not available". I have clicked "update" on all of them and the issue remains. The one that says "update ready" finishes with "The command finished successfully!" however the message never goes away. The ones that say "not available" are not changing status no matter what I do.
Any advice on the docker issue?
That sounds like what several users found, lots of upgrade notices for dockers but upgrades didn't work. I believe they all found that the same fix took care of it, deleting the docker.img (through the Docker settings page), recreating it, and adding back your containers through the Community Apps Previous Apps or through My Templates(?).
Squid: made the change.
I have already done these steps twice, how many times should I be repeating them?
Win 10 VM Will no Longer Start
in VM Engine (KVM)
Posted
Yes your guess is correct. I did not see that part in the announcement nor did I do that Save process. I expressed my displeasure about the update process in another thread and this process reiterates that. I did the upgrade from the Add On page and there was no mention of reading the announcement nor having to do anything more then simply "REBOOT REQUIRED". The upgrade process should either be taken out of the Add On section OR that section be amped up considerably to provide a lot more information on what to do with an update.
Just two cents from a frustrated two pro license customer!