From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: on starting HVM-domU whole system freezes with "soft lockup - CPU X stuck for XXs! [qemu-dm:...]" [xen 4.0, xen 4.1] Date: Mon, 18 Apr 2011 17:02:30 -0400 Message-ID: <20110418210230.GA8003@dumpdata.com> References: <4DA617EC.2020200@gmx.net> <20110414132327.GG5548@dumpdata.com> <4DA8C296.1010502@gmx.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <4DA8C296.1010502@gmx.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "MadLoisae@gmx.net" Cc: Keir Fraser , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Sat, Apr 16, 2011 at 12:11:34AM +0200, MadLoisae@gmx.net wrote: > I just saw that I made two threads instead of one ... hopefully this > email now receives in the correct one. ;) The log file is a bit stange. The HVM says: (XEN) HVM1: ata0 master: QEMU HARDDISK ATA-7 Hard-Disk ( 0 MBytes) Is your /home/guest1.dsk really 0 megabytes? Have you tried to use a physical device (say LVM logical volume) just to eliminate it being the blktap at fault here? (there was a bug in the blktap driver that Daniel posted recently here). Instead of using the configuration with the sxp expression can you just post the .xm one please? They are much easier to read.