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

In the spirit of ''release early, release often'',
here''s another binary
release...

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

The only thing that''s changed since 0.8.7 is that xennet should work
under amd64 again.

James

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

James Harper schrieb:
> In the spirit of ''release early, release often'',
here''s another binary
> release...
> 
> http://www.meadowcourt.org/WindowsXenPV-0.8.8.zip
> 
> The only thing that''s changed since 0.8.7 is that xennet should
work
> under amd64 again.
Still not working 2008 amd64 english, same error, maybe it is related 
with the fact that the two xen stub device driver entries also show an 
error (as far as i can see the same).

Florian
> 
> 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

Hello James,

James Harper schrieb:
> In the spirit of ''release early, release often'',
here''s another binary
> release...
>   
yes, that''s how it should be :-D thanks again, your work is really 
appreciated here.
> The only thing that''s changed since 0.8.7 is that xennet should
work
> under amd64 again.
>
>   
Well, I didn''t expect it to work, but just want to inform you that a 
German WinXP Prof SP2 still get''s the BSoD with afaik
"inaccessible boot
device" errorcode (0x7b?). Is there anything I could do, to provide you 
with debug that would help you fix this?
And if yes, which tools do I need and what do I have to do?

Greetz Age_M

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

On Monday March 31 2008 01:13:34 pm Age_M wrote:
> Well, I didn''t expect it to work, but just want to inform you that
a
> German WinXP Prof SP2 still get''s the BSoD with afaik
"inaccessible boot
> device" errorcode (0x7b?). Is there anything I could do, to provide
you
Well, I made the mistake of trying to run install.bat while still having 
booted w/ /gplpv. As soon as my PV nic (from 0.8.4) disappeared in Task 
Manager, I got the BSOD:

*** STOP: 0x0000007E (0xC0000005,0xF765639D,0xF8AF930C,0xF8AF9008)

***   xenenum.sys - Address F765639D base at F6540000, DateStamp 47f0c67f

Resuming the install after booting w/o /gplpv, I got the BSOD:

*** STOP: 0x0000007E (0xC0000005,0xF722F3DC,0xF8AF534b,0xF8AF5044)

***   xenpci.sys - Address F722F3DC base at F722B000, DateStamp 47f0c67f

At this point, rebooting w/o /gplpv consistently produced a hang (after the 
Windows logo). Mounting the vbd image offline, I see that the only xen*.sys 
that got updated was xenenum, so I copied the 0.8.4 xenenum on top of it, and 
rebooted w/o /gplpv. Looking in Device Manager, the only PV drivers Windows 
*thinks* are 0.8.8 are xenenum & xenpci (even tho'' it never copied
over
the .sys file), and the Xen PV nic is missing again. Proceeding with 
install.bat, and I get the BSOD:

*** STOP: 0x0000007E (0xC0000005,0xF6EE52D9,0xF8AF9064,0xF8AF8D60)

***   xenvbd.sys - Address F6EE52D9 base at F6EDB000, DateStamp 47f0c67d

Rebooting w/o /gplpv successfully, Device Manager thinks all listed Xen PV 
drivers are 0.8.8, except the nic is still missing (unless I select
''Show
Hidden Devices'', in which case the Packet Scheduler Miniport and
Virtual
Machine Network Services Driver attached to Xen Net Device Driver have 
Microsoft drivers, so this must be something that Microsoft provides 
automatically for all nics). The only xen*.sys files that have been updated 
in c:\windows\system32\drivers are xenstub and xenvbd and xenaddresource 
(since I copied over xenenum), but not xenhide or xenpci. Rerunning 
install.bat, it went all the way to the final screen. Copying over all the 
0.8.8 xen*.sys files to [...]\drivers, I scheduled a chkdsk & rebooted 
w/o /gplpv, the chkdsk did its corrections successfully, and rebooted and 
hung between selecting no gplpv, and what would have been the Windows logo. 
Destroyed and rebooted a couple of more times w/ and w/o /gplpv, and still no 
logo. Mounting offline, and looking at the xen*.sys files, xenenum is 0 
bytes, so I copied over the 0.8.8 version, and rebooted successfully 
w/o /gplpv. Still no Xen PV nic. Reboot w/ /gplpv, and get the 0x7B BSOD. 
Back to 0.8.4 for now (or just boot w/o /gplpv).

My impression is that there is something wrong w/ xenenum. That''s where
the
problems start with the install, and that''s when I lose my Xen nic.
Plus,
Windows starts asking me to revalidate as soon as I try to install something 
higher than 0.8.5 (because of large changes in hardware).

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

> 
> My impression is that there is something wrong w/ xenenum. That''s
where
> the problems start with the install, and that''s when I lose my Xen
nic.
> Plus, Windows starts asking me to revalidate as soon as I try to
install
> something higher than 0.8.5 (because of large changes in hardware).
> 
Xenenum is one of the more simple drivers in the whole thing, so I have
my doubts.

I have just found a bug that would be brought on by higher traffic loads
at boot time. I''m just testing it now.

At some point I started a ''ping -q -f'' to my test DomU, and
then forgot
about it, and I was starting to go crazy because the test DomU would
lock up or BSoD shortly after boot, when it had been running perfectly
previously.

James

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

Hi James,

James Harper schrieb:
> I have just found a bug that would be brought on by higher traffic loads
> at boot time. I''m just testing it now.
>
> At some point I started a ''ping -q -f'' to my test DomU,
and then forgot
> about it, and I was starting to go crazy because the test DomU would
> lock up or BSoD shortly after boot, when it had been running perfectly
> previously.
>
>   
yes, I think I could hear your "Aaaaaaaah" here in Germany, when
you''d
found out ;-)

Greetz Age_M

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