2:28 a.m.
Hi All,
I am trying to use fullyvirtualized guest direct kernel boot, but all I see
is the following error:
libvir: Xen Daemon error : POST operation failed: (xend.err 'Error creating
domain: (2, \'Invalid kernel\', "elf_xen_note_check: ERROR: Not a Xen-ELF
image: No ELF notes or \'__xen_guest\' section found.\\n")')
Kernel, initrd and root file system are extracted from working Fedora 9 disk
image without any additional tinkering. Guest Fedora is clean and was
installed from scratch. When I use this whole disk image with
fullyvirtualized guest BIOS boot with, everything works fine. I also tried
paravirtualized guest bootloader with another linux kernel and it also works
fine. Xen version is 3.2.1-rc1-pre. Host OS is Ubuntu Hardy.
Here is the libvirt config for direct kernel boot:
<domain type='xen' id='18'>
<name>test1</name>
<uuid>4dea22b31d52d8f32516782e98ab3fa0</uuid>
<os>
<type>linux</type>
<loader>/usr/lib/xen/boot/hvmloader</loader>
<kernel>/tmp/vmlinuz-2.6.25-14.fc9.i686</kernel>
<initrd>/tmp/initrd-2.6.25-14.fc9.i686.img</initrd>
<root>/dev/sda1</root>
<cmdline>ro</cmdline>
</os>
<memory>524288</memory>
<vcpu>1</vcpu>
<devices>
<emulator>/usr/lib/xen/bin/qemu-dm</emulator>
<disk type='file'>
<driver name="tap" type="aio"/>
<source file='/tmp/f9_disassembled/root.img'/>
<target dev='sda1'/>
</disk>
<disk type='file'>
<driver name="tap" type="aio"/>
<source file='/tmp/swap'/>
<target dev='sda3'/>
</disk>
<interface type='bridge'>
<source bridge='eth0'/>
<mac address='00:16:3e:5d:c7:9e'/>
<script path='/etc/xen/scripts/vif-bridge'/>
</interface>
<graphics type='vnc' port='5904'/>
</devices>
</domain>
What do you think can be the cause of this issue?
--
Thanks, Max
<libvir-list(a)redhat.com>
2:34 a.m.
On Wed, Nov 05, 2008 at 09:28:16PM +0300, Max Martynov wrote:
Hi All,
I am trying to use fullyvirtualized guest direct kernel boot, but all I see
is the following error:
libvir: Xen Daemon error : POST operation failed: (xend.err 'Error creating
domain: (2, \'Invalid kernel\', "elf_xen_note_check: ERROR: Not a Xen-ELF
image: No ELF notes or \'__xen_guest\' section found.\\n")')
Kernel, initrd and root file system are extracted from working Fedora 9 disk
image without any additional tinkering. Guest Fedora is clean and was
installed from scratch. When I use this whole disk image with
fullyvirtualized guest BIOS boot with, everything works fine. I also tried
paravirtualized guest bootloader with another linux kernel and it also works
fine. Xen version is 3.2.1-rc1-pre. Host OS is Ubuntu Hardy.
That Xen is too probably old - you need 3.3.x or newer. The Xen 3.2 in
Fedora has a backport of this functionality, and I doubt the Ubuntu xen
has copied that.
Here is the libvirt config for direct kernel boot:
<domain type='xen' id='18'>
<name>test1</name>
<uuid>4dea22b31d52d8f32516782e98ab3fa0</uuid>
<os>
<type>linux</type>
This tag is telling Xen todo a paravirt guest, but you say you want
a fullvirt one, so replace this with
<type>hvm</type>
<loader>/usr/lib/xen/boot/hvmloader</loader>
<kernel>/tmp/vmlinuz-2.6.25-14.fc9.i686</kernel>
<initrd>/tmp/initrd-2.6.25-14.fc9.i686.img</initrd>
<root>/dev/sda1</root>
<cmdline>ro</cmdline>
</os>
<memory>524288</memory>
<vcpu>1</vcpu>
<devices>
<emulator>/usr/lib/xen/bin/qemu-dm</emulator>
<disk type='file'>
<driver name="tap" type="aio"/>
<source file='/tmp/f9_disassembled/root.img'/>
<target dev='sda1'/>
</disk>
<disk type='file'>
<driver name="tap" type="aio"/>
<source file='/tmp/swap'/>
<target dev='sda3'/>
</disk>
<interface type='bridge'>
<source bridge='eth0'/>
<mac address='00:16:3e:5d:c7:9e'/>
<script path='/etc/xen/scripts/vif-bridge'/>
</interface>
<graphics type='vnc' port='5904'/>
</devices>
</domain>
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 :|
2:39 a.m.
On Wed, Nov 5, 2008 at 9:34 PM, Daniel P. Berrange <berrange(a)redhat.com> wrote:
On Wed, Nov 05, 2008 at 09:28:16PM +0300, Max Martynov wrote:
> Hi All,
>
> I am trying to use fullyvirtualized guest direct kernel boot, but all I see
> is the following error:
> libvir: Xen Daemon error : POST operation failed: (xend.err 'Error creating
> domain: (2, \'Invalid kernel\', "elf_xen_note_check: ERROR: Not a
Xen-ELF
> image: No ELF notes or \'__xen_guest\' section found.\\n")')
>
> Kernel, initrd and root file system are extracted from working Fedora 9 disk
> image without any additional tinkering. Guest Fedora is clean and was
> installed from scratch. When I use this whole disk image with
> fullyvirtualized guest BIOS boot with, everything works fine. I also tried
> paravirtualized guest bootloader with another linux kernel and it also works
> fine. Xen version is 3.2.1-rc1-pre. Host OS is Ubuntu Hardy.
That Xen is too probably old - you need 3.3.x or newer. The Xen 3.2 in
Fedora has a backport of this functionality, and I doubt the Ubuntu xen
has copied that.
Thanks, I will try to do that. However, the sample for
fullyvirtualized guest direct kernel boot uses Fedora.
> Here is the libvirt config for direct kernel boot:
> <domain type='xen' id='18'>
> <name>test1</name>
> <uuid>4dea22b31d52d8f32516782e98ab3fa0</uuid>
> <os>
> <type>linux</type>
This tag is telling Xen todo a paravirt guest, but you say you want
a fullvirt one, so replace this with
<type>hvm</type>
Yes, this was just a typo, because I tried
several variants. It was
hvm when I tested it.
> <loader>/usr/lib/xen/boot/hvmloader</loader>
> <kernel>/tmp/vmlinuz-2.6.25-14.fc9.i686</kernel>
> <initrd>/tmp/initrd-2.6.25-14.fc9.i686.img</initrd>
> <root>/dev/sda1</root>
> <cmdline>ro</cmdline>
> </os>
> <memory>524288</memory>
> <vcpu>1</vcpu>
> <devices>
> <emulator>/usr/lib/xen/bin/qemu-dm</emulator>
> <disk type='file'>
> <driver name="tap" type="aio"/>
> <source file='/tmp/f9_disassembled/root.img'/>
> <target dev='sda1'/>
> </disk>
> <disk type='file'>
> <driver name="tap" type="aio"/>
> <source file='/tmp/swap'/>
> <target dev='sda3'/>
> </disk>
> <interface type='bridge'>
> <source bridge='eth0'/>
> <mac address='00:16:3e:5d:c7:9e'/>
> <script path='/etc/xen/scripts/vif-bridge'/>
> </interface>
> <graphics type='vnc' port='5904'/>
> </devices>
> </domain>
>
>
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 :|
2:07 a.m.
> > Kernel, initrd and root file system are extracted from
working Fedora 9 disk
> > image without any additional tinkering. Guest Fedora is clean and was
> > installed from scratch. When I use this whole disk image with
> > fullyvirtualized guest BIOS boot with, everything works fine. I also tried
> > paravirtualized guest bootloader with another linux kernel and it also works
> > fine. Xen version is 3.2.1-rc1-pre. Host OS is Ubuntu Hardy.
>
> That Xen is too probably old - you need 3.3.x or newer. The Xen 3.2 in
> Fedora has a backport of this functionality, and I doubt the Ubuntu xen
> has copied that.
Thanks, I will try to do that. However, the sample for
fullyvirtualized guest direct kernel boot uses Fedora.
>
I have tried to perform the same experiment with Xen 3.3.0, and the
same error occured. Moreover, I have tried to use the kernel from my
host Ubuntu (vmlinuz-2.6.24-21-server) and error was the same.
However, using vmlinuz-2.6.24-21-xen kernel still worked fine, but in
paravirtualized mode I suppose.
All the kernels and initrds I have tried to use were taken from /boot/
without any additional modifications. Is it correct usage for full
virtualization or some tuning should be performed? Or maybe Ubuntu as
a host doesn't support full virtualization for direct kernel boot at
all?
--
Max
5838
days inactive
5839
days old
3 comments
2 participants
participants (2)
-
Daniel P. Berrange -
Max Martynov