Xen users - Mar 2008 - Release 0.8.6 of GPL PV drivers for Windows

(right lists this time)

After much delay and hair loss, I have finally uploaded another binary
release of the GPL PV drivers for Windows.

Download from http://www.meadowcourt.org/WindowsXenPV-0.8.6.zip

Changes in this release are:

. Xennet is configurable via the ''Advanced'' tab on the network
interface.
. Lots of bug fixes in Xennet (thanks Andy), and other changes mainly
related to differences between windows and linux in the way they do csum
and large send offload. Should work better than the qemu drivers in this
respect.
. Fixed a bug where an x32 DomU wouldn''t boot if it was configured with
4G or more of memory.
. Lots of other stuff probably.

To upgrade from a previous version, the following steps are probably the
best way forward:

1. Delete all of xen*.sys EXCEPT xenhide.sys from
C:\windows\system32\drivers
2. Boot into non-GPLPV mode
3. Run install.bat
4. Boot into GPLPV mode
5. Install the network drivers (windows should prompt that it has
detected new drivers)

Enjoy!

James

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

My test machine has been running fine under all the tests I could throw
at it, but within seconds of me hitting the send button, I get a BSoD...

Oh well... maybe don''t touch this release just yet :(

James
> -----Original Message-----
> From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-
> bounces@lists.xensource.com] On Behalf Of James Harper
> Sent: Saturday, 29 March 2008 22:01
> To: xen-devel@lists.xensource.com; xen-users@lists.xensource.com
> Subject: [Xen-devel] Release 0.8.6 of GPL PV drivers for Windows
> 
> (right lists this time)
> 
> After much delay and hair loss, I have finally uploaded another binary
> release of the GPL PV drivers for Windows.
> 
> Download from http://www.meadowcourt.org/WindowsXenPV-0.8.6.zip
> 
> Changes in this release are:
> 
> . Xennet is configurable via the ''Advanced'' tab on the
network
> interface.
> . Lots of bug fixes in Xennet (thanks Andy), and other changes mainly
> related to differences between windows and linux in the way they do
csum
> and large send offload. Should work better than the qemu drivers in
this
> respect.
> . Fixed a bug where an x32 DomU wouldn''t boot if it was configured
with
> 4G or more of memory.
> . Lots of other stuff probably.
> 
> To upgrade from a previous version, the following steps are probably
the
> best way forward:
> 
> 1. Delete all of xen*.sys EXCEPT xenhide.sys from
> C:\windows\system32\drivers
> 2. Boot into non-GPLPV mode
> 3. Run install.bat
> 4. Boot into GPLPV mode
> 5. Install the network drivers (windows should prompt that it has
> detected new drivers)
> 
> Enjoy!
> 
> James
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Okay I''ve definitely fixed a bug that would cause the BSoD I was
seeing,
so I''m trying again.

Please test and let me know!

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

Thanks

James

> -----Original Message-----
> From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-
> bounces@lists.xensource.com] On Behalf Of James Harper
> Sent: Saturday, 29 March 2008 22:17
> To: xen-devel@lists.xensource.com; xen-users@lists.xensource.com
> Subject: RE: [Xen-devel] Release 0.8.6 of GPL PV drivers for Windows
> 
> My test machine has been running fine under all the tests I could
throw
> at it, but within seconds of me hitting the send button, I get a
BSoD...
> 
> Oh well... maybe don''t touch this release just yet :(
> 
> James
> 
> > -----Original Message-----
> > From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-
> > bounces@lists.xensource.com] On Behalf Of James Harper
> > Sent: Saturday, 29 March 2008 22:01
> > To: xen-devel@lists.xensource.com; xen-users@lists.xensource.com
> > Subject: [Xen-devel] Release 0.8.6 of GPL PV drivers for Windows
> >
> > (right lists this time)
> >
> > After much delay and hair loss, I have finally uploaded another
binary
> > release of the GPL PV drivers for Windows.
> >
> > Download from http://www.meadowcourt.org/WindowsXenPV-0.8.6.zip
> >
> > Changes in this release are:
> >
> > . Xennet is configurable via the ''Advanced'' tab on
the network
> > interface.
> > . Lots of bug fixes in Xennet (thanks Andy), and other changes
mainly
> > related to differences between windows and linux in the way they do
> csum
> > and large send offload. Should work better than the qemu drivers in
> this
> > respect.
> > . Fixed a bug where an x32 DomU wouldn''t boot if it was
configured
> with
> > 4G or more of memory.
> > . Lots of other stuff probably.
> >
> > To upgrade from a previous version, the following steps are probably
> the
> > best way forward:
> >
> > 1. Delete all of xen*.sys EXCEPT xenhide.sys from
> > C:\windows\system32\drivers
> > 2. Boot into non-GPLPV mode
> > 3. Run install.bat
> > 4. Boot into GPLPV mode
> > 5. Install the network drivers (windows should prompt that it has
> > detected new drivers)
> >
> > Enjoy!
> >
> > James
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

