Yes, Kevin's fix is now checked in as 8474.
Please see if this resolves the problem.
Thanks,
Dan
> -----Original Message-----
> From: Tian, Kevin [mailto:kevin.tian@xxxxxxxxx]
> Sent: Thursday, January 05, 2006 4:58 AM
> To: yo.fujita; Magenheimer, Dan (HP Labs Fort Collins);
> xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> Subject: RE: [Xen-ia64-devel] DomU does not start.
>
> Hi, Fujita,
> I'm not sure about your target memory layout. But
> generally if you plug a >=2G memory bank in your box, you may
> need the patch I sent out yesterday to disable virtual memmap
> in guest. Or else vbd driver doesn't work. If you only have
> 1G-like system, then that's possibly a different issue.
>
> Thanks,
> Kevin
>
> >-----Original Message-----
> >From: yo.fujita [mailto:yo.fujita@xxxxxxxxxxxxxxxx]
> >Sent: 2006年1月5日 19:07
> >To: 'Magenheimer, Dan (HP Labs Fort Collins)'; Tian, Kevin;
> >xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> >Subject: RE: [Xen-ia64-devel] DomU does not start.
> >
> >Hi Dan, Kevin,
> >
> >Sorry for a late mail. And, thanks for thinking about my problem.
> >>8734 seems to be a future changeset. ;-)
> >Oops! Sorry it's a typing miss...
> >
> >I tried the start of domU with changeset:8473 this time.
> >problem of RAMDISK was able to be cleared this time.
> >But, the problem occurred newly.
> >It stops with the mount of root. ( Please look at an attached log.)
> >I investigated a little.
> >stop is done with ext3_fill_super of sb_bread.
> >( /linux-2.6.12-xenU/fs/ext3/super.c )
> >
> >this is my Configfile. Is there a wrong place?
> >
> >kernel = "/boot/vmlinux-2.6.12-xenU"
> >ramdisk = "/boot/initrd-2.6.12-xenU.img"
> >memory = 512
> >name = "rhel4-2"
> >disk = [ 'file:/root/rhel4.img,hda1,w' ]
> >root = "/dev/hda1 ro"
> >extra = "nomca nosmp xencons=tty0 console=tty0 3"
> >
> >thanks,
> >Fujita
> >
> >> -----Original Message-----
> >> From: Magenheimer, Dan (HP Labs Fort Collins)
> >[mailto:dan.magenheimer@xxxxxx]
> >> Sent: Friday, December 30, 2005 7:37 AM
> >> To: Tian, Kevin; yo.fujita; xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> >> Subject: RE: [Xen-ia64-devel] DomU does not start.
> >>
> >> Committed as cset 8436. Fujita, please test to see
> >> if this solves the problem with booting domU with and
> >> without initrd.
> >>
> >> Thanks,
> >> Dan
> >>
> >> > -----Original Message-----
> >> > From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
> >> > [mailto:xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf
> >> > Of Tian, Kevin
> >> > Sent: Thursday, December 29, 2005 2:23 AM
> >> > To: Tian, Kevin; yo.fujita; xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> >> > Subject: RE: [Xen-ia64-devel] DomU does not start.
> >> >
> >> > BTW, we may need this patch:
> >> >
> >> > diff -r f218e6ba2653 tools/libxc/xc_linux_build.c
> >> > --- a/tools/libxc/xc_linux_build.c Fri Dec 23 21:14:21 2005
> >> > +++ b/tools/libxc/xc_linux_build.c Thu Dec 29 16:43:19 2005
> >> > @@ -397,6 +397,9 @@
> >> > {
> >> > ctxt->initrd.start = vinitrd_start;
> >> > ctxt->initrd.size = initrd_len;
> >> > + } else {
> >> > + ctxt->initrd.start = 0;
> >> > + ctxt->initrd.size = 0;
> >> > }
> >> > strncpy((char *)ctxt->cmdline, cmdline,
> IA64_COMMAND_LINE_SIZE);
> >> > ctxt->cmdline[IA64_COMMAND_LINE_SIZE-1] = '\0';
> >> >
> >> > Thanks,
> >> > Kevin
> >> >
> >> > >-----Original Message-----
> >> > >From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
> >> > >[mailto:xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx] On
> >> > Behalf Of Tian, Kevin
> >> > >Sent: 2005年12月29日 17:04
> >> > >To: yo.fujita; xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> >> > >Subject: RE: [Xen-ia64-devel] DomU does not start.
> >> > >
> >> > >>From: yo.fujita
> >> > >>Sent: 2005年12月29日 16:20
> >> > >>Hi
> >> > >>
> >> > >>I can't start domU after changeset8372.
> >> > >>applied two patches of changeset 8734 after that.
> >> > >>However, the following message displays and DomU does
> not start.
> >> > >>
> >> > >>"RAMDISK: Couldn't find valid RAM disk image starting at 0 ."
> >> > >>
> >> > >>Don't someone have information?
> >> > >>
> >> > >>Thanks
> >> > >>Fujita
> >> > >
> >> > >8734 seems to be a future changeset. ;-)
> >> > >
> >> > >Do you need initrd to boot your domU image? If yes, you may
> >> > add an option in
> >> > >example file:
> >> > >
> >> > >ramdisk = "initrd_name"
> >> > >
> >> > >If no, can you try appending a "noinitrd" to extra field in
> >> > your example file like:
> >> > >
> >> > >Extra = "4 noinitrd"
> >> > >
> >> > >I guess there's some issue when domU image file doesn't
> >> > require an initrd.
> >> > >
> >> > >Thanks,
> >> > >Kevin
> >> > >
> >> > >_______________________________________________
> >> > >Xen-ia64-devel mailing list
> >> > >Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> >> > >http://lists.xensource.com/xen-ia64-devel
> >> >
> >> > _______________________________________________
> >> > Xen-ia64-devel mailing list
> >> > Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> >> > http://lists.xensource.com/xen-ia64-devel
> >> >
>
_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel
|
Home