Thanks to Dave's comment above, I successfully booted a precise ephemeral
image with the following patch applied to maas:
--- /usr/share/pyshared/provisioningserver/kernel_opts.py.dist 2013-01-31
15:43:30.419250392 -0500
+++ /usr/share/pyshared/provisioningserver/kernel_opts.py 2013-01-31
15:49:09.991260224 -0500
@@ -136,7 +136,9 @@
# in the initramfs.
"ip=::::%s:BOOTIF" % params.hostname,
# cloud-images have this filesystem label.
- "ro root=LABEL=cloudimg-rootfs",
+ "ro root=/dev/disk/by-path/ip-%s:%s-iscsi-%s:%s-lun-1" % (
+ params.fs_host, "3260", ISCSI_TARGET_NAME_PREFIX,
+ get_ephemeral_name(params.release, params.arch)),
# Read by overlayroot package.
"overlayroot=tmpfs",
# Read by cloud-init.
Basically, that ends up with a cmdline like:
nomodeset
iscsi_target_name=iqn.2004-05.com.ubuntu:maas:maas-precise-daily-amd64-ephemeral-20130107
iscsi_target_ip=10.98.191.16 iscsi_target_port=3260
iscsi_initiator=maas-enlist ip=::::maas-enlist:BOOTIF ro
root=/dev/disk/by-path/ip-10.98.191.16:3260-iscsi-iqn.2004-05.com.ubuntu:maas:maas-precise-daily-amd64-ephemeral-20130107-lun-1
overlayroot=tmpfs
cloud-config-url=http://10.98.191.16/MAAS/metadata/latest/enlist-preseed/?op=get_enlist_preseed
log_host=10.98.191.16 log_port=514 -- console=ttyS0,115200
initrd=amd64/generic/precise/commissioning/initrd.gz
BOOT_IMAGE=amd64/generic/precise/commissioning/linux BOOTIF=01-52-54-00-06-e4-d5
This may well be sufficent for our needs.
** Also affects: maas
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1075313
Title:
no reliable way to boot from iscsi root
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1075313/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
