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