May 4, 201610 yr I'm about to install a dual port NIC into my server to be used directly by a VM (pfSense) but unRaid wants to default to one of the ports on the new NIC instead of the onboard NIC it's been using. I vaguely recall a post by someone saying they did this but of cause, when needed, I can't find it. So, how do I force unRaid to use the onboard NIC and ignore the new dual NIC card I've added?
May 4, 201610 yr This one? https://lime-technology.com/forum/index.php?topic=48783.0 You'll want the method suggested by BobPhoenix.
May 4, 201610 yr Author This one? https://lime-technology.com/forum/index.php?topic=48783.0 You'll want the method suggested by BobPhoenix. No, not that one. But that's better Thanks.
May 4, 201610 yr Author This one? https://lime-technology.com/forum/index.php?topic=48783.0 You'll want the method suggested by BobPhoenix. emmm..... the new NIC has the same vendor & product ID of my internal NIC. If I stub 10ec:8168 that will affect my onboard NIC too.
May 5, 201610 yr This one? https://lime-technology.com/forum/index.php?topic=48783.0 You'll want the method suggested by BobPhoenix. emmm..... the new NIC has the same vendor & product ID of my internal NIC. If I stub 10ec:8168 that will affect my onboard NIC too. Not going to work to stub them. If you DO then ALL of your nics - the MB nics and the card nics will be hidden from unRAID. The model of the nic you bought on the card needs to be different then the model of the nic on your MB to get a different vendor & product ID. Get a different card. Maybe a different Manufacturer to make sure they are different maybe an Intel nic for instance. Here is an example of what I'm talking about below. My MB has Intel nic chips and they are different then the PCI nic card I installed: 0c:00.0 Ethernet controller [0200]: Intel Corporation 82574L Gigabit Network Connection [8086:10d3] 0d:00.0 Ethernet controller [0200]: Intel Corporation 82574L Gigabit Network Connection [8086:10d3] 0e:00.0 Ethernet controller [0200]: Intel Corporation 82541PI Gigabit Ethernet Controller [8086:107c] (rev 05) I have ordered the following PCI dual nic which should be different then my MB and SHOULD (but may not be won't know until I get it next week) different then my MB nics. http://www.ebay.com/itm/INTEL-Dual-Port-Gigabit-Server-Adapter-8492MT-32-bit-PCI-1000M-Network-Card-NIC-/201218198950?rmvSB=true I wanted PCI because my EP2C602-4L/D16 MB has a PCI slot and I wanted to reserve the PCIe slots for other cards. Edit: Another possibility is the method outlined here: http://lime-technology.com/forum/index.php?topic=48809.msg468831#msg468831
May 5, 201610 yr Author This one? https://lime-technology.com/forum/index.php?topic=48783.0 You'll want the method suggested by BobPhoenix. emmm..... the new NIC has the same vendor & product ID of my internal NIC. If I stub 10ec:8168 that will affect my onboard NIC too. Not going to work to stub them. If you DO then ALL of your nics - the MB nics and the card nics will be hidden from unRAID. The model of the nic you bought on the card needs to be different then the model of the nic on your MB to get a different vendor & product ID. Get a different card. Maybe a different Manufacturer to make sure they are different maybe an Intel nic for instance. Here is an example of what I'm talking about below. My MB has Intel nic chips and they are different then the PCI nic card I installed: 0c:00.0 Ethernet controller [0200]: Intel Corporation 82574L Gigabit Network Connection [8086:10d3] 0d:00.0 Ethernet controller [0200]: Intel Corporation 82574L Gigabit Network Connection [8086:10d3] 0e:00.0 Ethernet controller [0200]: Intel Corporation 82541PI Gigabit Ethernet Controller [8086:107c] (rev 05) I have ordered the following PCI dual nic which should be different then my MB and SHOULD (but may not be won't know until I get it next week) different then my MB nics. http://www.ebay.com/itm/INTEL-Dual-Port-Gigabit-Server-Adapter-8492MT-32-bit-PCI-1000M-Network-Card-NIC-/201218198950?rmvSB=true I wanted PCI because my EP2C602-4L/D16 MB has a PCI slot and I wanted to reserve the PCIe slots for other cards. Edit: Another possibility is the method outlined here: http://lime-technology.com/forum/index.php?topic=48809.msg468831#msg468831 This is frustrating, to say the very least. I just tested with SIX (6) network cards I have laying around and pull TWO (2) dual NICs from other machines ALL are displayed as REALTEK cards with the same IDs! Short of 'stubbing' them is there any other way to achieve this?
May 5, 201610 yr Edit: Another possibility is the method outlined here: http://lime-technology.com/forum/index.php?topic=48809.msg468831#msg468831 This is frustrating, to say the very least. I just tested with SIX (6) network cards I have laying around and pull TWO (2) dual NICs from other machines ALL are displayed as REALTEK cards with the same IDs! Short of 'stubbing' them is there any other way to achieve this? Did you look at my link I added? Will that not work for you? I've never tried it myself so have no experience but it sounded promising.
May 5, 201610 yr Author Edit: Another possibility is the method outlined here: http://lime-technology.com/forum/index.php?topic=48809.msg468831#msg468831 This is frustrating, to say the very least. I just tested with SIX (6) network cards I have laying around and pull TWO (2) dual NICs from other machines ALL are displayed as REALTEK cards with the same IDs! Short of 'stubbing' them is there any other way to achieve this? Did you look at my link I added? Will that not work for you? I've never tried it myself so have no experience but it sounded promising. Apologies, I didn't see you 'edit'. Reviewing that post now.
May 5, 201610 yr Author Edit: Another possibility is the method outlined here: http://lime-technology.com/forum/index.php?topic=48809.msg468831#msg468831 This is frustrating, to say the very least. I just tested with SIX (6) network cards I have laying around and pull TWO (2) dual NICs from other machines ALL are displayed as REALTEK cards with the same IDs! Short of 'stubbing' them is there any other way to achieve this? Did you look at my link I added? Will that not work for you? I've never tried it myself so have no experience but it sounded promising. After reading the post you linked I don't see how it is similar to what I want to achieve. Which is, assign a NIC card to a VM for native use. In my case, specifically for running a pfSense VM with native access to the dual NIC. I've browsed enough forum posts to know that running pfSense in a VM without native access to the NIC(s) will cause problems.
May 5, 201610 yr Edit: Another possibility is the method outlined here: http://lime-technology.com/forum/index.php?topic=48809.msg468831#msg468831 This is frustrating, to say the very least. I just tested with SIX (6) network cards I have laying around and pull TWO (2) dual NICs from other machines ALL are displayed as REALTEK cards with the same IDs! Short of 'stubbing' them is there any other way to achieve this? Did you look at my link I added? Will that not work for you? I've never tried it myself so have no experience but it sounded promising. After reading the post you linked I don't see how it is similar to what I want to achieve. Which is, assign a NIC card to a VM for native use. In my case, specifically for running a pfSense VM with native access to the dual NIC. I've browsed enough forum posts to know that running pfSense in a VM without native access to the NIC(s) will cause problems. In your post you said you wanted to get unRAID to use your MB nic. The method he outlines is to get unRAID to use a specific nic as eth0 which is the nic unRAID will use as it's nic. You don't need to stub a nic to use it with a VM I can use eth1-3 on my ASRock MB by just editing the XML for the VM with the appropriate parameters. But you wouldn't or at least shouldn't use eth0 as a nic in the VM.
May 5, 201610 yr Author Edit: Another possibility is the method outlined here: http://lime-technology.com/forum/index.php?topic=48809.msg468831#msg468831 This is frustrating, to say the very least. I just tested with SIX (6) network cards I have laying around and pull TWO (2) dual NICs from other machines ALL are displayed as REALTEK cards with the same IDs! Short of 'stubbing' them is there any other way to achieve this? Did you look at my link I added? Will that not work for you? I've never tried it myself so have no experience but it sounded promising. After reading the post you linked I don't see how it is similar to what I want to achieve. Which is, assign a NIC card to a VM for native use. In my case, specifically for running a pfSense VM with native access to the dual NIC. I've browsed enough forum posts to know that running pfSense in a VM without native access to the NIC(s) will cause problems. In your post you said you wanted to get unRAID to use your MB nic. The method he outlines is to get unRAID to use a specific nic as eth0 which is the nic unRAID will use as it's nic. You don't need to stub a nic to use it with a VM I can use eth1-3 on my ASRock MB by just editing the XML for the VM with the appropriate parameters. But you wouldn't or at least shouldn't use eth0 as a nic in the VM. You're right. I didn't properly highlight the exact scenario I wanted to achieve, instead, I only provided half of the story. As it turns out, rearranging the PCIE cards, and/or during the last (few) reboots the appropriate NIC is now being used by unRaid. So far as the subject title goes my problem has been resolved. Moving on to Stage 2 of my plan, assign 2 NIC ports to my VM.... how do you suggest I go about achieve this?
May 5, 201610 yr Edit: Another possibility is the method outlined here: http://lime-technology.com/forum/index.php?topic=48809.msg468831#msg468831 This is frustrating, to say the very least. I just tested with SIX (6) network cards I have laying around and pull TWO (2) dual NICs from other machines ALL are displayed as REALTEK cards with the same IDs! Short of 'stubbing' them is there any other way to achieve this? Did you look at my link I added? Will that not work for you? I've never tried it myself so have no experience but it sounded promising. After reading the post you linked I don't see how it is similar to what I want to achieve. Which is, assign a NIC card to a VM for native use. In my case, specifically for running a pfSense VM with native access to the dual NIC. I've browsed enough forum posts to know that running pfSense in a VM without native access to the NIC(s) will cause problems. In your post you said you wanted to get unRAID to use your MB nic. The method he outlines is to get unRAID to use a specific nic as eth0 which is the nic unRAID will use as it's nic. You don't need to stub a nic to use it with a VM I can use eth1-3 on my ASRock MB by just editing the XML for the VM with the appropriate parameters. But you wouldn't or at least shouldn't use eth0 as a nic in the VM. You're right. I didn't properly highlight the exact scenario I wanted to achieve, instead, I only provided half of the story. As it turns out, rearranging the PCIE cards, and/or during the last (few) reboots the appropriate NIC is now being used by unRaid. So far as the subject title goes my problem has been resolved. Moving on to Stage 2 of my plan, assign 2 NIC ports to my VM.... how do you suggest I go about achieve this? Edit the XML and add the following replacing my numbers with those appropriate for your NICs. You will need two entries one for each nic. <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </source> </hostdev> Which for my unRAID server stands for the following nics: 03:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection 04:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection 05:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection 06:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection When the VM starts unRAID disconnects the nic from unRAID use and passes it through to the VM automatically. You don't NEED to add a stub for the device the XML edit is enough to work. If you post your System Devices for your dual nic I could suggest what you need to paste in and where if you don't already know that.
May 5, 201610 yr Author The key information I was not aware of was is when a NIC is passed through to the VM in such a way that unRaid drops the connection to it. Thanks!
May 5, 201610 yr Author My PCI Devices are: 03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 11) 04:00.0 PCI bridge [0604]: Pericom Semiconductor Device [12d8:2304] (rev 05) 05:01.0 PCI bridge [0604]: Pericom Semiconductor Device [12d8:2304] (rev 05) 05:02.0 PCI bridge [0604]: Pericom Semiconductor Device [12d8:2304] (rev 05) 06:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 0c) 07:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 0c) 08:00.0 RAID bus controller [0104]: Silicon Image, Inc. SiI 3132 Serial ATA Raid II Controller [1095:3132] (rev 01) NIC 03:00.0 is my et0 and 06 & 07 are the dual port NIC I'll be assigning to pfSense. As such, the XML code should be? <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> <address domain='0x0000' bus='0x07' slot='0x00' function='0x0'/> </source> </hostdev> My only question is which tag should I include the above code within? Should I include it inside the Devices tag or simply inside the Domain tag? Eg, currently I have it inside the Domain tag, and I've placed it above the Devices tag for reference purposes. <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> <address domain='0x0000' bus='0x07' slot='0x00' function='0x0'/> </source> </hostdev> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/pfSense/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x0'/> </disk> Lastly, should I remove the reference to the default NIC interface the GUI / wizzard adds? <interface type='bridge'> <mac address='52:54:00:6c:f0:2b'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0'/> </interface>
May 5, 201610 yr I think the following XML will work. You need to specify them individually. </video> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> </source> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x07' slot='0x00' function='0x0'/> </source> </hostdev> <memballoon model='virtio'> Basically you put them between the end video tag </video> and the begin memballoon tag <memballoon model='virtio'> And YES I would remove the virtual nic since you are passing through the nics you want the VM to use.
May 5, 201610 yr Author The network card is being passed through to the VM correctly but something is definitely not working properly. Whenever the guest OS tries to access the NIC the below error appears in the VM log file. Inside the VM the NIC goes up and down as if the cable had been removed. processing error - resetting ehci HC Later tonight I'll test with other NIC cards, I'm hoping it's simply a faulty NIC - fingers crossed.
May 5, 201610 yr You are beyond my help NOW I'm afraid. Maybe jonp can get you through the rest of this. Never had an error like that before.
May 5, 201610 yr Author You are beyond my help NOW I'm afraid. Maybe jonp can get you through the rest of this. Never had an error like that before. Thanks for your help on this one, I'll plod along with some other NICs and see how it goes.
Archived
This topic is now archived and is closed to further replies.