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

[Juergen Gross <jgross@xxxxxxxx>]

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/

> 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.


Juergen

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