On Sat, Oct 19, 2013 at 11:15 PM, Earl A Ramirez earlaramirez@gmail.comwrote:
Sorry for top posting, this is the only option that the phone allow.
If the host is running a X server you can use -X option with ssh.
$ ssh -X user@host And start virt-manager to manage the VMs.
I am running putty from Windows. I do have X11 forwarding enabled. But I still get 'could not open display' I though perhaps I needed to install Xming, but I don't have admin rights on the Windows box, so I couldn't do that.
On Oct 20, 2013 11:40 AM, "Larry Martell" larry.martell@gmail.com wrote:
On Saturday, October 19, 2013, Earl Ramirez wrote:
On Sat, 2013-10-19 at 21:18 -0600, Larry Martell wrote:
On Saturday, October 19, 2013, Earl Ramirez wrote:
On Sat, 2013-10-19 at 17:23 -0600, Larry Martell wrote:
On Sat, Oct 19, 2013 at 4:56 PM, Larry Martell <
larry.martell@gmail.com
wrote:
> I had posted last week about trying to get VNC working. I was
never
> successful nor were multiple admins. But we realized that all
the
hosts we
> tried on were VMs. We followed the same procedure ( > http://wiki.centos.org/HowTos/VNC-Server) on a machine with
physical
HW
> and it worked with no problem. But on the VM I can connect,
but I
don't get
> any window displayed. Here is what is in the log: > > Sat Oct 19 18:39:55 2013 > vncext: VNC extension running! > vncext: Listening for VNC connections on all
interface(s),
port
5902
> vncext: created VNC server for screen 0 > GNOME_KEYRING_SOCKET=/tmp/keyring-Y6Tg3c/socket > SSH_AUTH_SOCK=/tmp/keyring-Y6Tg3c/socket.ssh > GNOME_KEYRING_PID=19728 > Failed to play sound: File or data not found > > ** (nm-applet:19775): WARNING **: <WARN> request_name(): Could
not
> acquire the NetworkManagerUserSettings service. > Error: (9) Connection ":1.552" is not allowed to own the
service
> "org.freedesktop.NetworkManagerUserSettings" due to security
policies
in
> the configuration file >
Googling that error I found this: https://bbs.archlinux.org/viewtopic.php?id=63576 and I followed
the
advice
there. Now I don't get that error, but I still get no display.
Now
all I
get in the log is this:
19/10/2013 07:14:27 PM [IPv6] Got connection from client ::ffff:10.250.151.75 19/10/2013 07:14:27 PM other clients: 19/10/2013 07:14:27 PM Client Protocol Version 3.7 19/10/2013 07:14:27 PM Advertising security type 2 19/10/2013 07:14:28 PM Client returned security type 2
My xstartup file is identical on the VM and the physical host.
Does anyone out there have VNC working on a VM?
> 19/10/2013 06:39:59 PM Autoprobing TCP port in (all) network
interface
> 19/10/2013 06:39:59 PM Listening IPv{4,6}://*:5900 > 19/10/2013 06:39:59 PM Autoprobing selected port 5900 > 19/10/2013 06:39:59 PM Advertising authentication type: 'VNC > Authentication' (2) > 19/10/2013 06:39:59 PM Advertising security type: 'VNC
Authentication'
(2)
> > (polkit-gnome-authentication-agent-1:19796):
GLib-GObject-WARNING
**:
> cannot regster existing type `_PolkitError' > > (polkit-gnome-authentication-agent-1:19796): GLib-CRITICAL **: > g_once_init_leave: assertion `initialization_value != 0' failed > Initializing nautilus-gdu extension > Initializing nautilus-open-terminal extension > > ** (gnome-panel:19761): CRITICAL **:
panel_applet_frame_change_background:
> assertion `PANEL_IS_WIDGET (GTK_WIDGET (frame)->parent)' failed > > (polkit-gnome-authentication-agent-1:19796):
polkit-gnome-1-WARNING
**: No
> icon for themed icon with name
'preferences-system-network-proxy'
> Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW
message
> with a timestamp of 0 for 0x2c00003 (Authentica)
From the KVM Guest, under "Show Virtual Hardware Detail", I change
the
type from VNC to Spice from the Display option, which was "Display VNC" prior to the change.
My only access to the host is via ssh so I don't think I can do that.
You don't have to make the change if you don't want to as I was able to connect to the KVM Guest after it was started with the following
command
and the Display was configured for VNC: $ sudo virsh start KVM_Guest
Once there is no sessions for the KVM that you are connecting to, you will be fine.
I'll try that tomorrow.