yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #51047
[Bug 1183885] Re: pxe boot a guest in nova is not possible anymore
This wishlist bug has been open a year without any activity. I'm going
to move it to "Opinion / Wishlist", which is an easily-obtainable queue
of older requests that have come on. This bug can be reopened (set back
to "New") if someone decides to work on this.
** Changed in: nova
Status: Confirmed => Opinion
--
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/1183885
Title:
pxe boot a guest in nova is not possible anymore
Status in OpenStack Compute (nova):
Opinion
Bug description:
Hi guys,
libvirt.xml.template support has been removed between diablo and
folsom (I guess) but we still need a way of PXE booting a guest OS in
some situation. All the forums I've read point us to modifying
libvirt.xml.template but that's not deprecated.
This patch permits the configuration of PXE boots in a hackish way:
--- /usr/lib/python2.6/site-packages/nova/virt/libvirt/driver.py.orig 2013-05-10 16:25:17.787862177 +0000
+++ /usr/lib/python2.6/site-packages/nova/virt/libvirt/driver.py 2013-05-10 16:26:39.442022870 +0000
@@ -87,6 +87,9 @@
LOG = logging.getLogger(name)
libvirtopts = [
+ cfg.StrOpt('defaultguestbootdev',
+ default='hd',
+ help='Sets the default guest boot device'),
cfg.StrOpt('rescueimageid',
default=None,
help='Rescue ami image'),
@@ -1792,7 +1795,7 @@
instance['name'],
"ramdisk")
else:
- guest.osbootdev = "hd"
+ guest.osbootdev = CONF.defaultguestboot_dev
if CONF.libvirt_type != "lxc" and CONF.libvirt_type != "uml":
guest.acpi = True
This may not be the best way as I would prefer to have two boot
devices in order to try "network" boot and then "hd" boot if the first
one failed. This is not a bug but we lost a possibility when
libvirt.xml.template usage was deprecated and some people will find it
hard to get it working easily.
Thank you very much,
Dave
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1183885/+subscriptions