Maximilian Wilhelm wrote: > Hi! > > The attached patch adds simple support for Xen Dom-Us which don't have > "a disk" as such (read: Not /dev/xvd[a-z] device) but get every > "partition" as a single /dev/xvd[a-z][0-9]+ device.
Why not just use the solution for this described in the Wiki? That works without changing the FAI code. Maybe, this patch might be interesting to make the file systems on these partitions, which, in the wiki solution requires explicitly write mkfs statements in the partition hook... Then again, not all people call their Xen disks xvd* - some use hd*, some sd* - all three work. At least currently, I also heard that this might change for some reason I did not fully understand - Fedora people say using hda/sda is not good, and they, and suse use xvda IIR. Still, the Debian tools for creating Xen DomU's use hda or sda, not xvda. And a last note - if you want more complex partitioning in xen domains, you can also just hand over the full disk, and give the domain a full hda, and partition it as usual. You can then also try booting with pygrub - then you can load the kernel from inside the vm, which makes the vm self-containing, and the vm config file the only one additional part you need. Some thoughts about that thing that come to my mind... Henning
