Release 0.8.4 of GPL PV Drivers for Windows

Release 0.8.4 of GPL PV Drivers for Windows

[James Harper]

This release fixes a BSoD on boot that some people were seeing sometimes
and other people were seeing all of the time.

http://www.meadowcourt.org/WindowsXenPV-0.8.4.zip

James

Re: Release 0.8.4 of GPL PV Drivers for Windows

[jamesshirley]

James,

This looks very good indeed, was getting tired of waiting for redhat to put
these out..

I've tried this new version (only trying 0.8.3 before) with some success..

I couldn't run update on PCI Device to uninstall 0.8.3, but manage to
unsinstall Xen PCI Bus & install 0.8.4 with everything upgraded ok..

Anyway I'm allways getting "Windows has finished install new devicces, The
software that supports your device requires that you restart your
computer.." on startup.

I have two drives QEMU & XEN PV VBD, appearing even though I only have disk
= ['phy:/dev/VolGroup00/tcsxis03-c,hda,w'] in my xen config file. The two
drives look like their mapping to the same logical drive i've configured in
RH XEN.

I get to chkdsks on startup everytime for c: & d:

Similar story for the ethernet, but I can disable the Realtec FV driver to
get around this one..

I can confirm the network latency is half on the PV driver, cool cheers,
down to 0.100ms vs 0.200ms from the dom0, and I get full 100MB speed over a
100MB LAN.. and 250MB to dom0 over bridged networks.

I'm having issues with this two disks though.. Any way to disable the FV
QEMU drivers?

Disk performance looks idential to FV drivers

This is on dom0=RHEL5.1 Xen 3.1.0-53.1.4.el5 
with domU=windows 2003 Standard + SP1


cheers,

James



James Harper wrote:
> 
> This release fixes a BSoD on boot that some people were seeing sometimes
> and other people were seeing all of the time.
> 
> http://www.meadowcourt.org/WindowsXenPV-0.8.4.zip
> 
> James
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 
> 

-- 
View this message in context: http://www.nabble.com/Release-0.8.4-of-GPL-PV-Drivers-for-Windows-tp15703201p15708502.html
Sent from the Xen - Dev mailing list archive at Nabble.com.

Re: Release 0.8.4 of GPL PV Drivers for Windows

[Pasi Kärkkäinen]

On Wed, Feb 27, 2008 at 12:33:47AM -0800, jamesshirley wrote:
> 
> James,
> 
> This looks very good indeed, was getting tired of waiting for redhat to put
> these out..
> 
> I've tried this new version (only trying 0.8.3 before) with some success..
> 
> I couldn't run update on PCI Device to uninstall 0.8.3, but manage to
> unsinstall Xen PCI Bus & install 0.8.4 with everything upgraded ok..
> 
> Anyway I'm allways getting "Windows has finished install new devicces, The
> software that supports your device requires that you restart your
> computer.." on startup.
> 
> I have two drives QEMU & XEN PV VBD, appearing even though I only have disk
> = ['phy:/dev/VolGroup00/tcsxis03-c,hda,w'] in my xen config file. The two
> drives look like their mapping to the same logical drive i've configured in
> RH XEN.
> 
> I get to chkdsks on startup everytime for c: & d:
> 
> Similar story for the ethernet, but I can disable the Realtec FV driver to
> get around this one..
> 
> I can confirm the network latency is half on the PV driver, cool cheers,
> down to 0.100ms vs 0.200ms from the dom0, and I get full 100MB speed over a
> 100MB LAN.. and 250MB to dom0 over bridged networks.
> 
> I'm having issues with this two disks though.. Any way to disable the FV
> QEMU drivers?
> 
> Disk performance looks idential to FV drivers
> 
> This is on dom0=RHEL5.1 Xen 3.1.0-53.1.4.el5 
> with domU=windows 2003 Standard + SP1
> 

Based on the benchmarks done lately, you should get 3-4x better disk
performance with these gplpv drivers for windows...

-- Pasi

RE: Release 0.8.4 of GPL PV Drivers for Windows

[James Harper]

