On Mon, Jul 19, 2010 at 01:26:10AM +0200, Matthias Bolte wrote: > Add a pointer to the primary context of a connection and use it in all > driver functions that don't dependent on the context type. This includes > almost all functions that deal with a virDomianPtr. Therefore, using > a vpx:// connection allows you to perform all the usual domain related > actions like start, destroy, suspend, resume, dumpxml etc. > > Some functions that require an explicitly specified ESX server don't work > yet. This includes the host UUID, the hostname, the general node info, the > max vCPU count and the free memory. Also not working yet are migration and > defining new domains. If you're connecting to vpx://example-vcenter.com how does the driver know which host you're asking for data on ? IIUC a vcenter reports on all hosts in a data center. Does new mode still guarentee that every domain has a unique name & ID, as well as UUID ? Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://deltacloud.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list