public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Nicholas Amon <namon@xceedium.com>
Cc: kvm <kvm@vger.kernel.org>
Subject: Re: Unable to single-step in kvm, always results in a resume
Date: Fri, 22 Jan 2010 16:06:24 +0100	[thread overview]
Message-ID: <4B59BEF0.80407@siemens.com> (raw)
In-Reply-To: <4B5922BE.7030002@xceedium.com>

Nicholas Amon wrote:
> So now I can step instruction but my breakpoints do not work.  I have 
> verified that disabling kvm restores the breakpoint functionality.  Any 
> suggestions?

What kind of breakpoints, hardware-assisted or normal BPs? Are you
trying to break into real-mode code (as stated below - BTW, top-postings
should be avoided!) that happens to run on a non-brand-new Intel host? I
never fully tested how well guest debugging works if KVM has to emulate
instructions, and I wouldn't be surprised if there are "limitations".

Jan

> Jan Kiszka wrote:
>> Hi Nicholas,
>>
>> please don't drop CCs on reply.
>>
>> Nicholas Amon wrote:
>>   
>>> Hi Jan,
>>>
>>> Thanks for responding.  Yes, I am able to step instruction when I 
>>> disable kvm w/ the no-kvm option.  My host kernel is 64bit  2.6.27 and 
>>> the program that I am debugging is 32 bit but starts in real mode.  But 
>>> the KVM module I am running is from kvm-88.  Is there anyway I can check 
>>> the version definitively?
>>>     
>> kvm modules issue a message when being loaded, check your kernel log.
>> qemu-kvm gives you the version via -version.
>>
>> OK, the problems you see is likely related to the very old versions you
>> use. Update to recent kvm-kmod (2.6.32 series) and qemu-kvm (0.12
>> series) and retry.
>>
>> Jan
>>
>>   
>>> Thanks,
>>>
>>> Nicholas
>>>
>>> Jan Kiszka wrote:
>>>     
>>>> Jan Kiszka wrote:
>>>>   
>>>>       
>>>>> Nicholas Amon wrote:
>>>>>     
>>>>>         
>>>>>> Hi All,
>>>>>>
>>>>>> I am trying to single-step through my kernel using qemu and kvm.  I have
>>>>>> run qemu via:  qemu-system-x86_64 -s -S -hda
>>>>>> /home/nickamon/lab1/obj/kernel.img and also connected to the process
>>>>>> using gdb.
>>>>>>
>>>>>> Problem is that whenever I try and step instruction, it seems to resume
>>>>>> my kernel rather than allowing me to progress instruction by
>>>>>> instruction.  I have built the kvm snapshot from git and still no luck. 
>>>>>> Tried following the code for a few hours and have no luck.  Any
>>>>>> suggestions?
>>>>>>       
>>>>>>           
>>>>> What's you host kernel or kvm-kmod version?
>>>>>
>>>>>     
>>>>>         
>>>> ...and does -no-kvm make any difference (except that it's much slower)?
>>>>
>>>> Jan
>>>>
>>>>   
>>>>       

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux

  reply	other threads:[~2010-01-22 15:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-19 14:23 Unable to single-step in kvm, always results in a resume Nicholas Amon
2010-01-19 15:11 ` Jan Kiszka
2010-01-19 15:13   ` Jan Kiszka
     [not found]     ` <4B566CB5.7080804@xceedium.com>
2010-01-20 10:08       ` Jan Kiszka
2010-01-20 14:34         ` Nicholas Amon
2010-01-22  3:59         ` Nicholas Amon
2010-01-22 15:06           ` Jan Kiszka [this message]
2010-01-29  3:57             ` Nicholas Amon

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=4B59BEF0.80407@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=kvm@vger.kernel.org \
    --cc=namon@xceedium.com \
    /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