Glad to hear it!
I'm planning on doing a guide to installing a F16 dom0/domU this
weekend, so I'll be sure to mention the bug and your workaround in it.
:)
On Wed, Nov 16, 2011 at 12:24 AM, Bud Bundy <budric@xxxxxxxxx> wrote:
> Kyle I think you're right. Installation was creating an extra partition. I
> erased it AND IT WORKED!!! THANK YOU.
> Also I made /boot ext3 just in case. But I think it was the extra 1 MB
> partition at the start of the disk.
>
> On Tue, Nov 15, 2011 at 3:06 AM, Kyle Lexmond <kyl191@xxxxxxxxxx> wrote:
>>
>> Ok, last thought. https://bugzilla.redhat.com/show_bug.cgi?id=745335
>> mentions a grub2 bug with pygrub's handling of F16's installation of
>> grub2. M Young summarized it as "By default Fedora 16 installs a Bios
>> boot partition as the first GPT partition to contain grub2 boot code,
>> and the grub2 configuration files are in the GPT second partition.
>> Pygrub currently only checks the first partition."
>>
>> http://lists.xensource.com/archives/html/xen-devel/2011-10/msg01121.html
>> has a mention of a patch, but I'm not sure if it's backported to Xen
>> 4.0, since it seems to be for Xen 4.1.
>>
>> On Tue, Nov 15, 2011 at 12:13 PM, Bud Bundy <budric@xxxxxxxxx> wrote:
>> > Kyle, thanks for the suggestions. The guest installs onto a logical
>> > volume
>> > in Dom 0 (/dev/storage/fc16). Then the guest further partitions that
>> > device
>> > into ext4 for /boot, and the rest is LVM and ext4 for / mount point. I
>> > don't think that's the problem. Nothing exotic like btrfs.
>> > Todd, thanks. I'm not sure I follow your suggestions. The link has a
>> > patch
>> > to pygrub. I can't install it since it's for Red Hat and I'm running
>> > Debian
>> > Squeeze. And there's nothing else in /var/log/xen/xend.log relevant to
>> > that
>> > domain that's failing to start.
>> >
>> >
>> >
>
>
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home