Hello, I have a server with two NICs running Xen 3.2 from Debian Lenny (eth0 and eth1). I''m wondering what the best method is to effectively dedicate eth1 to a particular domU. I have an existing DHCP entry for the MAC address of eth1, so assigning a different MAC to the virtual NIC in my domU and bridging that to eth1 within dom0 is an issue for me. I tried assigning the identical MAC address to my domU in the vif line in its config file. tcpdump in dom0 suggests that the DHCP requests are making it out onto the network, but the DHCP replies don''t seem to be getting through to the domU. I''ve also observed that it''s possible to dedicate a PCI device to a particular domU with pciback, but the necessary module is not part of the stock kernel and I don''t want the maintenance overhead of having to keep rebuilding a particular module, etc. Should I be doing this with a routing-based configuration? Performance would be nice but this server is not heavily loaded, so I''m not too worried about performance. Thanks for any suggestions, -Jon _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Jonathan M. McCune wrote:>I have a server with two NICs running Xen 3.2 from Debian Lenny >(eth0 and eth1). I''m wondering what the best method is to >effectively dedicate eth1 to a particular domU. I have an existing >DHCP entry for the MAC address of eth1, so assigning a different MAC >to the virtual NIC in my domU and bridging that to eth1 within dom0 >is an issue for me. I tried assigning the identical MAC address to >my domU in the vif line in its config file. tcpdump in dom0 >suggests that the DHCP requests are making it out onto the network, >but the DHCP replies don''t seem to be getting through to the domU.Either use pciback.hide to make the hardware directly available to the guest, or ... Create a bridge, so you''ll end up with a physical device, and the Dom0 virtual device attached. Then attached a virtual interface for the guest to this bridge. The Dom0 doesn''t need to have an IP address on the bridge, but you do need to bring up the interface (ip link set up dev ... IIRC) for it to pass traffic. -- Simon Hobson WANTED: "Software CD ROM Kit" for Canon CLBP 360-PS printer (Canon part no RH6-3612, or possibly RH6-3810, or RH6-3610 might do). I''ve a dead HD and need this CD so I can replace the disk and re-install the printer OS on it. If anyone knows where I might get hold of one I''d be grateful - requests to Canon drew a blank, it''s been out of support for years. Alternatively, if anyone has one of these and would let me image their hard disk ... Visit http://www.magpiesnestpublishing.co.uk/ for books by acclaimed author Gladys Hobson. Novels - poetry - short stories - ideal as Christmas stocking fillers. Some available as e-books. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Fri, Feb 12, 2010 at 8:32 AM, Jonathan M. McCune <jonmccune@cmu.edu> wrote:> I have an existing DHCP entry for the MAC address of > eth1, so assigning a different MAC to the virtual NIC in my domU and > bridging that to eth1 within dom0 is an issue for me.The "correct" way to do that is by assigning a new MAC address to domU, and ask your network admins to modify DHCP assignment. If you''re stuck with wanting that MAC on domU, then you can change the NIC''s MAC address on dom0 before putting it on the bridge. Something like ip link set eth0 address 00:16:3E:9d:77:76 then you can use the original MAC address for domU. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users