> On Sunday 03 February 2008 05:31:08 pm James Harper wrote:
> > I'm not sure that any benchmarks under the qemu disks is going to
mean
> > anything, as Dom0 is doing caching for them, unless this has changed
in
> > 0.3.2. Can you confirm that CPU usage is way down under the pV
drivers?
>
> I wouldn't say *way* down. I mostly use my hvm for multimedia that
wine or
> mplayer/xine can't handle, and that's a real cpu hog on an hvm guest,
> especially video.
Hmmm... I wonder how much acceleration we could do for a vfb driver...
> > Does anything useful get logged in the event log about that? Is it
> > possible that your windows domU got so roasted by the previous pv
driver
> > versions that it has other problems too?
>
> What log file in particular? (c:\windows\...) I've just recovered from
a
> bad
> chkdsk relocation of my home directory, plus some anti-virus &
anti-trojan
> checker files, but that happened after I installed 0.6.5.
Windows event log (eventvwr.msc)
> (Which reminds
> me,
> you never answered whether it's better to do an upgrade with Device
> Manager,
> or straight copies to c:\windows\system32\drivers?)
I've never done it by just copying files so I couldn't say for sure. It
should work, but I'm not sure windows can set itself up to do a 'last
known good configuration' boot if you do it that way.
> > Can you send me the config file, or at least the line for the block
> devices?
>
> disk=[ 'file:/var/lib/xen/images/winxp,ioemu:hda,w',
> 'phy:/dev/cdrom,hdc:cdrom,r' ]
I've never tried it with a physical cdrom, so maybe there's something
funny there. I also wouldn't normally use 'ioemu:', but I can't think
that it would matter.
James
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|