On Fri, Jun 25, 2010 at 03:05:42AM -0400, Christoph Hellwig wrote: > On Thu, Jun 24, 2010 at 02:01:52PM -0500, Javier Guerra Giraldez wrote: > > On Thu, Jun 24, 2010 at 1:32 PM, Freddie Cash <fjwcash@xxxxxxxxx> wrote: > > > ??* virt-manager which requires X and seems to be more desktop-oriented; > > > > don't know about the others, but virt-manager runs only on the admin > > station. on the VM hosts you run only libvirtd, which doesn't need X > > While it can connect to remote systems it seems totally unusable for > that to me. For one thing working over higher latency links like DSL > or even transatlantik links seems to be almost impossible. It is fair to say that virt-manager is not really targetted at high latency WAN scenearios. It is really aimed at small scale local LAN deployments with 5-20 hosts maximum. For a serious WAN deployment you can't use the hub <-> spoke synchronous RPC architecture, instead you need a asynchronous message bus - this is where something like oVirt or RHEV is best. So I'd agree that you shouldn't use virt-manager across high latency DSL or transatlantic links, just use it in your local home or office LAN. Regards, 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 :| -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
