public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: "Piotr Jaroszyński" <p.jaroszynski@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: kvm hardlocks on hp dv9010us
Date: Mon, 11 May 2009 12:26:23 +0300	[thread overview]
Message-ID: <4A07EF3F.9000300@redhat.com> (raw)
In-Reply-To: <d77765540905101220u2a10a66dsaa5d7f253d60c8fc@mail.gmail.com>

Piotr Jaroszyński wrote:
> Hello,
>
> kvm-85 with vanilla kernel 2.6.29.3 (kvm modules from kernel) hard locks for me:
> - sometimes at the very beginning, just after the QEMU window opens,
> but nothing is displayed before the hardlock.
> - sometimes during runtime with various guests: e.g. Windows XP 64bit
> and Exherbo 64bit [1]. The latter one seems to trigger it very often,
> so I should be able to test any fixes quickly.
>
> It has been also happening with other guest OSes and older versions of
> kvm and older kernels.
>
> This is how i run kvm:
>
> kvm \
>         -hda /home/data/guests/exherbo-kvm-amd64-20090504.img \
>         -localtime \
>         -net nic -net tap,script=no,downscript=no,ifname=tap0
>
> Also tried taskset 1 kvm ...
>
> I have a hp dv9010us laptop (one of those that hard locked before
> CONFIG_IO_DELAY_* options were introduced in kernel - not sure if it
> may be related at all).
>
> Is there anything I could do to debug it and provide more info?
>   

Are you updated to the latest BIOS revision?


-- 
error compiling committee.c: too many arguments to function


  parent reply	other threads:[~2009-05-11  9:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-10 19:20 kvm hardlocks on hp dv9010us Piotr Jaroszyński
2009-05-10 20:55 ` Piotr Jaroszyński
2009-05-11  9:26 ` Avi Kivity [this message]
2009-05-11 10:46   ` Piotr Jaroszyński
2009-05-11 10:57     ` Avi Kivity
2009-05-11 11:00       ` Piotr Jaroszyński
2009-05-11 11:20 ` Avi Kivity
2009-05-11 11:37   ` Piotr Jaroszyński

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=4A07EF3F.9000300@redhat.com \
    --to=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=p.jaroszynski@gmail.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