Mirano

Does this mean I can uninstall the plugin and start using it natively? Since i'm able to VF it here.

Update, I made a new VM and if i boot it up, first connect to RDP, delete the code 43 driver, wait 5 minutes then connect with Parsec it's got a working driver. Really strange tho.

Hey, so i've had this running for quite a while, but i restarted my VM today and it just stops working, it gives Code 43 and the following in the VM Log: char device redirected to /dev/pts/3 (label charserial0) 2025-07-22T15:22:50.062308Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument 2025-07-22T15:22:50.062353Z qemu-system-x86_64: vfio_container_dma_map(0x5606a2d63de0, 0x382800000000, 0x20000000, 0x154100000000) = -2 (No such file or directory) 2025-07-22T15:22:50.140639Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument 2025-07-22T15:22:50.140658Z qemu-system-x86_64: vfio_container_dma_map(0x5606a2d63de0, 0x382800000000, 0x20000000, 0x154100000000) = -22 (Invalid argument) 2025-07-22T15:22:54.230866Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument 2025-07-22T15:22:54.230889Z qemu-system-x86_64: vfio_container_dma_map(0x5606a2d63de0, 0x382800000000, 0x20000000, 0x154100000000) = -22 (Invalid argument) 2025-07-22T15:22:54.293984Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument 2025-07-22T15:22:54.294013Z qemu-system-x86_64: vfio_container_dma_map(0x5606a2d63de0, 0x382800000000, 0x20000000, 0x154100000000) = -22 (Invalid argument) 2025-07-22T15:22:54.443558Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument 2025-07-22T15:22:54.443582Z qemu-system-x86_64: vfio_container_dma_map(0x5606a2d63de0, 0x382800000000, 0x20000000, 0x154100000000) = -22 (Invalid argument) 2025-07-22T15:22:54.464231Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument 2025-07-22T15:22:54.464257Z qemu-system-x86_64: vfio_container_dma_map(0x5606a2d63de0, 0x382800000000, 0x20000000, 0x154100000000) = -22 (Invalid argument) 2025-07-22T15:22:58.141018Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument 2025-07-22T15:22:58.141040Z qemu-system-x86_64: vfio_container_dma_map(0x5606a2d63de0, 0x382800000000, 0x20000000, 0x154100000000) = -22 (Invalid argument) This issue seem to be common, so i checked all the steps i could find: Reboot of VM Reboot of Server Reassigned VFIO from 3 to 2 Tried VFIO booting, but that wasn't recommended and or working Assigned .bin for BIOS Uninstalled plugin > Reboot > Installed plugin Tried making new VM config Tried different versions of Intel drivers > All of them give code 43 I'm quite out of options, anyone else have ideas?

Thank you, this worked perfectly

No worries, thank you for responding! :)

@ich777 Have you had any chance to take a look into the issue, or require more information from me perhaps?

Alright that's clear now, is there a preference based on speed? Or is it similar enough that both will provide the same speed? (10GBe network)

Hey! to add to this, it seems like I cannot switch to IPVlan if Bridging is disabled, is that true?

Hey Ich777. It seems like, update 7.1.2 has broken the Virtual GPU for my VM. i've tried every step under troubleshooting but it gives code 45 (Not connected). Is the update working for you? Tried the following: Changing Modes within the plugin New VM Reinstalling Plugin (including restarts) Server reboots Unfortunately no luck yet

ah perfect, Thank you for the explanation, its currently rebuilding every container:

Btw, have you ever used this? Sounds like the only reason to use it you have a VM with a firewall on it to get DHCP working,

Yeah I got enough ports to connect it to their own ports, its stated weird in the description of the function then, it sounds like it creates a virtual network to get docker and vms connected to the port. Hence why I always used it. so replicate my test environment to production and that’s totally fine, correct?

Hey, That makes alot more sense. So what i could do with bridging is setup: ETH0 receives DHCP from my UDM Pro. ETH0 got bridge enabled and if i include ETH1 into it i can hook my PC to ETH1 so it receives an DHCP through the unraid server to the UDM Pro. Is what i'm saying correct?

Hey, Thank you for taking the time to answer to me. I understand the concept or a Bonding, to combine multiple physical adapters to get either more throughput or redundancy. I just don't understand the function of the Bridging function. I'm still confused by that, but that could just be me haha.