With win2008 it works exept networking.
Tell me how i could help you, fixing this?

Florian

James Harper schrieb:
> Okay I''ve definitely fixed a bug that would cause the BSoD I was
seeing,
> so I''m trying again.
> 
> Please test and let me know!
> 
> http://www.meadowcourt.org/WindowsXenPV-0.8.7.zip
> 
> Thanks
> 
> James
> 
> 
>> -----Original Message-----
>> From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-
>> bounces@lists.xensource.com] On Behalf Of James Harper
>> Sent: Saturday, 29 March 2008 22:17
>> To: xen-devel@lists.xensource.com; xen-users@lists.xensource.com
>> Subject: RE: [Xen-devel] Release 0.8.6 of GPL PV drivers for Windows
>>
>> My test machine has been running fine under all the tests I could
> throw
>> at it, but within seconds of me hitting the send button, I get a
> BSoD...
>> Oh well... maybe don''t touch this release just yet :(
>>
>> James
>>
>>> -----Original Message-----
>>> From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-
>>> bounces@lists.xensource.com] On Behalf Of James Harper
>>> Sent: Saturday, 29 March 2008 22:01
>>> To: xen-devel@lists.xensource.com; xen-users@lists.xensource.com
>>> Subject: [Xen-devel] Release 0.8.6 of GPL PV drivers for Windows
>>>
>>> (right lists this time)
>>>
>>> After much delay and hair loss, I have finally uploaded another
> binary
>>> release of the GPL PV drivers for Windows.
>>>
>>> Download from http://www.meadowcourt.org/WindowsXenPV-0.8.6.zip
>>>
>>> Changes in this release are:
>>>
>>> . Xennet is configurable via the ''Advanced'' tab
on the network
>>> interface.
>>> . Lots of bug fixes in Xennet (thanks Andy), and other changes
> mainly
>>> related to differences between windows and linux in the way they do
>> csum
>>> and large send offload. Should work better than the qemu drivers in
>> this
>>> respect.
>>> . Fixed a bug where an x32 DomU wouldn''t boot if it was
configured
>> with
>>> 4G or more of memory.
>>> . Lots of other stuff probably.
>>>
>>> To upgrade from a previous version, the following steps are
probably
>> the
>>> best way forward:
>>>
>>> 1. Delete all of xen*.sys EXCEPT xenhide.sys from
>>> C:\windows\system32\drivers
>>> 2. Boot into non-GPLPV mode
>>> 3. Run install.bat
>>> 4. Boot into GPLPV mode
>>> 5. Install the network drivers (windows should prompt that it has
>>> detected new drivers)
>>>
>>> Enjoy!
>>>
>>> James
>>>
>>> _______________________________________________
>>> Xen-devel mailing list
>>> Xen-devel@lists.xensource.com
>>> http://lists.xensource.com/xen-devel
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
> 



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

> 
> With win2008 it works exept networking.
I am assuming here that you see an adapter but it just doesn''t work.
> Tell me how i could help you, fixing this?
. Download DebugView from sysinternals.com
. Disable the xennet driver
. Reboot
. Start DebugView, and make sure that ''Capture Kernel'' is
selected
. Enable the xennet driver. DebugView should print up a heap of stuff
. Email the above stuff to me :)

I don''t have a Win2008 to test on at this time, but the above might
give me
a clue as to what is going wrong.

