[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] Xen 4.1.3rc XendAPI warnings and XendDomainInfo Problems (Rebooting fails)

  • To: xen-users@xxxxxxxxxxxxx
  • From: mailing lists <thelists@xxxxxxxxx>
  • Date: Thu, 9 Aug 2012 11:26:18 -0400
  • Delivery-date: Thu, 09 Aug 2012 15:27:27 +0000
  • List-id: Xen user discussion <xen-users.lists.xen.org>


I'm having some trouble with Xen 4.1.3rc (previously 4.1.2 with the same issues).  The problem was first identified by a lack of rebooting capability from DomU's.  Ubuntu (PV), CentOS (PV), and Windows DomU systems would run well, but simply halt on reboot request.  The domain-specific log file shows this:

:> Done. Rebooting now
:> failed to run bootloader: -3

and within the xend.log:

:> ERROR (XendDomainInfo:3244) Had a bootloader specified, but no disks are bootable

After looking at the XendDomainInfo.py file, it appears that it's looking at a variable called "vbd_refs" to locate a bootable disk for the DomU.  The call to XendDomainInfo.create_from_dict shows vbd_refs as "[]".  Further examination of the logs shows some errors about the XendAPI, including the following:

:> WARNING (XendAPI:708) API call: VBD.set_type not found
:> WARNING (XendAPI:708) API call: session.get_all_records not found
:> WARNING (XendAPI:708) API call: event.get_record not found
:> WARNING (XendAPI:708) API call: event.get_all not found

A little information about my setup.

* Xen versions: 4.1.2 initially, then moved to 4.1.3rc to see if it resolved the issue.
* Kernel: 3.2.20 (tried 3.3 and 2.6 as well)
* Compiled the kernel with options as specified for a Dom0 on the Xen wiki.
* SELinux is disabled.
* The firewall (netfilter / iptables) is disabled.
* The xencommons and xend services are started.
* The Linux DomU images were obtained from stacklet; the Windows DomU was installed from ISO.  Both exhibit the same problem rebooting.
* When creating the DomU via "xl create", the full path to the config file is used.

And here's an example of my DomU config file:

bootloader = "/usr/bin/pygrub"
vcpus = 4
memory = 2048
name = "xxx_001"
vif = [ 'model=rtl8139,bridge=br0' ]
disk = [ 'phy:/dev/vbds/vm_p_xxx_root,xvda,w' ]

Has anyone seen this behavior before?  Have I missed something so obvious it's painful?  Any pointers would be much appreciated.

Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.