Sorry, I should have mentioned that I did all that. Interestingly, it seems to
be related to the subnet I am in (am using ssh to connect to the host.) I am
investigating further, but it appears that If I am on the same subnet as the
host, it works. I was working before on the other end of an ipsec tunnel, where
I got no love. Pretty sure this all worked before, but will need to spend some
more time digging to figure it out.
----- Original Message -----
From: "Daniel P. Berrange" <berrange@redhat.com>
To: "Jim Klein" <jklein@saugus.k12.ca.us>
Cc: "fedora-xen" <fedora-xen@redhat.com>
Sent: Monday, December 1, 2008 2:27:22 AM GMT -08:00 US/Canada Pacific
Subject: Re: [Fedora-xen] RHEL Update Virt-Manager VNC Problems
On Sun, Nov 30, 2008 at 07:02:00PM -0800, Jim Klein wrote:
> Just updated all my RHEL4 VMs and RHEL 5 hosts, and virt-manager can no
> longer connect to the consoles on the vms. Tried recreating VNC adapters
> in virt-manager to no avail. VMs running kernel 2.6.9-78.0.8.ELxenU. Must
> be missing something, but not sure where to look. Any assistance would be
> greatly appreciated.
Use ''virsh dumpxml'' to look at the running domain config. It
should show
you a element like "<graphics type=''vnc''
port=''5900''/>". If the port
number is -1, then its failed to start VNC for some reason. If the graphics
tag is missing completely then the config file is wrong.
Daniel
--
|: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|