WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Re: pv_ops dom0 USB fixed

To: "Jeremy Fitzhardinge" <jeremy@xxxxxxxx>
Subject: Re: [Xen-devel] Re: pv_ops dom0 USB fixed
From: "Todd Deshane" <deshantm@xxxxxxxxx>
Date: Tue, 16 Dec 2008 00:04:44 -0500
Cc: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Andrew Lyon <andrew.lyon@xxxxxxxxx>, Aviv Grafi <aviv@xxxxxxxxxxxx>, Ian Campbell <Ian.Campbell@xxxxxxxxxx>
Delivery-date: Mon, 15 Dec 2008 21:05:16 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:reply-to :to:subject:cc:in-reply-to:mime-version:content-type:references; bh=s1DMaRLxTbihh5MPk4ekJC3ywhKb9QYCMP458qjAg80=; b=IZhDPyCr0lf3ODpSzM2aENJ73QkpEIDCs7BBTP1+WlDNITXqk5WCJv95RUlv/dQ0Lx 1sfTS7DxE8qB02bpeF66NAkWGs4nde85mbbXeP6/wLTMrFhW7SGNm2rifZMftInfSZ6s PmuUjIMEQ9TbH+oam822i+1h88mnMN9zjwTcE=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:to:subject:cc:in-reply-to :mime-version:content-type:references; b=PIDnyPbRIVQ5D/kNQS866zf+ATUmxE4vRN/HowWyVz3sRYlLDB9z9AI5movNB2VDoc KdGmvUFGk1yDaC5CWhG6J4OXM80ELka8ym+wnkBdZtEAXCOAtR1W9Vg+H920LDvQ2+6U cNoqV44UAL6OPmPUNcMjuE0tgXVs/LRnrPQZI=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4946BBF5.30508@xxxxxxxx>
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>
References: <4940210C.1060401@xxxxxxxx> <f4527be0812121420i2ff3ef03g1842170eb52f9de8@xxxxxxxxxxxxxx> <4942E6FD.6080601@xxxxxxxx> <f4527be0812130556v6ec00812y7f0e906ec97b56cd@xxxxxxxxxxxxxx> <1e16a9ed0812131102s79d231depef1466fda8e2b897@xxxxxxxxxxxxxx> <f4527be0812131126u2bfca838y2a4c5e65a774c5af@xxxxxxxxxxxxxx> <1e16a9ed0812131753m3412e3ffgd9028185c90c2c40@xxxxxxxxxxxxxx> <1229334549.25349.82.camel@xxxxxxxxxxxxxxxxxxxxxx> <1e16a9ed0812151015v50867776l100c1830380f8411@xxxxxxxxxxxxxx> <4946BBF5.30508@xxxxxxxx>
Reply-to: deshantm@xxxxxxxxx
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
So I've been getting things going on my test box here.  What I've observed:

When I set the SATA controller to either "Legacy" mode or "Native / IDE" mode in the BIOS, it works fine.

When I set it to AHCI, I see the same timeouts on IDENTIFY, but the DVD drive is detected properly.

USB seems to be working fine.  If I plug in a memory stick,  I can mount the filesystem and read things from it.


In these logs, it looks like you've overlooked the patch I added on Friday (vmap-allow-unflush-tlb.patch), and your udevd processes have been caught up in a deadlock which is preventing them from doing their thing.  I suspect that's the root cause of your problems.

  J

You are right. I hadn't had a chance to try the latest kernel until today.

I can now boot the usb disk with no problem.

I can also now boot the hard drive in ATA mode (in the bios called RAID, with a
note that says if not labeled then ATA mode)

I also was able to create an HVM guest (ubuntu 8.04 from an ISO file)

config below:

kernel="/usr/lib64/xen/boot/hvmloader"
builder="hvm"
device_model = "/usr/lib64/xen/bin/qemu-dm"
disk=['tap:aio:/xen/images/hvm.disk,hda,w','file:/xen/images/ubuntu-8.04.1-desktop-amd64.iso,hdc:cdrom,r']
disk=['tap:aio:/xen/images/hvm.disk,hda,w']
#sdl=1
vnc=1
vncviewer="yes"
boot="dc"
memory=1024
#vif=['type=ioemu,bridge=eth0']
acpi=0

Will I be able to do passthrough stuff on this VT-d box?

If so, I'll give it a shot tomorrow.
For example, could I passthrough a NIC?

So in general the dom0 kernel seems quite functional.

Some kinks to work out here and there, but it seems
quite usable (with some limitations).

What is the plan going forward?

What else needs to be tested etc.?

Cheers,
Todd

--
Todd Deshane
http://todddeshane.net
http://runningxen.com
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel