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: deshantm@xxxxxxxxx
Subject: Re: [Xen-devel] Re: pv_ops dom0 USB fixed
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Date: Tue, 16 Dec 2008 01:34:29 -0800
Cc: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Andrew Lyon <andrew.lyon@xxxxxxxxx>, Aviv Grafi <aviv@xxxxxxxxxxxx>, Ian Campbell <Ian.Campbell@xxxxxxxxxx>
Delivery-date: Tue, 16 Dec 2008 01:34:52 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1e16a9ed0812152104r3de1c0c6q58fa7471ed9d9a00@xxxxxxxxxxxxxx>
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> <1e16a9ed0812152104r3de1c0c6q58fa7471ed9d9a00@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.18 (X11/20081119)
Todd Deshane wrote:

    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.

Good.

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)

Excellent.

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

Oh, good, I hadn't tried that yet. The dom0 kernel doesn't really care much whether domains are pv or hvm, but its nice to know it works.

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

No, I haven't looked at passthrough at all yet.

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.?

Well, it would be nice to get to the bottom of why AHCI isn't working. If legacy mode works OK, then I guess that's an acceptable workaround for now. But it does suggest there's something screwy going on that will probably bite us on other devices too.

The big missing feature is netback. Once that's done all the major functionality will be present.

At that point the the TODO list would be something along the lines of:

   * blktap
   * MSI support
   * other backends (framebuffer, pci passthrough, etc)
   * wider testing on more hardware
   * performance tuning
   * complete decommissioning of 2.6.18-xen

   J

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel