I recently started having this issue after enabling nat networking for my
domU.
The domU is booting the 2.6.32.27 kernel with an initrd i generated and was
using before just fine. Output is as follows. Any help would be appreciated.
Here is the output I get:
0.161289] xvde1: detected capacity change from 0 to
10486808576> [ 0.260033] XENBUS: Device with no driver: device/console/0
> [ 0.260065] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
> [ 0.260173] Freeing unused kernel memory: 460k freed
> [ 0.260501] Write protecting the kernel read-only data: 3996k
> Loading, please wait...
> [ 0.316327] udev[43]: starting version 164
> Begin: Loading essential drivers ... [ 0.481641] SCSI subsystem
> initialized
> done.
> Begin: Running /scripts/init-premount ... done.
> Begin: Mounting root file system ... Begin: Running /scripts/local-top ...
> done.
> Begin: Waiting for root file system ... done.
> (drops to Busybox from here)
Here is my config:
kernel = "/boot/vmlinuz-2.6.32.27"> ramdisk = "/boot/initrd.img-2.6.32.27-xen"
> memory = 512
> vcpus = 1
> name = "ubuntu910_3"
> disk >
[''file:/media/vm/appliances/ubuntu910_3/ubuntu.9-10.x86-64.img,sda1,w'']
> root = "/dev/xvda1 ro"
> extra = "xencons=tty"
Chris Benninger
University of Victoria, Computer Science
cbenning@cs.uvic.ca
http://benninger.ca
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
On Tue, Jan 11, 2011 at 6:09 AM, chrisbenninger <chrisbenninger@gmail.com> wrote:> The domU is booting the 2.6.32.27 kernel with an initrd i generated and was > using before just fine.Really? 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 again). It might be easier if you use LABEL or UUID. That way you don''t have to worry about device name change. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tue, Jan 11, 2011 at 7:32 AM, chrisbenninger <chrisbenninger@gmail.com> wrote:> Whoops,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-2.6.32.27" >> ramdisk = "/boot/initrd.img-2.6.32.27-xen" >> memory = 512 >> vcpus = 1 >> name = "ubuntu910_3" >> disk >> [''file:/media/vm/appliances/ubuntu910_3/ubuntu.9-10.x86-64.img,sda1,w''] >> 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 > cbenning@cs.uvic.ca > http://benninger.ca > > > On Mon, Jan 10, 2011 at 4:21 PM, Fajar A. Nugraha <list@fajar.net> wrote: >> >> On Tue, Jan 11, 2011 at 6:09 AM, chrisbenninger >> <chrisbenninger@gmail.com> wrote: >> > The domU is booting the 2.6.32.27 kernel with an initrd i generated and >> > was >> > using before just fine. >> >> Really? >> 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 >> again). >> >> It might be easier if you use LABEL or UUID. That way you don''t have >> to worry about device name change. >> >> -- >> Fajar > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I generated a new image and this time it worked. I guess the internals of the image didn''t match the configuration in the .cfg file? Chris Benninger University of Victoria, Computer Science cbenning@cs.uvic.ca http://benninger.ca On Mon, Jan 10, 2011 at 6:28 PM, Fajar A. Nugraha <list@fajar.net> wrote:> On Tue, Jan 11, 2011 at 7:32 AM, chrisbenninger > <chrisbenninger@gmail.com> wrote: > > Whoops, > > 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-2.6.32.27" > >> ramdisk = "/boot/initrd.img-2.6.32.27-xen" > >> memory = 512 > >> vcpus = 1 > >> name = "ubuntu910_3" > >> disk > >> [''file:/media/vm/appliances/ubuntu910_3/ubuntu.9-10.x86-64.img,sda1,w''] > >> 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 > > cbenning@cs.uvic.ca > > http://benninger.ca > > > > > > On Mon, Jan 10, 2011 at 4:21 PM, Fajar A. Nugraha <list@fajar.net> > wrote: > >> > >> On Tue, Jan 11, 2011 at 6:09 AM, chrisbenninger > >> <chrisbenninger@gmail.com> wrote: > >> > The domU is booting the 2.6.32.27 kernel with an initrd i generated > and > >> > was > >> > using before just fine. > >> > >> Really? > >> 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 > >> again). > >> > >> It might be easier if you use LABEL or UUID. That way you don''t have > >> to worry about device name change. > >> > >> -- > >> Fajar > > > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users