On Tue, Jan 11, 2011 at 7:32 AM, chrisbenninger
Please keep list traffic on the list. Someone else might experience
the same problem and can benefit from reading the archives.
> Sorry that xvda was leftover after I tried something, My apologies: The
> config is:
>> kernel = "/boot/vmlinuz-22.214.171.124"
>> ramdisk = "/boot/initrd.img-126.96.36.199-xen"
>> memory = 512
>> vcpus = 1
>> name = "ubuntu910_3"
>> disk =
>> root = "/dev/sda1 ro"
>> extra = "xencons=tty"
> The output is identical to before.
Then the suggestion is identical as before. Have you done it?
> I feel like I am missing a module in the
> initrd but I am not sure which.
> Chris Benninger
> University of Victoria, Computer Science
> On Mon, Jan 10, 2011 at 4:21 PM, Fajar A. Nugraha <list@xxxxxxxxx> wrote:
>> On Tue, Jan 11, 2011 at 6:09 AM, chrisbenninger
>> <chrisbenninger@xxxxxxxxx> wrote:
>> > The domU is booting the 188.8.131.52 kernel with an initrd i generated and
>> > was
>> > using before just fine.
>> Usually things don't "just break"
>> >> 0.161289] xvde1: detected capacity change from 0 to 10486808576
>> >> ['file:/media/vm/appliances/ubuntu910_3/ubuntu.9-10.x86-64.img,sda1,w']
>> >> root = "/dev/xvda1 ro"
>> If you only map one disk, then something weird is happening, cause the
>> boot log say it's detected as xvde1. Try changing "root" parameter on
>> your config file to that (or whatever the boot log shows if it changes
>> It might be easier if you use LABEL or UUID. That way you don't have
>> to worry about device name change.
Xen-users mailing list