[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] GPLPV, clock drift and PVUSB in Windows XP HVM

1. Shouldn't the GPLPV drivers take care of the (bad) clock drift I'm 
experiencing in my Windows XP HVM? Or is there some other way around this 
problem that I haven't been able to find on Google? How can I tell if the GPLPV 
drivers are active? I've added the /gplpv switch to the boot.ini file and the 
virtual NIC is definitely using the GPLPV version but other than that I'm not 
sure how to tell. 

The clock drift is too bad to be corrected by Windows' built-in NTP utility, 
and besides it needs to be corrected constantly, not every 2 weeks or whatever. 
I'm using this particular VM as a scheduling agent that performs tasks at 
certain times each day so it's important for it to have an accurate sense of 

2. On this same Windows XP HVM, I'd like to experiment with the PVUSB 2.0 pass 
thru. My server (Dell PowerEdge 2900) does NOT support IOMMU so it can't be 
hardware. I've read that the PVUSB performance is up to about 60% of native 
2.0, but still better than the qemu 1.1 pass thru. Unfortunately, I can't find 
any documentation online about how to actually use it. Currently I have these 
lines in my .cfg file:
usb = 1
usbdevice = 'tablet'
usbdevice = 'host:xxxx:yyyy'
Obviously I would need to remove the host: line to free up the device from qemu 
pass thru so I can use PVUSB pass thru instead, but after that I'm not sure 
what commands to issue or put in the domain's .cfg file.
P.S. I did choose to install PvUsb when installing GPLPV so I'm assuming that's 
all I need to do on the domU end. 

Thanks in advance for your help,
Eric Lindsey
Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.