On Sun, Feb 17, 2008 at 09:26:04PM +0000, Daniel P. Berrange wrote:
> On Sun, Feb 17, 2008 at 02:14:43AM +0000, Daniel P. Berrange wrote:
> > Future enhancements for this:
> >
> > - Allow splitting across multiple disks (sda, sdb, etc)
> >
> > - When staging final image, use qemu-img to generate qcow2, vmdk
> > or raw files at user's choice. qcow2 would give huge size savings
> >
> > - Output XML file for use with 'virt-image' tool, so that the entire
> > build and deploy process consists of nothing more than:
> >
> > # disk-creator ovirt-wui-appliance.ks
> > # virt-image ovirt-wui-appliance.xml
>
> This new version of the patch implements all three of the above features.
>
> As an example, creating an appliance with 2 disks (sda & sdb), outputting
> in qcow2 format:
>
> disk-creator --format qcow2 \
> --name ovirt-wui \
> --disk ovirt-wui-os --size 5000 \
> --disk ovirt-wui-data --size 1000 \
> ovirt-wui-appliance.ks
>
> You'll end up with ovirt-wui-os.qcow2, ovirt-wui-data.qcow2 and ovirt-wui.xml
Opps, I meant to attach a copy of the ovirt-wui.xml for benefit of people
not familiar with virt-image / libvirt. The two files attached to this
mail are the ovirt-wui.xml created by disk-creator for feeding to virt-image.
The second XML file is the libvirt XML generated from ovirt-wui.xml for the
purposes of actually running the appliance in KVM
The core difference between the two is that the virt-image XML format
defines the *requirements* for running the VM, while the libvirt XML
format defines a specific *deployment* of the VM. The former is generic
to any HV, while the later is specific to the HV & host deployed under.
Regards,
Dan
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/ -=|
|=- Projects: http://freshmeat.net/~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
<image>
<name>ovirt-wui</name>
<domain>
<boot type='hvm'>
<guest>
<arch>x86_64</arch>
</guest>
<os>
<loader dev='hd'/>
</os>
<drive disk='ovirt-wui-os.qcow2' target='hda'/>
<drive disk='ovirt-wui-data.qcow2' target='hdb'/>
</boot>
<devices>
<vcpu>1</vcpu>
<memory>262144</memory>
<interface/>
<graphics/>
</devices>
</domain>
<storage>
<disk file='ovirt-wui-os.qcow2' use='system' format='qcow2'/>
<disk file='ovirt-wui-data.qcow2' use='system' format='qcow2'/>
</storage>
</image>
<domain type='kvm'>
<name>ovirt-wui</name>
<uuid>686c3d2c-49df-4cc5-b677-375d841453c6</uuid>
<memory>262144</memory>
<currentMemory>262144</currentMemory>
<vcpu>1</vcpu>
<os>
<type>hvm</type>
<boot dev='hd'/>
</os>
<clock offset='utc'/>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>destroy</on_crash>
<devices>
<emulator>/usr/bin/qemu-kvm</emulator>
<disk type='file' device='disk'>
<source file='/home/berrange/src/ovirt/livecd/tools/ovirt-wui-os.qcow2'/>
<target dev='hda'/>
</disk>
<disk type='file' device='disk'>
<source file='/home/berrange/src/ovirt/livecd/tools/ovirt-wui-data.qcow2'/>
<target dev='hdb'/>
</disk>
<interface type='network'>
<mac address='00:16:3e:3a:92:8c'/>
<source network='default'/>
</interface>
<input type='mouse' bus='ps2'/>
<graphics type='vnc' port='-1' listen='0.0.0.0'/>
</devices>
</domain>
--
Fedora-livecd-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/fedora-livecd-list
