Hi All, I have installed the Solaris Express Developer Edition 1/08 and I am having some issues with xen dom0 networking. Essentially when booted into the Vm version of the kernel, my networking fails. Pertinent information: * I am using the e1000g driver # /sbin/dladm show-link e1000g0 type: non-vlan mtu: 1500 device: e1000g0 * packets leave the interface and arrive at the destination and a response is sent back. Snoop can see the packets arriving. * arp addresses do not appear in the arp table Any hints welcome. Thanks Maurice Castro
Hi All, I have installed the Solaris Express Developer Edition 1/08 and I am having some issues with xen dom0 networking. Essentially when booted into the Vm version of the kernel, my networking fails. Pertinent information: * I am using the e1000g driver # /sbin/dladm show-link e1000g0 type: non-vlan mtu: 1500 device: e1000g0 * packets leave the interface and arrive at the destination and a response is sent back. Snoop can see the packets arriving. * arp addresses do not appear in the arp table Any hints welcome. Thanks Maurice Castro
> Hi All, > I have installed the Solaris Express Developer > r Edition 1/08 and I am > having some issues with xen dom0 networking. > Essentially when booted > into the > Vm version of the kernel, my networking fails. > > Pertinent information: > > * I am using the e1000g driver > # /sbin/dladm show-link > e1000g0 type: non-vlan mtu: 1500 > 0 device: e1000g0Would like to see :- # ifconfig -a . . . . . . . . . . . .> > * packets leave the interface and arrive at the > destination and a > response is > sent back. Snoop can see the packets arriving. > > * arp addresses do not appear in the arp table > > Any hints welcome. > > Thanks > Maurice Castro > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.orgThis message posted from opensolaris.org
The ifconfig reads the same when the working starndard kernel is booted as when the non-working dom0 kernel is booted. The output is:> /sbin/ifconfig -alo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1 inet 127.0.0.1 netmask ff000000 e1000g0: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2 inet 202.147.99.229 netmask ffffffe0 broadcast 202.147.99.255 lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu 8252 index 1 inet6 ::1/128>> Hi All, >> I have installed the Solaris Express Developer Edition 1/08 and I am >> having some issues with xen dom0 networking. >> Essentially when booted into the Vm version of the kernel, my >> networking fails. >> > Would like to see :- > # ifconfig -a
I apologize in advance for unprofessional questions. After numerous Solaris xVM installs (75A, 76.78,81) i''ve noticed that detected by SNV ethernet interface is automatically configured as DHCP. If you have DHCP Server on your LAN or you are on the bridge to DHCP enabled subnet just fine, otherwise run:- # ifconfig rge0 up 192.168.0.81 netmask 255.255.255.0 ( for example). When SNV Dom0 gets IP address assigned either via DHCP or manually. Any application (like ssh,telnet,ftp,....) running on the LAN (192.168.0.0) PCs can connect SNV Dom0 with no problems. I never cared about arp level. Are you saying , that applications level TCP/IP connectivity to SNV79 Dom0 is broken ? This message posted from opensolaris.org
Hi Boris, The interface is correctly configured ie the manual configuration of the Dom0 interface is identical to the manual configuration of the non Xen Solaris that I previously booted. The only difference is that networking does not appear to work when the xVm version of the kernel is booted. A failure at the ARP level necessarily implies a failure of all tcp and udp based applications as it makes it impossible to receive any responses. Maurice On 22/02/2008, at 9:17 PM, Boris Derzhavets wrote:> I apologize in advance for unprofessional questions. > After numerous Solaris xVM installs (75A, 76.78,81) i''ve noticed that > detected by SNV ethernet interface is automatically configured as > DHCP. > If you have DHCP Server on your LAN or you are on the bridge to > DHCP enabled > subnet just fine, otherwise run:- > # ifconfig rge0 up 192.168.0.81 netmask 255.255.255.0 ( for example). > When SNV Dom0 gets IP address assigned either via DHCP or manually. > Any application (like ssh,telnet,ftp,....) running on the LAN > (192.168.0.0) > PCs can connect SNV Dom0 with no problems. > I never cared about arp level. Are you saying , that applications > level TCP/IP > connectivity to SNV79 Dom0 is broken ? >