public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: bugzilla-daemon@bugzilla.kernel.org
Cc: kvm@vger.kernel.org, stefan.bosak@gmail.com
Subject: Re: [Bug 38672] New: KVM guest boot crashed
Date: Sat, 02 Jul 2011 09:44:44 +0200	[thread overview]
Message-ID: <4E0ECC6C.9020905@web.de> (raw)
In-Reply-To: <bug-38672-28872@https.bugzilla.kernel.org/>

[-- Attachment #1: Type: text/plain, Size: 2040 bytes --]

On 2011-07-02 08:56, bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=38672
> 
>            Summary: KVM guest boot crashed
>            Product: Virtualization
>            Version: unspecified
>     Kernel Version: 3.0.0-rc5+
>           Platform: All
>         OS/Version: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: high
>           Priority: P1
>          Component: kvm
>         AssignedTo: virtualization_kvm@kernel-bugs.osdl.org
>         ReportedBy: stefan.bosak@gmail.com
>         Regression: Yes
> 
> 
> Windows Server 2008 R2 KVM guest crashed during boot process.
> This situation also occur on other linux based guests.

What other Linux guests precisely? None of the Windows and Linux guest I
have around expose this problem.

What is your qemu command line?

> 
> Bug is in: git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git
> not in: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git.
> 
> Qemu-kvm repository checkouted before 9 days works well.
> 
> Problem could be in this:
> 
> author    Jan Kiszka <jan.kiszka@siemens.com>    
>     Mon, 27 Jun 2011 10:23:35 +0000 (12:23 +0200)
> committer    Avi Kivity <avi@redhat.com>    
>     Tue, 28 Jun 2011 08:20:08 +0000 (11:20 +0300)
> commit    bcd4f22796ebda2934a980060ea704ebedb46173
> tree    f16fe58d2d4120c7b94f23ddef3afb61beb30dfc    tree | snapshot
> parent    59539c913383fdd3350681301b44f02fa7ee2757    commit | diff
> 
> 
> author    Jan Kiszka <jan.kiszka@siemens.com>    
>     Mon, 27 Jun 2011 10:22:28 +0000 (12:22 +0200)
> committer    Avi Kivity <avi@redhat.com>    
>     Tue, 28 Jun 2011 08:18:58 +0000 (11:18 +0300)
> commit    59539c913383fdd3350681301b44f02fa7ee2757
> tree    bfdf23a13004d08d04589d02d3c4c754da3dd076    tree | snapshot
> parent    b7496707af10ce2827d0803c9e46ca8ddc543716    commit | diff
> 

Can you bisect which change precisely introduced the regression?

Thanks,
Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

  reply	other threads:[~2011-07-02  7:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-02  6:56 [Bug 38672] New: KVM guest boot crashed bugzilla-daemon
2011-07-02  7:44 ` Jan Kiszka [this message]
2011-07-02  8:24 ` [Bug 38672] " bugzilla-daemon
2011-07-02  9:05 ` bugzilla-daemon
2011-07-03  0:48 ` bugzilla-daemon
2011-07-03  1:00 ` bugzilla-daemon
2011-07-05 23:00 ` bugzilla-daemon
2011-07-05 23:44 ` bugzilla-daemon
2011-07-05 23:55 ` bugzilla-daemon
2011-07-06 11:45 ` bugzilla-daemon
2011-07-06 16:39 ` bugzilla-daemon
2011-07-06 18:32 ` bugzilla-daemon
2011-07-10 11:07 ` bugzilla-daemon
2011-07-10 11:09 ` bugzilla-daemon

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=4E0ECC6C.9020905@web.de \
    --to=jan.kiszka@web.de \
    --cc=bugzilla-daemon@bugzilla.kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=stefan.bosak@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