From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: Solaris 10 U2 installation failure Date: Mon, 01 Jan 2007 17:39:31 +0200 Message-ID: <45992B33.8070204@qumranet.com> References: <4597F8DF.6010602@qumranet.com> <4598C3CE.3050802@qumranet.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Return-path: To: Parag Warudkar In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.org Parag Warudkar wrote: > Avi Kivity writes: > > >> Parag Warudkar wrote: >> >>> And this in dmesg - >>> kvm_handle_exit: unexpected, valid vectoring info >>> and exit reason is 0x9 >>> >>> >> Exit 9 is a hardware task switch, which is not supported by vmx. It's >> unlikely solaris is using it; probably some other failure before caused >> it to take the wrong route. >> >> > > Yeah something obviously went wrong when the installation got stuck earlier. > One thing which is good is that the installation seems to get stuck at the > same place every time. > > Is there a way to know where it is getting stuck down under > in the bowels of KVM? > > You can add a signal handler to qemu/kvm-qemu.c to call kvm_get_regs() and print them out. From the rip you can see what Solaris is doing (assuming you have debug symbols). -- error compiling committee.c: too many arguments to function ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV