From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: Re: pv_ops dom0 USB fixed
Date: Wed, 17 Dec 2008 11:33:23 -0800
Message-ID: <49495403.1000400@goop.org>
References: <4940210C.1060401@goop.org>		<f4527be0812120112y13e74752kbd3d17d7daa98848@mail.gmail.com>		<4942D0F9.7080903@goop.org>		<f4527be0812121420i2ff3ef03g1842170eb52f9de8@mail.gmail.com>		<4942E6FD.6080601@goop.org>		<f4527be0812130556v6ec00812y7f0e906ec97b56cd@mail.gmail.com>		<1e16a9ed0812131102s79d231depef1466fda8e2b897@mail.gmail.com>		<f4527be0812131126u2bfca838y2a4c5e65a774c5af@mail.gmail.com>		<1e16a9ed0812131753m3412e3ffgd9028185c90c2c40@mail.gmail.com>		<1229334549.25349.82.camel@zakaz.uk.xensource.com>	<1e16a9ed0812151015v50867776l100c1830380f8411@mail.gmail.com>
	<4946BBF5.30508@goop.org> <49493182.9070707@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <49493182.9070707@redhat.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: deshantm@gmail.com, Aviv Grafi <aviv@neocleus.com>, Xen-devel <xen-devel@lists.xensource.com>, Andrew Lyon <andrew.lyon@gmail.com>, Ian Campbell <Ian.Campbell@citrix.com>
List-Id: xen-devel@lists.xenproject.org

Gerd Hoffmann wrote:
>   Hi,
>
>   
>> When I set it to AHCI, I see the same timeouts on IDENTIFY, but the DVD
>> drive is detected properly.
>>     
>
> Hopping in here ;)
>
> /me uses AHCI too.  Things work just fine for me initially.  After
> running for a while (more than just bootup:  I can login via ssh, do
> builds, run guests, ...) I suddenly get errors disk errors.  From a
> brief look it seems the disk stops responding to disk commands
> altogether.  The box is still sort-of alive at this point, I can even
> login remotely and grab a dmesg log.  Probably due to the important
> stuff being in the page cache, so no disk I/O is needed for that ...
>
> Intel 64bit box, 6GB RAM (dom0_mem=2g), running rawhide.
>   

OK, that's interesting.  The symptom is the same (drive stops talking), 
but after a while rather than immediate.  That suggests there might be 
some issue with what memory gets allocated or something?

Does putting the controller in IDE/legacy mode work OK?

Oooh, sound.  Does it work?

What are all the libvirtd/qemu-dm crashes?  Are they pertinent?

    J