It could also be that Windows 2008 doesn''t support NDIS5.1, in which
case I
don''t expect the above to tell us anything useful.

Thanks

James


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

> It could also be that Windows 2008 doesn''t support NDIS5.1, in
which
case
> I don''t expect the above to tell us anything useful.
According to a pre-longhorn power point document that google turned up:

"
NDIS 5.1 drivers using NDIS_PACKETs are supported in Windows codenamed
"Longhorn"- but not as high a performance as NDIS 6.0 drivers due to
translation overhead
"

So that shouldn''t be the problem you are seeing.

Did a previous version of xennet work at all?

James

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

On Saturday 29 March 2008 03:19:54 pm Florian Manschwetus
wrote:
> With win2008 it works exept networking.
> Tell me how i could help you, fixing this?
This probably relates to your problem. When I followed James''
instructions
(delete xen*.sys, except xenhide.sys, reboot w/o /gplpv, run install.bat), 
the final screen of the wizard box said all my drivers were status
''Device
Updated'', except xenenum & xennet, which said ''Ready to
Use'', which typically
means (based on previous experience with the PV drivers) that the driver 
wasn''t updated. However, for xenenum, a ''Found New
Hardware'' wizard box came
up automatically and lead me through installing it. Going into Device 
Manager, the Driver tab of ''Xen Enum Device Driver Properties''
correctly
showed a Driver Version of 0.8.7.

For xennet however, no device choice was given for the PV device under Network 
Adapters, and couldn''t be updated, not even by running install.bat
twice. I
rebooted w/ /gplpv, and got a BSOD, with:

*** STOP: 0x0000007B (0xF8AB5524,0xC0000034,0x00000000,0x00000000)

Btw, there does not seem to be a ''Xen PCI Device Hider'' in
Device Manger
anymore. xenhide.sys seems to be one of the drivers under ''Xen PCI
Device''
now. Probably related to not having a xenhide.inf anymore in the 0.8.x 
series. I do think that driver updates have been less reliable since this 
change, tho''.

2nd btw, if you click on View -> Show hidden devices, among other things, you
get:

Network Adapters
  Direct Parallel
  Realtek RTL8139 Family PCI Fast Ethernet NIC
  Realtek RTL8139 Family PCI Fast Ethernet NIC - Packet Scheduler Miniport
  Realtek RTL8139 Family PCI Fast Ethernet NIC - Virtual Machine Network 
Services Driver

but for Xen Net, only:

  Xen Net Device Driver - Packet Scheduler Miniport
  Xen Net Device Driver - Virtual Machine Network Services Driver

So, again, we are missing a device.

Copying xen*.sys from 0.8.6 on top of the of the ones in c:
\WINDOWS\system32\drivers still causes the same BSOD when booting w/ /gplpv. 
Also, the Xen Net PV nic is still missing.

When copying xen*.sys from 0.8.4 on top of the of the ones in c:
\WINDOWS\system32\drivers and rebooting w/ /gplpv, the Hardware Wizard came 
up for xennet. When I told it to install the 0.8.7 xennet, I got the BSOD:

*** STOP: 0x0000007E (0xC0000005,0xF5F349BC,0xF8AF14EC,0xF8AF11E8)

***   xennet.sys - Address F5F349BC base at F5F2D000, DateStamp 47ee3c8e

Repeating the above, but telling the Hardware Wizard to install the 0.8.4 
xennet, I got the BSOD:

*** STOP: 0x0000007E (0xC0000005,0xF81219BC,0xF8AE94EC,0xF8AE91E8)

***   xennet.sys - Address F81219BC base at F811A000, DateStamp 47ee3c8e

Apparently, the system restored the 0.8.7 xennet anyway. Repeating copying the 
0.8.4 xennet, I finally restored my gplpv functionality.


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

James Harper schrieb:
> Okay I''ve definitely fixed a bug that would cause the BSoD I was
seeing,
> so I''m trying again.
> 
> Please test and let me know!
> 
> http://www.meadowcourt.org/WindowsXenPV-0.8.7.zip
> 
> Thanks
> 
> James
Hi,

