Hi everyone, first I would like to thank James for the incredible works he is doing on the gplpv driver. I''ve been following the developpement for sometime with hard time installing and many BSODs. Now it installs like a charm (just press next a few time then reboot). No more little exclamation mark in the device manager, quick boot, good performance. Well we are getting close to a release! I stress tested it during a few days and performance were ok. I have noticed that it works very poorly when using weird block size, but well, it is more than enough for normal use anyway. So here is my issue : since it was performing ok, I wanted to give it a try on a non mission critical app (a few users rdesktoping on a ms access front end connecting through odbc to a postgres database). Performance are ok and user experience is quite positive. However about once per day, I get a BSOD that not only freeze the windows domU, but also make the dom0 unusable (ie if I try to xm create it just hang). The BSOD says (French localised screenshot attached) : DRIVER_IRQL_NOT_LESS_OR_EQUAL *** STOP : 0x000000D1 (0x00CA0B2C,0x000000FF,0x00000001,0x808877FA) I have not found a scenario for reproducing this error, actually it just happen sometime in the day. It is not load related because the stress test where much heavier on ressources and never produced a BSOD. Is there any config file parameters that I should be carefull about ? (I already removed the ioemu flag from the network card). Any advice or hint to get this Windows behaving nicely? Cheers, Denis -- Denis Cardon Tranquil IT Systems 44 bvd des pas enchantés 44230 Saint Sébastien sur Loire tel : +33 (0) 2.40.97.57.56 http://www.tranquil-it-systems.fr _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
What version of Xen are you running? I have a similar scenario, but not issues with BSOD or dom0 becoming unusable. I'm running Xen with SLES10SP2 as the dom0, which is 3.2. -Nick>>> On Tue, Aug 5, 2008 at 11:03 AM, Denis Cardon<denis.cardon@tranquil-it-systems.fr> wrote: Hi everyone, first I would like to thank James for the incredible works he is doing on the gplpv driver. I've been following the developpement for sometime with hard time installing and many BSODs. Now it installs like a charm (just press next a few time then reboot). No more little exclamation mark in the device manager, quick boot, good performance. Well we are getting close to a release! I stress tested it during a few days and performance were ok. I have noticed that it works very poorly when using weird block size, but well, it is more than enough for normal use anyway. So here is my issue : since it was performing ok, I wanted to give it a try on a non mission critical app (a few users rdesktoping on a ms access front end connecting through odbc to a postgres database). Performance are ok and user experience is quite positive. However about once per day, I get a BSOD that not only freeze the windows domU, but also make the dom0 unusable (ie if I try to xm create it just hang). The BSOD says (French localised screenshot attached) : DRIVER_IRQL_NOT_LESS_OR_EQUAL *** STOP : 0x000000D1 (0x00CA0B2C,0x000000FF,0x00000001,0x808877FA) I have not found a scenario for reproducing this error, actually it just happen sometime in the day. It is not load related because the stress test where much heavier on ressources and never produced a BSOD. Is there any config file parameters that I should be carefull about ? (I already removed the ioemu flag from the network card). Any advice or hint to get this Windows behaving nicely? Cheers, Denis -- Denis Cardon Tranquil IT Systems 44 bvd des pas enchantés 44230 Saint Sébastien sur Loire tel : +33 (0) 2.40.97.57.56 http://www.tranquil-it-systems.fr This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> > I stress tested it during a few days and performance were ok. I have > noticed that it works very poorly when using weird block size, butwell,> it is more than enough for normal use anyway.Disk performance will do that. Linux requires that blocks are aligned to a 512 byte boundary while Windows has no such requirement, and scsiport (windows scsi interface) has some fairly harsh restrictions about what you can do about it.> So here is my issue : since it was performing ok, I wanted to give ita> try on a non mission critical app (a few users rdesktoping on a ms > access front end connecting through odbc to a postgres database). > Performance are ok and user experience is quite positive. > > However about once per day, I get a BSOD that not only freeze the > windows domU, but also make the dom0 unusable (ie if I try to xmcreate> it just hang). The BSOD says (French localised screenshot attached) : > > DRIVER_IRQL_NOT_LESS_OR_EQUAL > > *** STOP : 0x000000D1 (0x00CA0B2C,0x000000FF,0x00000001,0x808877FA) > > I have not found a scenario for reproducing this error, actually itjust> happen sometime in the day. It is not load related because the stress > test where much heavier on ressources and never produced a BSOD. > > Is there any config file parameters that I should be carefull about ?(I> already removed the ioemu flag from the network card). Any advice or > hint to get this Windows behaving nicely? >This should not happen no matter what configuration parameters you specify. 0xD1 means that either the memory address is invalid, or that memory that was swapped out was accessed while a spinlock was held or something. That second parameter being 0xFF seems really strange though... it should be a maximum of 0x1F (31) under x32 and a maximum of 0x0F (15) under x64. Can you please turn on the driver verifier? Run verifier.exe from start->run Select ''Create custom settings'' then Next Select ''Select individual settings from a full list'' then Next Tick all but the last 3 options then Next Select ''Select driver names from a list'' then Next Tick all the xen drivers (down the bottom of the list) then Finish That should cause a BSoD as soon as the drivers do something that _could_ cause a crash, and report it in a more useful way, rather than waiting until the drivers _do_ something that causes a crash Thanks James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> > Can you please turn on the driver verifier? > > Run verifier.exe from start->run > > Select ''Create custom settings'' then Next > Select ''Select individual settings from a full list'' then Next > Tick all but the last 3 options then Next > Select ''Select driver names from a list'' then Next > Tick all the xen drivers (down the bottom of the list) then Finish > > That should cause a BSoD as soon as the drivers do something that > _could_ cause a crash, and report it in a more useful way, rather than > waiting until the drivers _do_ something that causes a crash >Actually, don''t do that yet :) I just tried it and it all falls to pieces - it looks like xenhide isn''t playing by the rules. I don''t think that this will be the cause of the problem you are seeing, but it renders the drivers unbootable when the verifier is enabled for it. Maybe try unticking xenhide.sys from the list of drivers for now. I''ll look at fixing it properly. James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users