Hi,
Henning Sprang wrote:
[...]
When trying to start the vm, I get the error:
"Error: Error creating domain: Kernel image does not exist:
/boot/vmlinuz-2.6.16-1.2080_FC5xenU"
I further investigated that.
Fedora seems to require to explicitly set the bootloader to pygrub in
the domU config.
When doing so, I get the error:
[root@localhost ~]# xm create -c basic-debian
Using config file "/etc/xen/basic-debian".
Traceback (most recent call last):
File "/usr/bin/pygrub", line 256, in ?
cf = get_config(file, isconfig)
File "/usr/bin/pygrub", line 119, in get_config
fs = fstype.open_fs(fn, offset)
File "/usr/lib/python2.4/site-packages/grub/fsys/ext2/__init__.py",
line 35, in open_fs
return Ext2Fs(fn, offset = offset)
ValueError: unable to open file
Error: Boot loader didn't return any data!
Which seems to be further described here:
http://lists.xensource.com/archives/html/xen-users/2006-03/msg00721.html
But I cannot find a solution. Does that mean I cannot use xen images
created in block devices the "normal" way all howto's about xen describe?
What Do I have to do to create a xen domU manually, or use a xen disk
image created on another machine/distribution on Fedora?
Why is Fedora not able to recognize the kernel variable in the config
file correctly as it is usually done on other distributions?
Henning
