similar to: vnc problem after OpenSuSE 11.1 update

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

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

I''m making use of the Java tightvnc client to get access to domU HVM console''s. Are there any web based management consoles that integrate such a feature automagically? As far as I can tell, enomalism doesn''t... Failing that, does anyone have any example code (python would be nice) to return a list of running domains and what port their VNC is listening on? Thanks

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

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

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.

I was working in terminal and then found this on the desktop when I do an ls [root at dtslinux Desktop]# ls bar-003ada89db.desktop hadjaha-00c578ceaf.desktop bar-004892226f.desktop hammer-0011bbeb3d.desktop blah-0055ff1151.desktop hammer-00d190a421.desktop blah-009c014480.desktop keepassx-0.4.1 eek-00db4ea619.desktop keepassx-0.4.1.tar.gz eek-00de4431f4.desktop

When I try to create a PV domU, the VM starts up and I can access it through "xm console <id>", but when I try to connect to it through VNC, the port just hangs. I''ve tried using RealVNC and TightVNC, and also tried on Linux and Windows. All that happens on the client is that it says that the connection has established, and hangs there. I''ve tried running

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

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

You would think installing via yum would handle dependencies, but perhaps fonts are not managed like dependencies..... Anyway, I installed tightvnc to test out its IPv6 support. Installed ok (after I erased regular vnc). But when I tried to start it, I got 5 warnings about: Font directory '/usr/X11R6/lib/X11/fonts/misc' not found - ignoring (then the same message for Speedo, Type1,

After several days of problems, I finally got Xen 3.0.1 set up in Ubuntu Breezy with the 2.6.12 kernel on a VT-enabled system with an Intel 930 processor and 2GB of memory. I have been able to install an unmodified guest without any issues other than performance. The guest runs extremely slowly and the mouse and keyboard are all but useless because of the extreme lag. I''ve tried multiple

That's kind of weird. I don't think VNC has anything to do with X really. Are you able to connect with VNC? If you are able to establish a connection the first thing you should see is a login prompt on most distributions (unless the distribution is configure to start X windows). Maybe there is some key you can press to get a console window. Like CTRL-ALT-F1 or F2 or F3. On Fri, Jul 10,

Hello, I want to run some program with Wine in a headless server. However, I want to access it via VNC, so I am using Xvnc (vncserver is a wrapper script) from tightvnc as a X server. But I have a problem: wine doesn't detect the display of the X server. This is what happens: Code: [martin at urano ~]$ DISPLAY=:1 [martin at urano ~]$ vncserver :1 New 'X' desktop is urano:1 (...)

Dear All, I'm replacing an older OpenSuse server with a new Centos6.4 server. So far that goes ok, except that the OpenSuse server is also a samba server with ldap connection. Since I replaced all but 2 machines in the building from Windows to Linux, I was hoping not to install Samba on the new server. ( And also because I can't get it to work on Centos. ) I saw a post on the

I''m trying to get linux domU going with opensolaris ''130. The CPU is a plain P4 3.2Ghz (no hardware Virt) but all I''m trying is --paravirt Here''s the command line I''m trying..... virt-install --paravirt --name=dom1 --ram=1024 --vnc \ --os-type=linux --os-variant=fedora8 \ --network bridge \ --file /dev/zvol/dsk/rpool/dom1 \ --location

The python3 bindings create unicode objects from application strings on the guest (i.e. installed rpm, deb packages). It is documented that rpm package fields such as description should be utf8 encoded - however in some cases they are not a valid unicode string, on SLES11 SP4 the following packages fail to be converted to unicode using guestfs_int_py_fromstring() (which invokes

Try some of these combinations: http://www.howtogeek.com/119293/4-ways-to-recover-from-a-crashed-or-frozen-x-server-on-linux/ The good thing is your vm is up and running. You should try SSHing into it if that works. On Fri, Jul 10, 2015 at 1:37 PM, KARR, DAVID <dk068x@att.com> wrote: > I’m confused. You’re asking if I’m able to connect with VNC in response > to my comment that

Hi, this has nothing directly to do with samba, but there might be some people who try to use samba with (Open)LDAP on OpenSUSE 11.1 like me. Between 10.2 and 11.1 the nss_ldap configuration has changed a bit. The file which configures the access to ldap is now /etc/nss-ldap.conf and seems to have the identical layout as the former /etc/ldap.conf. Also needed is the "nslcd"