public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Parag Warudkar <kernel-stuff-Wuw85uim5zDR7s880joybQ@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Solaris 10 U2 installation failure
Date: Mon, 01 Jan 2007 17:39:31 +0200	[thread overview]
Message-ID: <45992B33.8070204@qumranet.com> (raw)
In-Reply-To: <loom.20070101T163114-834-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>

Parag Warudkar wrote:
> Avi Kivity <avi@...> 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

  parent reply	other threads:[~2007-01-01 15:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-30 19:19 Solaris 10 U2 installation failure Parag Warudkar
     [not found] ` <loom.20061230T201339-43-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2006-12-31 17:52   ` Avi Kivity
2006-12-31 22:06     ` Parag Warudkar
2006-12-31 22:26       ` Parag Warudkar
     [not found]         ` <loom.20061231T232415-117-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2007-01-01  8:18           ` Avi Kivity
2007-01-01 15:34             ` Parag Warudkar
     [not found]               ` <loom.20070101T163114-834-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2007-01-01 15:39                 ` Avi Kivity [this message]
     [not found]                   ` <45992B33.8070204-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-01-02 23:41                     ` digital tech support
2007-01-03  2:02             ` Parag Warudkar
     [not found]               ` <loom.20070103T030116-115-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2007-01-03  8:38                 ` Avi Kivity
2007-01-03 21:02                   ` Parag Warudkar
     [not found]                     ` <loom.20070103T215402-599-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2007-01-04  9:18                       ` Avi Kivity

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=45992B33.8070204@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=kernel-stuff-Wuw85uim5zDR7s880joybQ@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox