[Libvir] Bug with libvirt in Xen 3.0.1?

Hi, I think I may have found a bug in libvirt and wanted see what people thought. I'm using the stock FC5 installation at the moment (with xen 3.0.1), and the newest version of libvirt. I am noticing that with xen 3.0.1 and newer versions of libvirt, getDomainsID() seems to return bogus values. For example: [root@test05 ~]# virsh list Id Name State ---------------------------------- 0 Domain-0 running libvir: Xen Daemon error : GET operation failed: No such domain 65486 libvir: Xen Daemon error : GET operation failed: No such domain 2986 But, if I use xm, I get what I expect: [root@test05 ~]# xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 1507 2 r----- 387.5 vm1 1 256 1 -b---- 151.3 vm2 2 256 1 -b---- 87.9 After some digging around in the code, I believe that libvirt is incorrectly identifying the hypervisor as being "old" in xen_internal.c:xenHypervisorInit, and is therefore passing the incorrect parameter structure into the hypervisor when it makes its ioctl in xen_internal.c:xenHypervisorListDomains. I've tried this same test on a system running xen 3.0.2, and as I expected everything works fine. So, there must be something different about xen 3.0.1 that libvirt is not accounting for. At this point, I don't really have more time to dig further but I thought I'd bring up the issue in case someone on this list can offer more insight. Pete