-
Posts
15,089 -
Joined
-
Days Won
193
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Report Comments posted by ich777
-
-
56 minutes ago, Ralf. said:
I am not 100% sure if my problem is related to the one above,
but I have several VMs that use a pass through unassigned device as main disk. Since Beta 29 non of them boots anymore with the following error (example):
Execution error
Unable to get devmapper targets for /dev/sdh: No such file or directory
In the LIBVIRT log, I got the following entries:
2020-09-29 09:29:24.847+0000: 6045: error : virDevMapperOnceInit:78 : internal error: Unable to find major for device-mapper
2020-09-29 09:29:24.847+0000: 6045: error : qemuSetupImagePathCgroup:91 : Unable to get devmapper targets for /dev/sdh: Success
2020-09-29 09:45:55.392+0000: 6048: warning : qemuDomainObjTaint:5983 : Domain id=2 name='Windows 10' uuid=e2a7c568-efce-61c9-a7ad-789c710201fc is tainted: high-privileges
2020-09-29 09:45:55.392+0000: 6048: warning : qemuDomainObjTaint:5983 : Domain id=2 name='Windows 10' uuid=e2a7c568-efce-61c9-a7ad-789c710201fc is tainted: host-cpu
2020-09-29 09:45:55.408+0000: 6048: error : qemuSetupImagePathCgroup:91 : Unable to get devmapper targets for /dev/sdh: No such file or directoryAny idea to what this problem is related or how it can be solved? Maybe with the next beta?
Same here, even if you bind it via /dev/disk/by-id/
@Ralf. You should definitely bind it via /dev/disk/by-id/ sometimes the drives can change with sda or sde or something.
-
@fmp4m what firmware is the card?
If you need the flash tool for unraid or how to read the firmware version, feel free to contact me.
I can create you a unraid version with the Mellanox Firmware Tools builtin.
-
No problem here with my Mellanox ConnectX-2 MNPA19-XTR on an ASUS Z9PA-D8 with one Intel Xeon 2670 on Unraid v6.9.0beta24
-
23 minutes ago, david279 said:
I should look like that.
Thank you will try that
EDIT: Thank you @david279 that seems to solve the problem
-
7 minutes ago, david279 said:
You have any VMs using virtio for the network bridge? Change the network from virtio to virtio-net.
I use 'br0' for all my VM's and half of my Docker Containers.
-
Today I noticed that my log directory is full, I've saw that my log is spammed with GSO errors looks like this:
Jun 21 07:21:33 chipsServer kernel: tun: unexpected GSO type: 0x0, gso_size 31, hdr_len 66 Jun 21 07:21:33 chipsServer kernel: tun: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ Jun 21 07:21:33 chipsServer kernel: tun: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ Jun 21 07:21:33 chipsServer kernel: tun: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ Jun 21 07:21:33 chipsServer kernel: tun: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ Jun 21 07:21:33 chipsServer kernel: tun: unexpected GSO type: 0x0, gso_size 31, hdr_len 66 Jun 21 07:21:33 chipsServer kernel: tun: 40 b7 92 0b 00 ea ff ff 00 10 00 00 00 00 00 00 @............... Jun 21 07:21:33 chipsServer kernel: tun: c0 6d 79 17 00 ea ff ff 00 10 00 00 00 00 00 00 .my............. Jun 21 07:21:33 chipsServer kernel: tun: 80 43 50 1e 00 ea ff ff 00 10 00 00 00 00 00 00 .CP............. Jun 21 07:21:33 chipsServer kernel: tun: 00 e0 44 1b 00 ea ff ff 00 10 00 00 00 00 00 00 ..D............. Jun 21 07:21:33 chipsServer kernel: tun: unexpected GSO type: 0x0, gso_size 39, hdr_len 66 Jun 21 07:21:33 chipsServer kernel: tun: 00 5a ee 01 00 ea ff ff 00 00 00 00 00 80 00 00 .Z.............. Jun 21 07:21:33 chipsServer kernel: tun: 00 60 0a a8 00 00 00 00 00 80 00 00 00 00 00 00 .`.............. Jun 21 07:21:33 chipsServer kernel: tun: 80 e7 d0 01 00 ea ff ff 00 00 00 00 00 20 00 00 ............. .. Jun 21 07:21:33 chipsServer kernel: tun: 00 e0 0a a8 00 00 00 00 00 20 00 00 00 00 00 00 ......... ...... Jun 21 07:21:37 chipsServer kernel: tun: unexpected GSO type: 0x0, gso_size 31, hdr_len 66 Jun 21 07:21:37 chipsServer kernel: tun: 00 08 ed 13 00 ea ff ff 00 10 00 00 00 00 00 00 ................ Jun 21 07:21:37 chipsServer kernel: tun: c0 77 ab 1c 00 ea ff ff 00 10 00 00 00 00 00 00 .w.............. Jun 21 07:21:37 chipsServer kernel: tun: c0 e4 d2 09 00 ea ff ff 00 10 00 00 00 00 00 00 ................ Jun 21 07:21:37 chipsServer kernel: tun: 80 3c c7 12 00 ea ff ff 00 10 00 00 00 00 00 00 .<.............. Jun 21 07:21:37 chipsServer kernel: tun: unexpected GSO type: 0x0, gso_size 31, hdr_len 66 Jun 21 07:21:37 chipsServer kernel: tun: c0 d6 4e 0e 00 ea ff ff 00 10 00 00 00 00 00 00 ..N............. Jun 21 07:21:37 chipsServer kernel: tun: c0 2e 67 16 00 ea ff ff 00 10 00 00 00 00 00 00 ..g............. Jun 21 07:21:37 chipsServer kernel: tun: 40 75 89 1e 00 ea ff ff 00 10 00 00 00 00 00 00 @u.............. Jun 21 07:21:37 chipsServer kernel: tun: c0 69 39 0f 00 ea ff ff 00 10 00 00 00 00 00 00 .i9............. Jun 21 07:21:37 chipsServer kernel: tun: unexpected GSO type: 0x0, gso_size 39, hdr_len 66 Jun 21 07:21:37 chipsServer kernel: tun: 00 03 18 1c 00 ea ff ff 00 00 00 00 00 10 00 00 ................ Jun 21 07:21:37 chipsServer kernel: tun: 00 50 c6 a6 00 00 00 00 00 10 00 00 00 00 00 00 .P.............. Jun 21 07:21:37 chipsServer kernel: tun: 80 d9 87 08 00 ea ff ff 00 00 00 00 00 10 00 00 ................ Jun 21 07:21:37 chipsServer kernel: tun: 00 60 c6 a6 00 00 00 00 00 10 00 00 00 00 00 00 .`.............. Jun 21 07:21:55 chipsServer kernel: tun: unexpected GSO type: 0x0, gso_size 39, hdr_len 66 Jun 21 07:21:55 chipsServer kernel: tun: 65 3a 38 31 20 66 5f 68 61 6e 64 6c 65 3a 64 34 e:81 f_handle:d4 Jun 21 07:21:55 chipsServer kernel: tun: 39 34 33 39 31 64 30 30 30 30 30 30 30 30 66 62 94391d00000000fb Jun 21 07:21:55 chipsServer kernel: tun: 64 31 35 34 37 36 0a 69 6e 6f 74 69 66 79 20 77 d15476.inotify w Jun 21 07:21:55 chipsServer kernel: tun: 64 3a 34 61 61 35 20 69 6e 6f 3a 31 61 34 39 63 d:4aa5 ino:1a49c
Can somebody help?
I'm on the latest unRaid 6.9.0beta22 and use a Mellanox ConnectX-2 Single Port 10GbE SFP+ MNPA19-XTR Card with a 10Gbit SFP+ Module
-
Changed Status to Solved
-
Actually the error was that i had a path like /mnt/user/... the path like you suggested /mnt/cache/... changes everything and it works now.
Thank you!
Unraid OS version 6.9.0-beta29 available
-
-
-
-
-
in Prereleases
Posted
Getting this error when I passthrough a whole device to a VM:
2020-09-29 13:09:01.351+0000: 7249: info : libvirt version: 6.6.0 2020-09-29 13:09:01.351+0000: 7249: info : hostname: chipsServer 2020-09-29 13:09:01.351+0000: 7249: warning : qemuDomainObjTaint:5983 : Domain id=1 name='Debian' uuid=dc6cf767-855b-f071-bfd7-d915e74a61e9 is tainted: high-privileges 2020-09-29 13:09:01.351+0000: 7249: warning : qemuDomainObjTaint:5983 : Domain id=1 name='Debian' uuid=dc6cf767-855b-f071-bfd7-d915e74a61e9 is tainted: host-cpu 2020-09-29 13:09:01.371+0000: 7249: error : virDevMapperOnceInit:78 : internal error: Unable to find major for device-mapper 2020-09-29 13:09:01.371+0000: 7249: error : qemuSetupImagePathCgroup:91 : Unable to get devmapper targets for /dev/disk/by-id/ata-WDC_WD5000AZLX-60K2TA0_WD-WCC6Z4DKE5L5: Success 2020-09-29 13:09:01.615+0000: 7249: error : qemuAutostartDomain:219 : internal error: Failed to autostart VM 'Debian': Unable to get devmapper targets for /dev/disk/by-id/ata-WDC_WD5000AZLX-60K2TA0_WD-WCC6Z4DKE5L5: Success
Seems like this issue isn't resolved with Libvirt 6.6.0 and CVE-2020-14339 applied.
Will try to compile libvirt 6.7.0 if I got time but I'm on vacation now and don't have much time for this...