Re: After switching from "xm" to "xl" toolstack, can't get Guest networking to work.

[erin.balid@inoutbox.com]

Hi Ian.

> Does "ifconfig -a" in dom0 show a vifX.Y device for the domain? You previous xenstore log
> suggests it should be there but lets double check.

edit /etc/xen/scripts/vif-bridge
	#!/bin/bash
+       exec 1>>/tmp/hotplog.log
+       exec 2>&1
+       echo "`date`: Running $0 $*"

xl create test.cfg


ifconfig -a
brINT     Link encap:Ethernet  HWaddr 00:52:35:11:26:3B
          inet addr:192.168.1.10  Bcast:192.168.1.255 
          Mask:255.255.252.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:444732 errors:0 dropped:0 overruns:0 frame:0
          TX packets:287814 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1096020765 (1045.2 Mb)  TX bytes:95900515 (91.4 Mb)

eth0      Link encap:Ethernet  HWaddr 00:52:35:11:26:3B
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:840591 errors:0 dropped:0 overruns:0 frame:0
          TX packets:376159 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1132351110 (1079.8 Mb)  TX bytes:100533253 (95.8 Mb)
          Interrupt:48

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:3922 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3922 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:252238 (246.3 Kb)  TX bytes:252238 (246.3 Kb)

vif7.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:32
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

xl network-list test
 Idx BE Mac Addr.         handle state evt-ch   tx-/rx-ring-ref BE-path
 0   0  00:16:3e:12:34:01      0     4     15   768/769        
 /local/domain/0/backend/vif/7/0


> Do you get anything in the logs under /var/log/xen?

Just this after the Guest launches.  It looks a bit suspect maybe?

cat /var/log/xen/*log
 domid: 7
 Warning: vlan 0 is not connected to host network
 -videoram option does not work with cirrus vga device model. Videoram
 set to 4M.
 /home/abuild/rpmbuild/BUILD/xen-4.1.2-testing/tools/ioemu-dir/hw/xen_blktap.c:704:
 Init blktap pipes
 Could not open /var/run/tap/qemu-read-7
 char device redirected to /dev/pts/1
 xs_read(): target get error. /local/domain/7/target.
 xs_read(): vncpasswd get error.
 /vm/22eef8a2-7b68-4bb6-a69f-632d20db0d84/vncpasswd.
 Waiting for domain test (domid 7) to die [pid 28807]

> Are your hotplug scripts running at all? ...

cat /tmp/hotplog.log
 Tue Jan 24 07:23:49 PST 2012: Running /etc/xen/scripts/vif-bridge
 online type_if=vif
 Tue Jan 24 07:23:49 PST 2012: Running /etc/xen/scripts/vif-bridge
 online

> http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen lists a bunch of
> configuration files and logs which might be of interest, at least to
> skim looking for anything odd.

cat /var/log/xen/xen-hotplug.log
cat /var/log/xen/qemu-dm-*.log
 above ...

cat /var/log/xeb/console/*
 cat: /var/log/xeb/console/*: No such file or directory

I'm not completely sure what to look for that I'd know to be "odd".  I
think/hope the rest has already been reported in this thread.  If you
need anything else, please ID it and I can post it.

Regards,

Erin

p.s. Over on the opensuse-virtual list, at this thread,
http://lists.opensuse.org/opensuse-virtual/2012-01/msg00015.html

I just received a new post (It hasn't propagated to the list archive
just yet) says:

	"We also have what appears to be this problem, on Fedora 16 with
	Xen 4.1.2. We can create guests with xm that connect to network
	but the same guest will not connect, when created by xl. In both
	cases we can see the appropriate vif has been created and
	attached (xl network-list shows it) but no connectivity from
	within the guest. (If I convert the same guest config file to
	virsh format, then virsh also creates and connects it to the
	network successfully.)

	I post this to the list as evidence that this is not just a
	problem with SuSE."