> James,
> 
> This looks very good indeed, was getting tired of waiting for redhat
to
> put
> these out..
> 
> I've tried this new version (only trying 0.8.3 before) with some
success..
> 
> I couldn't run update on PCI Device to uninstall 0.8.3, but manage to
> unsinstall Xen PCI Bus & install 0.8.4 with everything upgraded ok..
> 
> Anyway I'm allways getting "Windows has finished install new devicces,
The
> software that supports your device requires that you restart your
> computer.." on startup.
> 
> I have two drives QEMU & XEN PV VBD, appearing even though I only have
> disk
> = ['phy:/dev/VolGroup00/tcsxis03-c,hda,w'] in my xen config file. The
two
> drives look like their mapping to the same logical drive i've
configured
> in
> RH XEN.
> 

You will almost certainly get some fatal corruption before too long if
this is happening. It shouldn't happen obviously...

Can you go into device manager, right click on 'Intel(R) 82371SB PCI Bus
Master IDE Controller' and select Properties, select the 'Details' tab,
and tell me the contents of the 'Hardware Ids' property, and the
'Compatible Ids' property. I need to see why it isn't being disabled...

Thanks

James

Re: Release 0.8.4 of GPL PV Drivers for Windows

[Mark Williamson]

> > I have two drives QEMU & XEN PV VBD, appearing even though I only have
> > disk
> > = ['phy:/dev/VolGroup00/tcsxis03-c,hda,w'] in my xen config file. The
>
> two
>
> > drives look like their mapping to the same logical drive i've
>
> configured
>
> > in
> > RH XEN.
>
> You will almost certainly get some fatal corruption before too long if
> this is happening. It shouldn't happen obviously...

Side note: on an important VM, if you find yourself in this situation (two 
drives pointing at the same underlying data) and don't want to lose data, 
it's best to stop it as soon as possible.  Probably an xm destroy is better 
than a clean shutdown in this case!

(side note: unless you really have a clear idea of what you're doing and why 
it's safe or it's just a testing VM you can afford to hose)

Sorry to butt in on this, I just have a thing about pepperring the ML archives 
with warnings about this, having once (years ago) hosed a Xen machine 3 times 
in an afternoon doing stuff like this :-)

Cheers,
Mark

> Can you go into device manager, right click on 'Intel(R) 82371SB PCI Bus
> Master IDE Controller' and select Properties, select the 'Details' tab,
> and tell me the contents of the 'Hardware Ids' property, and the
> 'Compatible Ids' property. I need to see why it isn't being disabled...
>
> Thanks
>
> James
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel



