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

[erin.balid@inoutbox.com]

Ian.

On Tue, Jan 24, 2012, at 04:41 PM, Ian Campbell wrote:
> brINT is not the name you've been quoting before (which was br0). Are
> you running these tests on a variety of different systems with different
> configurations?
>
> It would be really helpful for those of us trying to help you if you
> could use the same system with the same setup (modulo requested changes)
> for the entirety of this conversation. Otherwise it becomes rather hard
> for us to correlate the facts.
> 
> In this case I now have to ask if you are sure that you used the
> appropriate "bridge=brINT" in your guest configuration instead of
> "bridge=br0" which you had before.

No, the same system.  Just a different bridge config file because I've
read some speculation re: bridge naming requirements, and have been
testing it -- in response to others that are trying to help me.

The email to this list was just a copy and paste problem from the notes
I'm trying to keep.

Returning to just =br0, the problem still exists exactly as I reported
above.  I can repost everything if you'd like to see that. Just to
remind, there are now at least 3 persons reporting similar problems with
no network access with xl-created Guests.

> At this point I'm afraid my only suggesting is to drop "echo made it to
> XXX" breadcrumbs throughout the script and try to narrow down to the
> line which exits.

I'll give that a try and report.

> You could also perhaps run "udevadm monitor" in another window while
> starting the guest, so wee can see what events you are actually seeing.

xl create /etc/xen/vm/test.cfg
 Parsing config file /etc/xen/vm/test.cfg
 Daemon running with PID 29685

xl list
 Name                                        ID   Mem VCPUs      State  
 Time(s)
 Domain-0                                     0  1010     1     r-----  
  2524.2
 test                                         8  2048     2     -b----  
     7.0

xl console test
 login ...

@ the Guest
dmesg | egrep -i "bus|eth|dri|pci"
 [    0.157505] PCI: Fatal: No config space access function found
 [    0.157512] PCI: setting up Xen PCI frontend stub
 [    0.157878] xen_mem: Initialising balloon driver.
 [    0.160157] PCI: System does not support PCI
 [    0.160157] PCI: System does not support PCI
 [    0.164020] PCI: max bus depth: 0 pci_try_num: 1
 [    0.166097] PCI: CLS 64 bytes
 [    0.227389] Block layer SCSI generic (bsg) driver version 0.4 loaded
 (major 253)
 [    0.227651] Non-volatile memory driver v1.3
 [    0.311840] Fixed MDIO Bus: probed
 [    0.412125] XENBUS: Device with no driver: device/vbd/51712
 [    0.412133] XENBUS: Device with no driver: device/vbd/51728
 [    0.412139] XENBUS: Device with no driver: device/vbd/51744
 [    0.412144] XENBUS: Device with no driver: device/vif/0
 [    0.412153]
 /home/abuild/rpmbuild/BUILD/kernel-xen-3.1.0/linux-3.1/drivers/rtc/hctosys.c:
 unable to open rtc device (rtc0)
 [    0.868480] netfront: Initialising virtual ethernet driver.

@ the Host
udevadm monitor
 monitor will print the received events for:
 UDEV - the event which udev sends out after rule processing
 KERNEL - the kernel uevent

 KERNEL[172855.382354] add      /devices/xen-backend/vbd-8-51712
 (xen-backend)
 KERNEL[172855.471281] add      /devices/xen-backend/vbd-8-51728
 (xen-backend)
 UDEV  [172855.491539] add      /devices/xen-backend/vbd-8-51712
 (xen-backend)
 KERNEL[172855.561121] add      /devices/xen-backend/vbd-8-51744
 (xen-backend)
 UDEV  [172855.579734] add      /devices/xen-backend/vbd-8-51728
 (xen-backend)
 KERNEL[172855.610413] add      /devices/xen-backend/vif-8-0
 (xen-backend)
 KERNEL[172855.635818] add      /devices/xen-backend/vif-8-0/net/vif8.0
 (net)
 KERNEL[172855.635839] add     
 /devices/xen-backend/vif-8-0/net/vif8.0/queues/rx-0 (queues)
 KERNEL[172855.635851] add     
 /devices/xen-backend/vif-8-0/net/vif8.0/queues/tx-0 (queues)
 KERNEL[172855.636154] online   /devices/xen-backend/vif-8-0
 (xen-backend)
 UDEV  [172855.655709] add      /devices/xen-backend/vif-8-0
 (xen-backend)
 UDEV  [172855.673354] add      /devices/xen-backend/vbd-8-51744
 (xen-backend)
 KERNEL[172855.700762] add      /devices/xen-backend/vfb-8-0
 (xen-backend)
 UDEV  [172855.706786] add      /devices/xen-backend/vfb-8-0
 (xen-backend)
 UDEV  [172855.720759] add      /devices/xen-backend/vif-8-0/net/vif8.0
 (net)
 UDEV  [172855.721130] add     
 /devices/xen-backend/vif-8-0/net/vif8.0/queues/rx-0 (queues)
 UDEV  [172855.721457] add     
 /devices/xen-backend/vif-8-0/net/vif8.0/queues/tx-0 (queues)
 KERNEL[172855.725625] add      /devices/xen-backend/vkbd-8-0
 (xen-backend)
 UDEV  [172855.732509] add      /devices/xen-backend/vkbd-8-0
 (xen-backend)
 KERNEL[172855.758430] add      /devices/xen-backend/console-8-0
 (xen-backend)
 UDEV  [172855.768396] add      /devices/xen-backend/console-8-0
 (xen-backend)
 UDEV  [172855.909030] online   /devices/xen-backend/vif-8-0
 (xen-backend)

> [...]
> > cat /var/log/xeb/console/*
> >  cat: /var/log/xeb/console/*: No such file or directory
> 
> Obviously a typo, but there's probably not too much of interest in the
> guest console logs.

Yes a typo.

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