Bobo_unraid

Members
  • Posts

    6
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Bobo_unraid's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Nice to have stomped upon this post as I’m in the pretty much same. I had tried proxmox and I don’t like it either. Underneath proxmox is kvm, which would be the same as unraid is using, I don’t mind doing it using the cli as I have tried that in proxmox earlier, but the steps is in fact the same. I still need the vbios, blacklist the device etc. but I don’t see a point here as this is basically same with unraid with some clustering feature added on. Xcp ng on the other hand is interesting as it uses the Xen to virtulise vms. But it would require conversion of vdisk and some additional steps to make the vm work, reformatting drive and install new os takes a long time and with the limited amount of time. We all have to think about more efficient ways. What I did is I passed a ssd using unassigned devices to a vm, and install xcp ng directly into that ssd. Therefore if anything goes wrong, I can easily go back to unraid. I really like xcpng but my current problem is to convert my vms(windows,truenas) to a vdisk format that xcpng uses. Looking at xcpng documentation suggest I have a use a tool called Dracut and do something with the image file, but I’m kinda struck here. Or I could just convert using qemu-Img to convert and see what happens. But again, lack of time here. my current setup now is I have a truenas vm set up and I put all my spinning drives into that vm. Then I’ve set up iscsi from truenas for be used for windows vm. the performance is great and zfs is just a hack of a file system. Unraid no longer manges my hard drive except for some nvme ssd and sata ssd for vm. I don’t have many hdds but it seems to be the biggest problem is that unraid reads data from the array one disk at a time and it’s kinda slow. Also I don’t like the parity checking which takes 7 hours for me. I can maybe secdule the parity check less often but I kinda wanna the assurance that my data is safe. and with the rising energy price I have to think about the what I need to use my server for as well. As it doesn’t make sense to have an file server with some docker containers on24/7. So I used a raspberry pi4 and installed open media vault and portainer on it. Which I migrated all my docker containers over, I have a donwloder, pi hole, adgarud home, UniFi controller, unbound dns, home assistant working with a 1tb usb drive for temporary storage and its amazing how well it runs and how little power it uses. I hope my setup could give you some ideas about what you want to do with you server.
  2. thank you again for this guide and its really helpful. I have the following situation that I can't get my head around. I hope you can share some guidance on it. I have 2 NICs in the system. one realtek 2.5Ghz nic and the Intel X550-T2 10Ghz nic witch is providing VFs. I have a truenas VM using 1 vf produced by the X550-T2. devices that is plug into the X550 parent PF can access to Truenas server no problem. but I kinda need to use the other realtek nic port because it has WOL capability. now if I plug the realtek nic to the main switch, other devices connected to the main switch can no longer access the Truenas VM. I have bridged the realtek nic and the parent PF in Unraid's webUI. but that does not grant access to the Truenas using VF. Now, how do I access the VF from other nic in the computer, or is it simply impossible? Can I plug both the realtek Nic and the X550 nic to the same main switch? do the VFs created by the same parent PF share network(2vfs, one for the truenas VM and one not bond and bridged it in the unraid)? I have searched online but this seems to be a difficult find.
  3. Currently, I'm surprised to find that the 9p driver for native file sharing works, I almost through there is a specific diver for folder sharing. One problem is really bugging me and I feel like this is simple question but the amount of time it make me to ban my head is getting too much. So I'm gonna ask here. Right now I have an opnsense vm using vf 0, instead of using virtio-net following this guide and making it work. everything works except that my pi-hole docker container cannot ping opnsense at 10.0.0.1. the pi-hole container is set-up using docker custom (bro). this is not an issue when using virtio-net. and all other container using custom network seems to be inaccessible. I googled around and come off this trust parameter with the command ip set link eth0 vf0 trust on However, this does not seem to work nor it stays over reboot, I wonder if you have encountered similar problems?
  4. Also, not too sure about the donwside of enabling this option. I tend to enable stuff as needed, less option enabled is less trouble for me. I think the script work only if you vf and phsical function are not in the same iommu group. my asus motherborad puts the vfs and pfs in the same group which was the problem. I'm not sure if this is the limation of the bind script but, looking at the author code descriton, it looks to me if all the vfs are in the same iommu group, by just supplying one of the vfs to the scipt, then scipt can just bind all(not sure). It seems to me that's what the author is excepting(maybe the default norm is pf in one group and vfs in another group). I wanted to modify the scipt to bind just the one specified and not include the devices in their iommu group, but my limited bash skill is just not letting me do that. I think, this might be a point to be added to your tutrial. looking at the iommu group of the machine and how it interacts with the pci-bind script.
  5. I got it. if i set to mutifunction+downstream. the vfs will be in their own group just as how you showed in your tutrioal. then it doesn't confict with the scipt. for anyone with the same problem. go to vm settings and set it to PCIe ACS override to both. this allows all the vfs to be in their own iommu group. don;t konw if this is needed or if someone can modifiy the scipt. but for now this works.
  6. Hi, thank you for a fantastic guide. I have been playing with it for some time and can't get it to work. I believe I have similiar problems with some of the people in this post. now let me decribe my setup and helpfully someone can point a light. -ASUS TUF GAMING B550M-PLUS bios Version 2604 -AMD Ryzen 7 5700G -32 gb cosair ram (3600mhz) -intel x550-t2 Before the nic shows up normally in system devices. both using the ixgbe driver Creating the VF was rather easy. whether editing the go file in method 1 or the echo method in option 2, they both work and I went with option 2 as its easier. sudo echo 4 > /sys/class/net/eth1/device/sriov_numvfs eth1 correspons to the 4:00.1 controller for the intel x550. eth0 is used for unarid. eth2 is the onboard 2.5g nic. After creating the vf, system device shows that VFs are created. run the bind scrip from the unraid command line. it shows that the scipt unbounds the physical device which should not happen. root@Tower:~# sudo bash /boot/config/vfio-pci-bind.sh 8086:1565 0000:05:10.1 Vendor:Device 8086:1565 found at 0000:05:10.1 IOMMU group members (sans bridges): /sys/bus/pci/devices/0000:05:10.1/iommu_group/devices/0000:04:00.0 /sys/bus/pci/devices/0000:05:10.1/iommu_group/devices/0000:04:00.1 /sys/bus/pci/devices/0000:05:10.1/iommu_group/devices/0000:05:10.1 /sys/bus/pci/devices/0000:05:10.1/iommu_group/devices/0000:05:10.3 /sys/bus/pci/devices/0000:05:10.1/iommu_group/devices/0000:05:10.5 /sys/bus/pci/devices/0000:05:10.1/iommu_group/devices/0000:05:10.7 Binding... Unbound 0000:04:00.0 from ixgbe Unbound 0000:04:00.1 from ixgbe /boot/config/vfio-pci-bind.sh: line 157: /sys/bus/pci/devices/0000:05:10.1/iommu_group/devices/0000:05:10.1/driver_override: No such file or directory /boot/config/vfio-pci-bind.sh: line 172: echo: write error: No such device /boot/config/vfio-pci-bind.sh: line 157: /sys/bus/pci/devices/0000:05:10.1/iommu_group/devices/0000:05:10.3/driver_override: No such file or directory /boot/config/vfio-pci-bind.sh: line 172: echo: write error: No such device /boot/config/vfio-pci-bind.sh: line 157: /sys/bus/pci/devices/0000:05:10.1/iommu_group/devices/0000:05:10.5/driver_override: No such file or directory /boot/config/vfio-pci-bind.sh: line 172: echo: write error: No such device /boot/config/vfio-pci-bind.sh: line 157: /sys/bus/pci/devices/0000:05:10.1/iommu_group/devices/0000:05:10.7/driver_override: No such file or directory /boot/config/vfio-pci-bind.sh: line 172: echo: write error: No such device success... Device 8086:1565 at 0000:05:10.1 bound to vfio-pci Devices listed in /sys/bus/pci/drivers/vfio-pci: lrwxrwxrwx 1 root root 0 Mar 30 11:08 0000:01:00.0 -> ../../../../devices/pci0000:00/0000:00:01.1/0000:01:00.0 lrwxrwxrwx 1 root root 0 Mar 30 11:08 0000:01:00.1 -> ../../../../devices/pci0000:00/0000:00:01.1/0000:01:00.1 lrwxrwxrwx 1 root root 0 Mar 30 11:08 0000:04:00.0 -> ../../../../devices/pci0000:00/0000:00:02.1/0000:02:00.2/0000:03:00.0/0000:04:00.0 lrwxrwxrwx 1 root root 0 Mar 30 11:08 0000:04:00.1 -> ../../../../devices/pci0000:00/0000:00:02.1/0000:02:00.2/0000:03:00.0/0000:04:00.1 ls -l /dev/vfio/ total 0 crw------- 1 root users 248, 1 Mar 30 10:52 10 crw------- 1 root root 248, 2 Mar 30 11:08 14 crw------- 1 root users 248, 0 Mar 30 10:52 9 crw-rw-rw- 1 root root 10, 196 Mar 30 10:52 vfio I think this is where the problem lies, when I run the bind script from andre-richter, it unbinds my phsical interface, then, as the phsical interface is being bound to vfio, the vf function I created just vanishes. after going into andre-richter' github, I found this line Afterward, system device shows that both the nics are bound to vfio, Which should not happen right? I think what happened was that, after creating the vf, the physical function and the vf are in the same immmo group. If my understanding is correct, the scipt shoudn't bind the phscial function to vfio since the ixgbe driver needs to be active in order to provide the vfs. And because the scipt binds all device in the same iommu group, in my case this will include the phsical function. In addition, from reading the guide, devices that uses the ixgbe driver does not have a abstrication layer. thus why am i getting 5 nics in total (including the phsical).