After googling around and reading the material on the opensolaris.org xvm community site, I still do not understanding the configuration of networking and would appreciate some assistance. Problem: I have successfully installed an hvm domU running Windows XP on opensolaris 2005.11 (build 94), and when the laptop (lenovo t61, core2 9300) is connected via the e1000g0 interface networking works just great (the domU gets a dhcp address and has connectivity to the outside world.) When i switch to using wireless networking via the iwk0 interface (Intel 4965 802.11agn Chipsets), the domU has no network connectivity and does not successfully retrieve a dhcp address. Questions: 1) Do wireless network interfaces work as bridged devices for domUs? I understood the requirement for GLDv3 drivers, which I believe is the case for the iwk driver, but networking does not "just work". 2) If bridged networking does not work via the iwk0 interface, what are the steps to create an internal NAT network like what is described in: http://blogs.sun.com/droux/entry/private_virtual_networks_for_solaris I understand that crossbow has not been integrated fully yet, but that some basics have in place to support xvm. Is there enough to get something like this going? If so, how? Thanks in advance, -- paul
On 30 Jul 2008, at 1:40pm, Paul Fisher wrote:> Questions: > > 1) Do wireless network interfaces work as bridged devices for domUs?No. Most wireless devices refuse to transmit packets with a source MAC address different to their own (at least when in client mode). This makes the VNIC implementation inoperable over wireless devices.> 2) If bridged networking does not work via the iwk0 interface, what > are > the steps to create an internal NAT network like what is described in: > > http://blogs.sun.com/droux/entry/private_virtual_networks_for_solaris > > I understand that crossbow has not been integrated fully yet, but that > some basics have in place to support xvm. Is there enough to get > something like this going? If so, how?Unfortunately, there aren''t all of the pieces integrated to take the approach that Nicolas describes, in particular the etherstub code is not yet present. Something that you might try when connected to the network via iwk0 is: - use e1000g0 as the ''bridge'' device for the domain, - create another VNIC over e1000g0 for use by dom0 (let''s call that ''vnic99''), - plumb and configure vnic99 in dom0, - now dom0 and domU can communicate via the VNICs over e1000g0, even if e1000g0 is down, - install NAT rules, routing configuration, etc. such that traffic from the guest domain can be passed out through iwk0.
David Edmondson wrote:> On 30 Jul 2008, at 1:40pm, Paul Fisher wrote: > >> 2) If bridged networking does not work via the iwk0 interface, what >> are >> the steps to create an internal NAT network like what is described in: >> >> http://blogs.sun.com/droux/entry/private_virtual_networks_for_solaris >> >> I understand that crossbow has not been integrated fully yet, but that >> some basics have in place to support xvm. Is there enough to get >> something like this going? If so, how? >> > > Unfortunately, there aren''t all of the pieces integrated to take the > approach that Nicolas describes, in particular the etherstub code is > not yet present. > > Something that you might try when connected to the network via iwk0 is: > - use e1000g0 as the ''bridge'' device for the domain, > - create another VNIC over e1000g0 for use by dom0 (let''s call that > ''vnic99''), > - plumb and configure vnic99 in dom0, > - now dom0 and domU can communicate via the VNICs over e1000g0, even > if e1000g0 is down, >Thank you very much. I''ve gotten this far (actually it looks like the virt-install created such a vnic already.), but ...> - install NAT rules, routing configuration, etc. such that traffic > from the guest domain can be passed out through iwk0. >So I should be able to use the instructions on that blog to setup that forwarding... I''ll report back on that. Thanks again! -- paul
On Wed, Jul 30, 2008 at 10:34:55AM -0500, Paul Fisher wrote:>> Something that you might try when connected to the network via iwk0 is: >> - use e1000g0 as the ''bridge'' device for the domain, >> - create another VNIC over e1000g0 for use by dom0 (let''s call that >> ''vnic99''), >> - plumb and configure vnic99 in dom0, >> - now dom0 and domU can communicate via the VNICs over e1000g0, even >> if e1000g0 is down, >> > Thank you very much. I''ve gotten this far (actually it looks like the > virt-install created such a vnic already.), but ...The tools will create a VNIC, but that''s for use by the guest. You''ll need to create another for use by dom0 yourself.
David Edmondson wrote:> On 30 Jul 2008, at 1:40pm, Paul Fisher wrote: > >> 2) If bridged networking does not work via the iwk0 interface, what >> are >> the steps to create an internal NAT network like what is described in: >> >> http://blogs.sun.com/droux/entry/private_virtual_networks_for_solaris >> >> I understand that crossbow has not been integrated fully yet, but that >> some basics have in place to support xvm. Is there enough to get >> something like this going? If so, how? >> > > Unfortunately, there aren''t all of the pieces integrated to take the > approach that Nicolas describes, in particular the etherstub code is > not yet present. > > Something that you might try when connected to the network via iwk0 is: > - use e1000g0 as the ''bridge'' device for the domain, > - create another VNIC over e1000g0 for use by dom0 (let''s call that > ''vnic99''), > - plumb and configure vnic99 in dom0, > - now dom0 and domU can communicate via the VNICs over e1000g0, even > if e1000g0 is down, > - install NAT rules, routing configuration, etc. such that traffic > from the guest domain can be passed out through iwk0. >Finally got a chance to try to do this, and I just cannot find the right combination of documentation/blogs/forum information that corresponds to the bits that exist in 2005.11 (B94). <rant> Rather than include it here: http://adventuresinopensolaris.blogspot.com/2008/07/xvm-marketing-madness.html </rant> I''ve looked at: http://blogs.sun.com/hasham/entry/sun_xvm_virtualbox_and_host http://www.virtualbox.org/download/1.6.2/UserManual.pdf (6.8.2) Basically, I''m stuck even being able to generate a vnic over my (inactive) e1000g0 interface: pfisher@pfisher-laptop:~$ pfexec dladm show-link LINK CLASS MTU STATE OVER e1000g0 phys 1500 down -- iwk0 phys 1500 up -- pfisher@pfisher-laptop:~$ /usr/lib/vna e1000g0 08:00:27:22:5E:3A Invalid link name: e1000g0 Can anyone give me some better pointers to doc on how to setup a virtual network, that I can then route externally to whatever interface is active as the default route (iwk0 or e1000g0)? -- paul
Paul Fisher wrote:> Basically, I''m stuck even being able to generate a vnic over my > (inactive) e1000g0 interface: > > pfisher@pfisher-laptop:~$ pfexec dladm show-link > LINK CLASS MTU STATE OVER > e1000g0 phys 1500 down -- > iwk0 phys 1500 up -- > > pfisher@pfisher-laptop:~$ /usr/lib/vna e1000g0 08:00:27:22:5E:3A > Invalid link name: e1000g0 >I went back and tried this again, hoping to make some more progress, and apparently I can get the vnic defined over the inactive e1000g0 interface. Please disregard, I believe it was as simple as being too tired (and forgetting to use pfexec). Local networking works just by manually doing: $ pfexec /usr/lib/vna e1000g0 08:00:27:22:5E:3A vnic0 $ pfexec ifconfig vnic0 plumb $ pfexec ifconfig vnic0 192.168.254.1/24 up $ pfexec svccfg -s xvm/xend setprop config/default-nic = \"vnic0\" $ pfexec xm start etch-01 The in the domU do: # ifconfig eth0 192.168.254.10/24 up Ping works both ways now! Now to get NAT configured... -- paul
On Sun, Aug 03, 2008 at 09:34:46PM -0500, Paul Fisher wrote:> $ pfexec svccfg -s xvm/xend setprop config/default-nic = \"vnic0\"This part is wrong - that should be ''e1000g0'' rather than ''vnic0''.
2005.11 ???? What sort of a beast is that ? I only find 2008.05 of opensolaris and of cource the SXCE builds ;-) This message posted from opensolaris.org
> 2005.11 ???? > What sort of a beast is that ? > I only find 2008.05 of opensolarisIt''s an updated release of opensolaris, using onnv build 95 components, firefox 3, ... http://www.opensolaris.org/jive/thread.jspa?messageID=269177 http://www.genunix.org/ This message posted from opensolaris.org