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

RE: [Xen-devel] Xen Signature == "NovellShimHv" ???


  • To: "Konrad Rzeszutek Wilk" <konrad.wilk@xxxxxxxxxx>
  • From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
  • Date: Tue, 15 Sep 2009 11:41:41 +1000
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Mon, 14 Sep 2009 18:42:07 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Aco1pJb58xqa+N35QDmyQgpA46XCGgAAJy4w
  • Thread-topic: [Xen-devel] Xen Signature == "NovellShimHv" ???

> 
> On Tue, Sep 15, 2009 at 11:24:43AM +1000, James Harper wrote:
> > A user of GPLPV is reporting a problem with the drivers on Windows
2008,
> > and it appears that GPLPV is finding a signature of 'NovellShimHv'
> > instead of 'XenVMMXenVMM'.
> >
> > Can anyone suggest a reason for this?
> 
> SLES10 SP2 Xen has the code for this. It is basically an early version
of the
> Veridian interface.

Ah. Hmmm. So does that mean that PV drivers on HVM domains (windows or
Linux) aren't going to work at all? Should I check for both
'NovellShimHv' and 'XenVMMXenVMM'? I notice that the unmodified drivers
tree under xen doesn't check for this, and neither does hvmloader.

James


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

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