-- 
Push Me Pull You - Distributed SCM tool (http://www.cl.cam.ac.uk/~maw48/pmpu/)

RE: Release 0.8.4 of GPL PV Drivers for Windows

[James Harper]

> > You will almost certainly get some fatal corruption before too long
if
> > this is happening. It shouldn't happen obviously...
> 
> Side note: on an important VM, if you find yourself in this situation
(two
> drives pointing at the same underlying data) and don't want to lose
data,
> it's best to stop it as soon as possible.  Probably an xm destroy is
> better
> than a clean shutdown in this case!

Yes, this is something that really can't be understated. Even on a
system I have booted, checked in device manager, found the duplicates,
and done an 'xm destroy', it has already been too late - the system
would no longer boot. A chkdsk from the recovery console fixed it up
again, but who knows what else was corrupt.

Other PV drivers appear to be able to tell windows that one drive is
just another path to the other. I'm not sure how to tell windows this
though. My preference is to hide the qemu device, but this doesn't
appear to work under all circumstances and the multipath thing would
prevent data corruption...

Anyone have any suggestions?

James

Re: Release 0.8.4 of GPL PV Drivers for Windows

[Steve Ofsthun]

James Harper wrote:
>>> You will almost certainly get some fatal corruption before too long
> if
>>> this is happening. It shouldn't happen obviously...
>> Side note: on an important VM, if you find yourself in this situation
> (two
>> drives pointing at the same underlying data) and don't want to lose
> data,
>> it's best to stop it as soon as possible.  Probably an xm destroy is
>> better
>> than a clean shutdown in this case!
> 
> Yes, this is something that really can't be understated. Even on a
> system I have booted, checked in device manager, found the duplicates,
> and done an 'xm destroy', it has already been too late - the system
> would no longer boot. A chkdsk from the recovery console fixed it up
> again, but who knows what else was corrupt.

I couldn't agree more.  You can never caution people enough when testing
new code anywhere in the storage stack.

> Other PV drivers appear to be able to tell windows that one drive is
> just another path to the other. I'm not sure how to tell windows this
> though. My preference is to hide the qemu device, but this doesn't
> appear to work under all circumstances and the multipath thing would
> prevent data corruption...

We (Virtual Iron) don't actually rely on any multipath detection in
Windows guests (or for that matter, Linux guests, which can have similar
problems).  We implement a device hiding mechanism (probe limits) in
dom0/qemu-dm to prevent the ide devices used by the guest BIOS during
bootstrap from responding to ide identify probes by the booting guest
operating system.  This has the benefit of working without any necessary
cooperation in the guest operating system.  The failure mode is a failed
boot, not a destroyed disk image.  Unfortunately, this probe limit
change is currently dependent on other dom0 control stack changes we
use.   If there is interest, we could look into breaking out a
standalone patch.  The changes to qemu are minimal.  Essentially, the
ide devices allow 1 probe each for the BIOS bootstrap and remain silent
after that.  No data path changes were required.

> Anyone have any suggestions?

The first issue with multipath is getting Windows to think that the disk
devices are identical.  Since the qemu device is ide and your PV device
is scsi, there is no real world example to guide you.  You could look at
the way Windows constructs it's disk identifier for ide drives and
attempt to generate an identical string in your driver.  If you used a
scsi device in qemu, you should only need to return identical target
identification strings for the same disk.

Steve

RE: Release 0.8.4 of GPL PV Drivers for Windows

[jamesshirley]

James,


James Harper wrote:
> 
> 
> Can you go into device manager, right click on 'Intel(R) 82371SB PCI Bus
> Master IDE Controller' and select Properties, select the 'Details' tab,
> and tell me the contents of the 'Hardware Ids' property, and the
> 'Compatible Ids' property. I need to see why it isn't being disabled...
> 
> 


My VM now has died, just sitting at Windows 2003 Loading screen and never
finishing.

I've restored the original (Pre PV) and done the following:

1. Installed .dot net framework 2.0

2. An unknown PCI device which i couldn't find any drivers for with the
following details:

device id=PCI\VEN_5853&DEV_0001&SUBSYS_00015853&REV_01\2&EBB567F&0&18

hardware id=PCI\VEN_5853&DEV_0001&SUBSYS_00015853&REV_01
PCI\VEN_5853&DEV_0001&SUBSYS_00015853
PCI\VEN_5853&DEV_0001&CC_FF8000
PCI\VEN_5853&DEV_0001&CC_FF80

not sure if this is causing the PV drivers any probs

3. install 0.8.4, but got an error when install ShutdownMon, i assume this
is only for xm shutdown to function, and not PV driver related:

Z:\software\windows\xen\WindowsXenPV-0.8.4>install
Windows 2003 (i386) Detected... Installing...

Unhandled Exception: System.Security.SecurityException: That assembly does
not allow partially trusted callers.
   at
System.Security.CodeAccessSecurityEngine.ThrowSecurityException(Assembly
asm, PermissionSet granted, PermissionSet refused, Ru
ntimeMethodHandle rmh, SecurityAction action, Object demand, IPermission
permThatFailed)
   at ShutdownMon.Program.Main(String[] args)
The action that failed was:
LinkDemand
The assembly or AppDomain that failed was:
ShutdownMon, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
The Zone of the assembly that failed was:
Internet
The Url of the assembly that failed was:
file:///Z:/software/windows/xen/WindowsXenPV-0.8.4/ShutdownMon.exe
Done

4. I rebooted

all fine, no mention of new drivers activated.

5. I made the changes to c:\boot.ini & rebooted

This sat at the gray screen & didn't reboot, I had to run an xm destroy &
create to get it up

6. I booted with /gplpv boot option

7. And now i'm just getting the Windows 2003 Server startup screen booting
for ever..

8. Tried again with same result

9. Tried again with safe mode 

Windows activated Xen Net Block device

And asked for System Reboot

Still seeing duplicate disk drives & cdrom drives..

10. Booted up without /gplpv

chkdsk asked to check e:, i cancelled

11. Booted, but when i login, it goes back to the Crtl-alt-del screen
immediately

suspect file system corruption

12. Will re-run from the top to confirm its not a once off..

Cheers

James



-- 
View this message in context: http://www.nabble.com/Release-0.8.4-of-GPL-PV-Drivers-for-Windows-tp15703201p15726972.html
Sent from the Xen - Dev mailing list archive at Nabble.com.

RE: Release 0.8.4 of GPL PV Drivers for Windows

[jamesshirley]

jamesshirley wrote:
> 
> James,
> 
> 12. Will re-run from the top to confirm its not a once off..
> 
> 

OK second run was slightly better:

I've restored the original (Pre PV) and done the following:

1. I didn't Install .dot net framework 2.0

2. I changed disk config to remove cdrom & ioemu:hda to hda:

import os, re
arch = os.uname()[4]
arch_libdir = 'lib'
kernel = '/usr/lib/xen/boot/hvmloader'
builder='hvm'
memory = 512
name = 'tcsxis03'
vcpus=1
cpus = "" # leave to Xen to pick
vif = [ 'type=ioemu, bridge=xenbr0' ]
disk = ['phy:/dev/VolGroup00/tcsxis03-c,hda,w']#,
'file:/fileshare/images/iso/w2003-r1.iso,hdc:cdrom,r']
on_crash='preserve'
device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm'
boot='c'
vnc=1
vnclisten="0.0.0.0"
vncunused=0
vncdisplay=6
ne2000=0
usbdevice='tablet'
localtime=1

