On Sat, Sep 06, 2008 at 11:55:54PM +0200, Emre Erenoglu wrote: > Hi Daniel, > > On Sat, Sep 6, 2008 at 11:17 PM, Daniel P. Berrange <berrange@xxxxxxxxxx>wrote: > > > libvirt supports it as of 0.4.4. For networks add <model type='virtio'/> > > to the <interface> section. For disks change the <disk> target element to > > <target dev='xvdXXX' bus='virtio'/> > > > Thanks, this is how I use it today. > > > > > virt-manager will support it in the very near future, automatically > > enabling > > virtio for disks we know include it > > > Will it also work in the virt-manager GUI when I create a new guest from > scratch? (not with a template etc.). I would like to be able to choose > "virtio" as disk device model as well as the ethernet device. Our design paradigm / goal is not to provide this kind of level of detail in the UI. The choice of IDE vs SCSI vs VirtIO vs Xen PV is determined automatically when you choose the OS Type & OS Variant. eg, if you choose Fedora >= 9, then we know that we should use VirtIO. Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| _______________________________________________ et-mgmt-tools mailing list et-mgmt-tools@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/et-mgmt-tools