i''ve tried 0.8.7 upon a freshly installed W2k3 SBS Server (german).
Xen Version is 3.2.0 amd64.

After running install.bat, the system starts with a msg. like "At least
one Service could not by started" (i didn''t investigate by now,
but I
assume this is the XenShutdown).

The netfront vif''s are completely missing, Hardware list shows one
"unknown device"
remaining in "other devices" (before installation there were two of
them), then
"Xen PCI Device" has a warning mark and "Could not be
initialized".

Booting into /gplpv results in a BSOD.


Looks like this build has some significant problems ;)

Cheers,

Stephan




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

Florian Manschwetus schrieb:
> Stephan Seitz schrieb:
>> James Harper schrieb:
>>> Okay I''ve definitely fixed a bug that would cause the BSoD
I was seeing,
>>> so I''m trying again.
>>>
>>> Please test and let me know!
>>>
>>> http://www.meadowcourt.org/WindowsXenPV-0.8.7.zip
>>>
>> i''ve tried 0.8.7 upon a freshly installed W2k3 SBS Server
(german).
>> Xen Version is 3.2.0 amd64.
> You should try an English version with German i have had a lot of trouble.
> 
> florian
Unfortunately, I don''t have an english version by hand.

But I forget to mention that i''ve tried vcpus=2. As far as I remember
there
have been problems with SMP. Can someone confirm the SMP bugs solved?

Thanks in advance.

Cheers,

Stephan



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

> Unfortunately, I don''t have an english version by hand.
> 
> But I forget to mention that i''ve tried vcpus=2. As far as I
remember
> there
> have been problems with SMP. Can someone confirm the SMP bugs solved?
> 
I do all my testing on SMP, so I doubt that is the cause of your
problems.

James

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

> James Harper schrieb:
> > Okay I''ve definitely fixed a bug that would cause the BSoD I
was
seeing,
> > so I''m trying again.
> >
> 
> i''ve tried 0.8.7 upon a freshly installed W2k3 SBS Server
(german).
> Xen Version is 3.2.0 amd64.
Hmmm... I''ll see if I can test amd64 again tonight. I''ve only
been
testing with i386 recently.
> After running install.bat, the system starts with a msg. like "At
least
> one Service could not by started" (i didn''t investigate by
now, but I
> assume this is the XenShutdown).
XenShutdown will probably fail if XenPCI isn''t running.
> The netfront vif''s are completely missing, Hardware list shows one
> "unknown device" remaining in "other devices" (before
installation
> there were two of them), then "Xen PCI Device" has a warning mark
and
> "Could not be initialized".
Yep. If XenPCI isn''t working then nothing else will work.
> Booting into /gplpv results in a BSOD.
Probably 0x7B which means boot device inaccessible. This presumably
means that xenhide is working and hiding your qemu devices, and because
xenpci isn''t working you have nothing to boot off.
> Looks like this build has some significant problems ;)
I''d like to find out if it''s an amd64 problem or a Germen
language
problem. What media are you using? This seems to be a big enough problem
that it''s probably worth investigating... I have installed Windows
enough times that I shouldn''t even need to read the screens :)

James

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

> On Saturday 29 March 2008 03:19:54 pm Florian Manschwetus wrote:
> > With win2008 it works exept networking.
> > Tell me how i could help you, fixing this?
> 
> This probably relates to your problem. When I followed James''
instructions
> (delete xen*.sys, except xenhide.sys, reboot w/o /gplpv, run
install.bat),
> the final screen of the wizard box said all my drivers were status
''Device
> Updated'', except xenenum & xennet, which said ''Ready
to Use'', which
> typically
> means (based on previous experience with the PV drivers) that the
driver
> wasn''t updated.
Well... what _should_ happen is that DPInst.exe (the Microsoft provided
thing that gets called by install.bat) should copy all the drivers into
Windows. Anything that is detect gets installed immediately, anything
else gets installed next time it is detected. Are you saying your
experience is contrary to this?

I found recently (eg an hour ago) a domain that crashed during update,
and left a dodgy version of WdfConInstaller01007.sys around, which meant
nothing else would install. That probably gave a fairly obvious message
though.
> However, for xenenum, a ''Found New Hardware'' wizard box
> came
> up automatically and lead me through installing it. Going into Device
> Manager, the Driver tab of ''Xen Enum Device Driver
Properties''
correctly
> showed a Driver Version of 0.8.7.
> 
> For xennet however, no device choice was given for the PV device under
> Network
> Adapters, and couldn''t be updated, not even by running install.bat
twice.
> I
> rebooted w/ /gplpv, and got a BSOD, with:
> 
> *** STOP: 0x0000007B (0xF8AB5524,0xC0000034,0x00000000,0x00000000)
> 
> Btw, there does not seem to be a ''Xen PCI Device Hider''
in Device
Manger
> anymore. xenhide.sys seems to be one of the drivers under ''Xen PCI
Device''
> now. Probably related to not having a xenhide.inf anymore in the 0.8.x
> series. I do think that driver updates have been less reliable since
this
> change, tho''.
Xenhide.sys gets attached to the windows PCI driver via xenpci.inf. I
think there is no really nice solution to this problem unfortunately.
The bad thing about the ''Xen PCI Device Hider'' was that
windows would
sometimes replace it with it''s own ''PCI Bus'' driver
again without
telling me (probably during a service pack or hotfix) and would cause
massive corruption to the system. The massive corruption problem should
be solved, but I''d rather stick with the current solution...
> 
> 2nd btw, if you click on View -> Show hidden devices, among other
things,
> you get:
> 
> Network Adapters
>   Direct Parallel
>   Realtek RTL8139 Family PCI Fast Ethernet NIC
>   Realtek RTL8139 Family PCI Fast Ethernet NIC - Packet Scheduler
Miniport
>   Realtek RTL8139 Family PCI Fast Ethernet NIC - Virtual Machine
Network
> Services Driver
> 
> but for Xen Net, only:
> 
>   Xen Net Device Driver - Packet Scheduler Miniport
>   Xen Net Device Driver - Virtual Machine Network Services Driver
> 
> So, again, we are missing a device.
Not sure what to make of that.
> Copying xen*.sys from 0.8.6 on top of the of the ones in c:
> \WINDOWS\system32\drivers still causes the same BSOD when booting w/
> /gplpv.
> Also, the Xen Net PV nic is still missing.
> 
> When copying xen*.sys from 0.8.4 on top of the of the ones in c:
> \WINDOWS\system32\drivers and rebooting w/ /gplpv, the Hardware Wizard
> came
> up for xennet. When I told it to install the 0.8.7 xennet, I got the
BSOD:
> 
> *** STOP: 0x0000007E (0xC0000005,0xF5F349BC,0xF8AF14EC,0xF8AF11E8)
> 
> ***   xennet.sys - Address F5F349BC base at F5F2D000, DateStamp
47ee3c8e
> 
> Repeating the above, but telling the Hardware Wizard to install the
0.8.4
> xennet, I got the BSOD:
> 
> *** STOP: 0x0000007E (0xC0000005,0xF81219BC,0xF8AE94EC,0xF8AE91E8)
> 
> ***   xennet.sys - Address F81219BC base at F811A000, DateStamp
47ee3c8e
> 
> Apparently, the system restored the 0.8.7 xennet anyway. Repeating
copying
> the
> 0.8.4 xennet, I finally restored my gplpv functionality.
> 
Well... that''s strange.

James


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

James Harper schrieb:
>
> Well... what _should_ happen is that DPInst.exe (the Microsoft provided
> thing that gets called by install.bat) should copy all the drivers into
> Windows.
Hi James,

is there a reason not to use dpinst.exe with /F option? I''d think /F 
would make sure that ALL drivers are updated.
Maybe you should consider using this option in the installer.bat

Greetz Age_M

