Ugo Bellavance wrote : > Ok, is there anyone here running Virtual machines using the "standard > method" included in RHEL5?
Yup. And if you like minimal installs, then you can easily short-circuit anaconda with no risk when using Xen, since all detected hardware will be identical for all virtualized servers. What I usually do is install a minimal RHEL5 guest, rip out all the extra fluff, pre-configure it partially (common network settings, additional base packages etc.), then keep that image handy and use it as a base for all virtual Xen guests. Being a huge anaconda/rpm fan myself, this is to be considered "ugly", but it works very well, and as long as you take care of all the little details (for instance not having the same host ssh keys, being careful not to have duplicate partition labels...), you'll be fine. I initially started using this method because I like my virtual guests to be on unpartitioned LVs from the host, which anaconda can't handle, unfortunately (i.e. I can mount the guest's "/" LV on the host when the guest is shut down without having to muck around with kpartx). Maybe not exactly the advice you were seeking, though... ;-) Matthias -- Clean custom Red Hat Linux rpm packages : http://freshrpms.net/ Fedora release 8 (Werewolf) - Linux kernel 2.6.24.4-64.fc8 Load : 0.07 0.24 0.21 _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
