[vdsm] F17's libvirt takes comments into LIBVIRTD_ARGS
On Tue, May 15, 2012 at 04:16:11PM +0800, Shu Ming wrote: On 2012-5-14 7:30, Dan Kenigsberg wrote: On Sun, May 13, 2012 at 11:51:48PM +0800, Shu Ming wrote: Hi, Recently, I found that my host in engine was always in a unassigned state after the host node was installed. After looking into the vdsm.log, it seemed that vdsm failed to call libvirt as an error, libvirtError: Cannot write data: Broken pipe. When I started virsh in the host node at that time, a warning was given WARNING: no socket to connect to and core dumped with virsh net-list. It looks like that no right socket was created for virsh to connect to libvirtd. Any comments about this problem? The followings are my steps in the node: [root@ovirt-node1 ~]# rpm -qa |grep vdsm vdsm-cli-4.9.6-0.183.git107644d.fc16.shuming1336622293.noarch vdsm-python-4.9.6-0.183.git107644d.fc16.shuming1336622293.noarch vdsm-hook-vhostmd-4.9.6-0.183.git107644d.fc16.shuming1336622293.noarch vdsm-4.9.6-0.183.git107644d.fc16.shuming1336622293.x86_64 vdsm-reg-4.9.6-0.183.git107644d.fc16.shuming1336622293.noarch vdsm-debug-plugin-4.9.6-0.183.git107644d.fc16.shuming1336622293.noarch vdsm-hook-faqemu-4.9.6-0.183.git107644d.fc16.shuming1336622293.noarch vdsm-bootstrap-4.9.6-0.183.git107644d.fc16.shuming1336622293.noarch [root@ovirt-node1 ~]# [root@ovirt-node1 ~]# ps -ef |grep libvirt libvirt-daemon-0.9.11-1.fc17.x86_64 libvirt-daemon-config-nwfilter-0.9.11-1.fc17.x86_64 libvirt-client-0.9.11-1.fc17.x86_64 libvirt-daemon-config-network-0.9.11-1.fc17.x86_64 libvirt-python-0.9.11-1.fc17.x86_64 [root@ovirt-node1 ~]# virsh net-list WARNING: no socket to connect to Segmentation fault I think that merits a libvirt bug. please attach strace output to bugzilla. [root@ovirt-node1 ~]# [root@ovirt-node1 ~]# ps -ef |grep vdsm root 1299 1 0 23:10 ?00:00:00 /usr/sbin/libvirtd --listen # by vdsm The command line of libvirt process is very odd - the comment that vdsm puts into /etc/sysconfig/libvirtd is somehow taken verbatim. That's bad, and may be related to Fedora 17's systemd services. Try to remove the comment and restart libvirtd to see if this is the case. The comment come from [root@ovirt-node1 ~]# cat /etc/sysconfig/libvirtd: I know that (see my text above). However, in F16 and before, comments have been stripped before being passed to commandline. Have you tested if all is well when the commment is removed? Let's see what our friends in libvir-list think. Dan. ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] F17's libvirt takes comments into LIBVIRTD_ARGS
On Wed, May 16, 2012 at 01:46:43PM +0300, Dan Kenigsberg wrote: On Tue, May 15, 2012 at 04:16:11PM +0800, Shu Ming wrote: On 2012-5-14 7:30, Dan Kenigsberg wrote: On Sun, May 13, 2012 at 11:51:48PM +0800, Shu Ming wrote: Hi, Recently, I found that my host in engine was always in a unassigned state after the host node was installed. After looking into the vdsm.log, it seemed that vdsm failed to call libvirt as an error, libvirtError: Cannot write data: Broken pipe. When I started virsh in the host node at that time, a warning was given WARNING: no socket to connect to and core dumped with virsh net-list. It looks like that no right socket was created for virsh to connect to libvirtd. Any comments about this problem? The followings are my steps in the node: [root@ovirt-node1 ~]# rpm -qa |grep vdsm vdsm-cli-4.9.6-0.183.git107644d.fc16.shuming1336622293.noarch vdsm-python-4.9.6-0.183.git107644d.fc16.shuming1336622293.noarch vdsm-hook-vhostmd-4.9.6-0.183.git107644d.fc16.shuming1336622293.noarch vdsm-4.9.6-0.183.git107644d.fc16.shuming1336622293.x86_64 vdsm-reg-4.9.6-0.183.git107644d.fc16.shuming1336622293.noarch vdsm-debug-plugin-4.9.6-0.183.git107644d.fc16.shuming1336622293.noarch vdsm-hook-faqemu-4.9.6-0.183.git107644d.fc16.shuming1336622293.noarch vdsm-bootstrap-4.9.6-0.183.git107644d.fc16.shuming1336622293.noarch [root@ovirt-node1 ~]# [root@ovirt-node1 ~]# ps -ef |grep libvirt libvirt-daemon-0.9.11-1.fc17.x86_64 libvirt-daemon-config-nwfilter-0.9.11-1.fc17.x86_64 libvirt-client-0.9.11-1.fc17.x86_64 libvirt-daemon-config-network-0.9.11-1.fc17.x86_64 libvirt-python-0.9.11-1.fc17.x86_64 [root@ovirt-node1 ~]# virsh net-list WARNING: no socket to connect to Segmentation fault I think that merits a libvirt bug. please attach strace output to bugzilla. [root@ovirt-node1 ~]# [root@ovirt-node1 ~]# ps -ef |grep vdsm root 1299 1 0 23:10 ?00:00:00 /usr/sbin/libvirtd --listen # by vdsm The command line of libvirt process is very odd - the comment that vdsm puts into /etc/sysconfig/libvirtd is somehow taken verbatim. That's bad, and may be related to Fedora 17's systemd services. Try to remove the comment and restart libvirtd to see if this is the case. The comment come from [root@ovirt-node1 ~]# cat /etc/sysconfig/libvirtd: I know that (see my text above). However, in F16 and before, comments have been stripped before being passed to commandline. Have you tested if all is well when the commment is removed? Let's see what our friends in libvir-list think. In F16 we were using the shell to launch libvirtd, in F17 we are using systemd. systemd has stricter requirements around the syntax of /etc/sysconfig/libvirtd file. Specifically it treats the entire line as the value. FYI I add a BZ for this against vdsm along with a suggested solution https://bugzilla.redhat.com/show_bug.cgi?id=821867 Daniel -- |: http://berrange.com -o-http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/vdsm-devel
[vdsm] [PATCH libvirt] Reject any non-option command line arguments
From: Daniel P. Berrange berra...@redhat.com
Due to a bug in editing /etc/sysconfig/libvirtd, VDSM was causing
libvirt processes to run with the following command line args
/usr/sbin/libvirtd --listen '#' 'by vdsm'
While it correctly rejects any invalid option flags, libvirtd
was not rejecting any non-option command line arguments
* daemon/libvirtd.c: Reject non-option argv
---
daemon/libvirtd.c |6 ++
1 file changed, 6 insertions(+)
diff --git a/daemon/libvirtd.c b/daemon/libvirtd.c
index 2696c54..0b5ae35 100644
--- a/daemon/libvirtd.c
+++ b/daemon/libvirtd.c
@@ -999,6 +999,12 @@ int main(int argc, char **argv) {
}
}
+if (optind != argc) {
+fprintf(stderr, %s: unexpected, non-option, command line arguments\n,
+argv[0]);
+exit(EXIT_FAILURE);
+}
+
if (!(config = daemonConfigNew(privileged))) {
VIR_ERROR(_(Can't create initial configuration));
exit(EXIT_FAILURE);
--
1.7.10.1
___
vdsm-devel mailing list
vdsm-devel@lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] RESTful VM creation
No comments at all on this?? On Wed, May 09, 2012 at 09:35:29AM -0500, Adam Litke wrote: I would like to discuss a problem that is going to affect VM creation in the new REST API. This topic has come up previously and I want to revive that discussion because it is blocking a proper implementation of VM.create(). Consider a RESTful VM creation sequence: POST /api/vms/define - Define a new VM in the system POST /api/vms/id/disks/add - Add a new disk to the VM POST /api/vms/id/cdroms/add - Add a cdrom POST /api/vms/id/nics/add - Add a NIC PUT /api/vms/id - Change boot sequence POST /api/vms/id/start - Boot the VM Unfortunately this is not possible today with vdsm because a VM must be fully-specified at the time of creation and it will be started immediately. As I see it there are two ways forward: 1.) Deviate from a REST model and require a VM resource definition to include all sub-collections inline. -- or -- 2.) Support storage of vm definitions so that powered off VMs can be manipulated by the API. My preference would be #2 because: it makes the API more closely follow RESTful principles, it maintains parity with the cluster-level VM manipulation API, and it makes the API easier to use in standalone mode. Here is my idea on how this could be accomplished without committing to stateful host storage. In the past we have discussed adding an API for storing arbitrary metadata blobs on the master storage domain. If this API were available we could use it to create a transient VM construction site. Let's walk through the above RESTful sequence again and see how my idea would work in practice: * POST /api/vms/define - Define a new VM in the system A new VM definition would be written to the master storage domain metadata area. * GET /api/vms/new-uuid The normal 'list' API is consulted as usual. The VM will not be found there because it is not yet created. Next, the metadata area is consulted. The VM is found there and will be returned. The VM state will be 'New'. * POST /api/vms/id/disks/add - Add a new disk to the VM For 'New' VMs, this will update the VM metadata blob with the new disk information. Otherwise, this will call the hotplugDisk API. * POST /api/vms/id/cdroms/add - Add a cdrom For 'New' VMs, this will update the VM metadata blob with the new cdrom information. If we want to support hotplugged CDROMs we can call that API later. * POST /api/vms/id/nics/add - Add a NIC For 'New' VMs, this will update the VM metadata blob with the new nic information. Otherwise it triggers the hotplugNic API. * PUT /api/vms/id - Change boot sequence Only valid for 'New' VMs. Updates the metadata blob according to the parameters specified. * POST /api/vms/id/start - Boot the VM Load the metadata from the master storage domain metadata area. Call the VM.create() API. Remove the metadata from the master storage domain. VDSM will automatically purge old metadata from the master storage domain. This could be done any time a domain is: attached as master, deactivated, and periodically. How does this idea sound? I am certain that it can be improved by those of you with more experience and different viewpoints. Thoughts and comments? -- Adam Litke a...@us.ibm.com IBM Linux Technology Center ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/vdsm-devel -- Adam Litke a...@us.ibm.com IBM Linux Technology Center ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] [libvirt] [PATCH libvirt] Reject any non-option command line arguments
On 05/16/2012 05:05 AM, Daniel P. Berrange wrote: From: Daniel P. Berrange berra...@redhat.com Due to a bug in editing /etc/sysconfig/libvirtd, VDSM was causing libvirt processes to run with the following command line args /usr/sbin/libvirtd --listen '#' 'by vdsm' While it correctly rejects any invalid option flags, libvirtd was not rejecting any non-option command line arguments * daemon/libvirtd.c: Reject non-option argv --- daemon/libvirtd.c |6 ++ 1 file changed, 6 insertions(+) ACK. -- Eric Blake ebl...@redhat.com+1-919-301-3266 Libvirt virtualization library http://libvirt.org signature.asc Description: OpenPGP digital signature ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] F17's libvirt takes comments into LIBVIRTD_ARGS
On 2012-5-16 18:46, Dan Kenigsberg wrote: On Tue, May 15, 2012 at 04:16:11PM +0800, Shu Ming wrote: On 2012-5-14 7:30, Dan Kenigsberg wrote: On Sun, May 13, 2012 at 11:51:48PM +0800, Shu Ming wrote: Hi, Recently, I found that my host in engine was always in a unassigned state after the host node was installed. After looking into the vdsm.log, it seemed that vdsm failed to call libvirt as an error, libvirtError: Cannot write data: Broken pipe. When I started virsh in the host node at that time, a warning was given WARNING: no socket to connect to and core dumped with virsh net-list. It looks like that no right socket was created for virsh to connect to libvirtd. Any comments about this problem? The followings are my steps in the node: [root@ovirt-node1 ~]# rpm -qa |grep vdsm vdsm-cli-4.9.6-0.183.git107644d.fc16.shuming1336622293.noarch vdsm-python-4.9.6-0.183.git107644d.fc16.shuming1336622293.noarch vdsm-hook-vhostmd-4.9.6-0.183.git107644d.fc16.shuming1336622293.noarch vdsm-4.9.6-0.183.git107644d.fc16.shuming1336622293.x86_64 vdsm-reg-4.9.6-0.183.git107644d.fc16.shuming1336622293.noarch vdsm-debug-plugin-4.9.6-0.183.git107644d.fc16.shuming1336622293.noarch vdsm-hook-faqemu-4.9.6-0.183.git107644d.fc16.shuming1336622293.noarch vdsm-bootstrap-4.9.6-0.183.git107644d.fc16.shuming1336622293.noarch [root@ovirt-node1 ~]# [root@ovirt-node1 ~]# ps -ef |grep libvirt libvirt-daemon-0.9.11-1.fc17.x86_64 libvirt-daemon-config-nwfilter-0.9.11-1.fc17.x86_64 libvirt-client-0.9.11-1.fc17.x86_64 libvirt-daemon-config-network-0.9.11-1.fc17.x86_64 libvirt-python-0.9.11-1.fc17.x86_64 [root@ovirt-node1 ~]# virsh net-list WARNING: no socket to connect to Segmentation fault I think that merits a libvirt bug. please attach strace output to bugzilla. [root@ovirt-node1 ~]# [root@ovirt-node1 ~]# ps -ef |grep vdsm root 1299 1 0 23:10 ?00:00:00 /usr/sbin/libvirtd --listen # by vdsm The command line of libvirt process is very odd - the comment that vdsm puts into /etc/sysconfig/libvirtd is somehow taken verbatim. That's bad, and may be related to Fedora 17's systemd services. Try to remove the comment and restart libvirtd to see if this is the case. The comment come from [root@ovirt-node1 ~]# cat /etc/sysconfig/libvirtd: I know that (see my text above). However, in F16 and before, comments have been stripped before being passed to commandline. Have you tested if all is well when the commment is removed? I removed the # by vdsm line from the config file. And restarted the libvirtd and vdsmd service. But no luck to make virsh net-list successful, still got Segmentation fault, while virsh -c qemu:///system -r worked. virsh # net-list Segmentation fault [root@ovirt-node1 ~]# virsh net-list Segmentation fault [root@ovirt-node1 ~]# virsh -c qemu:///system Please enter your authentication name: ^C [root@ovirt-node1 ~]# virsh -c qemu:///system -r Welcome to virsh, the virtualization interactive terminal. Type: 'help' for help with commands 'quit' to quit virsh net-list Name State Autostart - vdsm-ovirtmgmt active yes virsh Let's see what our friends in libvir-list think. Dan. -- Shu Mingshum...@linux.vnet.ibm.com IBM China Systems and Technology Laboratory ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] F17's libvirt takes comments into LIBVIRTD_ARGS
On Wed, May 16, 2012 at 11:05:16PM +0800, Shu Ming wrote: On 2012-5-16 18:46, Dan Kenigsberg wrote: On Tue, May 15, 2012 at 04:16:11PM +0800, Shu Ming wrote: On 2012-5-14 7:30, Dan Kenigsberg wrote: On Sun, May 13, 2012 at 11:51:48PM +0800, Shu Ming wrote: Hi, Recently, I found that my host in engine was always in a unassigned state after the host node was installed. After looking into the vdsm.log, it seemed that vdsm failed to call libvirt as an error, libvirtError: Cannot write data: Broken pipe. When I started virsh in the host node at that time, a warning was given WARNING: no socket to connect to and core dumped with virsh net-list. It looks like that no right socket was created for virsh to connect to libvirtd. Any comments about this problem? The followings are my steps in the node: [root@ovirt-node1 ~]# rpm -qa |grep vdsm vdsm-cli-4.9.6-0.183.git107644d.fc16.shuming1336622293.noarch vdsm-python-4.9.6-0.183.git107644d.fc16.shuming1336622293.noarch vdsm-hook-vhostmd-4.9.6-0.183.git107644d.fc16.shuming1336622293.noarch vdsm-4.9.6-0.183.git107644d.fc16.shuming1336622293.x86_64 vdsm-reg-4.9.6-0.183.git107644d.fc16.shuming1336622293.noarch vdsm-debug-plugin-4.9.6-0.183.git107644d.fc16.shuming1336622293.noarch vdsm-hook-faqemu-4.9.6-0.183.git107644d.fc16.shuming1336622293.noarch vdsm-bootstrap-4.9.6-0.183.git107644d.fc16.shuming1336622293.noarch [root@ovirt-node1 ~]# [root@ovirt-node1 ~]# ps -ef |grep libvirt libvirt-daemon-0.9.11-1.fc17.x86_64 libvirt-daemon-config-nwfilter-0.9.11-1.fc17.x86_64 libvirt-client-0.9.11-1.fc17.x86_64 libvirt-daemon-config-network-0.9.11-1.fc17.x86_64 libvirt-python-0.9.11-1.fc17.x86_64 [root@ovirt-node1 ~]# virsh net-list WARNING: no socket to connect to Segmentation fault I think that merits a libvirt bug. please attach strace output to bugzilla. [root@ovirt-node1 ~]# [root@ovirt-node1 ~]# ps -ef |grep vdsm root 1299 1 0 23:10 ?00:00:00 /usr/sbin/libvirtd --listen # by vdsm The command line of libvirt process is very odd - the comment that vdsm puts into /etc/sysconfig/libvirtd is somehow taken verbatim. That's bad, and may be related to Fedora 17's systemd services. Try to remove the comment and restart libvirtd to see if this is the case. The comment come from [root@ovirt-node1 ~]# cat /etc/sysconfig/libvirtd: I know that (see my text above). However, in F16 and before, comments have been stripped before being passed to commandline. Have you tested if all is well when the commment is removed? I removed the # by vdsm line from the config file. And restarted the libvirtd and vdsmd service. But no luck to make virsh net-list successful, still got Segmentation fault, while virsh -c qemu:///system -r worked. Thanks. Please strace that segfault, there's a libvirt bug lying there. And thanks again for finding the vdsm/libvirt configuration problem in F17. ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] minutes: today's call
On Wed, May 16, 2012 at 09:43:57AM -0500, Ryan Harper wrote: * Dan Kenigsberg dan...@redhat.com [2012-05-07 05:42]: On Mon, Apr 23, 2012 at 05:52:13PM +0300, Dan Kenigsberg wrote: On Mon, Apr 23, 2012 at 07:34:14AM -0500, Adam Litke wrote: On Mon, Apr 23, 2012 at 04:17:18AM -0400, Ayal Baron wrote: Hi all, I would like to discuss the following on today's call: 1. Gerrit vs. mailing list Gerrit is an inhibiter for some contributors. One approach to solve this improve gerrit: - Gerrit should send the patch when it notified of a change. This may attract more reviewers. I'm happy to inform that Gal has sent a patch for this to upstream gerrit: https://gerrit-review.googlesource.com/#/c/34861/ Add unified diff to newchange mail template. Any eta on getting the gerrit notifications of changes to include the full patch in the email? You can +1 them in googlesource, maybe it helps ;-) I'm definitely happy to see notification on new posts and changes; helps me see what new activity is happening, but I'd really enjoy seeing the the patch series attached (via threading) as well. Itamar, I know Red Hat hates to do it, but can we take these patches to ovirt's gerrit before they are accepted upstream? Regards, Dan. ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] minutes: today's call
On 05/16/2012 06:11 PM, Dan Kenigsberg wrote: On Wed, May 16, 2012 at 09:43:57AM -0500, Ryan Harper wrote: * Dan Kenigsbergdan...@redhat.com [2012-05-07 05:42]: On Mon, Apr 23, 2012 at 05:52:13PM +0300, Dan Kenigsberg wrote: On Mon, Apr 23, 2012 at 07:34:14AM -0500, Adam Litke wrote: On Mon, Apr 23, 2012 at 04:17:18AM -0400, Ayal Baron wrote: Hi all, I would like to discuss the following on today's call: 1. Gerrit vs. mailing list Gerrit is an inhibiter for some contributors. One approach to solve this improve gerrit: - Gerrit should send the patch when it notified of a change. This may attract more reviewers. I'm happy to inform that Gal has sent a patch for this to upstream gerrit: https://gerrit-review.googlesource.com/#/c/34861/ Add unified diff to newchange mail template. Any eta on getting the gerrit notifications of changes to include the full patch in the email? You can +1 them in googlesource, maybe it helps ;-) indeed, please help push them upstream... https://gerrit-review.googlesource.com/#/c/34861/ https://gerrit-review.googlesource.com/#/c/34862/ I'm definitely happy to see notification on new posts and changes; helps me see what new activity is happening, but I'd really enjoy seeing the the patch series attached (via threading) as well. Itamar, I know Red Hat hates to do it, but can we take these patches to ovirt's gerrit before they are accepted upstream? yes we can. after i'll upgrade it to 2.3, which i prefer to do after i return from PTO in case there are some issues with the upgrade. so ETA end of the month for clean upgrade to 2.3, then after we see all is ok, let's say another week to upgrade to the version with these patches. Regards, Dan. ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] [libvirt] F17's libvirt takes comments into LIBVIRTD_ARGS
On Wed, May 16, 2012 at 11:45:13PM +0800, Shu Ming wrote: On 2012-5-16 23:35, Daniel P. Berrange wrote: [root@ovirt-node1 ~]# rpm -qa |grep vdsm vdsm-cli-4.9.6-0.183.git107644d.fc16.shuming1336622293.noarch vdsm-python-4.9.6-0.183.git107644d.fc16.shuming1336622293.noarch vdsm-hook-vhostmd-4.9.6-0.183.git107644d.fc16.shuming1336622293.noarch vdsm-4.9.6-0.183.git107644d.fc16.shuming1336622293.x86_64 vdsm-reg-4.9.6-0.183.git107644d.fc16.shuming1336622293.noarch vdsm-debug-plugin-4.9.6-0.183.git107644d.fc16.shuming1336622293.noarch vdsm-hook-faqemu-4.9.6-0.183.git107644d.fc16.shuming1336622293.noarch vdsm-bootstrap-4.9.6-0.183.git107644d.fc16.shuming1336622293.noarch [snip] [root@ovirt-node1 ~]# debuginfo-install libvirt Loaded plugins: langpacks, presto, refresh-packagekit enabling fedora-debuginfo enabling updates-debuginfo No debuginfo packages available to install [root@ovirt-node1 ~]# debuginfo-install libvirt --releasever=17 Loaded plugins: langpacks, presto, refresh-packagekit enabling fedora-debuginfo enabling updates-debuginfo No debuginfo packages available to install [root@ovirt-node1 ~]# What is your actual distro ? You see to have a wierd mix of Fedora 16 and Fedora 17 packages here, so I presume you've been installing custom built packages, or mixing different Fedora repositories There is definitely a libvirt-debuginfo RPM present in the normal Fedora 17 repositories. Daniel -- |: http://berrange.com -o-http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/vdsm-devel
