similar to: Web based management console with integrated Java VNC Viewer

Hello all: I am trying to install CentOS 5.4 as a KVM guest. The host is running CentOS 5.4 and does not have X installed. I used ssh to connect to the host and ran this command (I formatted it for readability, it is all on one line): virt-install -n jamm12e -r 1024 --vcpus=1 --check-cpu --os-type=linux --os-variant=rhel5 --hvm --accelerate --cdrom=/tmp/CentOS-5.4-x86_64-netinstall.iso

Hi, I am pretty new to libvirt, but have succeeded in setting up two VM's, Windows 10 and ClearOS (a Centos derivative) and they both have the same issue. I have installed both of them with a UK English keyboard, but the host machine is remote and in the US with a US locale. When I access either through VNC (I've tried TightVNC and VNC-Viewer), a number of my keys don't map

Hi, I''ve run into a problem, and no amount of Googling seems to help. I''m running Xen 3.4 and have the consoles of my DOMUs setup to be VNC. I can connect to them just fine from Chicken of the VNC etc etc. I cannot, however, connect using the built in vnc client using vnc://machine_name:59XX. I''m running os X 10.6.3 BTW Has anyone found a way around this? My end game

virt-viewer-plugin is deprecated and will be replaced w/ ovirt-viewer-plugin, vm details pane uri indicates ovirt-viewer should be used with the specified hostname --- src/app/views/vm/show.rhtml | 18 ++++-------------- 1 files changed, 4 insertions(+), 14 deletions(-) diff --git a/src/app/views/vm/show.rhtml b/src/app/views/vm/show.rhtml index ffe5055..30b17cb 100644 ---

The new merged qemu no longer has the ability to spawn a vnc viewer process in the bowels of the xend/qemu stack. In this patch we provide support for this use case in a different manner - one more akin to the mechanism used for `xm console'' and `xm create -c''. We introduce new xm options: xm create --vncviewer [--vncviewer-autopass] xm vncviewer [--vncviewer-autopass]

I''ve found that if a vncviewer is already connected to a DomU (ie vncveiwer dom0server:5901) then another connection attempt hangs (it seems to go into a queue). Is it possible to change this behaviour in any of the following ways? - simultaneous connections mean that users fight over mouse and keyboard - the new connection breaks the old - the length of the connection is limited Are

Hi, I have configured vnc on my centos server machine. But, unable to access the vnc client. When ever i try to access my client. All I get is a blank screen with only mouse working. I am very clue less about the problem, Can I find out this error. Regards, Vijay Shanker Dubey -------------- next part -------------- An HTML attachment was scrubbed... URL:

Need some pointers here. I've got CentOS 4.4, and I want to control my OSX 10.4.9 box via VNC. It connects, and I get a little dot for the mouse cursor, but just a black screen. I can see the mouse controlling the OSX desktop... Here's the output when I start in a terminal: [d at f ~]$ vncviewer VNC server supports protocol version 3.889 (viewer 3.3) VNC authentication succeeded

I''ve just uneventfully installed SLES10 as an HVM DomU (after finding out, the hard way, that OpenSUSE 10.3 won''t install on Intel VT). This almost went without a hitch, but I''ve been banging my head against a brick wall for a few hours trying to get VNC working. I can get a remote desktop, but a few seconds after I log in to the remote desktop, the screen goes

My Windows XP TightVNC (1.3.9.0) client-session into host OS (named pq3) ... - Xen 3.3.1_18546_24-0.4.13-x86_64 running on - Xen kernel 2.6.27.56-0.1.1-x86_64 and - KDE 3.5.10-17.5.1-x86_64 ... works fine. However, since a recent update it has stopped working for the Xen guest OpenSuSE 11.1 (named pq5) which is at the same revision as the host - pq3. The symptom is ... - connection

A couple of days ago, I posted a question about using vnc with winbind users (i.e. users from a Win2k3 Active Directory domain being authenticated locally on a Linux box -- in this case Fedora Core 3 -- with winbind). The consensus seemed to be that it wasn't possible, at least with the free versions of VNC. Well, not so. Here's how I did it. First, I found out by accident (i.e. just

Hello all, I have a problem getting a working VNC console for HVM guests on Xen 4.1. When I start the DomU with xm create everything is fine the DomU runs and in xm list it has the running state but when I try to connect to the VNC console to install an operating system (Ubuntu and Debian I have tested) the VNC viewer only shows a black screen. So I searched in the logs and found a log entry

Hi. What system or software are you using to show the iptables log files (for example the dropped packages tagged as LOG in the Shorewall rules)? Thank you very much! Bye. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files

Hi all, I am having issues with running tightvnc-server on a CentOS 5.1 x86_64 machine (currently up-to-date, kernel 2.6.18-53.1.6.el5). Occasionally, the Xvnc instance will just crash, taking with it everything that I was running. When it crashes, it seems to do so when I try to open some GUI program. So, for instance, I click on a shortcut to open a program, and poof, it crashes. But it does

On Tuesday, December 30, 2014 13:01:57 SilverTip257 wrote: > On Tue, Dec 30, 2014 at 9:58 AM, Marcelo Roccasalva < > > marcelo-centos at irrigacion.gov.ar> wrote: > > On Tue, Dec 30, 2014 at 11:46 AM, Bill Gee <bgee at campercaver.net> wrote: > > > Hello everyone - > > > > > > I am trying to use virt-viewer to connect to KVM virtual machines

I am using the XenAPI viewer, to access consoles on my server using the embedded XenServerConsole.jar How does it access the framebuffer? The information says RFB, but what is the address for that RFB? I would like to connect with my own client if possible. Thank you _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com

Just new to Centos 5.6. I'm trying to install an Xvnc server Downloaded tightvnc-1.3.10_unixsrc.bz2 I made thru configure but when I make I get these messages make[3]: Leaving directory `/home/michel/importe/tightvnc-1.3.10_unixsrc/vnc_unixsrc/Xvnc/programs/Xserver/hw/vnc' make[2]: *** No rule to make target `../.././/../libvncauth/libvncauth.a', needed by `Xvnc'. Stop.

I tried to use tightvnc back in August and had some help, but I stopped due to IPv6 support. Now I am back at tightvnc and cannot get the server started. This is on a new Centos install that did have regular vncserver working on it (I did a yum erase vnc-server first). So I have a working /etc/sysconfig/vncserver and my user has the appropriate ~/.vnc files that worked with regular vnc.

Hi, I''ve been trying to get the vnc support working with my pure pv guests, but all that seems to happen is the guest goes into 100% cpu use and fails to boot. All I have to do is enable vnc, and try to start a guest and it locks up like that. What is the proper way to setup vnc support on a vnc guest? That is, vnc access to the console, and not a guest run X server or anything like

Hi, gang. I''m having major issues with getting the VNC consoles to accept keystrokes. I''m trying to get Windows 2003 Server SP2 to run as a fully-virtualized guest. I get the VNC window for the installer, but I can''t get it to accept any keystrokes (e.g. hitting the F5 so I can tell it to use a standard PC HAL). If I opt to use SDL, I get no console at all.