Xen users - Mar 2011 - GPLPV 0.11.0.238 and Windows 2008 R2 requiring extra reboot

James,

 

I am running Windows 2008 R2 on Xen that is packaged with CentOS 5.4. I
installed gplpv_Vista2008x64_0.11.0.238.msi using the falling steps:

 

1.       Turn on testsigning

2.       Reboot

3.       Install gplpv_Vista2008x64_0.11.0.238.msi

4.       Install process requests a reboot at the end.

5.       At the end of the subsequent boot, there is a prompt for a reboot
again.

 

I am wondering about the reboot in step 5. Any idea why the extra reboot is
being requested? Is there a way to get around it? I do not see this on
Window 2008 x64.

 

Thanks,

AP

 



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

> 
> I am running Windows 2008 R2 on Xen that is packaged with CentOS 5.4.
I
> installed gplpv_Vista2008x64_0.11.0.238.msi using the falling steps:
> 
> 
> 
> 1.       Turn on testsigning
> 
> 2.       Reboot
> 
> 3.       Install gplpv_Vista2008x64_0.11.0.238.msi
> 
> 4.       Install process requests a reboot at the end.
> 
> 5.       At the end of the subsequent boot, there is a prompt for a
reboot
> again.
> 
> I am wondering about the reboot in step 5. Any idea why the extra
reboot is
> being requested? Is there a way to get around it? I do not see this on
Window
> 2008 x64.
> 
GPLPV depends on KMDF (Kernel Mode Driver Framework). If there is no
KMDF currently installed then it is installed along with the drivers and
everything will be active on the next boot. If the same or newer KMDF is
already installed then the drivers are installed and everything will be
active on the next boot. If an older version is installed then it will
be upgraded but the drivers won''t load until the new KMDF is loaded.
When the new KMDF is loaded on the next boot, the drivers load but too
late in the boot process so it''s only on the next boot that they can
properly take control.

What you''re seeing is almost the opposite of this though... when you
first install, does xenpci load (the unknown PCI device should be gone
and replaced with xenpci and have not exclamation marks etc)? Do any of
the other devices load (xenvbd/xenpci/xenusb/xenscsi etc)? What about on
the first reboot?

James

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

> GPLPV depends on KMDF (Kernel Mode Driver Framework). If there is no
> KMDF currently installed then it is installed along with the drivers
> and
> everything will be active on the next boot. If the same or newer KMDF
> is
> already installed then the drivers are installed and everything will be
> active on the next boot. If an older version is installed then it will
> be upgraded but the drivers won''t load until the new KMDF is
loaded.
> When the new KMDF is loaded on the next boot, the drivers load but too
> late in the boot process so it''s only on the next boot that they
can
> properly take control.
On a fresh install of W2k8 R2 Enterprise, I see that
/Windows/System32/drivers/Wdf01000.sys and WdfLdr.sys are present and the
version is 1.9.7600.16385. I am assuming this means that KMDF is installed.
> What you''re seeing is almost the opposite of this though... when
you
> first install, does xenpci load (the unknown PCI device should be gone
> and replaced with xenpci and have not exclamation marks etc)?
> Do any of the other devices load (xenvbd/xenpci/xenusb/xenscsi etc)?
After the first gplpv install and before the first reboot, I can see that
there are no exclamation marks in device manager. "Xen Block Device
Driver",
"Xen Net Driver" and "Xen PCI Device Driver" are also loaded
i.e. they show
up in Device Manager with no exclamation marks.
>What about on the first reboot?
On the first reboot, the answer is same as above except I see an exclamation
mark against the "Intel Bus Master IDE Controller". However, that
remains
even after the second reboot.

Thanks,
AP



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

