[libvirt] remote driver?
Daniel P. Berrange
berrange at redhat.com
Mon Sep 1 09:11:19 UTC 2008
On Mon, Sep 01, 2008 at 12:29:16PM +0900, Jun Koi wrote:
> I am connecting to libvirtd with virsh using qemu:///system connection
> type. However, it seems virsh uses "remote" driver for all the action
> on the VM. So this means qemu:///system considers all the action is
> done "remotely" even if it is on the same physical machine?
> I really expected that it uses "QEMU" driver, but that is not the
> case. So I wonder in which case "QEMU" driver is used?
The QEMU driver is what we call a 'stateful' driver, which means it only
lives within the libvirtd daemon, and applications communicate with the
QEMU driver indirectly via the 'remote' driver. 'remote' was probably
a bad name for this driver - its really just doing local RPC calls over
a UNIX domain socket and is very fast. So the behaviour you see is
totally expected & nothing to worry about.
|: 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 :|
More information about the libvir-list