This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] ahci errors with xen 4.1.1, linux 3.0, virtualbox

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] ahci errors with xen 4.1.1, linux 3.0, virtualbox
From: Sven Köhler <sven.koehler@xxxxxxxxx>
Date: Sat, 30 Jul 2011 17:32:06 +0200
Delivery-date: Sat, 30 Jul 2011 08:31:40 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:5.0) Gecko/20110705 Thunderbird/5.0

when booting xen 4.1.1, vanilla linux 3.0 (+ vga patch, all 64bit)
inside a virtualbox with 4 CPUs (virtualbox 4.1, my host has 2 cores, 2
threads each), the virtual machine has serious AHCI problems during
boot. Sometimes up to the point, that it doesn't boot at all. However,
usually after a few errors everything works fine.

I tried clocksource=xen, but it didn't improve the behaviour.
When reducing the number of CPUs seems to decreases the likelyhood of
AHCI errors (well, this is my experience so far).

Any ideas, what might be the cause of this?
You find a tgz with dmesg, xm dmesg, etc.

The errors also happened with konrad's 2.6.39 kernel.
The errors never happen with the good old 2.6.18.


Attachment: ahci.tgz
Description: application/compressed-tar

Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>