On Thu, Feb 21, 2008 at 11:54 AM, jim burns <
jim_burn@xxxxxxxxxxxxx> wrote:
On Thursday 21 February 2008 05:05:56 am James Harper wrote:
> . pvSCSI support (eg can pass through tape drives and cd burners,
> although I haven't tested the latter). This hasn't seen nearly as much
> testing as everything else, but I've run the tests in the HP Library &
> Tape Tools successfully, including a firmware update.
Nice. Any special syntax needed in the domain config, or dom0 grub, beyond the
standard pciback hide stuff? Do you need xen 3.2/Vt-d?
I think this shall be using paravirtual drivers, so no vt-d stuff or pciback kind of trick. James, could you confirm?
Some additional questions:
- Can we say this is "faster" than the other SCSI paravirtual driver?
- Does the driver still work if I didn't apply those patches for pvSCSI
- Does anybody know if there's any plan to merge those patches into xen-unstable? If not, why?
> I highly recommend uninstalling all trace of any previous version before
> installing this one. Particularly put the Windows PCI Bus driver back
> the way it was (eg update drivers and just click next a few times).
What's the best order to uninstall in - the reverse order of installing? That
would make it xenhide, xenstub, xennet, xenvbd, xenenum, xenpci? Everytime I
rip out xenhide, I have a massive hardware reconfiguration with the Add
Hardware Wizard on the next reboot.
I think the best is to boot with standard kernel, then remove xennet, xenenum, xenblk, xenpci and then replace xenhide with standard PCI controller, reboot again with std controller, let the system re-enumarate the devices.