xen vnc not working in Centos

 
Thread Tools Search this Thread
Operating Systems Linux Red Hat xen vnc not working in Centos
# 1  
Old 02-17-2011
xen vnc not working in Centos

i configured XEN to use port 5902 and it worked. I installed vncserver on the host machine. Now when i connect to 5902 it redirects me to the centos machine not to the XEN guest.
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. Red Hat

Log rotation not working in Centos 7.2

All, I am facing an issue as log rotation not working for me as expected for tomcat in centos 7.2. I configured log rotation command in crontab */5 * * * * root /usr/sbin/logrotate /etc/logrotate.conf >/dev/null 2>&1 I am trying to rotate below tomcat logs owned by application... (0 Replies)
Discussion started by: shekar777
0 Replies

2. Red Hat

Network Teaming not working in RHEL/CentOS 7

I was testing Networking Teaming (activebackup) with a VM hosted on VmWare Workstation and VirtualBox, and the result is, if the active interface is down, the system is not using the backup interface. Tested on both CentOS / RHEL 7 Please find below the command I have used to configure teaming.... (0 Replies)
Discussion started by: atanubanerji
0 Replies

3. UNIX for Dummies Questions & Answers

vnc No Longer Working Correctly

Hello All, Yesterday, all day, I was using x11vnc and vncviewer to connect to a server. But today for some reason it is not working. I don't remember changing any settings or anything like that, but because it stopped working correctly I guess something has...? I'm issuing the exact same... (0 Replies)
Discussion started by: mrm5102
0 Replies

4. UNIX Desktop Questions & Answers

Jar command nor working in centos

Hi All, I have a jar file and I want to extract that jar file. I am using command jar xf Sample_Pack.jar After pressing enter this command returns no error and is not even executed. Pls help (1 Reply)
Discussion started by: Palak Sharma
1 Replies

5. Red Hat

Help using XEN in CentOS 5.9

Hey guys, I've been straddling with this issue for quite some time now and I'm getting absolutely nowhere with it. It took me a long time to get XEN up and running on my server. We only use SSH to manipulate our servers, but we finally got it up and running. Now I'm at the point of actually... (1 Reply)
Discussion started by: mccabec123
1 Replies

6. Red Hat

Help with setting up Networking for XEN on CentOS 5.9

Hey guys, I've reached the point of setting up VM's on XEN but the net installations seem to be failing when I am in the netinstall on the actual VM, so this leads me to believe that the networking on the host machine is not set up correctly. I am running CentOS 5.9 along with XEN and was just... (0 Replies)
Discussion started by: mccabec123
0 Replies

7. Red Hat

Os Open source dialer not working on Centos Asterisk platform

Hi We have one centos Server on Asterisk platform and using OS Open source dialer for dialing outbound connections.We are using eyebeam as a softphone for calling with Server ip 192.168.1.X.Today i found dialing issues with each client side phones.Not showing pause/resume button when browse... (0 Replies)
Discussion started by: Vaibhav.T
0 Replies

8. Emergency UNIX and Linux Support

New centos dedicated server - cant get mysql working

Hi all, I installed centos 5, with LAMP. httpd is working fine, ssh, ftp all working ok. But, when I try to use mysql its not, when I give the command mysql I get ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) (4 Replies)
Discussion started by: lawstudent
4 Replies

9. Red Hat

need help in installing Xen on Centos 6

Hello folks, I am trying to install Xen on centos 6! Kindly check out the following screen shots! What should I do? Regards (0 Replies)
Discussion started by: ahmedamer12
0 Replies
Login or Register to Ask a Question
vncserver(1)						     Virtual Network Computing						      vncserver(1)

NAME
vncserver - start or stop a VNC server SYNOPSIS
vncserver [:display#] [-name desktop-name] [-geometry widthxheight] [-depth depth] [-pixelformat format] [-fp font-path] [-fg] [-autokill] [Xvnc-options...] vncserver -kill :display# DESCRIPTION
vncserver is used to start a VNC (Virtual Network Computing) desktop. vncserver is a Perl script which simplifies the process of starting an Xvnc server. It runs Xvnc with appropriate options and starts a window manager on the VNC desktop. vncserver can be run with no options at all. In this case it will choose the first available display number (usually :1), start Xvnc with that display number, and start the default window manager in the Xvnc session. You can also specify the display number, in which case vnc- server will attempt to start Xvnc with that display number and exit if the display number is not available. For example: vncserver :13 Editing the file $HOME/.vnc/xstartup allows you to change the applications run at startup (but note that this will not affect an existing VNC session.) OPTIONS
You can get a list of options by passing -h as an option to vncserver. In addition to the options listed below, any unrecognised options will be passed to Xvnc - see the Xvnc man page, or "Xvnc -help", for details. -name desktop-name Each VNC desktop has a name which may be displayed by the viewer. The desktop name defaults to "host:display# (username)", but you can change it with this option. The desktop name option is passed to the xstartup script via the $VNCDESKTOP environment variable, which allows you to run a different set of applications depending on the name of the desktop. -geometry widthxheight Specify the size of the VNC desktop to be created. Default is 1024x768. -depth depth Specify the pixel depth (in bits) of the VNC desktop to be created. Default is 24. Other possible values are 8, 15 and 16 - any- thing else is likely to cause strange behaviour by applications. -pixelformat format Specify pixel format for Xvnc to use (BGRnnn or RGBnnn). The default for depth 8 is BGR233 (meaning the most significant two bits represent blue, the next three green, and the least significant three represent red), the default for depth 16 is RGB565, and the default for depth 24 is RGB888. -cc 3 As an alternative to the default TrueColor visual, this allows you to run an Xvnc server with a PseudoColor visual (i.e. one which uses a color map or palette), which can be useful for running some old X applications which only work on such a display. Values other than 3 (PseudoColor) and 4 (TrueColor) for the -cc option may result in strange behaviour, and PseudoColor desktops must have an 8-bit depth. -kill :display# This kills a VNC desktop previously started with vncserver. It does this by killing the Xvnc process, whose process ID is stored in the file "$HOME/.vnc/host:display#.pid". The -kill option ignores anything preceding the first colon (":") in the display argument. Thus, you can invoke "vncserver -kill $DISPLAY", for example at the end of your xstartup file after a particular application exits. -list Lists running VNC servers. -fp font-path If the vncserver script detects that the X Font Server (XFS) is running, it will attempt to start Xvnc and configure Xvnc to use XFS for font handling. Otherwise, if XFS is not running, the vncserver script will attempt to start Xvnc and allow Xvnc to use its own preferred method of font handling (which may be a hard-coded font path or, on more recent systems, a font catalog.) In any case, if Xvnc fails to start, the vncserver script will then attempt to determine an appropriate X font path for this system and start Xvnc using that font path. The -fp argument allows you to override the above fallback logic and specify a font path for Xvnc to use. -fg Runs Xvnc as a foreground process. This has two effects: (1) The VNC server can be aborted with CTRL-C, and (2) the VNC server will exit as soon as the user logs out of the window manager in the VNC session. This may be necessary when launching TigerVNC from within certain grid computing environments. -autokill Automatically kill Xvnc whenever the xstartup script exits. In most cases, this has the effect of terminating Xvnc when the user logs out of the window manager. FILES
Several VNC-related files are found in the directory $HOME/.vnc: $HOME/.vnc/xstartup A shell script specifying X applications to be run when a VNC desktop is started. If this file does not exist, then vncserver will create a default xstartup script which attempts to launch your chosen window manager. $HOME/.vnc/passwd The VNC password file. $HOME/.vnc/host:display#.log The log file for Xvnc and applications started in xstartup. $HOME/.vnc/host:display#.pid Identifies the Xvnc process ID, used by the -kill option. SEE ALSO
vncviewer(1), vncpasswd(1), vncconfig(1), Xvnc(1) http://www.tigervnc.org AUTHOR
Tristan Richardson, RealVNC Ltd. D. R. Commander VNC was originally developed by the RealVNC team while at Olivetti Research Ltd / AT&T Laboratories Cambridge. TightVNC additions were implemented by Constantin Kaplinsky. Many other people participated in development, testing and support. TigerVNC 13 Mar 2011 vncserver(1)