Re: [Xen-users] xenfs: not registering fielsystem on no-xen platform

[jrun <darwinskernel@xxxxxxxxx>]

On Wed, May 11, 2016 at 04:16:29PM +0200, Juergen Gross wrote:
> On 11/05/16 15:59, jrun wrote:
> > On Wed, May 11, 2016 at 03:37:17PM +0200, Juergen Gross wrote:
> >> As I suspected: you only boot the kernel. Normally the boot entries
> >> for Xen are between the lines:
> >>
> >> ### BEGIN /etc/grub.d/20_linux_xen ###
> >> ### END /etc/grub.d/20_linux_xen ###
> >>
> >> They look like:
> >>
> >> ...
> >> multiboot /boot/xen.gz ...
> >> module  /boot/vmlinuz-4.1.20-11-xen ...
> >> ...
> > 
> > grub-mkconfig doesn't pick up 20_linux_xen for some reason. looking into
> > it... thanks.
> > 
> >> So you are booting the Xen hypervisor which will then start Linux as
> >> dom0. You'll probably have to install Xen (either from your distribution
> >> or by building it by yourself).
> >>
> >>
> >> Juergen
> > 
> > the distro (slackware) has a script for creating xen.gz by calling
> > mkinitrd.
> 
> This seems unlikely. mkinitrd is used to build a ramdisk (that's the
> reason for it's name: MaKe INITial RamDisk). xen.gz should be installed
> separately, see e.g.
> 
> https://slackbuilds.org/repository/14.1/system/xen/

that's what i've been trying; see system/xen/dom0/kernel-xen.sh for the
mkinitrd call which creates initrd-$KERNEL-xen.gz

> > but then when i try to boot off the resulting xen.gz grub says
> > 'wrong magic number'. can i have something like this:
> > 
> > multiboot /boot/vmlinuz
> > module  /boot/vmlinuz
> > 
> > i.e. can the hypervisor (which btw i understand Xen above to be the
> > hypervisor) and dom0 be the same kernel image?
> 
> No, they are built from completely different sources.

would you care to give me some pointers for building xen.gz? i will have to
do it myself it seems.


--jrun

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users