> > GPLPV depends on KMDF (Kernel Mode Driver Framework). If there is no
> > KMDF currently installed then it is installed along with the drivers
> > and
> > everything will be active on the next boot. If the same or newer KMDF
> > is
> > already installed then the drivers are installed and everything will
> be
> > active on the next boot. If an older version is installed then it
> will
> > be upgraded but the drivers won''t load until the new KMDF is
loaded.
> > When the new KMDF is loaded on the next boot, the drivers load but
> too
> > late in the boot process so it''s only on the next boot that
they can
> > properly take control.
> 
> On a fresh install of W2k8 R2 Enterprise, I see that
> /Windows/System32/drivers/Wdf01000.sys and WdfLdr.sys are present and
> the
> version is 1.9.7600.16385. I am assuming this means that KMDF is
> installed.
BTW, I ran the WdfVerifier from the DDK and it confirmed that KMDF 1.9 is
installed on Win2k8 R2 out of the box.

Thanks,
Aravindh



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

> 
> > > GPLPV depends on KMDF (Kernel Mode Driver Framework). If there is
no
> > > KMDF currently installed then it is installed along with the
drivers
> > > and
> > > everything will be active on the next boot. If the same or newer
KMDF
> > > is
> > > already installed then the drivers are installed and everything
will
> > be
> > > active on the next boot. If an older version is installed then it
> > will
> > > be upgraded but the drivers won''t load until the new
KMDF is
loaded.
> > > When the new KMDF is loaded on the next boot, the drivers load
but
> > too
> > > late in the boot process so it''s only on the next boot
that they
can
> > > properly take control.
> >
> > On a fresh install of W2k8 R2 Enterprise, I see that
> > /Windows/System32/drivers/Wdf01000.sys and WdfLdr.sys are present
and
> > the
> > version is 1.9.7600.16385. I am assuming this means that KMDF is
> > installed.
> 
> BTW, I ran the WdfVerifier from the DDK and it confirmed that KMDF 1.9
is
> installed on Win2k8 R2 out of the box.
> 
Yes that''s right, which is why I said your situation was backwards to
what I expected - normally 7/2008R2 should work without the additional
reboot. If you are getting the qemu devices showing up though then I
suspect you are using a 3.x.x series Xen. Can you confirm what version
you are using?

James

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

> Yes that''s right, which is why I said your situation was backwards
to
> what I expected - normally 7/2008R2 should work without the additional
> reboot. If you are getting the qemu devices showing up though then I
> suspect you are using a 3.x.x series Xen. Can you confirm what version
> you are using?
xen_major              : 3
xen_minor              : 1
xen_extra              : .2-229.el5

You are right. I am using Xen 3.1 + whatever patches RedHat / CentOS deemed
fit to include.

PS: I am using the Xen packages from RedHat 5.6 to allow me to run R2 under
CentOS 5.5.

Thanks,
AP



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

> 
> > Yes that''s right, which is why I said your situation was
backwards
to
> > what I expected - normally 7/2008R2 should work without the
additional
> > reboot. If you are getting the qemu devices showing up though then I
> > suspect you are using a 3.x.x series Xen. Can you confirm what
version
> > you are using?
> 
> xen_major              : 3
> xen_minor              : 1
> xen_extra              : .2-229.el5
> 
> You are right. I am using Xen 3.1 + whatever patches RedHat / CentOS
deemed
> fit to include.
> 
> PS: I am using the Xen packages from RedHat 5.6 to allow me to run R2
under
> CentOS 5.5.
> 
With that version of Xen I think you''ll just need to put up with the
extra reboot. GPLPV can''t disable the qemu devices properly so it has
to
put a filter in and cause them to fail (hence the exclamation mark) and
if the qemu devices are running when xenpci loads it refuses to start up
fully (or else you risk your filesystem being trashed).

Jaems

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

> > You are right. I am using Xen 3.1 + whatever patches RedHat / CentOS
> deemed
> > fit to include.
> >
> > PS: I am using the Xen packages from RedHat 5.6 to allow me to run R2
> under
> > CentOS 5.5.
> >
> 
> With that version of Xen I think you''ll just need to put up with
the
> extra reboot. GPLPV can''t disable the qemu devices properly so it
has
> to
> put a filter in and cause them to fail (hence the exclamation mark) and
> if the qemu devices are running when xenpci loads it refuses to start
> up
> fully (or else you risk your filesystem being trashed).
Ok, I understand. Thanks for all the help.

Regards,
AP


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