Re: [Xen-devel] After switching from "xm" to "xl" toolstack, can't get Guest networking to work.

[Roger Pau Monnà <roger.pau@xxxxxxxxxxxxx>]

2012/1/22  <erin.balid@xxxxxxxxxxxx>:
> Hi Roger.
>
> Here is "ifconfig -a" output from the DomU when launched with xm.
>
> xm create test.cfg
> xm list
> ÂName                    ÂID  Mem VCPUs   ÂState
> ÂTime(s)
> ÂDomain-0 Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â 0 Â1010 Â Â 1 Â Â r-----
> Â913.4
> Âtemplate                   1 Â2048   2   -b----
> Â 86.0
> xm console template
> Â...
> ifconfig -a
> Âeth0 Â Â ÂLink encap:Ethernet ÂHWaddr 00:16:3E:12:34:01
> Â Â Â Â Â UP BROADCAST RUNNING MULTICAST ÂMTU:1500 ÂMetric:1
> Â Â Â Â Â RX packets:38658 errors:0 dropped:24935 overruns:0 frame:0
> Â Â Â Â Â TX packets:11009 errors:0 dropped:0 overruns:0 carrier:0
> Â Â Â Â Â collisions:0 txqueuelen:1000
> Â Â Â Â Â RX bytes:2621879 (2.5 Mb) ÂTX bytes:10432153 (9.9 Mb)
>
> Âeth0:1 Â ÂLink encap:Ethernet ÂHWaddr 00:16:3E:12:34:01
> Â Â Â Â Â inet addr:192.168.1.32 Â Bcast:192.168.1.255
> Â Â Â Â Â Mask:255.255.255.0
> Â Â Â Â Â UP BROADCAST RUNNING MULTICAST ÂMTU:1500 ÂMetric:1
>
> Âlo    ÂLink encap:Local Loopback
> Â Â Â Â Â inet addr:127.0.0.1 ÂMask:255.0.0.0
> Â Â Â Â Â UP LOOPBACK RUNNING ÂMTU:16436 ÂMetric:1
> Â Â Â Â Â RX packets:7 errors:0 dropped:0 overruns:0 frame:0
> Â Â Â Â Â TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
> Â Â Â Â Â collisions:0 txqueuelen:0
> Â Â Â Â Â RX bytes:563 (563.0 b) ÂTX bytes:563 (563.0 b)
>
>
> And, "ifconfig -a" output from the DomU when launched with xl.
>
> xl create test.cfg
> xl list
> ÂName                    ÂID  Mem VCPUs   ÂState
> ÂTime(s)
> ÂDomain-0 Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â 0 Â1010 Â Â 1 Â Â r-----
> Â Â66.8
> Âtemplate                   1 Â2048   2   -b----
> Â Â 6.8
>
> ifconfig -a
> Âeth0 Â Â ÂLink encap:Ethernet ÂHWaddr 00:16:3E:12:34:01
> Â Â Â Â Â UP BROADCAST RUNNING MULTICAST ÂMTU:1500 ÂMetric:1
> Â Â Â Â Â RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> Â Â Â Â Â TX packets:114 errors:0 dropped:0 overruns:0 carrier:0
> Â Â Â Â Â collisions:0 txqueuelen:1000
> Â Â Â Â Â RX bytes:0 (0.0 b) ÂTX bytes:5241 (5.1 Kb)
>
> Âeth0:1 Â ÂLink encap:Ethernet ÂHWaddr 00:16:3E:12:34:01
> Â Â Â Â Â inet addr:192.168.1.32 Â Bcast:192.168.1.255
> Â Â Â Â Â Mask:255.255.255.0
> Â Â Â Â Â UP BROADCAST RUNNING MULTICAST ÂMTU:1500 ÂMetric:1
>
> Âlo    ÂLink encap:Local Loopback
> Â Â Â Â Â inet addr:127.0.0.1 ÂMask:255.0.0.0
> Â Â Â Â Â UP LOOPBACK RUNNING ÂMTU:16436 ÂMetric:1
> Â Â Â Â Â RX packets:52 errors:0 dropped:0 overruns:0 frame:0
> Â Â Â Â Â TX packets:52 errors:0 dropped:0 overruns:0 carrier:0
> Â Â Â Â Â collisions:0 txqueuelen:0
> Â Â Â Â Â RX bytes:4431 (4.3 Kb) ÂTX bytes:4431 (4.3 Kb)
>
>> Also paste the output from "xenstore-ls -fp" on the Dom0 when the xl
>> DomU is up and running. From what I saw above in /var/log/messages the
>> problem seem to be related to hotplug scripts.
>
> Here is the paste of that output. ===> http://pastebin.com/s0e03VnW


Apart from the fact that you have quite a lot of junk in xenstore I
don't see anything strange, devices seem to be connected ok. I've
realized that you have installed
patterns-openSUSE-xen_server-12.1-25.21.1.x86_64, what's this? I've
never used Xen with OpenSUSE, but this seems related to XenServer
comercial version, not open source Xen. Maybe someone familiar with
Xen on OpenSUSE can provide more helpful information.

The only strange thing I see are the hotplug error messages in
/var/log/messages, but I don't know what could cause them. Maybe old
udev rules or hotplug scripts that didn't get cleaned when updating?

> On Sun, Jan 22, 2012, at 10:49 AM, djmagee@xxxxxxxxxxxx wrote:
>> You're missing the opening single quote on your vif line.
>
> That's just a copy/paste typo in the email.
>
> Regards,
>
> Erin

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel