<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Arial; font-size: 10pt; color: #000000'>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.<br><br><br>----- Original Message -----<br>From: "Daniel P. Berrange" <berrange@redhat.com><br>To: "Jim Klein" <jklein@saugus.k12.ca.us><br>Cc: "fedora-xen" <fedora-xen@redhat.com><br>Sent: Monday, December 1, 2008 2:27:22 AM GMT -08:00 US/Canada Pacific<br>Subject: Re: [Fedora-xen] RHEL Update Virt-Manager VNC Problems<br><br>On Sun, Nov 30, 2008 at 07:02:00PM -0800, Jim Klein wrote:<br>> Just updated all my RHEL4 VMs and RHEL 5 hosts, and virt-manager can no <br>> longer connect to the consoles on the vms. Tried recreating VNC adapters <br>> in virt-manager to no avail. VMs running kernel 2.6.9-78.0.8.ELxenU. Must<br>> be missing something, but not sure where to look. Any assistance would be<br>> greatly appreciated. <br><br>Use 'virsh dumpxml' to look at the running domain config. It should show<br>you a element like "<graphics type='vnc' port='5900'/>". If the port<br>number is -1, then its failed to start VNC for some reason. If the graphics<br>tag is missing completely then the config file is wrong.<br><br>Daniel<br>-- <br>|: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :|<br>|: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :|<br>|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|<br>|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|<br></div></body></html>