Xen users - Mar 2012 - BSOD w/ gplpv drivers and Windows 2008 R2 64-bit

Hey,

I''ve been trying to get the gplpv drivers working with Windows 2008 R2 
64-bit on both a stock CentOS 5.8 install and CentOS 5.8 w/ Xen 4.1.2 
from the gitco repos.

I''m getting a BSOD shortly after boot up and it can be seen at 
http://techmonkeys.org/xen/ -- along with the qemu log.

Has anyone had success with these drivers and Windows 2008 R2 64-bit? If 
so, what am I doing wrong?

Thanks,
Jeff

El 12/03/12 21:22, Jeff Fisher escribió:
> I''m getting a BSOD shortly after boot up and it can be seen at
> http://techmonkeys.org/xen/ -- along with the qemu log.
Probably, windows is trying to load the driver in order to access it''s 
block device, fails becouse it does not like the driver signature, and 
then panics into a blue screen.

I got it working myself, putting windows into "test mode". There is
lot
of reference, tons one is good enough (GPL PV Drivers section):
http://plone.lucidsolutions.co.nz/linux/xen/windows/windows-server-2008-r2-xen-hvm-installation-with-gpvpv-drivers

-- 
Alexandre Kouznetsov
Systems Officer
Ondore, S.A. de C.V.
Tel. +52(55) 5559-0090
E-mail alk@ondore.com

On Mar 16, 2012 10:56 PM, "Alexandre Kouznetsov"
<alk@ondore.com> wrote:
>
> El 12/03/12 21:22, Jeff Fisher escribió:
>>
>> I''m getting a BSOD shortly after boot up and it can be seen at
>> http://techmonkeys.org/xen/ -- along with the qemu log.
>
> Probably, windows is trying to load the driver in order to access
it''s
block device, fails becouse it does not like the driver signature, and then
panics into a blue screen.
>
> I got it working myself, putting windows into "test mode". There
is lot
of reference, tons one is good enough (GPL PV Drivers
section):
>
http://plone.lucidsolutions.co.nz/linux/xen/windows/windows-server-2008-r2-xen-hvm-installation-with-gpvpv-drivers
>
It even has a link to signed GPLPV drivers :-)

Rgds,


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

El 16/03/12 11:45, Pandu Poluan escribió:
> It even has a link to signed GPLPV drivers :-)
lol, missed that.

-- 
Alexandre Kouznetsov

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

> Probably, windows is trying to load the driver in order to access
it''s
> block device, fails becouse it does not like the driver signature, and
> then panics into a blue screen.
>
> I got it working myself, putting windows into "test mode". There
is lot
> of reference, tons one is good enough (GPL PV Drivers section):
>
http://plone.lucidsolutions.co.nz/linux/xen/windows/windows-server-2008-r2-xen-hvm-installation-with-gpvpv-drivers
Yeah, this happens with the signed drivers and without (using test mode).

The http://www.techmonkeys.org/xen/ link works again -- I broke it 
mistakenly.

I''m using a Windows image I made originally with a machine running Xen 
3.0.3 -- maybe I''ll try a fresh install.

Jeff

> 
> El 12/03/12 21:22, Jeff Fisher escribió:
> > I''m getting a BSOD shortly after boot up and it can be seen
at
> > http://techmonkeys.org/xen/ -- along with the qemu log.
> Probably, windows is trying to load the driver in order to access
it''s block
> device, fails becouse it does not like the driver signature, and then
panics
> into a blue screen.
> 
> I got it working myself, putting windows into "test mode". There
is lot of
> reference, tons one is good enough (GPL PV Drivers section):
> http://plone.lucidsolutions.co.nz/linux/xen/windows/windows-server-2008-
> r2-xen-hvm-installation-with-gpvpv-drivers
> 
A lack of signing would give a different error.

james

> Hey,
> 
> I''ve been trying to get the gplpv drivers working with Windows
2008 R2 64-bit
> on both a stock CentOS 5.8 install and CentOS 5.8 w/ Xen 4.1.2 from the
gitco
> repos.
> 
> I''m getting a BSOD shortly after boot up and it can be seen at
> http://techmonkeys.org/xen/ -- along with the qemu log.
> 
> Has anyone had success with these drivers and Windows 2008 R2 64-bit? If
> so, what am I doing wrong?
> 
I''m using 2008 R2 without any problems. Can you please post your
config, especially the vbd config? Its failing to connect to the backend and
shouldn''t be that hard to replicate. I''m guessing you are
using tap:aio or something which I haven''t really tested with.

