[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] virtio-blk/qdev failure in the current git tree

From: Gerd Hoffmann
Subject: Re: [Qemu-devel] virtio-blk/qdev failure in the current git tree
Date: Tue, 11 Aug 2009 21:28:41 +0200
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1b3pre) Gecko/20090513 Fedora/3.0-2.3.beta2.fc11 Lightning/1.0pre Thunderbird/3.0b2

On 08/11/09 18:36, Christoph Hellwig wrote:
On Tue, Aug 11, 2009 at 06:13:02PM +0200, Christoph Hellwig wrote:
With the fix pulled it the guest kernel now hangs after

        input: ImExPS/2 Generic Explorer Mouse as /class/input/input2
        Clocksource tsc unstable (delta = -782142631 ms)

when reducing the config to just one virtio-blk device it books, but
with a longish break at the point where the original config hangs.

The culprit is commit d176c495b6664b72dc1e595f6e89dc5648aa248b

        qdev-ify virtio-blk.

reverting it (needs some manual work due to the macrofication of the
qdev attributes) fixes the boot again.

Hmm. I suspect this is not related to qdev and virtio-blk at all. I've noticed now and then that some pci devices don't work if you have many of them. Didn't try (yet) to root-cause that one.

The commit changes the initialization order of the virtio-blk devices, which probably makes them being placed in other PCI slots, which in turn might uncover the bug mentioned above in your setup.

How are the pci devices assigned to slots with and without the patch?

Does removing the balloon device (-balloon none) change the behavior?
Does removing the nic (-net none) too change the behavior?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]