PS: On a german Windows XP SP2 i still get a BSoD when using /gplpv with 
latest driver package :-(

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

> James Harper schrieb:
> >
> > Well... what _should_ happen is that DPInst.exe (the Microsoft
provided
> > thing that gets called by install.bat) should copy all the drivers
into
> > Windows.
> Hi James,
> 
> is there a reason not to use dpinst.exe with /F option? I''d think
/F
> would make sure that ALL drivers are updated.
> Maybe you should consider using this option in the installer.bat
Have you tried it? It sounds like it would only make a difference if the
current driver was newer, which should never be the case.
> 
> PS: On a german Windows XP SP2 i still get a BSoD when using /gplpv
with
> latest driver package :-(
BSoD 0x7B?

James

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

Thanks for your reply,

I was not really clear, the hypervisor is amd64, the W2k3 SBS HVM domU is i386.

After a few installations, i skipped the install.bat and tried the former way
of installing each device manually. I did accidently choose winxp (instead of
winnet) and the xenpci device has been initialized. After seeing my fault, I
installed all subsequent drivers from winxp, but the result was also not having
any netfront available.

Please ask, if you need more specific details.

Cheers,

Stephan





James Harper schrieb:
>> James Harper schrieb:
>>> Okay I''ve definitely fixed a bug that would cause the BSoD
I was
> seeing,
>>> so I''m trying again.
>>>
>> i''ve tried 0.8.7 upon a freshly installed W2k3 SBS Server
(german).
>> Xen Version is 3.2.0 amd64.
> 
> Hmmm... I''ll see if I can test amd64 again tonight. I''ve
only been
> testing with i386 recently.
> 
>> After running install.bat, the system starts with a msg. like "At
> least
>> one Service could not by started" (i didn''t investigate
by now, but I
>> assume this is the XenShutdown).
> 
> XenShutdown will probably fail if XenPCI isn''t running.
> 
>> The netfront vif''s are completely missing, Hardware list shows
one
>> "unknown device" remaining in "other devices"
(before installation
>> there were two of them), then "Xen PCI Device" has a warning
mark and
>> "Could not be initialized".
> 
> Yep. If XenPCI isn''t working then nothing else will work.
> 
>> Booting into /gplpv results in a BSOD.
> 
> Probably 0x7B which means boot device inaccessible. This presumably
> means that xenhide is working and hiding your qemu devices, and because
> xenpci isn''t working you have nothing to boot off.
> 
>> Looks like this build has some significant problems ;)
> 
> I''d like to find out if it''s an amd64 problem or a Germen
language
> problem. What media are you using? This seems to be a big enough problem
> that it''s probably worth investigating... I have installed Windows
> enough times that I shouldn''t even need to read the screens :)
> 
> James

-- 
Stephan Seitz
Senior System Administrator

*netz-haut* e.K.
multimediale kommunikation

zweierweg 22
97074 würzburg

fon: +49 931 2876247
fax: +49 931 2876248

web: www.netz-haut.de <http://www.netz-haut.de/>

registriergericht: amtsgericht würzburg, hra 5054



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

Just an update to my recent post:

This time, I installed the recommended Windows updates first (it''s now
SP2).
The drivers installed now without any problem.
Anyway, the netfront vif''s are missing again.

Cheers,

Stephan





James Harper schrieb:
>> James Harper schrieb:
>>> Okay I''ve definitely fixed a bug that would cause the BSoD
I was
> seeing,
>>> so I''m trying again.
>>>
>> i''ve tried 0.8.7 upon a freshly installed W2k3 SBS Server
(german).
>> Xen Version is 3.2.0 amd64.
> 
> Hmmm... I''ll see if I can test amd64 again tonight. I''ve
only been
> testing with i386 recently.
> 


-- 
Stephan Seitz
Senior System Administrator

*netz-haut* e.K.
multimediale kommunikation

zweierweg 22
97074 würzburg

fon: +49 931 2876247
fax: +49 931 2876248

web: www.netz-haut.de <http://www.netz-haut.de/>

registriergericht: amtsgericht würzburg, hra 5054



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

> Just an update to my recent post:
> 
> This time, I installed the recommended Windows updates first (it''s
now
> SP2).
> The drivers installed now without any problem.
> Anyway, the netfront vif''s are missing again.
> 
Well... fwiw, I just finished installing a copy of W2K3R2 x64 EE, and
installed the drivers using install.bat, and everything worked fine up
until the network drivers wanted to install on the next boot, and they
just say ''Code 10''. I''m putting that down to an x64
problem for the
moment.

