From: Ian Campbell <Ian.Campbell@citrix.com>
To: Sandi Romih <romihs.forums@gmail.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Stefano Stabellini <stefano.stabellini@citrix.com>
Subject: Re: Failed to run bootloader
Date: Mon, 23 Apr 2012 09:41:56 +0100 [thread overview]
Message-ID: <1335170516.30700.12.camel@zakaz.uk.xensource.com> (raw)
In-Reply-To: <CAFoWEVMTBhBO1hgW0qeYKLeLwCKrigd5a0VFKT7S_5qi7KK9UQ@mail.gmail.com>
On Sat, 2012-04-21 at 12:04 +0100, Sandi Romih wrote:
> [...]
> kernel = "/etc/xen/kernels/oi151a/unix"
> ramdisk = "/etc/xen/kernels/oi151a/boot_archive"
I forget how this works -- do you need to comment these out while using
pygrub or are these paths inside the ISO?
[...]
> disk =
> [ 'file:/mnt/media/comp_files/os-iso/oi151a.iso,xvdc:cdrom,r' ,
> 'phy:/dev/dom0/oi_boot,xvda,w' ]
> bootloader = "/usr/bin/pygrub"
Sadly I don't think xl is currently capable of booting using pygrub from
a file:/// type device.
I expect this will be resolved by Stefano's "qdisk local attach" series
which was on the list last week.
In the meantime as a workaround you could try using losetup on the iso
and pointing xl at phy:/dev/loop$N.
Ian.
next prev parent reply other threads:[~2012-04-23 8:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-21 11:04 Failed to run bootloader Sandi Romih
2012-04-23 8:41 ` Ian Campbell [this message]
2012-04-23 11:29 ` Stefano Stabellini
2012-04-23 11:30 ` Ian Campbell
2012-04-24 20:28 ` Sandi Romih
[not found] ` <1335371921.28015.56.camel@zakaz.uk.xensource.com>
[not found] ` <CAFoWEVOkg5q9iyKcxM_LAkBgiBC_xCiVLqfFDGAtt2HzuWr9Rw@mail.gmail.com>
2012-04-26 7:30 ` Ian Campbell
2012-04-26 9:40 ` Sandi Romih
2012-04-27 18:11 ` Sandi Romih
2012-04-27 18:19 ` Ian Campbell
2012-04-27 23:06 ` Sandi Romih
2012-04-28 5:45 ` Ian Campbell
2012-04-28 6:12 ` Ian Campbell
[not found] ` <4F953D7B.2090608@citrix.com>
2012-04-24 20:04 ` Sandi Romih
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=1335170516.30700.12.camel@zakaz.uk.xensource.com \
--to=ian.campbell@citrix.com \
--cc=romihs.forums@gmail.com \
--cc=stefano.stabellini@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.