I have noticed similar problems when the first interface that is listed from the command,
#/usr/sbin/dladm show-link is not configured properly in Dom0. Xen uses this first interface by default. Here is how you can override the default, # svccfg -s xvm/xend setprop \ config/default-nic = astring: <your interface> # svcadm refresh xvm/xend # svcadm restart xvm/xend The command, # svccfg -s xvm/xend listprop will list the current properties of xend. Augustus. Andrzej Szeszo wrote: > I've been trying to setup a paravirtualized domUs on OS200805 and SXCE b89. > domUs work fine except for the networking. I'm pretty sure I'm doing > everything correctly. I've setup a number of (HVM) domUs on different > machines successfully. > > I can start domU just fine. I simply can't use the network interface from it. > I can't see any incoming packets on the network interface in domU with > tcpdump even when I can see them on the dom0's interface (when pinging domU's > ip from some other physical machine on the network). > > I'm wondering whether this is a network driver problem or some > misconfiguration. I'm having the same problem on OS200805 and SXCE b89 with > Ubuntu Hardy and OS200805 guests. CPU in the machine doesn't support HVMs > (Dell Precision 380) so I can't test them. I'll try with a different network > adapter tomorrow. > > Any help would be appreciated. > > Here are some details about the SXCE setup (OS200805 is set up in a similar > way): > > --- Dom0 --- > # isainfo > amd64 i386 > > # uname -a > SunOS unknown 5.11 snv_89 i86pc i386 i86xpv > > # syseventadm list|grep xen > class=EC_xendev /usr/lib/xen/scripts/xpvd-event action=$subclass > domain=$domain vdev=$vdev device=$device devclass=$devclass febe=$fob > class=EC_xpvsys /usr/lib/xen/scripts/xpvsys-event subclass=$subclass > shutdown=$shutdown > > # virsh dumpxml vm1 #sorry, had to re-format the output for the forum > [domain type='xen' id='3'] > [name]vm1[/name] > [uuid]501df921-f2cb-e419-5fe5-4564f681af38[/uuid] > [bootloader]/usr/lib/xen/bin/pygrub[/bootloader] > [os] > [type]linux[/type] > [/os] > [memory]524288[/memory] > [vcpu]1[/vcpu] > [on_poweroff]destroy[/on_poweroff] > [on_reboot]restart[/on_reboot] > [on_crash]restart[/on_crash] > [devices] > [interface type='ethernet'] > [target dev='vif3.0'/] > [mac address='00:16:3e:39:d3:a1'/] > [script path='vif-vnic'/] > [/interface] > [disk type='block' device='disk'] > [driver name='phy'/] > [source dev='/dev/dsk/c2t010000137252A86B00002A004768F9BDd0p0'/] > [target dev='xvda1'/] > [/disk] > [console tty='/dev/pts/4'/] > [/devices] > [/domain] > > # xm list > Name ID Mem VCPUs State > Time(s) > Domain-0 0 1453 2 r----- 595.6 > vm1 3 512 1 -b---- 203.0 > > # ifconfig bge0 > bge0: flags=201004843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4,CoS> mtu 1500 > index 2 > inet 10.20.30.123 netmask ffffff00 broadcast 10.20.30.255 > ether 0:12:3f:74:e8:37 > > # /usr/lib/vna > vnic2 bge0 0:16:3e:39:d3:a1 > > --- DomU --- > # xm console vm1 > > # uname -a > Linux ubuntu-hardy 2.6.24-16-xen #1 SMP Thu Apr 10 15:51:04 UTC 2008 i686 > GNU/Linux > > # ifconfig eth0 > eth0 Link encap:Ethernet HWaddr 00:16:3e:39:d3:a1 > inet addr:10.20.30.28 Bcast:10.20.30.255 Mask:255.255.255.0 > inet6 addr: fe80::216:3eff:fe39:d3a1/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:26 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:0 (0.0 B) TX bytes:1308 (1.2 KB) > > > Regards, > > Andrzej > > > This message posted from opensolaris.org > _______________________________________________ > xen-discuss mailing list > [email protected] -- Augustus Franklin, Solaris Cluster http://blogs.sun.com/augustus _______________________________________________ xen-discuss mailing list [email protected]
