From: "Sławomir Skowron" <szibis@gmail.com>
To: Josh Durgin <josh.durgin@dreamhost.com>
Cc: Tommi Virtanen <tommi.virtanen@dreamhost.com>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: RBD attach via libvirt to kvm vm - VM kernel hang
Date: Wed, 28 Mar 2012 21:36:31 +0200 [thread overview]
Message-ID: <6656798785653552046@unknownmsgid> (raw)
In-Reply-To: <4F733B2A.7050902@dreamhost.com>
On 28 mar 2012, at 18:24, Josh Durgin <josh.durgin@dreamhost.com> wrote:
> On 03/28/2012 09:13 AM, Tommi Virtanen wrote:
>> 2012/3/28 Sławomir Skowron<szibis@gmail.com>:
>>> VM on-01 with config like in attachment (dumpxml) - hang, after
>>> attaching rbd device with kernel_bug in attachment.
>>
>> [ 68.630913] BUG: unable to handle kernel NULL pointer dereference
>> at 0000000000000049
>> [ 68.632016] IP: [<ffffffff8130a6a5>] pci_find_capability+0x15/0x60
>> ...
>> [ 68.632016] Call Trace:
>> [ 68.632016] [<ffffffff8131a9f7>] pci_set_payload+0xa7/0x140
>> [ 68.632016] [<ffffffff8131ae38>] pci_configure_slot.part.6+0x18/0x100
>> [ 68.632016] [<ffffffff8131af52>] pci_configure_slot+0x32/0x40
>> [ 68.632016] [<ffffffffa003a7e8>] enable_device+0x188/0x9a0 [acpiphp]
>> [ 68.632016] [<ffffffff81307349>] ? pci_bus_read_config_dword+0x89/0xa0
>> ...
>>
>> Well, that sure looks like a bug. I can't tell whether it's in QEmu,
>> the QEmu rbd driver, or what. Josh, have you seen a crash like this?
>
> I've not seen a crash like this before. I'm not aware of RBD being
> treated differently from other block devices in the pci layer in qemu,
> so I'd guess this is a qemu or guest kernel bug.
>
> Does attaching a non-rbd disk (still using the virtio driver) cause the
> same problem?
File disk via virtio exist in vm config. But this configuration works
stable for some time without rbd.
We use for tests qemu-kvm 1.0.0+dfsg+rc2-1~oneiric1 with distro
libvirt, but we experience some stabilization problems with vf
functions on Intel 10GE cards. Rbd cause some problems too.
With same kernel as used now on Guest, and with this 1.0.0-rc2 kvm rbd
attaching goes smooth, but after some time, when rbd was mounted in
VM, network goes down.
Only with console/vnc we can go into VM, and then reload network.
After that everything was fine for some time, and again.
That's why we try newer libvirt, and kvm. And now vf in Intel network
card work like a charm, but after attaching rbd crash the vm as you
can see. Kernel on VM is always stay as bottom.
We try to create kernel on newer version of stable in oneiric, and try
to reproduce, but i feel that kernel is not a trigger for this bug.
> If not, what distro and kernel version is the guest
> running?
It's distro kernel 3.0.0-13-server from ubuntu oneiric with compiled
compatibility of xen. That's why is 3.0.0-13-xen.
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-03-28 19:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-28 13:27 RBD attach via libvirt to kvm vm - VM kernel hang Sławomir Skowron
2012-03-28 16:13 ` Tommi Virtanen
2012-03-28 16:24 ` Josh Durgin
2012-03-28 19:36 ` Sławomir Skowron [this message]
2012-04-02 16:33 ` Tommi Virtanen
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=6656798785653552046@unknownmsgid \
--to=szibis@gmail.com \
--cc=ceph-devel@vger.kernel.org \
--cc=josh.durgin@dreamhost.com \
--cc=tommi.virtanen@dreamhost.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.