[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] HVM direct boot broken in xen-unstable



Daniel, Ian:

No difference with "loader". The domain still disappears almost immediately.

I'll try to understand the original code (now that I know where to look) and 
see if I can understand what is happening.

Thanks for your help,

John Byrne


> -----Original Message-----
> From: Byrne, John (HP Labs)
> Sent: Monday, July 21, 2008 8:59 AM
> To: 'Daniel P. Berrange'; Ian Jackson
> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: RE: [Xen-devel] HVM direct boot broken in xen-unstable
>
> Daniel, Ian:
>
> The old ioemu version functions without the "loader" line which I was
> missing in my config. I'm testing to make sure that isn't the issue I'm
> seeing with the git version.
>
> John
>
>
> > -----Original Message-----
> > From: Daniel P. Berrange [mailto:berrange@xxxxxxxxxx]
> > Sent: Monday, July 21, 2008 8:52 AM
> > To: Ian Jackson
> > Cc: Byrne, John (HP Labs); xen-devel@xxxxxxxxxxxxxxxxxxx
> > Subject: Re: [Xen-devel] HVM direct boot broken in xen-unstable
> >
> > On Mon, Jul 21, 2008 at 04:46:17PM +0100, Ian Jackson wrote:
> > > Daniel P. Berrange writes ("Re: [Xen-devel] HVM direct boot broken
> in
> > xen-unstable"):
> > > > On Sat, Jul 19, 2008 at 12:52:07AM +0000, Byrne, John (HP Labs)
> > wrote:
> > > > > Hi!
> > > > >
> > > > > On x86_64, changeset 18081, running/building on rhel5, trying
> to
> > use
> > > > > the HVM direct boot causes the domain to reboot immediately and
> > then
> > > > > the log says the domain is restarting too rapidly. No obvious
> > hints
> > > > > as to where the problem is. If I build the in-tree ioemu code,
> > things
> > > > > work. Any clues as to where to look or how to get some useful
> > debugging
> > > > > output?
> > >
> > > Byrne, could you send me a copy of your config file so I can
> > reproduce
> > > this ?  Also, some idea of how you made (or how you obtained) the
> > > kernel image and initramfs.  I don't think I've ever done a direct
> > > kernel boot using this code (which is in patches supplied by
> Daniel)
> > > and offhand I can't seem to find the documentation.
> >
> > It works in the same way as booting PV off kernel+initrd - basically
> > take a HVM guest config file and add
> >
> >   loader="/usr/lib/xen/bin/hvmloader"
> >   kernel="/path/to/vmlinuz"
> >   ramdisk="/path/to/initrd"
> >
> > The vmlinuz & initrd  would typically be the ones for installation
> > of your distro, eg The $URL/images/pxeboot/ files for Fedora/RHEL
> >
> >
> http://download.fedora.redhat.com/pub/fedora/linux/releases/9/Fedora/i3
> > 86/os/images/pxeboot/
> >
> > It should boot your kernel & initrd and not pay attention to hardisk
> > or CDROM devices.
> >
> > As mentioned in the original commit logs, older kernels need to use
> the
> > evil helper, newer kernels should 'just work' (thanks to the
> > relocatable
> > kernel support).
> >
> > Daniel
> > --
> > |: Red Hat, Engineering, London   -o-
> > http://people.redhat.com/berrange/ :|
> > |: http://libvirt.org  -o-  http://virt-manager.org  -o-
> > http://ovirt.org :|
> > |: http://autobuild.org       -o-
> > http://search.cpan.org/~danberr/ :|
> > |: GnuPG: 7D3B9505  -o-  F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B
> > 9505 :|

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.