From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gerry Reno Subject: Re: After upgrading from F7 kvm-65-15 to F10 kvm-74-10 Date: Sun, 29 Mar 2009 21:18:06 -0400 Message-ID: <49D01DCE.9010401@verizon.net> References: <49CF9EBB.3070404@verizon.net> <49CFEC54.60507@verizon.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit To: kvm@vger.kernel.org Return-path: Received: from vms173005pub.verizon.net ([206.46.173.5]:35606 "EHLO vms173005pub.verizon.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751043AbZC3BSO (ORCPT ); Sun, 29 Mar 2009 21:18:14 -0400 Received: from [192.168.2.100] ([72.91.189.24]) by vms173005.mailsrvcs.net (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit)) with ESMTPA id <0KHA003RZOYC2UOT@vms173005.mailsrvcs.net> for kvm@vger.kernel.org; Sun, 29 Mar 2009 20:18:12 -0500 (CDT) In-reply-to: <49CFEC54.60507@verizon.net> Sender: kvm-owner@vger.kernel.org List-ID: Gerry Reno wrote: > Gerry Reno wrote: >> Hi, >> We had setup a number of VM's using KVM-65 running on F7 some time >> ago. We just ocmpleted upgrading a number of hosts to F10 and with >> that came KVM-74-10. We had some problems after that upgrade. >> we are having a lot of problems with the dreaded "TCP/IP VNC >> connection to hypervisor host has been refused or disconnected". >> This has now happened to one of the VM's after it was shutdown and >> then we tried to Run it again and we haven't found a way to reconnect >> to it. This is happening on a VM that was just anaconda upgraded to F9 and is on its first reboot. But that reboot we cannot make happen because the VM refuses to run. >> Also, another VM has this weird problem that when you run it, it >> looks like its running because the screen keeps changing size but all >> we see is a blank palette on the console page, no screen at all, but >> the thing is running. How do we fix these things? We kicked everyone off the VM's and rebooted the host and now we have access again to this VM. >> > And we have a VM that when you start it says its Connecting to console > for guest. But the console message just stays like that and yet the > machine completely boots up and we can log into it remotely in a > terminal window. We just cannot get a console screen. This also got corrected through a host reboot. So the only problem I'm very concerned about at the moment is the VM that was at the point of first reboot after the successful completion of an F9 install. Any suggestions as to how to get that VM running? Regards, Gerry