3. An unknown PCI device which i couldn't find any drivers for with the
following details:

device id=PCI\VEN_5853&DEV_0001&SUBSYS_00015853&REV_01\2&EBB567F&0&18

hardware id=PCI\VEN_5853&DEV_0001&SUBSYS_00015853&REV_01
PCI\VEN_5853&DEV_0001&SUBSYS_00015853
PCI\VEN_5853&DEV_0001&CC_FF8000
PCI\VEN_5853&DEV_0001&CC_FF80

not sure if this is causing the PV drivers any probs

4. install 0.8.4, but got error about .dot 2. not installed..

4. I rebooted

all fine, no mention of new drivers activated.

5. I made the changes to c:\boot.ini & rebooted with /gplpv

This booted correctly,

Activating new devices,

When activating ethernet, i loose my xen ssh connection & re-login a few
seconds later

6. I reboot again as requested without /gplpv

7. Looks good, but I thought you only had to run the /gplpv once, so i
reboot again with /gplpv boot param

8. chkdsk d: & c: cancelled

9. login very slow

10. two disk drives again..

11. ignore system reboot message

12. The Intel(R) 82371SB PCI Bus
Master IDE Controller' Hardware ID are:
PCI\VEN_8086&DEV_7010&SUBSYS_00015853&REV_00
PCI\VEN_8086&DEV_7010&SUBSYS_00015853
PCI\VEN_8086&DEV_7010&CC_010180
PCI\VEN_8086&DEV_7010&CC_0101

13. The Intel(R) 82371SB PCI Bus
Master IDE Controller' Compatible Ids are:
PCI\VEN_8086&DEV_7010&REV_00
PCI\VEN_8086&DEV_7010
PCI\VEN_8086&CC_010180
PCI\VEN_8086&CC_0101
PCI\VEN_8086
PCI\CC_010180
PCI\CC_0101

cheers,

James



-- 
View this message in context: http://www.nabble.com/Release-0.8.4-of-GPL-PV-Drivers-for-Windows-tp15703201p15727183.html
Sent from the Xen - Dev mailing list archive at Nabble.com.

RE: Release 0.8.4 of GPL PV Drivers for Windows

[James Harper]

> 
> 7. Looks good, but I thought you only had to run the /gplpv once, so i
> reboot again with /gplpv boot param
> 

Nope. When it's working properly, booting with /gplpv will activate the
gpl pv drivers, booting without /gplpv will leave them deactivated.

> 12. The Intel(R) 82371SB PCI Bus
> Master IDE Controller' Hardware ID are:
> PCI\VEN_8086&DEV_7010&SUBSYS_00015853&REV_00
> PCI\VEN_8086&DEV_7010&SUBSYS_00015853
> PCI\VEN_8086&DEV_7010&CC_010180
> PCI\VEN_8086&DEV_7010&CC_0101
> 
> 13. The Intel(R) 82371SB PCI Bus
> Master IDE Controller' Compatible Ids are:
> PCI\VEN_8086&DEV_7010&REV_00
> PCI\VEN_8086&DEV_7010
> PCI\VEN_8086&CC_010180
> PCI\VEN_8086&CC_0101
> PCI\VEN_8086
> PCI\CC_010180
> PCI\CC_0101

