From: 0bo0 <0.bugs.only.0@gmail.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: trying to debug xen4 & qemu-dm, Xen reports "core dump failed"
Date: Wed, 27 Jan 2010 08:20:41 -0800 [thread overview]
Message-ID: <c67eed301001270820g489ee4ve59e5537af975715@mail.gmail.com> (raw)
In-Reply-To: <C7861060.78F9%keir.fraser@eu.citrix.com>
On Wed, Jan 27, 2010 at 7:46 AM, Keir Fraser <keir.fraser@eu.citrix.com> 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 ...
next prev parent reply other threads:[~2010-01-27 16:20 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-26 18:36 trying to debug xen4 & qemu-dm, Xen reports "core dump failed" 0bo0
2010-01-26 18:36 ` Konrad Rzeszutek Wilk
2010-01-26 18:55 ` 0bo0
2010-01-26 21:10 ` Keir Fraser
2010-01-26 21:25 ` 0bo0
2010-01-26 21:38 ` Keir Fraser
2010-01-26 22:12 ` 0bo0
2010-01-26 22:30 ` Keir Fraser
2010-01-26 22:47 ` 0bo0
2010-01-27 0:25 ` 0bo0
2010-01-27 0:59 ` 0bo0
2010-01-27 8:27 ` Keir Fraser
2010-01-27 9:10 ` Keir Fraser
2010-01-27 15:41 ` 0bo0
2010-01-27 15:46 ` Keir Fraser
2010-01-27 16:19 ` Sander Eikelenboom
2010-01-27 16:22 ` 0bo0
2010-01-27 16:40 ` 0bo0
2010-01-28 22:08 ` 0bo0
2010-01-27 16:20 ` 0bo0 [this message]
2010-01-27 8:27 ` Keir Fraser
2010-01-29 0:21 ` Justin T. Gibbs
2010-01-29 0:42 ` 0bo0
2010-01-29 0:44 ` Justin T. Gibbs
2010-01-29 0:54 ` 0bo0
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c67eed301001270820g489ee4ve59e5537af975715@mail.gmail.com \
--to=0.bugs.only.0@gmail.com \
--cc=keir.fraser@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).