xenapi: pygrub running in domU
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Low
|
Mate Lakat |
Bug Description
While I was playing with boot from volume, I discovered that I end up with a:
PV instance if --image-id specified
HVM instance if --image-id is NOT specified
That should be an issue caused by not having the proper metadata without --image-id switch. But, as part of the investigation, interesting log entries appeared in cpu log:
DEBUG nova.virt.
WARNING nova.virt.
6c59aa does not boot correctly, try with image metadata.
DEBUG nova.virt.
DEBUG nova.openstack.
Error while executing pygrub! Please, ensure the binary is installed correctly, and available in your PATH; on some Linux distros, pygrub may be installed in /usr/lib/
TRACE nova.virt.
TRACE nova.virt.
TRACE nova.virt.
TRACE nova.virt.
TRACE nova.virt.
TRACE nova.virt.
TRACE nova.virt.
TRACE nova.virt.
TRACE nova.virt.
TRACE nova.virt.
TRACE nova.virt.
TRACE nova.virt.
TRACE nova.virt.
This error says, you need to have pygrub in domU. I think, we should really be calling down to dom0, and asking those tools to detect if the machine is PV bootable or not.
tags: | added: xenserver |
description: | updated |
Changed in nova: | |
importance: | Undecided → Medium |
importance: | Medium → Low |
status: | New → Triaged |
Changed in nova: | |
assignee: | nobody → Mate Lakat (mate-lakat) |
Changed in nova: | |
status: | Triaged → In Progress |
Changed in nova: | |
milestone: | none → havana-3 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | havana-3 → 2013.2 |
xen-utils package contains pygrub, although:
- it is not added to the path, it's only available at: xen-4.1/ bin/pygrub
/usr/lib/
- it could be out-of sync with the hypervisor's revision