[bzimage checksum error]

I too can confirm that this fixed my issue when updating from 6.9 to .10

 

mellanox give an explanation on what they do. If anything it’s a performance boost

[Reset Network to default]

11 minutes ago, yogy said:

I'm gonna ask here since search on the forum didn't bring anything related to my question. I'm on v6.9.1 stable

 

Is it still the correct way to reset pci network card and add this command "vfio-pci.ids=8086:105e" to syslinux config file and then reboot the server so changes can take effect.

 

This is the network card with 2 eth NICs

IOMMU group 47:[8086:105e] 01:00.0 Ethernet controller: Intel Corporation 82571EB/82571GB Gigabit Ethernet Controller D0/D1 (copper applications) (rev 06)

IOMMU group 48:[8086:105e] 01:00.1 Ethernet controller: Intel Corporation 82571EB/82571GB Gigabit Ethernet Controller D0/D1 (copper applications) (rev 06)

They are both market as "currently in use by Unraid" and I cannot BIND SELECTED TO VFIO AT BOOT. 

 

I would like to use this network card assigned to VM passthrough. If my assumption is correct, does this command need to stay in syslinux config permanently.

just connect to it via a network bridge, any particular reason needing iit as a direct passthrough

[How to Set Up a Multi-Streaming Server with Unraid]

what if you have more than one pc to stream? as in two gamers streaming at the same time. would you need to duplicate the container after setup and point each individually or can you have both stream to the same container?

[Unable to use dockers on any other ip than host]

As the title says i cant use any docker other that when the network is set to host or bridge. They boot up fine and can be viewed from local but can't connect to external web ie sonarr app loads but can't search unless set to host/bridge

 

its been fine for 9 months then i've had to rebuild unraid due to a failed shutdown destroying the boot drive.

diagnostics attached

diagnostics-20200324-1358.zip

[[Support] SpaceinvaderOne - Macinabox]

23 hours ago, ghost82 said:

It means your processor doesn't support that args, so you can delete them from the vm xml (xsave, avx, xsaveopt): I don't know if that args have important impacts on your vm; anyway these are "warnings", so if your vm performs well, you can delete them, as I explained, from the xml, your vm will run the same as now and the warnings will disappear.

Ah thanks! It seems to be performing better now without the arguments present.

but now looks like i had other error messages
 

2019-11-01 11:13:12.191+0000: Domain id=3 is tainted: high-privileges
2019-11-01 11:13:12.191+0000: Domain id=3 is tainted: custom-argv
2019-11-01 11:13:12.191+0000: Domain id=3 is tainted: host-cpu
char device redirected to /dev/pts/0 (label charserial0)
usb_desc_get_descriptor: 1 unknown type 33 (len 10)
usb_desc_get_descriptor: 1 unknown type 33 (len 10)

think this might be do do with bios settings on the r710 from what google said,
 

Quote

enter the BIOS setup and enable "SR_IOV Global Enable" option under "Integrated Devices".

thaqnks for the help

[[Support] SpaceinvaderOne - Macinabox]

so im getting this in the logs;

2019-10-31T08:31:03.341240Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.xsave [bit 26]
2019-10-31T08:31:03.341255Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.avx [bit 28]
2019-10-31T08:31:03.341263Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.0DH:EAX.xsaveopt [bit 0]
2019-10-31T08:31:03.341270Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.0DH:EAX [bit 0]
2019-10-31T08:31:03.341277Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.0DH:EAX [bit 1]
2019-10-31T08:31:03.341284Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.0DH:EAX [bit 2]

My system is an dell r710 with dual x5670 and 72gb ram