Hi All,
I am trying to use fullyvirtualized guest direct kernel boot, but all I see
is the following error:
Error: (2, 'Invalid kernel', 'elf_init: not an ELF binary\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 cfg file for BIOS boot:
name = "xen_f9_hvm"
builder = "hvm"
memory = "512"
disk = [ 'tap:aio:/tmp/f9.img,hda,w', ]
vif = [ 'type=ioemu, mac=00:16:3e:5a:af:2a, bridge=eth0', ]
kernel = "/usr/lib/xen/boot/hvmloader"
device_model = '/usr/lib/xen/bin/qemu-dm'
vnc=1
vncunused=1
vnclisten="0.0.0.0"
vncconsole=1
apic=1
acpi=1
vcpus=1
serial = "pty" # enable serial console
on_reboot = 'restart'
on_crash = 'restart'
Here is the cfg file for fullyvirtualized guest direct kernel boot:
name = "xen_f9_hvm"
builder = "hvm"
memory = "512"
kernel = '/tmp/vmlinuz-2.6.25-14.fc9.i686'
ramdisk = '/tmp/initrd-2.6.25-14.fc9.i686.img'
root= '/dev/hda2 ro'
disk = [ 'tap:aio:/tmp/f9_disassembled/swap,hda1,w',
'tap:aio:/tmp/f9_disassembled/root.img,hda2,w', ]
vif = [ 'type=ioemu, mac=00:16:3e:5a:af:2a, bridge=eth0', ]
device_model = '/usr/lib/xen/bin/qemu-dm'
vnc=1
vncunused=1
vnclisten="0.0.0.0"
vncconsole=1
apic=1
acpi=1
vcpus=1
serial = "pty" # enable serial console
on_reboot = 'restart'
on_crash = 'restart'
What do you think can be the cause of this issue?
--
Thanks, Max
I am trying to use fullyvirtualized guest direct kernel boot, but all I see
is the following error:
Error: (2, 'Invalid kernel', 'elf_init: not an ELF binary\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 cfg file for BIOS boot:
name = "xen_f9_hvm"
builder = "hvm"
memory = "512"
disk = [ 'tap:aio:/tmp/f9.img,hda,w', ]
vif = [ 'type=ioemu, mac=00:16:3e:5a:af:2a, bridge=eth0', ]
kernel = "/usr/lib/xen/boot/hvmloader"
device_model = '/usr/lib/xen/bin/qemu-dm'
vnc=1
vncunused=1
vnclisten="0.0.0.0"
vncconsole=1
apic=1
acpi=1
vcpus=1
serial = "pty" # enable serial console
on_reboot = 'restart'
on_crash = 'restart'
Here is the cfg file for fullyvirtualized guest direct kernel boot:
name = "xen_f9_hvm"
builder = "hvm"
memory = "512"
kernel = '/tmp/vmlinuz-2.6.25-14.fc9.i686'
ramdisk = '/tmp/initrd-2.6.25-14.fc9.i686.img'
root= '/dev/hda2 ro'
disk = [ 'tap:aio:/tmp/f9_disassembled/swap,hda1,w',
'tap:aio:/tmp/f9_disassembled/root.img,hda2,w', ]
vif = [ 'type=ioemu, mac=00:16:3e:5a:af:2a, bridge=eth0', ]
device_model = '/usr/lib/xen/bin/qemu-dm'
vnc=1
vncunused=1
vnclisten="0.0.0.0"
vncconsole=1
apic=1
acpi=1
vcpus=1
serial = "pty" # enable serial console
on_reboot = 'restart'
on_crash = 'restart'
What do you think can be the cause of this issue?
--
Thanks, Max