Thanks Ant. I wasn't aware of this, but our Xen.org team was, as there was a thread about it on xen-devel. This is a daft thing for Ubuntu to have done, and it has been reverted:
Do we need workaround code in the meantime? We could maybe autodetect the broken versions of Ubuntu, and fix up the problem. An alternative would be for you to add a udev rule that symlinked xvdX to sdX when it was hotplugged. That would work I think.
I don't like the idea of unconditionally assuming that it's sdX if xvdX isn't there -- we'll destroy someone's root filesystem that way.
Thanks Ant. I wasn't aware of this, but our Xen.org team was, as there was a thread about it on xen-devel. This is a daft thing for Ubuntu to have done, and it has been reverted:
https:/ /bugs.launchpad .net/ubuntu/ +source/ linux/+ bug/684875 www.gossamer- threads. com/lists/ xen/devel/ 192003
http://
Do we need workaround code in the meantime? We could maybe autodetect the broken versions of Ubuntu, and fix up the problem. An alternative would be for you to add a udev rule that symlinked xvdX to sdX when it was hotplugged. That would work I think.
I don't like the idea of unconditionally assuming that it's sdX if xvdX isn't there -- we'll destroy someone's root filesystem that way.