From justin.conover at gmail.com Sat Jun 6 11:03:39 2015 Content-Type: multipart/mixed; boundary="===============2470158533828476999==" MIME-Version: 1.0 From: Justin Conover To: xen at lists.fedoraproject.org Subject: Re: [Fedora-xen] vnc trick? Date: Fri, 27 Oct 2006 21:51:12 -0500 Message-ID: In-Reply-To: 20061027131435.GC32556@redhat.com --===============2470158533828476999== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable On 10/27/06, Daniel P. Berrange wrote: > > On Thu, Oct 26, 2006 at 08:25:04PM -0500, Justin Conover wrote: > > Is there something I'm missing with VNCserver/viewer? > > > > # xenguest-install > > Would you like a fully virtualized guest (yes or no)? This will allow > you > > to run unmodified operating systems. yes > > What is the name of your virtual machine? fc6-httpd01 > > How much RAM should be allocated (in megabytes)? 512 > > What would you like to use as the disk (path)? /home/xen/fc6-httpd01 > > How large would you like the disk to be (in gigabytes)? 6 > > Would you like to enable graphics support? (yes or no) yes > > What would you like to use for the virtual CD image? > /home/xen/FC-6-x86_64- > > DVD.iso > > > > > > Starting install... > > libvir: Xen Daemon error : GET operation failed: No such domain > fc6-httpd01 > > > > VNC Viewer Free Edition 4.1.2 for X - built Oct 25 2006 09:08:37 > > Copyright (C) 2002-2005 RealVNC Ltd. > > See http://www.realvnc.com for information on VNC. > > > > Thu Oct 26 20:21:19 2006 > > main: unable to connect to host: Connection refused (111) > > Domain installation still in progress. You can reconnect > > to the console to complete the installation process. > > [root(a)kainos xen]# xm list > > Name ID Mem(MiB) VCPUs State > Time(s) > > Domain-0 0 1477 2 r----- > 1003.2 > > fc6-httpd01 12 512 1 r----- > 34.2 > > [root(a)kainos xen]# xm console fc6-httpd01 > > xenconsole: Could not read tty from store: No such file or directory > > Ok, a couple of things to check: > > - Run 'virsh dumpxml fc6-httpd01' and look to see if there is a > tag, and whether it has a port number in it > - Run 'ps -axuwwf | grep vnc' to see if there is a 'xen-vncfb' > server daemon running in Dom0 > - Run 'netstat -t -l -n -p' to see if this server daemon is listening > on the port indicated by the XML dump in step 1. This will also tell > you if its listening on 127.0.0.1, or all interfaces > > If any of that is missing/wrong, then /var/log/xen/xend-debug.log is > where the VNC server stucks its logs. > > Regards, > Dan. > -- > |=3D- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 24= 96 > -=3D| > |=3D- Perl modules: http://search.cpan.org/~danberr/ > -=3D| > |=3D- Projects: http://freshmeat.net/~danielpb/ > -=3D| > |=3D- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B > 9505 -=3D| > # virsh dumpxml fc6-httpd01 fc6-httpd01 5ba9787fba6a82a1d3780ca7be1101ff linux /var/lib/xen/vmlinuz.7EPZk8 /var/lib/xen/initrd.img.4S_Xjg method=3D http://download.fedora.redhat.com/pub/fedora/linux/core/6/x86_64/os 524288 1 destroy destroy destroy