I search for PCI\VEN_8086&DEV_7010, and it is definitely there in your
list. I'm baffled at this point. After the next release (soon) I'll have
a closer look.

James

RE: Release 0.8.4 of GPL PV Drivers for Windows

[James Harper]

> 
> My VM now has died, just sitting at Windows 2003 Loading screen and
never
> finishing.

Hmm... that was supposed to have been fixed in 0.8.4. I guess your crash
is probably caused by the duplication though.

> 2. An unknown PCI device which i couldn't find any drivers for with
the
> following details:
> 
> device id=PCI\VEN_5853&DEV_0001&SUBSYS_00015853&REV_01\2&EBB567F&0&18
> 
> hardware id=PCI\VEN_5853&DEV_0001&SUBSYS_00015853&REV_01
> PCI\VEN_5853&DEV_0001&SUBSYS_00015853
> PCI\VEN_5853&DEV_0001&CC_FF8000
> PCI\VEN_5853&DEV_0001&CC_FF80
> 
> not sure if this is causing the PV drivers any probs

That is the PCI device that the XenPCI driver should attach to.

> 3. install 0.8.4, but got an error when install ShutdownMon, i assume
this
> is only for xm shutdown to function, and not PV driver related:
> 
> Z:\software\windows\xen\WindowsXenPV-0.8.4>install
> Windows 2003 (i386) Detected... Installing...
> 
> Unhandled Exception: System.Security.SecurityException: That assembly
does
> not allow partially trusted callers.
>    at
>
System.Security.CodeAccessSecurityEngine.ThrowSecurityException(Assembly
> asm, PermissionSet granted, PermissionSet refused, Ru
> ntimeMethodHandle rmh, SecurityAction action, Object demand,
IPermission
> permThatFailed)
>    at ShutdownMon.Program.Main(String[] args)
> The action that failed was:
> LinkDemand
> The assembly or AppDomain that failed was:
> ShutdownMon, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
> The Zone of the assembly that failed was:
> Internet
> The Url of the assembly that failed was:
> file:///Z:/software/windows/xen/WindowsXenPV-0.8.4/ShutdownMon.exe
> Done

I assume Z: is a network drive. Copy the entire xen directory to C:\xen.
.NET is a but funny about running stuff not from the local machine.

> 
> suspect file system corruption
> 

That is quite likely.

James

RE: Release 0.8.4 of GPL PV Drivers for Windows

[jamesshirley]

James,



James Harper wrote:
> 
> 
> Can you go into device manager, right click on 'Intel(R) 82371SB PCI Bus
> Master IDE Controller' and select Properties, select the 'Details' tab,
> and tell me the contents of the 'Hardware Ids' property, and the
> 'Compatible Ids' property. I need to see why it isn't being disabled...
> 
> 

Any ideas whats going on here..

There was talk of language settings, mine is set to Australia, not sure if
this could be causing these problems..

Cheers

James Shirley
-- 
View this message in context: http://www.nabble.com/Release-0.8.4-of-GPL-PV-Drivers-for-Windows-tp15703201p15817405.html
Sent from the Xen - Dev mailing list archive at Nabble.com.

RE: Release 0.8.4 of GPL PV Drivers for Windows

[James Harper]

> 
> Any ideas whats going on here..
> 
> There was talk of language settings, mine is set to Australia, not
sure if
> this could be causing these problems..
> 

I'm in Australia too, and that problem was to do with the pv drivers
never being activated at all, instead of being activated in addition to
the qemu devices which appears to be the problem you are having.

By the time the xenhide driver could have figured out that it didn't
find and hide the qemu ide driver, it is too late in the boot sequence
to not enable the pv block device driver. Given the damage it causes
when this happens, I think it would be appropriate to throw a BSoD at
that point. At least then you'd get a BSoD instead of corruption. If I
can I'll put that in the next release so at least we can look further
into the problem you are having without you having to rebuild windows
DomU's all the time (I'm sure you know I understand how much of a pain
that is :)

