On Mon, Jan 19, 2009 at 10:57:58PM +0100, Guido G?nther wrote: > On Mon, Jan 19, 2009 at 11:40:15AM -0500, Cole Robinson wrote: > > The attached patch allows specifying a device model when adding a > > network device to an existing VM (ex. 'virtio', 'e1000', 'pcnet', etc. > > depending on the emulator). > > > > A screenshot of the new UI: > > > > http://fedorapeople.org/~crobinso/virt-manager/vmm-net-model.png > This is very useful! > > > + mod_list = [ "rtl8139", "ne2k_pci", "pcnet" ] > > + if self.vm.get_type().lower() == "kvm": > > + mod_list.append("e1000") > > + mod_list.append("virtio") > It would be nice if this type of information (available sound card > emulations, available network card emulations) would be exposed by > libvirt so not all management app do have to keep track of it. Indeed. The existing host capabilities XML gives a reasonable amount of data on the core hypervisor features. We need equivalent data that covers device emulation features. This will quite dramatically expand the amount of capability data, since there are soooo many combinations. Figuring out the correct available options will be fun too, but clearly we need to adress this at some point. We only get away with it now because both Xen and KVM are both reasonably similar in device capabilities via the shared QEMU base. If we ever get a VMWare driver for libvirt there will be dramatically different device emulation features to worry about. 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