Hello, I have a question regarding setups With bridging / macvlan and ipvlan I've recently switched backed to macvlan so each docker is shown in the unifi ui, now i came to some questions: My production server is running the following: Network settings: ETH0 Enable bonding no Enable Bridging: yes Bridging members of br0: eth0 Docker: Docker custom network type: macvlan Host access to custom networks: enabled My test server is running: ETH0 Enable bonding no Enable Bridging: no Docker: Docker custom network type: macvlan Host access to custom networks: enabled Both seem to function exactly the same. other than i have for my dockers on production br0.10 and on my test server eth0.10 What is the benefit of running "Enable Bridging: yes"? It seems like it's got no function, or none that i'm seeing. The function description: "Bridging is a feature which creates a virtual bridge and allows VMs and Docker containers to communicate directly with the physical Ethernet port. Both bonding and bridging can be combined to let VMs or containers communicate over a bonded interface." The "strange" thing is that on both setups it seems to work, so it only looks like bridging adds another layer of networking to handle. Can anyone advise me on the differences and best practices?

Gave it more power (Unrestricted it) and it goes blazing

Looks like that's giving me more performance: I also have the Minisforum i9 variant, but power limited to 40 watts. so that isn't really beneficial either i think to the drive speeds

Ever figured it out? My raidz1 is stuck on 1gb/s as well..

I am using a Minisforum MS-01

Hey, So i have the following configuration running: Running 3 Samsung 980 in a ZFS RaidZ1. I'm getting really bad internal Speeds: What could cause this to run really slowly, the drives are rated for at least 3/3 GB/s of read and write, yet im getting 1/3 with a Raidz1

Hey everyone! So it all worked out quite well. (other than accidently deleting a database). I've got one question remaining: I currently have the following: the pool with 1 disk is called; "extra" the pool with 3 disks is called: "main" which is a raidz1 I'm goign to move the data back to the main pool and remove the 1TB nvme from the system. Here's my problem. i went over to my test server and tried to emulate it: on my test server i have 2 pools: When i do "New Config" under tools and i tell it to preserve the full layout: Going back to the main page i can see that the pools stay there and i can remove the one i wanted gone: What i've noticed which is my question: the File system went from "ZFS" to "AUTO". My question: What happens if i do that with my Raidz1 array on my production machine, would i need to place the disks in the same pattern as now and set it to Raidz1 again and it will just work? tldr: When doing new config and retaining pool devices it doesn't keep the config set to make it RaidZ1 and instead resets to "auto"

Hey. Looking back it indeed sounds a bit weird. What i do is the following. i have a share called "Appdata" i currently have my 2 disks with BTRFS on that share with no secundairy storage. What my plan is to: 1. Assign the temp storage as a 1st storage and the btrfs disks as secundairy 1. Stop the docker container 2. Move the files from the docker to the temp storage 3. Since all connections are still to "/mnt/user/Appdata/* it should all still work. 4. Start the docker When looking at your command you would've moved it to a unassigned disk: 1. Assign temp storage to unassigned disk 2. Stop docker container 3. Move the files to the unassigned disk on "/mnt/disks/*" 4. Change the storage paths to the unassigned disk on "/mnt/disks/*" 5. Start the docker Could you, perhaps shed some light on which you would choose and why?

Good shot! I will try that. I first had to figure out how to create the virtual share on the new datashare haha Edit 1: i just tried that, but it cannot find a difference between the 2 shares, it only finds the shares not the disks its on

Hey. I've just tried this but i can only seem to copy, and not move the files. or am i mistaken?

Hey, So the moment was there when i wanted to move files to a temp SSD which was USB mounted (T7 Samsung). I decided to use Unblanace and quite fast found out that this is not smart method as it threw me around 300.000 + permission errors. PEople told me to nuke permissions but i don't think that's a smart option since many dockers require their respective permissions. What would you advice on be the smartest way to transfer it? i thought about doing each folder with 'mv' but i'm not sure if that's the smartest move. Edit 1: Since i have only 3 slots for nvme, i've just purchased a PCIE to NVME adapter so i can put the 4th NVME it so i can transfer it to a internal NVME instead of external SSD. Question still remains.