All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabio Fantoni <fabio.fantoni@m2r.biz>
To: xen-devel <xen-devel@lists.xensource.com>,
	Ian Campbell <ian.campbell@citrix.com>,
	Ian Jackson <ian.jackson@eu.citrix.com>,
	George Dunlap <George.Dunlap@eu.citrix.com>
Subject: Xen-unstable failed to start Sid pv domU with pygrub after latest upgrades
Date: Fri, 08 Nov 2013 12:18:15 +0100	[thread overview]
Message-ID: <527CC877.6020408@m2r.biz> (raw)

[-- Attachment #1: Type: text/plain, Size: 832 bytes --]

This morning I booted correctly Sid (Debian unstable) pv domU with xl 
and with pygrub on xen-unstable commit 
68bd172e6fa565899c846eb72755c8ffd8562c8a.
After an aptitude full-upgrade, the Sid domU fails to boot:
> xl create /etc/xen/sid.cfg
> Parsing config from /etc/xen/sid.cfg
> libxl: error: libxl_bootloader.c:628:bootloader_finished: bootloader 
> failed - consult logfile /var/log/xen/bootloader.11.log
> libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: 
> bootloader [22895] exited with error status 1
> libxl: error: libxl_create.c:972:domcreate_rebuild_done: cannot 
> (re-)build domain: -3
On attachment /var/log/xen/bootloader.11.log.
Replacing the domU's grub.cfg with minimal grub1 configuration solve the 
boot problem.
If you need more details/tests tell me and I'll post them.

Thanks for any reply.


[-- Attachment #2: bootloader.11.log --]
[-- Type: application/octet-stream, Size: 2407 bytes --]

[-- Attachment #3: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

             reply	other threads:[~2013-11-08 11:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-08 11:18 Fabio Fantoni [this message]
2013-11-08 11:46 ` Xen-unstable failed to start Sid pv domU with pygrub after latest upgrades George Dunlap
2013-11-08 12:23   ` Fabio Fantoni

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=527CC877.6020408@m2r.biz \
    --to=fabio.fantoni@m2r.biz \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.