Daniel P. Berrange wrote:
On Tue, Nov 06, 2007 at 11:23:22AM +0100, Daniel Hokka Zakrisson wrote:
Daniel Veillard wrote:
Ah, yes, I missed that. How about:
<os>
<type machine='i586'>vserver</type>
<hostname>testvm</hostname>
<release>2.6.12</release>
<distribution method='debootstrap'>etch</distribution>
</os>
Do we really think boot strapping should be part of the domain description?
It feels very wrong to me, because this isn't information describing a guest
domain configuration. It is installation information. To me it makes more
sense to keep that separate & just refer to the disk (or directory) where the
results are.
I totally agree, I don't think it belongs there either, but I just
didn't see any alternative ;-)
It could well be that we need new APIs to enumerate the list of available
guest OS distributions (and the method of install, eg boot ISO, direct kenrel
and initrd, or bootstrap). And perhaps an API for performing a bootstrap
tasks against a disk volue (as managed by the storage APis we're developing).
This sounds good to me, but it complicates matters by not having it
available at define time. I guess that's workaroundable though.
Regards,
Dan.
--
Daniel Hokka Zakrisson
--
Libvir-list mailing list
Libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list