Tim Edwards wrote:
We currently use LVM to provide disks to our Xen VMs. It seems as though
kickstart insists on always creating a partition on a disk, instead of
just using the whole disk.
However what we'd like to do is, for example, the LVM volume appears as
/dev/hdd to the VM, we'd like to have kickstart just create a filesystem
on this device and use it.
There's no problem doing this after the kickstart (eg. mkfs.ext3
/dev/hdd; mount /dev/hdd /somewhere) but kickstart seems to insist on
creating a /dev/hdd1. This causes problems as we have to calculate the
offset and can't easily take advantage of LVM features like snapshotting
for backups.
Anyone know of a way to do this?
It seems probable to me something that the authors of Anaconda, which
drives the process, chose not to support, maybe because they didn't
think of it, maybe because "it's a silly idea."
Since Anaconda drives the ks process, whether it's even supported is an
Anaconda question. What Anaconda doesn't support, ks probably cannot do
- there are some things ks can do indirectly, bu use of %pre and %post
scripts, but this probably isn't one of them.
There is no doubt in my mind that, in the world of virtual machines,
it's not a silly idea - I can trivially mount a guest volume on the host
if needs be provided that it's not partitioned, but manipulating a
partitioned volume is much trickier.
One thing you might try next is to do a manual install, with the target
volume being a partition on a host drive. You could also just futz
around to see what you can do manually, and if that succeeeds see what's
in the ks file that gets created.
If no joy there, then some discussion with the current authors on the
anaconda list would be my next try for help.
--
Cheers
John
-- spambait
[email protected] [email protected]
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375
You cannot reply off-list:-)
_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list
