** Changed in: nova
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1531197
Title:
Xen host can't boot a instance with btrfs as filesystem
Status in OpenStack Compute (nova):
Invalid
Bug description:
### tested with Juno (latest commit from git) and also with Liberty)
###
Starting a para-virtualized instance on an Xen host where the instance
has a btrfs filesystem leads to:
2015-09-04 14:51:31.325 5359 TRACE nova.compute.manager [instance:
f4889cf9-f083
-4c48-b036-655f46c5d819] libvirtError: POST operation failed: xend_post:
error f
rom xen daemon: (xend.err "Boot loader didn't return any data!")
The missing thing in the libvirt domain config is the <kernel>
parameter:
<os>
<kernel>/usr/lib/grub2/x86_64-xen/grub.xen</kernel>
</os>
"/usr/lib/grub2/x86_64-xen/grub.xen" is the correct path on a SUSE
system. I guess on Debian it's "/usr/lib/grub-xen/grub-i386-xen.bin".
The default, /usr/bin/pygrub, doesn't support btrfs .
Steps to reproduce:
1) Create a image: openstack image create --file
openSUSE-Leap-42.1-JeOS-for-XEN.x86_64.qcow2 --public --disk-format qcow2
--property hypervisor_type=xen --property vm_mode=xen xen-image
2) boot a VM: nova boot --flavor my-flavor --image xen-image testvm
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1531197/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
