March 4, 201511 yr Ok, Thanks archedraft, gave me a good pointer. I was getting very confused between passthrough and virtualisation. Copied my xml to /boot and used virsh - problem solved. Sorry for being a nuisance and quite frankly I feel a bit of a pillock!
May 5, 201511 yr Are any of you having trouble with PfSense since upgrading to V15 and the new VM manager? Since the update, I have tried re-installing PfSense and am having trouble with the bridges working correctly. They are being handed off to PfSense (i can assign the interfaces) but it doesn't seem like they are getting outside of my unraid box. Were there any changes to assigning bridges using the go file? If one of you have PfSense working with V15 will you please post your xml so I can compare? Thanks!
May 7, 201511 yr Are any of you having trouble with PfSense since upgrading to V15 and the new VM manager? Since the update, I have tried re-installing PfSense and am having trouble with the bridges working correctly. They are being handed off to PfSense (i can assign the interfaces) but it doesn't seem like they are getting outside of my unraid box. Were there any changes to assigning bridges using the go file? If one of you have PfSense working with V15 will you please post your xml so I can compare? Thanks! I have the latest version of pfsense installed, I haven't set it up yet, but it's booting and I can access the webui. I'm no longer using this method to passthrough my dual Intel NIC and I'm pretty sure archedraft isn't either. Here's the new method detailed by jonp that I think both myself and archedraft are now using. Here's a copy of my xml file <domain type='kvm' id='2'> <name>pfSense</name> <uuid>677d7037-b71d-d2e5-22f3-0f3b67408b0a</uuid> <memory unit='KiB'>4194304</memory> <currentMemory unit='KiB'>1048576</currentMemory> <memoryBacking> <nosharepages/> <locked/> </memoryBacking> <vcpu placement='static'>1</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-2.2'>hvm</type> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='1' threads='1'/> </cpu> <clock offset='utc'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/bin/qemu-system-x86_64</emulator> <disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='none' io='native'/> <source file='/mnt/disk/KVM/VM/pfSense/vdisk1.qcow2'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='2'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/disk/KVM/Media/pfSense-2.2.2.iso'/> <backingStore/> <target dev='hda' bus='ide'/> <readonly/> <boot order='1'/> <alias name='ide0-0-0'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <controller type='usb' index='0'> <alias name='usb0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </controller> <controller type='ide' index='0'> <alias name='ide0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <serial type='pty'> <source path='/dev/pts/0'/> <target port='0'/> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/0'> <source path='/dev/pts/0'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <input type='tablet' bus='usb'> <alias name='input0'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='5900' autoport='yes' websocket='5700' listen='0.0.0.0'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='vmvga' vram='16384' heads='1'/> <alias name='video0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x04' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </hostdev> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </memballoon> </devices> </domain> syslinux.cfg default /syslinux/menu.c32 menu title Lime Technology prompt 0 timeout 50 label unRAID OS menu default kernel /bzimage append pcie_acs_override=downstream pci-stub.ids=8086:105e initrd=/bzroot label unRAID OS Safe Mode (no plugins) kernel /bzimage append initrd=/bzroot unraidsafemode label Memtest86+ kernel /memtest label Xen/unRAID OS kernel /syslinux/mboot.c32 append /xen --- /bzimage --- /bzroot label Xen/unRAID OS Safe Mode (no plugins) kernel /syslinux/mboot.c32 append /xen --- /bzimage --- /bzroot unraidsafemode My go file doesn't contain any bridge setups any longer. Hope that helps
May 7, 201511 yr Are any of you having trouble with PfSense since upgrading to V15 and the new VM manager? Since the update, I have tried re-installing PfSense and am having trouble with the bridges working correctly. They are being handed off to PfSense (i can assign the interfaces) but it doesn't seem like they are getting outside of my unraid box. Were there any changes to assigning bridges using the go file? If one of you have PfSense working with V15 will you please post your xml so I can compare? Thanks! I have the latest version of pfsense installed, I haven't set it up yet, but it's booting and I can access the webui. I'm no longer using this method to passthrough my dual Intel NIC and I'm pretty sure archedraft isn't either. Here's the new method detailed by jonp that I think both myself and archedraft are now using. Here's a copy of my xml file My go file doesn't contain any bridge setups any longer. Hope that helps Thanks! I will compare with my setup tonight. I assume new way JonP posted requires VT-D? If not I will also go down that path.
May 7, 201511 yr Are any of you having trouble with PfSense since upgrading to V15 and the new VM manager? Since the update, I have tried re-installing PfSense and am having trouble with the bridges working correctly. They are being handed off to PfSense (i can assign the interfaces) but it doesn't seem like they are getting outside of my unraid box. Were there any changes to assigning bridges using the go file? If one of you have PfSense working with V15 will you please post your xml so I can compare? Thanks! I have the latest version of pfsense installed, I haven't set it up yet, but it's booting and I can access the webui. I'm no longer using this method to passthrough my dual Intel NIC and I'm pretty sure archedraft isn't either. Here's the new method detailed by jonp that I think both myself and archedraft are now using. Here's a copy of my xml file My go file doesn't contain any bridge setups any longer. Hope that helps Thanks! I will compare with my setup tonight. I assume new way JonP posted requires VT-D? If not I will also go down that path. Pass through of ANY PCI devices required Intel VT-d or AMD-Vi
May 7, 201511 yr the only thing holding me back from VM'ing pfsense is it being dependant on the array being up.
May 7, 201511 yr Author You may already know this but I figure I'll clarify anyway. Once the array starts and the pfsense vm turns on, the array will get its IP address. After unraid has an IP address you can stop the array (which will turn off the pfsense VM) and still access unraid's web GUI through the IP address. Of course the Internet will be down at this point so you wouldn't want to leave the array down for extended periods of time.
May 7, 201511 yr Are any of you having trouble with PfSense since upgrading to V15 and the new VM manager? Since the update, I have tried re-installing PfSense and am having trouble with the bridges working correctly. They are being handed off to PfSense (i can assign the interfaces) but it doesn't seem like they are getting outside of my unraid box. Were there any changes to assigning bridges using the go file? If one of you have PfSense working with V15 will you please post your xml so I can compare? Thanks! I have the latest version of pfsense installed, I haven't set it up yet, but it's booting and I can access the webui. I'm no longer using this method to passthrough my dual Intel NIC and I'm pretty sure archedraft isn't either. Here's the new method detailed by jonp that I think both myself and archedraft are now using. Here's a copy of my xml file My go file doesn't contain any bridge setups any longer. Hope that helps Thanks! I will compare with my setup tonight. I assume new way JonP posted requires VT-D? If not I will also go down that path. As jonp says whatever method you want to use requires vt-d, might explain why you're having trouble.
May 7, 201511 yr Are any of you having trouble with PfSense since upgrading to V15 and the new VM manager? Since the update, I have tried re-installing PfSense and am having trouble with the bridges working correctly. They are being handed off to PfSense (i can assign the interfaces) but it doesn't seem like they are getting outside of my unraid box. Were there any changes to assigning bridges using the go file? If one of you have PfSense working with V15 will you please post your xml so I can compare? Thanks! I have the latest version of pfsense installed, I haven't set it up yet, but it's booting and I can access the webui. I'm no longer using this method to passthrough my dual Intel NIC and I'm pretty sure archedraft isn't either. Here's the new method detailed by jonp that I think both myself and archedraft are now using. Here's a copy of my xml file My go file doesn't contain any bridge setups any longer. Hope that helps Thanks! I will compare with my setup tonight. I assume new way JonP posted requires VT-D? If not I will also go down that path. As jonp says whatever method you want to use requires vt-d, might explain why you're having trouble. My current board does not support VT-D, however, I had PfSense running previously using bridges. Using bridges eliminates the need to passthrough any devices. This obviously isn't the ideal solution. I may just go to a stand alone PfSense machine. VT-D support is the only thing my little 8-core atom is missing. Thanks for the help!
May 8, 201511 yr My current board does not support VT-D, however, I had PfSense running previously using bridges. Using bridges eliminates the need to passthrough any devices. This obviously isn't the ideal solution. I may just go to a stand alone PfSense machine. VT-D support is the only thing my little 8-core atom is missing. Thanks for the help! You're quite right, I do apologise, I'm putting it down to working nights at the moment.
May 11, 201511 yr Fixed it!! Just an update to anyone who might run across this. Before Beta15 the "virtio" network adapter would not work correctly with my PfSense. I had to change the virtual network devices in the xml to 'e1000' in order to get them to have any kind of throughput. Now that Beta15 has taken over, I had to switch back to the "virtio" adapter, once I made the change all is well again!!
Archived
This topic is now archived and is closed to further replies.