James

Re: Release 0.8.4 of GPL PV Drivers for Windows

[zen]

[-- Attachment #1.1: Type: text/plain, Size: 2293 bytes --]

You can try the pv tools at www.halsign.com
They can support multiple platforms like rhel5, fc8 etc.


On 2/27/08, jamesshirley <james.shirley@westernpower.com.au> wrote:
>
>
> James,
>
> This looks very good indeed, was getting tired of waiting for redhat to
> put
> these out..
>
> I've tried this new version (only trying 0.8.3 before) with some success..
>
> I couldn't run update on PCI Device to uninstall 0.8.3, but manage to
> unsinstall Xen PCI Bus & install 0.8.4 with everything upgraded ok..
>
> Anyway I'm allways getting "Windows has finished install new devicces, The
> software that supports your device requires that you restart your
> computer.." on startup.
>
> I have two drives QEMU & XEN PV VBD, appearing even though I only have
> disk
> = ['phy:/dev/VolGroup00/tcsxis03-c,hda,w'] in my xen config file. The two
> drives look like their mapping to the same logical drive i've configured
> in
> RH XEN.
>
> I get to chkdsks on startup everytime for c: & d:
>
> Similar story for the ethernet, but I can disable the Realtec FV driver to
> get around this one..
>
> I can confirm the network latency is half on the PV driver, cool cheers,
> down to 0.100ms vs 0.200ms from the dom0, and I get full 100MB speed over
> a
> 100MB LAN.. and 250MB to dom0 over bridged networks.
>
> I'm having issues with this two disks though.. Any way to disable the FV
> QEMU drivers?
>
> Disk performance looks idential to FV drivers
>
> This is on dom0=RHEL5.1 Xen 3.1.0-53.1.4.el5
> with domU=windows 2003 Standard + SP1
>
>
> cheers,
>
> James
>
>
>
> James Harper wrote:
> >
> > This release fixes a BSoD on boot that some people were seeing sometimes
> > and other people were seeing all of the time.
> >
> > http://www.meadowcourt.org/WindowsXenPV-0.8.4.zip
> >
> > James
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Release-0.8.4-of-GPL-PV-Drivers-for-Windows-tp15703201p15708502.html
> Sent from the Xen - Dev mailing list archive at Nabble.com.
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>

[-- Attachment #1.2: Type: text/html, Size: 3222 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: Release 0.8.4 of GPL PV Drivers for Windows

[Age_M]

Hello James,

first of all, thx again for the great work!
I have a question about the ShutdownMon.exe
All versions of the gpl pv drivers including this file, I get an error 
on a _german_ Win XP Prof SP2 version, when installing. This is the 
translation of the error message (i guess): "Application could not be 
initialised (0x0000135). Click 'OK' to proceed"
Do you have any idea why this happens?

Greetz Holger


James Harper wrote:
> This release fixes a BSoD on boot that some people were seeing sometimes
> and other people were seeing all of the time.
>
> http://www.meadowcourt.org/WindowsXenPV-0.8.4.zip
>
> James
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>
>   

Re: Release 0.8.4 of GPL PV Drivers for Windows

[Stephan Seitz]

[-- Attachment #1.1.1: Type: text/plain, Size: 810 bytes --]

Age_M schrieb:
> Hello James,
> 
> first of all, thx again for the great work!
> I have a question about the ShutdownMon.exe
> All versions of the gpl pv drivers including this file, I get an error 
> on a _german_ Win XP Prof SP2 version, when installing. This is the 
> translation of the error message (i guess): "Application could not be 
> initialised (0x0000135). Click 'OK' to proceed"
> Do you have any idea why this happens?
> 
> Greetz Holger

This indicates that you don't have .net framework installed. You'll probably
need to install version 2.

Btw.
ShutdownMon doesn't run on x86_64 XP SP2, it's also not possible to compile it.
It complains at some filedescriptor. Sorry for this bad info, but I don't have
this system available now. I'll post clear informations later.



[-- Attachment #1.1.2: s_seitz.vcf --]
[-- Type: text/x-vcard, Size: 335 bytes --]

begin:vcard
fn:Stephan Seitz
n:Seitz;Stephan
org:netz-haut e.K.
adr:;;Zweierweg 22;Wuerzburg;Bayern;97074;Deutschland
email;internet:s.seitz@netz-haut.de
title:Senior System Administrator
tel;work:+49-931-287-6247
tel;fax:+49-931-287-6248
x-mozilla-html:FALSE
url:http://www.schwarz-mode.de/files/
version:2.1
end:vcard


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

[-- Attachment #2: Type: text/plain, Size: 137 bytes --]

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

Re: Release 0.8.4 of GPL PV Drivers for Windows

[Age_M]

hi stephan,

thanks for you reply. installing .net-framework-2 did the trick.

greetz holger

Stephan Seitz wrote:
> Age_M schrieb:
>> Hello James,
>>
>> first of all, thx again for the great work!
>> I have a question about the ShutdownMon.exe
>> All versions of the gpl pv drivers including this file, I get an 
>> error on a _german_ Win XP Prof SP2 version, when installing. This is 
>> the translation of the error message (i guess): "Application could 
>> not be initialised (0x0000135). Click 'OK' to proceed"
>> Do you have any idea why this happens?
>>
>> Greetz Holger
>
> This indicates that you don't have .net framework installed. You'll 
> probably
> need to install version 2.
>
> Btw.
> ShutdownMon doesn't run on x86_64 XP SP2, it's also not possible to 
> compile it.
> It complains at some filedescriptor. Sorry for this bad info, but I 
> don't have
> this system available now. I'll post clear informations later.
>
>

RE: [Xen-users] Release 0.8.4 of GPL PV Drivers for Windows

[James Harper]

> Btw.
> ShutdownMon doesn't run on x86_64 XP SP2, it's also not possible to
> compile it.
> It complains at some filedescriptor. Sorry for this bad info, but I
don't
> have
> this system available now. I'll post clear informations later.

Hmmm... it seems to work on W2K3 x64. I will need more information to
look into it further...

James

Re: Release 0.8.4 of GPL PV Drivers for Windows

[Holger Miefert]

Hello James,

I have another gpl pv drivers related question. Is it right that 
xenhide.inf is missing? If yes, you need to update the install.txt 
because there the xenhide.inf is still in the file-listing.
Is it right that even with /gplpv boot-option there only is a qemu-disk 
and the realtek nic?
I have reason to believe that the gplpv drivers are installed on the 
system, but are not active...

Greetz Holger

James Harper schrieb:
> This release fixes a BSoD on boot that some people were seeing sometimes
> and other people were seeing all of the time.
> 
> http://www.meadowcourt.org/WindowsXenPV-0.8.4.zip
> 
> James
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
> 

RE: Release 0.8.4 of GPL PV Drivers for Windows

[James Harper]

> Hello James,
> 
> I have another gpl pv drivers related question. Is it right that
> xenhide.inf is missing? If yes, you need to update the install.txt
> because there the xenhide.inf is still in the file-listing.

Thanks for the reminder. That file was well out of date in that respect
- it is fixed in hg now.

> Is it right that even with /gplpv boot-option there only is a
qemu-disk
> and the realtek nic?
> I have reason to believe that the gplpv drivers are installed on the
> system, but are not active...

I wonder if this is the same problem as I suspect another guy was having
when the language was set to 'French'. Are you using 'German' as your
system language? If so, can you tell me what the name of the 'PCI Bus'
device is in device manager? I think it could be 'Bus PCI' in French...
I probably need to use something a little more unchanging to detect the
PCI Bus to attach xenhide to.

James

Re: Release 0.8.4 of GPL PV Drivers for Windows

[Holger Miefert]

James Harper wrote:
> Are you using 'German' as your system language?
Yes, german is the system language

> If so, can you tell me what the name of the 'PCI Bus' device is in device manager?
It's called 'PCI-Bus'

> I probably need to use something a little more unchanging to detect the PCI Bus to attach xenhide to.
If you could use more information or help, let me know.

Greetz Holger

RE: Release 0.8.4 of GPL PV Drivers for Windows

[James Harper]

> James Harper wrote:
> > Are you using 'German' as your system language?
> Yes, german is the system language
> 
> > If so, can you tell me what the name of the 'PCI Bus' device is in
> device manager?
> It's called 'PCI-Bus'

Yep. That'll do it.

I have just updated it to check for the hardwareid instead. I'll do
another release shortly.

James