hi Daniel,
From the webpage, I can see that dbus and gnome-python-desktop are
optional, but when our release engineer try to build, seems they are
not, so could you confirm me if we can build/run virt-manager correctly
without Dbus?
I carefully read the content in "Dbus Services", My understanding is
that Dbus in virt-manager is used to make other external application
call some core function, so that they can get display the window/dialog .
When Dbus is used?
"The remote control module provides the DBus service
<http://virt-manager.et.redhat.com/dbusservice.html> allowing various UI
functions to be controlled remotely.": My understanding for "remotely"
is to run virt-manager remotely, is it correct? so will dbus only used
when remotely? if some application in local machine, it may also use
Dbus to run some function?
Thanks,
Henry
Daniel P. Berrange 写道:
On Wed, Nov 22, 2006 at 07:31:07PM +0800, Henry Zhang wrote:
Hi Daniel,
Here I have another question on virt-manager, as you write "an embedded
VNC client viewer provides console access to each of the guest domains",
my concern is where is the vnc server, who provide it, and start it?
Need we setup vnc? I looked through the process used to create guest,
seems there is no any step for vnc...
The VNC server depends on what type of domain is being run. For HVM guests
the VNC server is provided by the qemu-dm process assoicated with that
guest. For paravirt guests, VNC is only available if you have the paravirt
framebuffer patches applied to your xen tree - these are not in xen-unstable
yet. In paravirt, XenD will launch a xen-vncfb process to provide the VNC
server. So in both case all you need to do is set 'vnc=1' in the guest
config file & XenD will ensure the VNC servers are started as required.
Dan.
--
Fedora-xen mailing list
Fedora-xen@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-xen