James

> I''m using 2008 R2 without any problems. Can you please post your
config, especially the vbd config? Its failing to connect to the backend and
shouldn''t be that hard to replicate. I''m guessing you are
using tap:aio or something which I haven''t really tested with.
This is my config:

import os, re
arch = os.uname()[4]
if re.search(''64'', arch):
       arch_libdir = ''lib64''
else:
       arch_libdir = ''lib''

kernel     = ''/usr/lib/xen/boot/hvmloader''
builder    = ''hvm''
memory     = 1024
shadow_memory   = ''8''
cpu_weight = 256
name       = ''vm135''
vif        = [''type=ioemu, ip=x.x.x.x, vifname=vifvm135.0, 
mac=00:16:3e:9c:73:80'']
acpi        = 1
apic        = 1
vnc        = 1
vcpus      = 2
vncdisplay = 9
vncviewer  = 0
vncconsole = 1
serial     = ''pty''
disk       = [''phy:/dev/bigfs/vm135_img,hda,w'',
'',hdc:cdrom,r'']
device_model = ''/usr/'' + arch_libdir +
''/xen/bin/qemu-dm''
boot       = ''cd''
sdl         = ''0''
usbdevice  = ''tablet''
pae=1

> 
> This is my config:
> 
> import os, re
> arch = os.uname()[4]
> if re.search(''64'', arch):
>        arch_libdir = ''lib64''
> else:
>        arch_libdir = ''lib''
> 
> kernel     = ''/usr/lib/xen/boot/hvmloader''
> builder    = ''hvm''
> memory     = 1024
> shadow_memory   = ''8''
> cpu_weight = 256
> name       = ''vm135''
> vif        = [''type=ioemu, ip=x.x.x.x, vifname=vifvm135.0,
> mac=00:16:3e:9c:73:80'']
> acpi        = 1
> apic        = 1
> vnc        = 1
> vcpus      = 2
> vncdisplay = 9
> vncviewer  = 0
> vncconsole = 1
> serial     = ''pty''
> disk       = [''phy:/dev/bigfs/vm135_img,hda,w'',
'',hdc:cdrom,r'']
> device_model = ''/usr/'' + arch_libdir +
''/xen/bin/qemu-dm''
> boot       = ''cd''
> sdl         = ''0''
> usbdevice  = ''tablet''
> pae=1
> 
That looks fine. Are you using xm or xl?

James

>
> That looks fine. Are you using xm or xl?
That box is using xm.

I''m going to try a fresh install on my Xen 4.1.2 box -- right now
I''m
using a Windows image I created on a Xen 3.0.3 box.

I probably won''t get around to that until tomorrow.

Jeff

> >
> > That looks fine. Are you using xm or xl?
> 
> That box is using xm.
> 
> I''m going to try a fresh install on my Xen 4.1.2 box -- right now
I''m using a
> Windows image I created on a Xen 3.0.3 box.
> 
> I probably won''t get around to that until tomorrow.
> 
One thing that would be useful once the domain is in a crashed state:

Send me the output of: 
xenstore-ls /local/domain/<domid>/device/vbd

In that output will be the backend paths, also send me the output of:
xenstore-ls <backend path>

The crash is a result of a bug in Xen where it isn''t handling a failure
of the frontend/backend device setup. I don''t know why the setup is
failing though.

I also just noticed that you are using 308. Before you do the above can you try
a newer version - I''ve just put 357 in the regular download area and
maybe this bug is already fixed.

James

> One thing that would be useful once the domain is in a crashed state:
>
> Send me the output of:
> xenstore-ls /local/domain/<domid>/device/vbd
>
> In that output will be the backend paths, also send me the output of:
> xenstore-ls<backend path>
>
> The crash is a result of a bug in Xen where it isn''t handling a
failure of the frontend/backend device setup. I don''t know why the
setup is failing though.
>
> I also just noticed that you are using 308. Before you do the above can you
try a newer version - I''ve just put 357 in the regular download area
and maybe this bug is already fixed.
K, I''ll try the 357 download and if it doesn''t work, get you
all that info.

Hopefully the signed drivers will be updated soon if it does indeed work :)

Thanks,
Jeff

>
> K, I''ll try the 357 download and if it doesn''t work, get
you all that info.
>
> Hopefully the signed drivers will be updated soon if it does indeed work :)
The 357 drivers seem to be working -- it is booted and I''m able to 
remote in. It would BSOD before I could even get logged in before.

Thanks,
Jeff