WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] Funny output from virsh vncdisplay

Subject: Re: [Xen-users] Funny output from virsh vncdisplay
From: Jonathan Dye <jdye@xxxxxxxxxxxxxxxxxxxx>
Date: Mon, 02 Feb 2009 14:16:21 -0700
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 02 Feb 2009 13:17:14 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C8A31AB1-B98D-49B0-9E3F-2A779DB1CA46@xxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <C8A31AB1-B98D-49B0-9E3F-2A779DB1CA46@xxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.19 (X11/20090105)
Mike O'Brien wrote:
"virsh vncdisplay <dom-id> " is supposed to deliver both the IP address and the console number of a virtual console, suitable for use by a VNC client. However, on a Fedora 9 domU running on a CentOS 5.2 dom0, I get this:

# virsh vncdisplay Fedora9
:0

#

    This isn't exactly helpful.  Any ideas what's wrong?

Mike O'Brien

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
in virsh.c (in libvirt), it omits the ip address if it is either not present, not in the right format, or all 0s:

    if ((obj == NULL) || (obj->type != XPATH_STRING) ||
       (obj->stringval == NULL) || (obj->stringval[0] == 0) ||
       STREQ((const char*)obj->stringval, "0.0.0.0")) {
       vshPrint(ctl, ":%d\n", port-5900);
   } else {
       vshPrint(ctl, "%s:%d\n", (const char *)obj->stringval, port-5900);
   }

since you are either on the hypervisor calling virsh, or passing a correct ip address to virsh -c (?), the IP should be known. (you are aware that the vnc server is running on the hypervisor and not the guest, yes?)

- jonathan

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>