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

Re: [Xen-devel] trying to debug xen4 & qemu-dm, Xen reports "core dump failed"


  • To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
  • From: 0bo0 <0.bugs.only.0@xxxxxxxxx>
  • Date: Wed, 27 Jan 2010 08:20:41 -0800
  • Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Wed, 27 Jan 2010 08:21:05 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=JwB5ftiKWLPMXSJPSjubH1gErluCp+t6pRcw97c33ptH78hEESVsVs8VO+CQ4gTUS9 d/aqOQ2nu9+mJ8X9LRINfzOfkbERTUCbwttSlOlTQvLdnGgIpcbSZXhJyeXCMeUhLZ4O ZfOPU8TONmOgdo9GR+C3tYH9/hzjZgN3br8nU=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

On Wed, Jan 27, 2010 at 7:46 AM, Keir Fraser <keir.fraser@xxxxxxxxxxxxx> wrote:
> Hm, well, can you try stripping your config file right back (but still
> specifying vfb=['']) -- like removing all vbds for example? Obviously your
> guest will not successfully boot, but qemu-dm crashing is no doubt
> preventing your guest from even starting in the first place. So you can
> strip back and see whether at any point behaviour changes from 'qemu-dm
> crashes' to 'guest partially boots but then fails to find a rootfs'.

i've been stripping back as suggested, and trying different config
option combos.  nothing seems to make any difference to ability to
launch, so far, except removal of 'vfb=['']' :-/

i've switched to booting from a different local vmlinuz & initrd,
instead of either the domUbootloader.py or the distro release -xen
imgs, and have noticed one change in logs:

...
[2010-01-27 08:16:51 2217] WARNING (XendDomainInfo:2072) Domain has
crashed: name=nas id=30.
[2010-01-27 08:16:51 2217] DEBUG (XendDomainInfo:3061)
XendDomainInfo.destroy: domid=30
[2010-01-27 08:16:52 2217] DEBUG (pciif:460)
XendDomainInfo.handleAerStateWatch
[2010-01-27 08:16:52 2217] DEBUG (XendDomainInfo:1892)
XendDomainInfo.handleShutdownWatch
[2010-01-27 08:16:52 2217] DEBUG (XendDomainInfo:2416) Destroying
device model
[2010-01-27 08:16:53 2217] DEBUG (XendDomainInfo:2423) Releasing
devices
[2010-01-27 08:16:53 2217] DEBUG (XendDomainInfo:2429) Removing vif/0
[2010-01-27 08:16:53 2217] DEBUG (XendDomainInfo:1271)
XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0
[2010-01-27 08:16:54 2217] DEBUG (XendDomainInfo:2429) Removing vif/1
[2010-01-27 08:16:54 2217] DEBUG (XendDomainInfo:1271)
XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/1
[2010-01-27 08:16:54 2217] DEBUG (XendDomainInfo:2429) Removing vif/2
[2010-01-27 08:16:54 2217] DEBUG (XendDomainInfo:1271)
XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/2
[2010-01-27 08:16:54 2217] DEBUG (XendDomainInfo:2429) Removing vif/3
[2010-01-27 08:16:54 2217] DEBUG (XendDomainInfo:1271)
XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/3
[2010-01-27 08:16:54 2217] DEBUG (XendDomainInfo:2429) Removing vkbd/0
[2010-01-27 08:16:54 2217] DEBUG (XendDomainInfo:1271)
XendDomainInfo.destroyDevice: deviceClass = vkbd, device = vkbd/0
[2010-01-27 08:16:55 2217] DEBUG (XendDomainInfo:2429) Removing
vbd/51712
[2010-01-27 08:16:55 2217] DEBUG (XendDomainInfo:1271)
XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/51712
[2010-01-27 08:16:55 2217] DEBUG (XendDomainInfo:2429) Removing
vbd/51728
[2010-01-27 08:16:55 2217] DEBUG (XendDomainInfo:1271)
XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/51728
[2010-01-27 08:16:55 2217] DEBUG (XendDomainInfo:2429) Removing
vbd/51744
[2010-01-27 08:16:55 2217] DEBUG (XendDomainInfo:1271)
XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/51744
[2010-01-27 08:16:55 2217] DEBUG (XendDomainInfo:2429) Removing vfb/0
[2010-01-27 08:16:55 2217] DEBUG (XendDomainInfo:1271)
XendDomainInfo.destroyDevice: deviceClass = vfb, device = vfb/0
[2010-01-27 08:16:55 2217] DEBUG (XendDomainInfo:2429) Removing pci/0
[2010-01-27 08:16:55 2217] DEBUG (XendDomainInfo:1271)
XendDomainInfo.destroyDevice: deviceClass = pci, device = pci/0
[2010-01-27 08:16:55 2217] DEBUG (pciif:578) pci: unregister aer watch
[2010-01-27 08:16:55 2217] ERROR (XendConfig:1175) dumping sxp from
device controllers
Traceback (most recent call last):
  File "/usr/lib64/python2.6/site-packages/xen/xend/XendConfig.py",
line 1161, in to_sxp
    configs = controller.configurations(txn)
  File "/usr/lib64/python2.6/site-packages/xen/xend/server/DevController.py",
line 242, in configurations
    return map(lambda x: self.configuration(x, transaction),
self.deviceIDs(transaction))
  File "/usr/lib64/python2.6/site-packages/xen/xend/server/DevController.py",
line 242, in <lambda>
    return map(lambda x: self.configuration(x, transaction),
self.deviceIDs(transaction))
  File "/usr/lib64/python2.6/site-packages/xen/xend/server/DevController.py",
line 249, in configuration
    configDict = self.getDeviceConfiguration(devid, transaction)
  File "/usr/lib64/python2.6/site-packages/xen/xend/server/netif.py",
line 194, in getDeviceConfiguration
    y = self.readBackendTxn(transaction, devid, x)
  File "/usr/lib64/python2.6/site-packages/xen/xend/server/DevController.py",
line 447, in readBackendTxn
    raise VmError("Device %s not connected" % devid)
VmError: Device 2 not connected

the

[2010-01-27 08:16:55 2217] ERROR (XendConfig:1175) dumping sxp from
device controllers
Traceback (most recent call last):
...

are not there in other circumstances ...

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


 


Rackspace

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