From: George Dunlap <george.dunlap@eu.citrix.com>
To: AL13N <alien@rmail.be>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: booting from HVM (?pv?)
Date: Tue, 25 Jun 2013 11:51:08 +0100 [thread overview]
Message-ID: <51C9761C.8070200@eu.citrix.com> (raw)
In-Reply-To: <e0ea16f1e0f9f55f609ea16bfbbcb1ba.squirrel@mail.rmail.be>
On 06/25/2013 11:47 AM, AL13N wrote:
>> On Mon, Jun 24, 2013 at 9:21 PM, AL13N <alien@rmail.be> wrote:
>>> Hi,
>>>
>>> I'm the Mageia XEN packager and during QA, we stumbled into a problem.
>>>
>>> in fact, we wanted to test Mageia 3 installation on a HVM.
>>>
>>> so, we had a sparse image and a iso file:
>>>
>>> [ 'file:/opt/testhvm.img,sda,w', 'file:/opt/mageialive.iso,hdb:cdrom,r'
>>> ]
>>>
>>> the live booted, and was able to install to disk, but it never seemed to
>>> boot
>>> after the install... (for some reason)
>>>
>>> in the end, this "worked" when we changed to:
>>>
>>> [ 'file:/opt/testhvm.img,xvda,w', 'file:/opt/testhvm.img,sda,w' ]
>>>
>>> apparently 'xvda' to get grub to boot the kernel; and 'sda' so that it
>>> could
>>> start...
>>
>> My HVM Linux config files have 'hda' instead of 'sda' -- can you try
>> that instead?
>>
>> Normally what happens is that qemu begins by exposing the hda device
>> to the guest, to boot via grub; but when the Xen PV drivers in the
>> Linux kernel come up, they write to a magic port which causes the
>> physical hda device to disappear. I *think* then that the Xen PV
>> drivers actually take over that major/minor, so that further reads and
>> writes to the hda go through the PV protocol instead.
>>
>> All of this might get mixed up if you're using sda instead.
>>
>> -George
>>
>
>
> well, hda is what we tried first, but we couldn't see the disk from the
> live system with hda. only sda seemed to work for that...
When you say, "we couldn't see the disk from the live system", you're
talking about booting from the live CD?
If post-install you try 'hda' and it boots (after changing the grub and
/etc/fstab if necessary), then I would suspect that there's a problem
with your live CD kernel. Do you use a different kernel image, and/or
are the modules for the Xen PV devices not included?
-George
next prev parent reply other threads:[~2013-06-25 10:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-24 20:21 booting from HVM (?pv?) AL13N
2013-06-25 9:38 ` George Dunlap
2013-06-25 10:47 ` AL13N
2013-06-25 10:51 ` George Dunlap [this message]
2013-06-25 10:57 ` AL13N
2013-06-25 11:09 ` George Dunlap
2013-06-25 12:18 ` AL13N
2013-06-25 12:28 ` Alex Bligh
2013-06-25 13:18 ` AL13N
2013-06-25 15:39 ` Pasi Kärkkäinen
2013-06-25 17:21 ` AL13N
2013-06-25 17:25 ` Pasi Kärkkäinen
2013-06-25 17:32 ` AL13N
2013-06-25 17:35 ` Pasi Kärkkäinen
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=51C9761C.8070200@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=alien@rmail.be \
--cc=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xen.org \
/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.