So I guess all the problems you and others are having must be language
based... I can''t see where in the code that could be though, but
it''s
12:30am over here so I''m getting some sleep :)

James

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

> Thanks for your reply,
> 
> I was not really clear, the hypervisor is amd64, the W2k3 SBS HVM domU
is
> i386.
> 
> After a few installations, i skipped the install.bat and tried the
former
> way
> of installing each device manually. I did accidently choose winxp
(instead
> of
> winnet) and the xenpci device has been initialized. After seeing my
fault,
> I
> installed all subsequent drivers from winxp, but the result was also
not
> having
> any netfront available.
> 
> Please ask, if you need more specific details.
> 
If you could attach a debugger to the DomU when it boots and send me the
output it would be much appreciated. I need to see what the difference
is between the different language editions of windows...

James

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

James Harper schrieb:
>   
>> PS: On a german Windows XP SP2 i still get a BSoD when using /gplpv
with latest driver package :-(
>>     
>
> BSoD 0x7B?
>
> James
>
>   
Yes, this is the exact failure message:

0x0000007B (0xF7A09528,0xC0000034,0x00000000,0x00000000)

Any ideas what''s causing it??

Greetz Age_M

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

James Harper schrieb:
>> Thanks for your reply,
>>
>> I was not really clear, the hypervisor is amd64, the W2k3 SBS HVM domU
> is
>> i386.
Ok, I have to say that my system is completely amd64, so the network 
thing could eb an amd64 issue. When i find the time, i could test this 
version on my 2003EE test box, (but i have to install it first to 
english), also when i have the time i will setup i386 test installs.

Florian
>>.....
>> Please ask, if you need more specific details.
>>
> 
> If you could attach a debugger to the DomU when it boots and send me the
> output it would be much appreciated. I need to see what the difference
> is between the different language editions of windows...
> 
> James
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
> 


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

On Sunday March 30 2008 08:34:50 am James Harper wrote:
> > is there a reason not to use dpinst.exe with /F option? I''d
think /F
> > would make sure that ALL drivers are updated.
> > Maybe you should consider using this option in the installer.bat
>
> Have you tried it? It sounds like it would only make a difference if the
> current driver was newer, which should never be the case.
It might do something. I copied the 0.8.4 xen*.sys files over to c:
\windows\system32\drivers, then edited the 0.8.7 install.bat to add /F to 
dpinst and ran it. I ended up with a system that would not boot, even 
w/o /gplpv. When I did get a BSOD, it was 0x7E, xenenum.sys. I finally got it 
working with losetup/kpartx/mount -o force to copy over the 0.8.4 files. 
Apparently the /F option had copied over 0.8.7 xenenum and xennet on top of 
the 0.8.4 files before the system crashed.

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

> 
> Yes, this is the exact failure message:
> 
> 0x0000007B (0xF7A09528,0xC0000034,0x00000000,0x00000000)
> 
> Any ideas what''s causing it??
> 
0x7B is boot device inaccessible, so it''s not a crash like overwriting
memory or calling something at the wrong IRQL, it''s just windows
throwing up its hands because it can''t find anything to boot off. It
means that xenvbd isn''t being loaded, either because of a problem in
xenpci or in xenvbd. I either need the debug output from booting under
the German version of windows, or I need to get hold of the german media
myself and install it...

James

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

i have similiar situation on english i386 w2k3 with 0.8.5 gplpv (with
russian mui installed) but dont have time now for additional testing with
0.8.7 and debugger
may be you write what i must check first time?


On 3/31/08, James Harper <james.harper@bendigoit.com.au>
wrote:
>
> >
> > Yes, this is the exact failure message:
> >
> > 0x0000007B (0xF7A09528,0xC0000034,0x00000000,0x00000000)
> >
> > Any ideas what''s causing it??
> >
>
> 0x7B is boot device inaccessible, so it''s not a crash like
overwriting
> memory or calling something at the wrong IRQL, it''s just windows
> throwing up its hands because it can''t find anything to boot off.
It
> means that xenvbd isn''t being loaded, either because of a problem
in
> xenpci or in xenvbd. I either need the debug output from booting under
> the German version of windows, or I need to get hold of the german media
> myself and install it...
>
> James
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>

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