Moritz Mühlenhoff
2011-Sep-09 07:50 UTC
[Xen-devel] Signed GPLPV drivers available for download
Hi, for inclusion in Univention Corporate Server - a Linux distribution based on Debian targeted towards enterprise environments, which also includes Xen for virtualisation - we''re now building/signing the excellent GPLPV drivers written by James Harper with a Software Publishers Certificate obtained from GlobalSign. [1] This allows installation of the GPLPV drivers on 64 bit Windows without the need to enable the test mode. The drivers are available from http://apt.univention.de/download/addons/gplpv- drivers/ and should be compatible with any Xen installation. The installation is detailed in http://wiki.univention.de/index.php?title=Installing-signed-GPLPV-drivers So far only new installation of the GPLPV drivers have been tested. We welcome general feedback and experiences with upgrades from test-signed versions of GPLPV. Cheers, Moritz Footnotes: [1] We''re well aware of the recent claims of a potential compromise of that CA, but as of today this is still under investigation: http://www.globalsign.com/company/press/090611-security-response.html -- Moritz Mühlenhoff muehlenhoff@univention.de Open Source Software Engineer and Consultant Univention GmbH Linux for Your Business fon: +49 421 22 232- 0 Mary-Somerville-Str.1 28359 Bremen fax: +49 421 22 232-99 http://www.univention.de _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Moritz Mühlenhoff
2011-Sep-12 13:31 UTC
Re: [Xen-devel] Signed GPLPV drivers available for download
Moritz Mühlenhoff wrote:> The drivers are available from > http://apt.univention.de/download/addons/gplpv- drivers/ and should be > compatible with any Xen installation. > > The installation is detailed in > http://wiki.univention.de/index.php?title=Installing-signed-GPLPV-drivers > > So far only new installation of the GPLPV drivers have been tested.FYI; we''ve now also tested/documented the upgrade path from the test-signed drivers from meadowcourt.org to the SPC-signed drivers. The installation docs have been amended: http://wiki.univention.de/index.php?title=Installing-signed-GPLPV-drivers Cheers, Moritz -- Moritz Mühlenhoff muehlenhoff@univention.de Open Source Software Engineer and Consultant Univention GmbH Linux for Your Business fon: +49 421 22 232- 0 Mary-Somerville-Str.1 28359 Bremen fax: +49 421 22 232-99 http://www.univention.de _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Tobias Geiger
2011-Sep-14 16:03 UTC
Re: [Xen-devel] Signed GPLPV drivers available for download
i have very strange effects as soon as i install the GPLPV drivers under windows7 (64bit): - no network connection as soon as anything which accesses the graphiccard in 3d mode is started; thats what buffles me most... i can''t really tell you more than that, its really that strange (first i thought of a virus or something like that, but i was able to circle it down to the gplpv drivers,..) this also happens with non-signed gplpv drivers, and also with a version prior to 308 (was it 238?) - really better read-performance WITH gplpv, but much worse write-performance: here is the performance without gplpv: http://img238.imagevenue.com/img.php?image=15846_HDTune_File_Benchmark_QEMU_HARDDISK_VOR_signedGPLPV_122_354lo.jpg here WITH gplpv: http://img278.imagevenue.com/img.php?image=15846_HDTune_File_Benchmark_XEN____PV_DISK________NACH_gplpv_SIGNED_122_530lo.jpg Greetings Tobias Am Freitag, 9. September 2011, 09:50:04 schrieb Moritz Mühlenhoff:> Hi, > for inclusion in Univention Corporate Server - a Linux distribution based > on Debian targeted towards enterprise environments, which also includes > Xen for virtualisation - we''re now building/signing the excellent GPLPV > drivers written by James Harper with a Software Publishers Certificate > obtained from GlobalSign. [1] > > This allows installation of the GPLPV drivers on 64 bit Windows without the > need to enable the test mode. > > The drivers are available from > http://apt.univention.de/download/addons/gplpv- drivers/ and should be > compatible with any Xen installation. > > The installation is detailed in > http://wiki.univention.de/index.php?title=Installing-signed-GPLPV-drivers > > So far only new installation of the GPLPV drivers have been tested. We > welcome general feedback and experiences with upgrades from test-signed > versions of GPLPV. > > Cheers, > Moritz > > Footnotes: > [1] We''re well aware of the recent claims of a potential compromise of that > CA, but as of today this is still under investigation: > http://www.globalsign.com/company/press/090611-security-response.html_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Tobias Geiger
2011-Sep-14 16:14 UTC
Re: [Xen-devel] Signed GPLPV drivers available for download
Am Mittwoch, 14. September 2011, 18:03:04 schrieb Tobias Geiger:> - really better read-performance WITH gplpv, but much worse > write-performance: here is the performance without gplpv:well, after reviewing my own screenshots i declare even the readperformance gets worse after installing GPLPV drivers, not only the writeperformance... Any hints on that ?! i remember this not being the case with windows xp iirc... Greetings Tobias _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Pasi Kärkkäinen
2011-Sep-14 22:26 UTC
Re: [Xen-devel] Signed GPLPV drivers available for download
On Wed, Sep 14, 2011 at 06:14:28PM +0200, Tobias Geiger wrote:> Am Mittwoch, 14. September 2011, 18:03:04 schrieb Tobias Geiger: > > - really better read-performance WITH gplpv, but much worse > > write-performance: here is the performance without gplpv: > > well, after reviewing my own screenshots i declare even the readperformance > gets worse after installing GPLPV drivers, not only the writeperformance... > > Any hints on that ?! i remember this not being the case with windows xp > iirc... >Are your partitions aligned properly? if not, that''ll cause a big performance hit. -- Pasi _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Tobias Geiger
2011-Sep-14 23:10 UTC
Re: [Xen-devel] Signed GPLPV drivers available for download
Disk /dev/nbd0: 193.3 GB, 193273528320 bytes
255 heads, 63 sectors/track, 23497 cylinders, total 377487360 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x047328a3
Device Boot Start End Blocks Id System
/dev/nbd0p1 * 2048 206847 102400 7 HPFS/NTFS/exFAT
/dev/nbd0p2 206848 377485311 188639232 7 HPFS/NTFS/exFAT
seems to be proper aligned...
Am Donnerstag 15 September 2011, 00:26:41 schrieb Pasi
Kärkkäinen:> On Wed, Sep 14, 2011 at 06:14:28PM +0200, Tobias Geiger wrote:
> > Am Mittwoch, 14. September 2011, 18:03:04 schrieb Tobias Geiger:
> > > - really better read-performance WITH gplpv, but much worse
> >
> > > write-performance: here is the performance without gplpv:
> > well, after reviewing my own screenshots i declare even the
> > readperformance gets worse after installing GPLPV drivers, not only
the
> > writeperformance...
> >
> > Any hints on that ?! i remember this not being the case with windows
xp
> > iirc...
>
> Are your partitions aligned properly? if not, that''ll cause a big
> performance hit.
>
> -- Pasi
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Moritz Mühlenhoff wrote> > Hi, > for inclusion in Univention Corporate Server - a Linux distribution based > on > Debian targeted towards enterprise environments, which also includes Xen > for > virtualisation - we're now building/signing the excellent GPLPV drivers > written by James Harper with a Software Publishers Certificate obtained > from > GlobalSign. [1] > > This allows installation of the GPLPV drivers on 64 bit Windows without > the > need to enable the test mode. > > The drivers are available from > http://apt.univention.de/download/addons/gplpv- > drivers/ and should be compatible with any Xen installation. > > The installation is detailed in > http://wiki.univention.de/index.php?title=Installing-signed-GPLPV-drivers > > So far only new installation of the GPLPV drivers have been tested. We > welcome > general feedback and experiences with upgrades from test-signed versions > of > GPLPV. > > Cheers, > Moritz > > Footnotes: > [1] We're well aware of the recent claims of a potential compromise of > that > CA, but as of today this is still under investigation: > http://www.globalsign.com/company/press/090611-security-response.html > -- > Moritz Mühlenhoff muehlenhoff@ > Open Source Software Engineer and Consultant > Univention GmbH Linux for Your Business fon: +49 421 22 232- 0 > Mary-Somerville-Str.1 28359 Bremen fax: +49 421 22 232-99 > http://www.univention.de > > _______________________________________________ > Xen-devel mailing list > Xen-devel@.xensource > http://lists.xensource.com/xen-devel >A new build version (357) of GPLPV is available, do you plan to sign that too? Thanks for any reply. -- View this message in context: http://xen.1045712.n5.nabble.com/Signed-GPLPV-drivers-available-for-download-tp4785381p5595011.html Sent from the Xen - Dev mailing list archive at Nabble.com. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Teo En Ming (Zhang Enming)
2012-Mar-26 12:18 UTC
Re: Signed GPLPV drivers available for download
On 26/03/2012 19:57, Fantu wrote:> Moritz Mühlenhoff wrote >> Hi, >> for inclusion in Univention Corporate Server - a Linux distribution based >> on >> Debian targeted towards enterprise environments, which also includes Xen >> for >> virtualisation - we're now building/signing the excellent GPLPV drivers >> written by James Harper with a Software Publishers Certificate obtained >> from >> GlobalSign. [1] >> >> This allows installation of the GPLPV drivers on 64 bit Windows without >> the >> need to enable the test mode. >> >> The drivers are available from >> http://apt.univention.de/download/addons/gplpv- >> drivers/ and should be compatible with any Xen installation. >> >> The installation is detailed in >> http://wiki.univention.de/index.php?title=Installing-signed-GPLPV-drivers >> >> So far only new installation of the GPLPV drivers have been tested. We >> welcome >> general feedback and experiences with upgrades from test-signed versions >> of >> GPLPV. >> >> Cheers, >> Moritz >> >> Footnotes: >> [1] We're well aware of the recent claims of a potential compromise of >> that >> CA, but as of today this is still under investigation: >> http://www.globalsign.com/company/press/090611-security-response.html >> -- >> Moritz Mühlenhoff muehlenhoff@ >> Open Source Software Engineer and Consultant >> Univention GmbH Linux for Your Business fon: +49 421 22 232- 0 >> Mary-Somerville-Str.1 28359 Bremen fax: +49 421 22 232-99 >> http://www.univention.de >> >> _______________________________________________ >> Xen-devel mailing list >> Xen-devel@.xensource >> http://lists.xensource.com/xen-devel >> > A new build version (357) of GPLPV is available, do you plan to sign that > too? > Thanks for any reply. > > -- > View this message in context: http://xen.1045712.n5.nabble.com/Signed-GPLPV-drivers-available-for-download-tp4785381p5595011.html > Sent from the Xen - Dev mailing list archive at Nabble.com. > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-develHi, Are there any 64-bit GPLPV drivers for Windows 8 Consumer Preview? Thank you very much. -- Yours sincerely, Mr. Teo En Ming (Zhang Enming) Singapore _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Teo En Ming (Zhang Enming)
2012-Mar-26 12:18 UTC
Re: [Xen-devel] Signed GPLPV drivers available for download
On 26/03/2012 19:57, Fantu wrote:> Moritz Mühlenhoff wrote >> Hi, >> for inclusion in Univention Corporate Server - a Linux distribution based >> on >> Debian targeted towards enterprise environments, which also includes Xen >> for >> virtualisation - we're now building/signing the excellent GPLPV drivers >> written by James Harper with a Software Publishers Certificate obtained >> from >> GlobalSign. [1] >> >> This allows installation of the GPLPV drivers on 64 bit Windows without >> the >> need to enable the test mode. >> >> The drivers are available from >> http://apt.univention.de/download/addons/gplpv- >> drivers/ and should be compatible with any Xen installation. >> >> The installation is detailed in >> http://wiki.univention.de/index.php?title=Installing-signed-GPLPV-drivers >> >> So far only new installation of the GPLPV drivers have been tested. We >> welcome >> general feedback and experiences with upgrades from test-signed versions >> of >> GPLPV. >> >> Cheers, >> Moritz >> >> Footnotes: >> [1] We're well aware of the recent claims of a potential compromise of >> that >> CA, but as of today this is still under investigation: >> http://www.globalsign.com/company/press/090611-security-response.html >> -- >> Moritz Mühlenhoff muehlenhoff@ >> Open Source Software Engineer and Consultant >> Univention GmbH Linux for Your Business fon: +49 421 22 232- 0 >> Mary-Somerville-Str.1 28359 Bremen fax: +49 421 22 232-99 >> http://www.univention.de >> >> _______________________________________________ >> Xen-devel mailing list >> Xen-devel@.xensource >> http://lists.xensource.com/xen-devel >> > A new build version (357) of GPLPV is available, do you plan to sign that > too? > Thanks for any reply. > > -- > View this message in context: http://xen.1045712.n5.nabble.com/Signed-GPLPV-drivers-available-for-download-tp4785381p5595011.html > Sent from the Xen - Dev mailing list archive at Nabble.com. > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-develHi, Are there any 64-bit GPLPV drivers for Windows 8 Consumer Preview? Thank you very much. -- Yours sincerely, Mr. Teo En Ming (Zhang Enming) Singapore _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
> > Am Mittwoch, 14. September 2011, 18:03:04 schrieb Tobias Geiger: > > - really better read-performance WITH gplpv, but much worse > > write-performance: here is the performance without gplpv: > > well, after reviewing my own screenshots i declare even the > readperformance gets worse after installing GPLPV drivers, not only the > writeperformance... > > Any hints on that ?! i remember this not being the case with windows xp > iirc... >That is worrying. What backend are you using in Dom0? file or phy? James
Hi James! glad you ask - because just yesterday i re-tested the 357-version of the drivers under Windows7 64bit HVM guest - here are the results: (everyting in mb/s) W/O gplpv-drivers and WITH pci-passthrough: Seq. reading: 311.8 Seq. writing: 106.3 4k reading: 10.2 4k writing: 9.3 4k64thread reading: 11.1 4k64threads writing: 10.9 WITH gplpv-drivers and WITH pci-passthrough: Seq. reading: 98.8 Seq. writing: 31.6 4k reading: 12.0 4k writing: 19.3 4k64thread reading: 15.4 4k64threads writing: 29.6 WITH gplpv-drivers and WITHOUT pci-passthrough: Seq. reading: 104.4 Seq. writing: 85.2 4k reading: 12.7 4k writing: 20.4 4k64thread reading: 16.6 4k64threads writing: 32.6 Strange thing is, that even without pci-passthrough the performance with gplpv is''nt that much better compared to w/o gplpv but with pci-passthrough - well it is overall a bit better, but just a bit, and seq. read performance is much worse... i haven''t made a test without gplpv and without passthrough at the same time - tell me if you want to see how that performs. Greetings! Tobias P.S.: i''m using phy backend pointing to a LVM device on an SSD for this tests. Am Dienstag, 27. März 2012, 08:48:55 schrieb James Harper:> > Am Mittwoch, 14. September 2011, 18:03:04 schrieb Tobias Geiger: > > > - really better read-performance WITH gplpv, but much worse > > > > > write-performance: here is the performance without gplpv: > > well, after reviewing my own screenshots i declare even the > > readperformance gets worse after installing GPLPV drivers, not only the > > writeperformance... > > > > Any hints on that ?! i remember this not being the case with windows xp > > iirc... > > That is worrying. What backend are you using in Dom0? file or phy? > > James
Teo En Ming (Zhang Enming)
2012-Mar-27 11:01 UTC
Re: Signed GPLPV drivers available for download
On 26/03/2012 19:57, Fantu wrote:> Moritz Mühlenhoff wrote >> Hi, >> for inclusion in Univention Corporate Server - a Linux distribution based >> on >> Debian targeted towards enterprise environments, which also includes Xen >> for >> virtualisation - we're now building/signing the excellent GPLPV drivers >> written by James Harper with a Software Publishers Certificate obtained >> from >> GlobalSign. [1] >> >> This allows installation of the GPLPV drivers on 64 bit Windows without >> the >> need to enable the test mode. >> >> The drivers are available from >> http://apt.univention.de/download/addons/gplpv- >> drivers/ and should be compatible with any Xen installation. >> >> The installation is detailed in >> http://wiki.univention.de/index.php?title=Installing-signed-GPLPV-drivers >> >> So far only new installation of the GPLPV drivers have been tested. We >> welcome >> general feedback and experiences with upgrades from test-signed versions >> of >> GPLPV. >> >> Cheers, >> Moritz >> >> Footnotes: >> [1] We're well aware of the recent claims of a potential compromise of >> that >> CA, but as of today this is still under investigation: >> http://www.globalsign.com/company/press/090611-security-response.html >> -- >> Moritz Mühlenhoff muehlenhoff@ >> Open Source Software Engineer and Consultant >> Univention GmbH Linux for Your Business fon: +49 421 22 232- 0 >> Mary-Somerville-Str.1 28359 Bremen fax: +49 421 22 232-99 >> http://www.univention.de >> >> _______________________________________________ >> Xen-devel mailing list >> Xen-devel@.xensource >> http://lists.xensource.com/xen-devel >> > A new build version (357) of GPLPV is available, do you plan to sign that > too? > Thanks for any reply. > > -- > View this message in context: http://xen.1045712.n5.nabble.com/Signed-GPLPV-drivers-available-for-download-tp4785381p5595011.html > Sent from the Xen - Dev mailing list archive at Nabble.com. > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-develDon't have any Xen GPLPV drivers for Windows 8 Consumer Preview and Windows 7? -- Yours sincerely, Mr. Teo En Ming (Zhang Enming) Singapore _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Teo En Ming (Zhang Enming) wrote> > On 26/03/2012 19:57, Fantu wrote: >> Moritz Mühlenhoff wrote >>> Hi, >>> for inclusion in Univention Corporate Server - a Linux distribution >>> based >>> on >>> Debian targeted towards enterprise environments, which also includes Xen >>> for >>> virtualisation - we're now building/signing the excellent GPLPV drivers >>> written by James Harper with a Software Publishers Certificate obtained >>> from >>> GlobalSign. [1] >>> >>> This allows installation of the GPLPV drivers on 64 bit Windows without >>> the >>> need to enable the test mode. >>> >>> The drivers are available from >>> http://apt.univention.de/download/addons/gplpv- >>> drivers/ and should be compatible with any Xen installation. >>> >>> The installation is detailed in >>> http://wiki.univention.de/index.php?title=Installing-signed-GPLPV-drivers >>> >>> So far only new installation of the GPLPV drivers have been tested. We >>> welcome >>> general feedback and experiences with upgrades from test-signed versions >>> of >>> GPLPV. >>> >>> Cheers, >>> Moritz >>> >>> Footnotes: >>> [1] We're well aware of the recent claims of a potential compromise of >>> that >>> CA, but as of today this is still under investigation: >>> http://www.globalsign.com/company/press/090611-security-response.html >>> -- >>> Moritz Mühlenhoff muehlenhoff@ >>> Open Source Software Engineer and Consultant >>> Univention GmbH Linux for Your Business fon: +49 421 22 232- 0 >>> Mary-Somerville-Str.1 28359 Bremen fax: +49 421 22 232-99 >>> http://www.univention.de >>> >>> _______________________________________________ >>> Xen-devel mailing list >>> Xen-devel@.xensource >>> http://lists.xensource.com/xen-devel >>> >> A new build version (357) of GPLPV is available, do you plan to sign >> that >> too? >> Thanks for any reply. >> >> -- >> View this message in context: >> http://xen.1045712.n5.nabble.com/Signed-GPLPV-drivers-available-for-download-tp4785381p5595011.html >> Sent from the Xen - Dev mailing list archive at Nabble.com. >> >> _______________________________________________ >> Xen-devel mailing list >> Xen-devel@.xen >> http://lists.xen.org/xen-devel > > Don't have any Xen GPLPV drivers for Windows 8 Consumer Preview and > Windows 7? > > -- > Yours sincerely, > > Mr. Teo En Ming (Zhang Enming) > Singapore > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@.xen > http://lists.xen.org/xen-devel >For windows 7 there are already, the "vista" build, I tested and know working build version 238 and 308 on windows 7 pro 64 bit mainly systems on dom0 Squeeze with kernel pvops and xen 4.0.x. The only problem found for now is shutdown monitor service not installed on some cause unknown. About windows 8 not tested for now. Sorry for bad english. -- View this message in context: http://xen.1045712.n5.nabble.com/Signed-GPLPV-drivers-available-for-download-tp4785381p5599609.html Sent from the Xen - Dev mailing list archive at Nabble.com. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Teo En Ming (Zhang Enming)
2012-Mar-29 15:09 UTC
Re: Signed GPLPV drivers available for download
On 28/03/2012 14:08, Fantu wrote:> Teo En Ming (Zhang Enming) wrote >> On 26/03/2012 19:57, Fantu wrote: >>> Moritz Mühlenhoff wrote >>>> Hi, >>>> for inclusion in Univention Corporate Server - a Linux distribution >>>> based >>>> on >>>> Debian targeted towards enterprise environments, which also includes Xen >>>> for >>>> virtualisation - we're now building/signing the excellent GPLPV drivers >>>> written by James Harper with a Software Publishers Certificate obtained >>>> from >>>> GlobalSign. [1] >>>> >>>> This allows installation of the GPLPV drivers on 64 bit Windows without >>>> the >>>> need to enable the test mode. >>>> >>>> The drivers are available from >>>> http://apt.univention.de/download/addons/gplpv- >>>> drivers/ and should be compatible with any Xen installation. >>>> >>>> The installation is detailed in >>>> http://wiki.univention.de/index.php?title=Installing-signed-GPLPV-drivers >>>> >>>> So far only new installation of the GPLPV drivers have been tested. We >>>> welcome >>>> general feedback and experiences with upgrades from test-signed versions >>>> of >>>> GPLPV. >>>> >>>> Cheers, >>>> Moritz >>>> >>>> Footnotes: >>>> [1] We're well aware of the recent claims of a potential compromise of >>>> that >>>> CA, but as of today this is still under investigation: >>>> http://www.globalsign.com/company/press/090611-security-response.html >>>> -- >>>> Moritz Mühlenhoff muehlenhoff@ >>>> Open Source Software Engineer and Consultant >>>> Univention GmbH Linux for Your Business fon: +49 421 22 232- 0 >>>> Mary-Somerville-Str.1 28359 Bremen fax: +49 421 22 232-99 >>>> http://www.univention.de >>>> >>>> _______________________________________________ >>>> Xen-devel mailing list >>>> Xen-devel@.xensource >>>> http://lists.xensource.com/xen-devel >>>> >>> A new build version (357) of GPLPV is available, do you plan to sign >>> that >>> too? >>> Thanks for any reply. >>> >>> -- >>> View this message in context: >>> http://xen.1045712.n5.nabble.com/Signed-GPLPV-drivers-available-for-download-tp4785381p5595011.html >>> Sent from the Xen - Dev mailing list archive at Nabble.com. >>> >>> _______________________________________________ >>> Xen-devel mailing list >>> Xen-devel@.xen >>> http://lists.xen.org/xen-devel >> Don't have any Xen GPLPV drivers for Windows 8 Consumer Preview and >> Windows 7? >> >> -- >> Yours sincerely, >> >> Mr. Teo En Ming (Zhang Enming) >> Singapore >> >> >> _______________________________________________ >> Xen-devel mailing list >> Xen-devel@.xen >> http://lists.xen.org/xen-devel >> > For windows 7 there are already, the "vista" build, I tested and know > working build version 238 and 308 on windows 7 pro 64 bit mainly systems on > dom0 Squeeze with kernel pvops and xen 4.0.x. > The only problem found for now is shutdown monitor service not installed on > some cause unknown. > About windows 8 not tested for now. > Sorry for bad english. > > -- > View this message in context: http://xen.1045712.n5.nabble.com/Signed-GPLPV-drivers-available-for-download-tp4785381p5599609.html > Sent from the Xen - Dev mailing list archive at Nabble.com. > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-develDear Fantu, Thank you very much for your reply. I will be waiting for Xen GPLPV drivers for Windows 8. -- Yours sincerely, Mr. Teo En Ming (Zhang Enming) Singapore _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Teo En Ming (Zhang Enming)
2012-Mar-29 15:12 UTC
Re: Signed GPLPV drivers available for download
Dear Andrew Lyon, Thank you for your reply. I will be trying Xen GPLPV drivers for Windows Vista on my Windows 8 Consumer Preview HVM domU. -- Yours sincerely, Mr. Teo En Ming (Zhang Enming) Singapore On 28/03/2012 19:31, Andrew Lyon wrote:> Apologies for top posting but I''m using a mobile device, have you > tried using the vista drivers? I don''t think the driver model has > changed much between vista>7>8 so they should work. > > Andy > > On 27/03/2012, Teo En Ming (Zhang Enming) > <singapore.mr.teo.en.ming@gmail.com> wrote: >> On 26/03/2012 19:57, Fantu wrote: >>> Moritz Mühlenhoff wrote >>>> Hi, >>>> for inclusion in Univention Corporate Server - a Linux distribution based >>>> on >>>> Debian targeted towards enterprise environments, which also includes Xen >>>> for >>>> virtualisation - we''re now building/signing the excellent GPLPV drivers >>>> written by James Harper with a Software Publishers Certificate obtained >>>> from >>>> GlobalSign. [1] >>>> >>>> This allows installation of the GPLPV drivers on 64 bit Windows without >>>> the >>>> need to enable the test mode. >>>> >>>> The drivers are available from >>>> http://apt.univention.de/download/addons/gplpv- >>>> drivers/ and should be compatible with any Xen installation. >>>> >>>> The installation is detailed in >>>> http://wiki.univention.de/index.php?title=Installing-signed-GPLPV-drivers >>>> >>>> So far only new installation of the GPLPV drivers have been tested. We >>>> welcome >>>> general feedback and experiences with upgrades from test-signed versions >>>> of >>>> GPLPV. >>>> >>>> Cheers, >>>> Moritz >>>> >>>> Footnotes: >>>> [1] We''re well aware of the recent claims of a potential compromise of >>>> that >>>> CA, but as of today this is still under investigation: >>>> http://www.globalsign.com/company/press/090611-security-response.html >>>> -- >>>> Moritz Mühlenhoff muehlenhoff@ >>>> Open Source Software Engineer and Consultant >>>> Univention GmbH Linux for Your Business fon: +49 421 22 232- 0 >>>> Mary-Somerville-Str.1 28359 Bremen fax: +49 421 22 232-99 >>>> http://www.univention.de >>>> >>>> _______________________________________________ >>>> Xen-devel mailing list >>>> Xen-devel@.xensource >>>> http://lists.xensource.com/xen-devel >>>> >>> A new build version (357) of GPLPV is available, do you plan to sign that >>> too? >>> Thanks for any reply. >>> >>> -- >>> View this message in context: >>> http://xen.1045712.n5.nabble.com/Signed-GPLPV-drivers-available-for-download-tp4785381p5595011.html >>> Sent from the Xen - Dev mailing list archive at Nabble.com. >>> >>> _______________________________________________ >>> Xen-devel mailing list >>> Xen-devel@lists.xen.org >>> http://lists.xen.org/xen-devel >> Don''t have any Xen GPLPV drivers for Windows 8 Consumer Preview and >> Windows 7? >> >> -- >> Yours sincerely, >> >> Mr. Teo En Ming (Zhang Enming) >> Singapore >> >> >> _______________________________________________ >> Xen-devel mailing list >> Xen-devel@lists.xen.org >> http://lists.xen.org/xen-devel >>
> Dear Fantu, > > Thank you very much for your reply. I will be waiting for Xen GPLPV drivers > for Windows 8. >The current Vista/2008 drivers should work under Windows 8 although I haven''t tested them. I''ve got separate drivers for 2000, XP, 2003, and Vista/2008 because there are a few different features for those versions of the OS. 7/2008R2 has new networking features (NDIS6.2 or whatever version) but I''m not using those so the Vista/2008 drivers work just fine. If I ever need to support newer features I''ll do a new specific build but until then it should work as is. I am interested in hearing reports of anyone testing with Windows 8. James
Teo En Ming (Zhang Enming)
2012-Mar-30 04:08 UTC
Re: Signed GPLPV drivers available for download
On 30/03/2012 07:08, James Harper wrote:>> Dear Fantu, >> >> Thank you very much for your reply. I will be waiting for Xen GPLPV drivers >> for Windows 8. >> > The current Vista/2008 drivers should work under Windows 8 although I haven''t tested them. > > I''ve got separate drivers for 2000, XP, 2003, and Vista/2008 because there are a few different features for those versions of the OS. 7/2008R2 has new networking features (NDIS6.2 or whatever version) but I''m not using those so the Vista/2008 drivers work just fine. If I ever need to support newer features I''ll do a new specific build but until then it should work as is. > > I am interested in hearing reports of anyone testing with Windows 8. > > JamesDear James Harper, I will be testing with Windows 8 soon. Thank you very much. -- Yours sincerely, Mr. Teo En Ming (Zhang Enming) Singapore
> > glad you ask - because just yesterday i re-tested the 357-version of the > drivers under Windows7 64bit HVM guest - here are the results: > > (everyting in mb/s) > > W/O gplpv-drivers and WITH pci-passthrough: > > Seq. reading: 311.8 > Seq. writing: 106.3 > 4k reading: 10.2 > 4k writing: 9.3 > 4k64thread reading: 11.1 > 4k64threads writing: 10.9 > > > WITH gplpv-drivers and WITH pci-passthrough: > > Seq. reading: 98.8 > Seq. writing: 31.6 > 4k reading: 12.0 > 4k writing: 19.3 > 4k64thread reading: 15.4 > 4k64threads writing: 29.6 > > > WITH gplpv-drivers and WITHOUT pci-passthrough: > > Seq. reading: 104.4 > Seq. writing: 85.2 > 4k reading: 12.7 > 4k writing: 20.4 > 4k64thread reading: 16.6 > 4k64threads writing: 32.6 > > > Strange thing is, that even without pci-passthrough the performance with > gplpv is''nt that much better compared to w/o gplpv but with pci-passthrough > - well it is overall a bit better, but just a bit, and seq. read performance is > much worse... > i haven''t made a test without gplpv and without passthrough at the same > time - tell me if you want to see how that performs. > > Greetings! > Tobias > > P.S.: i''m using phy backend pointing to a LVM device on an SSD for this tests. >What are you testing this with? I just ran some tests with iometer under 2008R2 and it reminded me of something... DRBD *hates* having outstanding writes to the same block, and complains about it, so gplpv serialises such requests (stalling the queue until the first request is complete). This almost never happens in production but iometer sends such requests frequently, which will significantly impact performance. You can test with the debug build to see if this is happening with whatever you are testing with - you''ll see messages like "Concurrent outstanding write detected". Be aware though that qemu will rate limit writes to the debug log so if it happens a lot (like under iometer) it will slow to a crawl. James
2012/4/6 James Harper <james.harper@bendigoit.com.au>:> > What are you testing this with? I just ran some tests with iometer under 2008R2 and it reminded me of something... DRBD *hates* having outstanding writes to the same block, and complains about it, so gplpv serialises such requests (stalling the queue until the first request is complete). This almost never happens in production but iometer sends such requests frequently, which will significantly impact performance. > > You can test with the debug build to see if this is happening with whatever you are testing with - you''ll see messages like "Concurrent outstanding write detected". Be aware though that qemu will rate limit writes to the debug log so if it happens a lot (like under iometer) it will slow to a crawl. > > James >Sorry, but i have another problem with disk write when use gplpv: I''m create simple winpe windows installer with windows aik and integrate into it xen gpl pv drivers. Sometimes i can''t install windows to hard drive. Windows syas, that hard disk not properly configured in bios or not able to boot from it. Disk is the phisical device, domU config: kernel=''hvmloader'' builder=''hvm'' memory=1024 name="21-706" vcpus=4 vif="mac=00:16:3e:00:17:b9,ip=62.76.47.68,type=paravirtualised" disk="file:/var/storage/iso/SW_DVD5_Windows_Svr_DC_EE_SE_Web_2008_R2_64Bit_Russian_w_SP1_MLF_X17-22616_vase.iso,hdc:cdrom,r" disk="phy:/dev/disk/vbd/21-1206,hda,w" device_model=''qemu-dm'' boot=''c'' vnc=1 vncpasswd=''uRFCg8oPkD'' serial=''pty'' usbdevice=''tablet'' keymap=''en-us'' boot=''d'' -p disk="file:/var/storage/iso/winpe_amd64.iso,hdb:cdrom,r" on_reboot=destroy on_poweroff=destroy on_crash=destroy qemu-dm log conains this messages: domid: 1155 Using file /var/storage/iso/SW_DVD5_Windows_Svr_DC_EE_SE_Web_2008_R2_64Bit_Russian_w_SP1_MLF_X17-22616_vase.iso in read-only mode Using file /dev/disk/vbd/21-1206 in read-write mode Using file /var/storage/iso/winpe_amd64.iso in read-only mode Watching /local/domain/0/device-model/1155/logdirty/cmd Watching /local/domain/0/device-model/1155/command char device redirected to /dev/pts/59 qemu_map_cache_init nr_buckets = 10000 size 4194304 /usr/src/packages/BUILD/xen-4.0.1-testing/tools/ioemu-dir/hw/xen_blktap.c:704: Init blktap pipes shared page at pfn feffd buffered io page at pfn feffb Guest uuid = 64ebb4f3-827b-4bbd-3ada-358b66e61a95 Time offset set 0 populating video RAM at ff000000 mapping video RAM from ff000000 Register xen platform. Done register platform. platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. xs_read(/local/domain/0/device-model/1155/xen_extended_power_mgmt): read error medium change watch on `hdc'' (index: 0): /var/storage/iso/SW_DVD5_Windows_Svr_DC_EE_SE_Web_2008_R2_64Bit_Russian_w_SP1_MLF_X17-22616_vase.iso I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 medium change watch on `hdb'' (index: 2): /var/storage/iso/winpe_amd64.iso I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 Log-dirty: no command yet. I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 xs_read(/local/domain/1155/log-throttling): read error qemu: ignoring not-understood drive `/local/domain/1155/log-throttling'' medium change watch on `/local/domain/1155/log-throttling'' - unknown device, ignored log_throttling disabled qemu: ignoring not-understood drive `/local/domain/1155/log-throttling'' medium change watch on `/local/domain/1155/log-throttling'' - unknown device, ignored cirrus vga map change while on lfb mode mapping vram to f0000000 - f0400000 platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro state. 12974973492593: XenPCI --> XenPci_InitialBalloonDown 12974973492593: XenPCI base = 0x40000000, Xen Signature XenVMMXenVMM, EAX = 0x40000003 12974973492593: XenPCI Xen Version 4.0 12974973492593: XenPCI Hypercall area at FFFFFA80010B7000 12974973492593: XenPCI XENMEM_maximum_reservation = 263168 12974973492593: XenPCI XENMEM_current_reservation = 263160 12974973492593: XenPCI Trying to give 32 KB (0 MB) to Xen 12974973492609: XenPCI <-- XenPci_InitialBalloonDown 12974973492609: XenPCI KeInitializeCrashDumpHeader status 00000000, size = 8192 12974973492609: XenPCI GPLPV 0.10.0.357 12974973492609: XenPCI --> XenPci_FixLoadOrder 12974973492609: XenPCI dummy_group_index = -1 12974973492609: XenPCI wdf_load_group_index = 2 12974973492609: XenPCI xenpci_group_index = -1 12974973492609: XenPCI boot_bus_extender_index = 3 12974973492609: XenPCI <-- XenPci_FixLoadOrder 12974973492609: XenPCI SystemStartOptions = MININT REDIRECT RDIMAGEOFFSET=8192 RDIMAGELENGTH=3161088 RDPATH=MULTI(0)DISK(0)CDROM(0)\SOURCES\BOOT.WIM 12974973492625: XenPCI Version = 1 Unknown PV product 2 loaded in guest PV driver build 1 12974973492625: XenPCI Disabled qemu devices 01 12974973492625: XenPCI <-- DriverEntry 12974973492625: XenPCI Xen PCI device found - must be fdo 12974973492625: XenPCI --> XenPci_EvtDeviceAdd_XenPci 12974973492625: XenPCI <-- XenPci_EvtDeviceAdd_XenPci 12974973492640: XenPCI --> XenPci_EvtDevicePrepareHardware 12974973492640: XenPCI IoPort Address(c000) Length: 256 12974973492640: XenPCI Private Data: 0x01 0x00 0x00 12974973492640: XenPCI Memory mapped CSR:(f2000000:0) Length:(16777216) 12974973492640: XenPCI Memory flags = 0084 12974973492640: XenPCI Private Data: 0x01 0x01 0x00 12974973492640: XenPCI irq_number = 01c 12974973492640: XenPCI irq_vector = 0a2 12974973492640: XenPCI irq_level = 00a 12974973492640: XenPCI irq_mode = LevelSensitive 12974973492656: XenPCI ShareDisposition = CmResourceShareShared 12974973492656: XenPCI <-- XenPci_EvtDevicePrepareHardware 12974973492656: XenPCI --> XenPci_EvtDeviceD0Entry 12974973492656: XenPCI WdfPowerDeviceD3Final 12974973492656: XenPCI --> XenPci_Init 12974973492656: XenPCI base = 0x40000000, Xen Signature XenVMMXenVMM, EAX = 0x40000003 12974973492656: XenPCI Xen Version 4.0 12974973492656: XenPCI Hypercall area at FFFFFA80011BD000 12974973492656: XenPCI shared_info_area_unmapped.QuadPart = f2000000 12974973492656: XenPCI gpfn = f2000 12974973492656: XenPCI hypervisor memory op (XENMAPSPACE_shared_info) ret = 0 12974973492671: XenPCI <-- XenPci_Init 12974973492671: XenPCI --> GntTbl_Init 12974973492671: XenPCI grant_frames = 32 12974973492671: XenPCI grant_entries = 16384 12974973492671: XenPCI pfn = 3fa1e 12974973492671: XenPCI Calling HYPERVISOR_memory_op - pfn = 3fa1e 12974973492671: XenPCI decreased 1 pages for grant table frame 0 12974973492671: XenPCI pfn = 3fa1f 12974973492671: XenPCI Calling HYPERVISOR_memory_op - pfn = 3fa1f 12974973492671: XenPCI decreased 1 pages for grant table frame 1 12974973492671: XenPCI pfn = 3fa20 12974973492671: XenPCI Calling HYPERVISOR_memory_op - pfn = 3fa20 12974973492687: XenPCI decreased 1 pages for grant table frame 2 12974973492687: XenPCI pfn = 3fa21 12974973492687: XenPCI Calling HYPERVISOR_memory_op - pfn = 3fa21 12974973492687: XenPCI decreased 1 pages for grant table frame 3 12974973492687: XenPCI pfn = 3fa22 12974973492687: XenPCI Calling HYPERVISOR_memory_op - pfn = 3fa22 12974973492687: XenPCI decreased 1 pages for grant table frame 4 12974973492687: XenPCI pfn = 3fa23 12974973492687: XenPCI Calling HYPERVISOR_memory_op - pfn = 3fa23 12974973492703: XenPCI decreased 1 pages for grant table frame 5 12974973492703: XenPCI pfn = 3fa24 12974973492703: XenPCI Calling HYPERVISOR_memory_op - pfn = 3fa24 12974973492703: XenPCI decreased 1 pages for grant table frame 6 12974973492703: XenPCI pfn = 3fa25 12974973492703: XenPCI Calling HYPERVISOR_memory_op - pfn = 3fa25 12974973492703: XenPCI decreased 1 pages for grant table frame 7 12974973492718: XenPCI pfn = 3fa26 12974973492718: XenPCI Calling HYPERVISOR_memory_op - pfn = 3fa26 12974973492718: XenPCI decreased 1 pages for grant table frame 8 12974973492718: XenPCI pfn = 3fa27 12974973492718: XenPCI Calling HYPERVISOR_memory_op - pfn = 3fa27 12974973492718: XenPCI decreased 1 pages for grant table frame 9 12974973492718: XenPCI pfn = 3fa28 12974973492718: XenPCI Calling HYPERVISOR_memory_op - pfn = 3fa28 12974973492718: XenPCI decreased 1 pages for grant table frame 10 12974973492734: XenPCI pfn = 3fa29 12974973492734: XenPCI Calling HYPERVISOR_memory_op - pfn = 3fa29 12974973492734: XenPCI decreased 1 pages for grant table frame 11 12974973492734: XenPCI pfn = 3fa2a 12974973492734: XenPCI Calling HYPERVISOR_memory_op - pfn = 3fa2a 12974973492734: XenPCI decreased 1 pages for grant table frame 12 12974973492734: XenPCI pfn = 3fa2b 12974973492734: XenPCI Calling HYPERVISOR_memory_op - pfn = 3fa2b 12974973492750: XenPCI decreased 1 pages for grant table frame 13 12974973492750: XenPCI pfn = 3fa2c 12974973492750: XenPCI Calling HYPERVISOR_memory_op - pfn = 3fa2c 12974973492750: XenPCI decreased 1 pages for grant table frame 14 12974973492750: XenPCI pfn = 3fa2d 12974973492750: XenPCI Calling HYPERVISOR_memory_op - pfn = 3fa2d 12974973492750: XenPCI decreased 1 pages for grant table frame 15 12974973492750: XenPCI pfn = 3fa2e 12974973492750: XenPCI Calling HYPERVISOR_memory_op - pfn = 3fa2e 12974973492765: XenPCI decreased 1 pages for grant table frame 16 12974973492765: XenPCI pfn = 3fa2f 12974973492765: XenPCI Calling HYPERVISOR_memory_op - pfn = 3fa2f 12974973492765: XenPCI decreased 1 pages for grant table frame 17 12974973492765: XenPCI pfn = 3fa30 12974973492765: XenPCI Calling HYPERVISOR_memory_op - pfn = 3fa30 12974973492765: XenPCI decreased 1 pages for grant table frame 18 12974973492765: XenPCI pfn = 3fa31 12974973492765: XenPCI Calling HYPERVISOR_memory_op - pfn = 3fa31 12974973492765: XenPCI decreased 1 pages for grant table frame 19 12974973492781: XenPCI pfn = 3fa32 12974973492781: XenPCI Calling HYPERVISOR_memory_op - pfn = 3fa32 12974973492781: XenPCI decreased 1 pages for grant table frame 20 12974973492781: XenPCI pfn = 3fa33 12974973492781: XenPCI Calling HYPERVISOR_memory_op - pfn = 3fa33 12974973492781: XenPCI decreased 1 pages for grant table frame 21 12974973492781: XenPCI pfn = 3fa34 12974973492781: XenPCI Calling HYPERVISOR_memory_op - pfn = 3fa34 12974973492796: XenPCI decreased 1 pages for grant table frame 22 12974973492796: XenPCI pfn = 3fa35 12974973492796: XenPCI Calling HYPERVISOR_memory_op - pfn = 3fa35 12974973492796: XenPCI decreased 1 pages for grant table frame 23 12974973492796: XenPCI pfn = 3fa36 12974973492796: XenPCI Calling HYPERVISOR_memory_op - pfn = 3fa36 12974973492796: XenPCI decreased 1 pages for grant table frame 24 12974973492796: XenPCI pfn = 3fa37 12974973492812: XenPCI Calling HYPERVISOR_memory_op - pfn = 3fa37 12974973492812: XenPCI decreased 1 pages for grant table frame 25 12974973492812: XenPCI pfn = 3fa38 12974973492812: XenPCI Calling HYPERVISOR_memory_op - pfn = 3fa38 12974973492812: XenPCI decreased 1 pages for grant table frame 26 12974973492812: XenPCI pfn = 3fa39 12974973492812: XenPCI Calling HYPERVISOR_memory_op - pfn = 3fa39 12974973492812: XenPCI decreased 1 pages for grant table frame 27 12974973492812: XenPCI pfn = 3fa3a 12974973492812: XenPCI Calling HYPERVISOR_memory_op - pfn = 3fa3a 12974973492828: XenPCI decreased 1 pages for grant table frame 28 12974973492828: XenPCI pfn = 3fa3b 12974973492828: XenPCI Calling HYPERVISOR_memory_op - pfn = 3fa3b 12974973492828: XenPCI decreased 1 pages for grant table frame 29 12974973492828: XenPCI pfn = 3fa3c 12974973492828: XenPCI Calling HYPERVISOR_memory_op - pfn = 3fa3c 12974973492828: XenPCI decreased 1 pages for grant table frame 30 12974973492828: XenPCI pfn = 3fa3d 12974973492843: XenPCI Calling HYPERVISOR_memory_op - pfn = 3fa3d 12974973492843: XenPCI decreased 1 pages for grant table frame 31 12974973492859: XenPCI --> GntTbl_Map 12974973492875: XenPCI <-- GntTbl_Map 12974973492875: XenPCI <-- GntTbl_Init 12974973492875: XenPCI --> EvtChn_Init 12974973492875: XenPCI --> _hvm_set_parameter 12974973492890: XenPCI HYPERVISOR_hvm_op retval = 0 12974973492890: XenPCI <-- _hvm_set_parameter 12974973492890: XenPCI hvm_set_parameter(HVM_PARAM_CALLBACK_IRQ, 28) = 0 12974973492890: XenPCI --> EvtChn_AllocIpi 12974973492890: XenPCI <-- EvtChn_AllocIpi 12974973492890: XenPCI --> EvtChn_BindDpc 12974973492890: XenPCI <-- EvtChn_BindDpc 12974973492890: XenPCI pdo_event_channel = 7 12974973492890: XenPCI <-- EvtChn_Init 12974973492890: XenPCI <-- XenPci_EvtDeviceD0Entry 12974973492890: XenPCI --> EvtChn_EvtInterruptEnable 12974973492890: XenPCI <-- EvtChn_EvtInterruptEnable 12974973492906: XenPCI --> XenPci_EvtDeviceD0EntryPostInterruptsEnabled 12974973492906: XenPCI --> XenBus_Init 12974973492906: XenPCI --> _hvm_get_parameter 12974973492906: XenPCI HYPERVISOR_hvm_op retval = 0 12974973492906: XenPCI <-- _hvm_get_parameter 12974973492906: XenPCI --> _hvm_get_parameter 12974973492906: XenPCI HYPERVISOR_hvm_op retval = 0 12974973492906: XenPCI <-- _hvm_get_parameter 12974973492906: XenPCI --> EvtChn_BindDpc 12974973492906: XenPCI <-- EvtChn_BindDpc 12974973492906: XenPCI <-- XenBus_Init 12974973492906: XenPCI suspend event channel = 8 12974973492906: XenPCI --> EvtChn_BindDpc 12974973492906: XenPCI <-- EvtChn_BindDpc 12974973492906: XenPCI --> XenPci_SysrqHandler 12974973492906: XenPCI SysRq Value = (null) 12974973492921: XenPCI <-- XenPci_SysrqHandler 12974973492921: XenPCI --> XenPci_ShutdownHandler 12974973492921: XenPCI Initial Memory Value = 1048576 (1048576) 12974973492953: Error reading shutdown path - ENOENT 12974973492953: XenPCI <-- XenPci_ShutdownHandler 12974973492953: XenPCI --> XenPci_BalloonThreadProc 12974973492953: XenPCI --> XenPci_DeviceWatchHandler 12974973492953: XenPCI low_mem_event = FFFFFA8000C865C0, state = 0 12974973492953: XenPCI <-- XenPci_DeviceWatchHandler 12974973492953: XenPCI <-- XenPci_EvtDeviceD0EntryPostInterruptsEnabled 12974973492953: XenPCI --> XenPci_BalloonHandler 12974973492953: XenPCI --> XenPci_EvtChildListScanForChildren 12974973492953: XenPCI target memory value = 1048576 (1048576) 12974973492953: XenPCI Found path = device/vfb/0 12974973492953: XenPCI Got balloon event, current = 1048576, target = 1048576 12974973492968: XenPCI Found path = device/vbd/5632 12974973492968: XenPCI No change to memory 12974973492968: XenPCI <-- XenPci_BalloonHandler 12974973492968: XenPCI Found path = device/vbd/768 12974973492968: XenPCI Found path = device/vbd/832 12974973492968: XenPCI Found path = device/vif/0 12974973492968: XenPCI Found path = device/suspend/event-channel 12974973492968: XenPCI <-- XenPci_EvtChildListScanForChildren 12974973492968: XenPCI --> XenPci_EvtChildListCreateDevice 12974973492968: XenPCI device = ''vfb'', index = ''0'', path = ''device/vfb/0'' 12974973492968: XenPCI <-- XenPci_EvtChildListCreateDevice 12974973492968: XenPCI --> XenPci_EvtChildListCreateDevice 12974973492984: XenPCI device = ''vbd'', index = ''5632'', path ''device/vbd/5632'' 12974973492984: XenPCI <-- XenPci_EvtChildListCreateDevice 12974973492984: XenPCI --> XenPci_EvtChildListCreateDevice 12974973492984: XenPCI device = ''vbd'', index = ''768'', path ''device/vbd/768'' 12974973492984: XenPCI <-- XenPci_EvtChildListCreateDevice 12974973492984: XenPCI --> XenPci_EvtChildListCreateDevice 12974973492984: XenPCI device = ''vbd'', index = ''832'', path ''device/vbd/832'' 12974973492984: XenPCI <-- XenPci_EvtChildListCreateDevice 12974973492984: XenPCI --> XenPci_EvtChildListCreateDevice 12974973492984: XenPCI device = ''vif'', index = ''0'', path = ''device/vif/0'' 12974973492984: XenPCI <-- XenPci_EvtChildListCreateDevice 12974973492984: XenPCI --> XenPci_EvtChildListCreateDevice 12974973493000: XenPCI device = ''suspend'', index = ''0'', path ''device/suspend/event-channel'' 12974973493000: XenPCI <-- XenPci_EvtChildListCreateDevice 12974973503046: XenPCI --> XenPciPdo_EvtDeviceWdmIrpPreprocess_START_DEVICE 12974973503046: XenPCI device/vbd/5632 12974973503046: XenPCI CmResourceTypeMemory (0) 12974973503046: XenPCI Start = f2000000, Length = 0 12974973503046: XenPCI pfn[0] = 0001b0ac 12974973503046: XenPCI New Start = 000000001b0ac000, Length = 4096 12974973503046: XenPCI CmResourceTypeMemory (1) 12974973503046: XenPCI Start = f2000001, Length = 0 12974973503046: XenPCI <-- XenPciPdo_EvtDeviceWdmIrpPreprocess_START_DEVICE 12974973503046: XenPCI --> XenPciPdo_EvtDevicePrepareHardware 12974973503046: XenPCI <-- XenPciPdo_EvtDevicePrepareHardware 12974973503046: XenPCI --> XenPciPdo_EvtDeviceD0Entry 12974973503062: XenPCI path = device/vbd/5632 12974973503062: XenPCI WdfPowerDeviceD3Final 12974973503062: XenPCI --> XenPci_GetBackendAndAddWatch 12974973503062: XenPCI <-- XenPci_GetBackendAndAddWatch 12974973503062: XenPCI --> XenPci_UpdateBackendState 12974973503078: XenPCI --> XenConfig_InitConfigPage 12974973503078: XenPCI Backend State Changed to InitWait 12974973503078: XenPCI fdo_driver_object = FFFFFA8000CFB8A0 12974973503078: XenPCI <-- XenPci_UpdateBackendState 12974973503078: XenPCI fdo_driver_extension = 0000000000000000 12974973503078: XenPCI fdo_driver_object = FFFFFA8000F93DE0 12974973503078: XenPCI fdo_driver_extension = 0000000000000000 12974973503078: XenPCI <-- XenConfig_InitConfigPage 12974973503078: XenPCI --> XenPci_XenConfigDeviceSpecifyBuffers 12974973503078: XenPCI --> XenPci_ChangeFrontendStateMap 12974973503093: XenPCI <-- XenPci_ChangeFrontendStateMap 12974973503093: XenPCI --> XenPci_ChangeFrontendStateMap 12974973503093: XenPCI <-- XenPci_ChangeFrontendStateMap 12974973503093: XenPCI <-- XenPci_XenConfigDeviceSpecifyBuffers 12974973503093: XenPCI <-- XenPciPdo_EvtDeviceD0Entry 12974973503093: XenVbd --> XenVbd_VirtualHwStorFindAdapter 12974973503093: XenVbd IRQL = 0 12974973503093: XenVbd xvdd = FFFFFA80013C8008 12974973503093: XenVbd BusInterruptLevel = 28 12974973503093: XenVbd BusInterruptVector = 01c 12974973503093: XenVbd NumberOfAccessRanges = 1 12974973503093: XenVbd RangeStart = 1b0ac000, RangeLength = 00001000 12974973503093: XenVbd --> XenVbd_InitConfig 12974973503109: XenVbd XEN_INIT_TYPE_13 12974973503109: XenVbd XEN_INIT_TYPE_VECTORS 12974973503109: XenVbd XEN_INIT_TYPE_11 12974973503109: XenVbd XEN_INIT_TYPE_17 12974973503109: XenPCI --> XenPci_XenConfigDeviceSpecifyBuffers 12974973503109: XenPCI XEN_INIT_TYPE_RING - ring-ref = FFFFFA80013D7000 12974973503109: XenPCI XEN_INIT_TYPE_RING - ring-ref = 16383 12974973503109: XenPCI XEN_INIT_TYPE_EVENT_CHANNEL - event-channel = 9 12974973503109: XenPCI --> XenPci_DeviceWatchHandler 12974973503109: XenPCI --> EvtChn_BindDpc 12974973503109: XenPCI <-- XenPci_DeviceWatchHandler 12974973503125: XenPCI <-- EvtChn_BindDpc 12974973503125: XenPCI --> XenPci_DeviceWatchHandler 12974973503125: XenPCI --> XenPci_ChangeFrontendStateMap 12974973503125: XenPCI <-- XenPci_DeviceWatchHandler 12974973503125: XenPCI --> XenPci_ChangeFrontendState 12974973503125: XenPCI --> XenPci_DeviceWatchHandler 12974973503125: XenPCI <-- XenPci_DeviceWatchHandler 12974973503125: XenPCI --> XenPci_UpdateBackendState 12974973503140: XenPCI Backend State Changed to Connected 12974973503140: XenPCI <-- XenPci_UpdateBackendState 12974973503140: XenPCI <-- XenPci_ChangeFrontendState 12974973503140: XenPCI <-- XenPci_ChangeFrontendStateMap 12974973503140: XenPCI --> XenPci_ChangeFrontendStateMap 12974973503140: XenPCI --> XenPci_ChangeFrontendState 12974973503140: XenPCI <-- XenPci_ChangeFrontendState 12974973503140: XenPCI --> XenPci_DeviceWatchHandler 12974973503156: XenPCI <-- XenPci_ChangeFrontendStateMap 12974973503156: XenPCI <-- XenPci_DeviceWatchHandler 12974973503156: XenPCI <-- XenPci_XenConfigDeviceSpecifyBuffers 12974973503156: XenVbd <-- XenVbd_InitConfig 12974973503156: XenVbd --> XenVbd_InitFromConfig 12974973503156: XenVbd XEN_INIT_TYPE_VECTORS 12974973503156: XenVbd XEN_INIT_TYPE_DEVICE_STATE - 00000000013795D0 12974973503156: XenVbd XEN_INIT_TYPE_RING - ring-ref = FFFFFA80013D7000 12974973503156: XenVbd XEN_INIT_TYPE_EVENT_CHANNEL - event-channel = 9 (00000009) 12974973503156: XenVbd XEN_INIT_TYPE_READ_STRING - device-type = cdrom 12974973503156: XenVbd device-type = CDROM 12974973503156: XenVbd XEN_INIT_TYPE_READ_STRING - mode = r 12974973503156: XenVbd mode = r 12974973503156: XenVbd XEN_INIT_TYPE_READ_STRING - sectors = 6544648 12974973503171: XenVbd XEN_INIT_TYPE_READ_STRING - sector-size = 512 12974973503171: XenVbd qemu_hide_flags_value = 1 12974973503171: XenVbd Device is inactive 12974973503171: XenVbd <-- XenVbd_InitFromConfig 12974973503171: XenVbd aligned_buffer_data = FFFFFA80013CA8E8 12974973503171: XenVbd aligned_buffer = FFFFFA80013CB000 12974973503171: XenVbd ConfigInfo->MaximumTransferLength = 4194304 12974973503171: XenVbd ConfigInfo->NumberOfPhysicalBreaks = 1024 12974973503171: XenVbd ConfigInfo->VirtualDevice = 1 12974973503187: XenVbd ConfigInfo->NeedPhysicalAddresses = 1 12974973503187: XenVbd Dma64BitAddresses supported 12974973503187: XenVbd <-- XenVbd_VirtualHwStorFindAdapter 12974973503187: XenVbd --> XenVbd_HwStorInitialize 12974973503187: XenVbd IRQL = 0 12974973503187: XenVbd dump_mode = 0 12974973503187: XenVbd <-- XenVbd_HwStorInitialize 12974973503187: XenVbd Inactive srb->Function = 00000000 12974973503203: XenVbd Inactive srb->Function = 00000000 12974973503203: XenVbd Inactive srb->Function = 00000000 12974973503203: XenVbd Inactive srb->Function = 00000000 12974973503203: XenPCI --> XenPciPdo_EvtDeviceWdmIrpPreprocess_START_DEVICE 12974973503203: XenPCI device/vbd/768 12974973503203: XenPCI CmResourceTypeMemory (0) 12974973503203: XenPCI Start = f2000000, Length = 0 12974973503203: XenPCI pfn[0] = 0001afad 12974973503203: XenPCI New Start = 000000001afad000, Length = 4096 12974973503203: XenPCI CmResourceTypeMemory (1) 12974973503203: XenPCI Start = f2000001, Length = 0 12974973503218: XenPCI <-- XenPciPdo_EvtDeviceWdmIrpPreprocess_START_DEVICE 12974973503218: XenPCI --> XenPciPdo_EvtDevicePrepareHardware 12974973503234: XenPCI <-- XenPciPdo_EvtDevicePrepareHardware 12974973503234: XenPCI --> XenPciPdo_EvtDeviceD0Entry 12974973503234: XenPCI path = device/vbd/768 12974973503234: XenPCI WdfPowerDeviceD3Final 12974973503234: XenPCI --> XenPci_GetBackendAndAddWatch 12974973503234: XenPCI <-- XenPci_GetBackendAndAddWatch 12974973503234: XenPCI --> XenPci_UpdateBackendState 12974973503234: XenPCI --> XenConfig_InitConfigPage 12974973503234: XenPCI fdo_driver_object = FFFFFA8000CFB8A0 12974973503250: XenPCI Backend State Changed to InitWait 12974973503250: XenPCI fdo_driver_extension = 0000000000000000 12974973503250: XenPCI <-- XenPci_UpdateBackendState 12974973503250: XenPCI fdo_driver_object = FFFFFA8000F93DE0 12974973503250: XenPCI fdo_driver_extension = 0000000000000000 12974973503250: XenPCI <-- XenConfig_InitConfigPage 12974973503250: XenPCI --> XenPci_XenConfigDeviceSpecifyBuffers 12974973503265: XenPCI --> XenPci_ChangeFrontendStateMap 12974973503265: XenPCI <-- XenPci_ChangeFrontendStateMap 12974973503265: XenPCI --> XenPci_ChangeFrontendStateMap 12974973503265: XenPCI <-- XenPci_ChangeFrontendStateMap 12974973503265: XenPCI <-- XenPci_XenConfigDeviceSpecifyBuffers 12974973503265: XenPCI <-- XenPciPdo_EvtDeviceD0Entry 12974973503265: XenVbd --> XenVbd_VirtualHwStorFindAdapter 12974973503281: XenVbd IRQL = 0 12974973503281: XenVbd xvdd = FFFFFA800141B008 12974973503281: XenVbd BusInterruptLevel = 28 12974973503281: XenVbd BusInterruptVector = 01c 12974973503281: XenVbd NumberOfAccessRanges = 1 12974973503281: XenVbd RangeStart = 1afad000, RangeLength = 00001000 12974973503281: XenVbd --> XenVbd_InitConfig 12974973503281: XenVbd XEN_INIT_TYPE_13 12974973503281: XenVbd XEN_INIT_TYPE_VECTORS 12974973503296: XenVbd XEN_INIT_TYPE_11 12974973503296: XenVbd XEN_INIT_TYPE_17 12974973503296: XenPCI --> XenPci_XenConfigDeviceSpecifyBuffers 12974973503296: XenPCI XEN_INIT_TYPE_RING - ring-ref = FFFFFA800142A000 12974973503296: XenPCI XEN_INIT_TYPE_RING - ring-ref = 16382 12974973503296: XenPCI XEN_INIT_TYPE_EVENT_CHANNEL - event-channel = 10 12974973503312: XenPCI --> XenPci_DeviceWatchHandler 12974973503328: XenPCI --> EvtChn_BindDpc 12974973503343: XenPCI <-- XenPci_DeviceWatchHandler 12974973503343: XenPCI <-- EvtChn_BindDpc 12974973503343: XenPCI --> XenPci_DeviceWatchHandler 12974973503343: XenPCI --> XenPci_ChangeFrontendStateMap 12974973503375: XenPCI <-- XenPci_DeviceWatchHandler 12974973503375: XenPCI --> XenPci_ChangeFrontendState 12974973503390: XenPCI --> XenPci_DeviceWatchHandler 12974973503390: XenPCI <-- XenPci_DeviceWatchHandler 12974973503390: XenPCI --> XenPci_UpdateBackendState 12974973503406: XenPCI Backend State Changed to Connected 12974973503406: XenPCI <-- XenPci_UpdateBackendState 12974973503406: XenPCI <-- XenPci_ChangeFrontendState 12974973503406: XenPCI <-- XenPci_ChangeFrontendStateMap 12974973503406: XenPCI --> XenPci_ChangeFrontendStateMap 12974973503421: XenPCI --> XenPci_ChangeFrontendState 12974973503421: XenPCI <-- XenPci_ChangeFrontendState 12974973503421: XenPCI --> XenPci_DeviceWatchHandler 12974973503421: XenPCI <-- XenPci_ChangeFrontendStateMap 12974973503437: XenPCI <-- XenPci_DeviceWatchHandler 12974973503437: XenPCI <-- XenPci_XenConfigDeviceSpecifyBuffers 12974973503437: XenVbd <-- XenVbd_InitConfig 12974973503437: XenVbd --> XenVbd_InitFromConfig 12974973503437: XenVbd XEN_INIT_TYPE_VECTORS 12974973503437: XenVbd XEN_INIT_TYPE_DEVICE_STATE - 000000000137B5D0 12974973503437: XenVbd XEN_INIT_TYPE_RING - ring-ref = FFFFFA800142A000 12974973503453: XenVbd XEN_INIT_TYPE_EVENT_CHANNEL - event-channel = 10 (0000000a) 12974973503453: XenVbd XEN_INIT_TYPE_READ_STRING - device-type = disk 12974973503453: XenVbd device-type = Disk 12974973503453: XenVbd XEN_INIT_TYPE_READ_STRING - mode = w 12974973503453: XenVbd mode = w 12974973503468: XenVbd XEN_INIT_TYPE_READ_STRING - sectors = 44038000 12974973503468: XenVbd XEN_INIT_TYPE_READ_STRING - sector-size = 512 12974973503468: XenVbd qemu_hide_flags_value = 1 12974973503468: XenVbd <-- XenVbd_InitFromConfig 12974973503468: XenVbd aligned_buffer_data = FFFFFA800141D8E8 12974973503468: XenVbd aligned_buffer = FFFFFA800141E000 12974973503484: XenVbd ConfigInfo->MaximumTransferLength = 4194304 12974973503484: XenVbd ConfigInfo->NumberOfPhysicalBreaks = 1024 12974973503484: XenVbd ConfigInfo->VirtualDevice = 1 12974973503484: XenVbd ConfigInfo->NeedPhysicalAddresses = 1 12974973503500: XenVbd Dma64BitAddresses supported 12974973503500: XenVbd <-- XenVbd_VirtualHwStorFindAdapter 12974973503515: XenVbd --> XenVbd_HwStorInitialize 12974973503515: XenVbd IRQL = 0 12974973503515: XenVbd dump_mode = 0 12974973503515: XenVbd <-- XenVbd_HwStorInitialize 12974973503515: XenVbd --- HwStorStartIo (Still figuring out ring) 12974973503531: XenVbd ring_detect_state = 1, index = 0, operation = ff, id = 0, status = -1 12974973503531: XenVbd req_prod = 2, rsp_prod = 1, rsp_cons = 0 12974973503531: XenVbd ring_detect_state = 2, index = 1, operation = ff, id = 0, status = -1 12974973503546: XenVbd req_prod = 2, rsp_prod = 2, rsp_cons = 1 12974973503656: XenVbd Unhandled EXECUTE_SCSI Command = A0 12974973503656: XenVbd EXECUTE_SCSI Command = A0 returned error 00 12974973503656: XenVbd --- HwStorStartIo (Out of bounds - PathId = 0, TargetId = 1, Lun = 0) 12974973503656: XenVbd --- HwStorStartIo (Out of bounds - PathId = 0, TargetId = 1, Lun = 0) 12974973503656: XenVbd SRB_FUNCTION_PNP 12974973503671: XenVbd StorQueryCapabilities 12974973503671: XenVbd SrbPnPFlags = 00000000 12974973503671: XenPCI --> XenPciPdo_EvtDeviceWdmIrpPreprocess_START_DEVICE 12974973503718: XenPCI device/vbd/832 12974973503718: XenPCI CmResourceTypeMemory (0) 12974973503718: XenPCI Start = f2000000, Length = 0 12974973503718: XenPCI pfn[0] = 0001afae 12974973503718: XenPCI New Start = 000000001afae000, Length = 4096 12974973503718: XenPCI CmResourceTypeMemory (1) 12974973503718: XenPCI Start = f2000001, Length = 0 12974973503718: XenPCI <-- XenPciPdo_EvtDeviceWdmIrpPreprocess_START_DEVICE 12974973503734: XenPCI --> XenPciPdo_EvtDevicePrepareHardware 12974973503734: XenPCI <-- XenPciPdo_EvtDevicePrepareHardware 12974973503734: XenPCI --> XenPciPdo_EvtDeviceD0Entry 12974973503734: XenPCI path = device/vbd/832 12974973503734: XenPCI WdfPowerDeviceD3Final 12974973503734: XenPCI --> XenPci_GetBackendAndAddWatch 12974973503734: XenPCI <-- XenPci_GetBackendAndAddWatch 12974973503734: XenPCI --> XenPci_UpdateBackendState 12974973503750: XenPCI --> XenConfig_InitConfigPage 12974973503750: XenPCI Backend State Changed to InitWait 12974973503750: XenPCI fdo_driver_object = FFFFFA8000CFB8A0 12974973503750: XenPCI <-- XenPci_UpdateBackendState 12974973503750: XenPCI fdo_driver_extension = 0000000000000000 12974973503750: XenPCI fdo_driver_object = FFFFFA8000F93DE0 12974973503750: XenPCI fdo_driver_extension = 0000000000000000 12974973503750: XenPCI <-- XenConfig_InitConfigPage 12974973503750: XenPCI --> XenPci_XenConfigDeviceSpecifyBuffers 12974973503750: XenPCI --> XenPci_ChangeFrontendStateMap 12974973503750: XenPCI <-- XenPci_ChangeFrontendStateMap 12974973503765: XenPCI --> XenPci_ChangeFrontendStateMap 12974973503765: XenPCI <-- XenPci_ChangeFrontendStateMap 12974973503765: XenPCI <-- XenPci_XenConfigDeviceSpecifyBuffers 12974973503765: XenPCI <-- XenPciPdo_EvtDeviceD0Entry 12974973503765: XenVbd --> XenVbd_VirtualHwStorFindAdapter 12974973503765: XenVbd IRQL = 0 12974973503765: XenVbd xvdd = FFFFFA8001471008 12974973503765: XenVbd BusInterruptLevel = 28 12974973503765: XenVbd BusInterruptVector = 01c 12974973503781: XenVbd NumberOfAccessRanges = 1 12974973503781: XenVbd RangeStart = 1afae000, RangeLength = 00001000 12974973503781: XenVbd --> XenVbd_InitConfig 12974973503781: XenVbd XEN_INIT_TYPE_13 12974973503781: XenVbd XEN_INIT_TYPE_VECTORS 12974973503796: XenVbd XEN_INIT_TYPE_11 12974973503796: XenVbd XEN_INIT_TYPE_17 12974973503796: XenPCI --> XenPci_XenConfigDeviceSpecifyBuffers 12974973503796: XenPCI XEN_INIT_TYPE_RING - ring-ref = FFFFFA8001480000 12974973503796: XenPCI XEN_INIT_TYPE_RING - ring-ref = 16381 12974973503812: XenPCI XEN_INIT_TYPE_EVENT_CHANNEL - event-channel = 11 12974973503828: XenPCI --> XenPci_DeviceWatchHandler 12974973503843: XenPCI --> EvtChn_BindDpc 12974973503843: XenPCI <-- XenPci_DeviceWatchHandler 12974973503843: XenPCI <-- EvtChn_BindDpc 12974973503843: XenPCI --> XenPci_DeviceWatchHandler 12974973503843: XenPCI --> XenPci_ChangeFrontendStateMap 12974973503843: XenPCI <-- XenPci_DeviceWatchHandler 12974973503843: XenPCI --> XenPci_ChangeFrontendState 12974973503843: XenPCI --> XenPci_DeviceWatchHandler 12974973503843: XenPCI <-- XenPci_DeviceWatchHandler 12974973503859: XenPCI --> XenPci_UpdateBackendState 12974973503859: XenPCI Backend State Changed to Connected 12974973503859: XenPCI <-- XenPci_UpdateBackendState 12974973503859: XenPCI <-- XenPci_ChangeFrontendState 12974973503859: XenPCI <-- XenPci_ChangeFrontendStateMap 12974973503859: XenPCI --> XenPci_ChangeFrontendStateMap 12974973503859: XenPCI --> XenPci_ChangeFrontendState 12974973503859: XenPCI <-- XenPci_ChangeFrontendState 12974973503859: XenPCI --> XenPci_DeviceWatchHandler 12974973503859: XenPCI <-- XenPci_ChangeFrontendStateMap 12974973503875: XenPCI <-- XenPci_DeviceWatchHandler 12974973503875: XenPCI <-- XenPci_XenConfigDeviceSpecifyBuffers 12974973503875: XenVbd <-- XenVbd_InitConfig 12974973503875: XenVbd --> XenVbd_InitFromConfig 12974973503875: XenVbd XEN_INIT_TYPE_VECTORS 12974973503875: XenVbd XEN_INIT_TYPE_DEVICE_STATE - 000000000137C9C0 12974973503875: XenVbd XEN_INIT_TYPE_RING - ring-ref = FFFFFA8001480000 12974973503875: XenVbd XEN_INIT_TYPE_EVENT_CHANNEL - event-channel = 11 (0000000b) 12974973503875: XenVbd XEN_INIT_TYPE_READ_STRING - device-type = cdrom 12974973503875: XenVbd device-type = CDROM 12974973503875: XenVbd XEN_INIT_TYPE_READ_STRING - mode = r 12974973503875: XenVbd mode = r 12974973503890: XenVbd XEN_INIT_TYPE_READ_STRING - sectors = 422560 12974973503890: XenVbd XEN_INIT_TYPE_READ_STRING - sector-size = 512 12974973503890: XenVbd qemu_hide_flags_value = 1 12974973503890: XenVbd Device is inactive 12974973503890: XenVbd <-- XenVbd_InitFromConfig 12974973503890: XenVbd aligned_buffer_data = FFFFFA80014738E8 12974973503890: XenVbd aligned_buffer = FFFFFA8001474000 12974973503890: XenVbd ConfigInfo->MaximumTransferLength = 4194304 12974973503890: XenVbd ConfigInfo->NumberOfPhysicalBreaks = 1024 12974973503890: XenVbd ConfigInfo->VirtualDevice = 1 12974973503906: XenVbd ConfigInfo->NeedPhysicalAddresses = 1 12974973503906: XenVbd Dma64BitAddresses supported 12974973503906: XenVbd <-- XenVbd_VirtualHwStorFindAdapter 12974973503906: XenVbd --> XenVbd_HwStorInitialize 12974973503906: XenVbd IRQL = 0 12974973503906: XenVbd dump_mode = 0 12974973503906: XenVbd <-- XenVbd_HwStorInitialize 12974973503906: XenVbd Inactive srb->Function = 00000000 12974973503906: XenVbd Inactive srb->Function = 00000000 12974973503906: XenVbd Inactive srb->Function = 00000000 12974973503906: XenVbd Inactive srb->Function = 00000000 12974973503921: XenVbd SRB_FUNCTION_IO_CONTROL 12974973503921: XenVbd SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 28, allocation_length = 192 12974973503921: XenVbd SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 8, allocation_length = 192 12974973503921: XenVbd SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 8, allocation_length = 192 12974973503937: XenVbd SRB_FUNCTION_PNP 12974973503937: XenVbd StorQueryCapabilities 12974973503937: XenVbd SrbPnPFlags = 00000000 12974973504203: XenVbd Inactive srb->Function = 00000017 12974973504218: XenVbd Unhandled srb->Function = 00000017 12974973504218: XenVbd Inactive srb->Function = 00000017 12974973504218: XenVbd Unhandled srb->Function = 00000017 12974973505265: Trying to enable physical device already in use. 12974973524343: XenNet --> DriverEntry 12974973524343: XenNet Driver MajorNdisVersion = 6, Driver MinorNdisVersion = 1 12974973524359: XenNet Windows MajorNdisVersion = 6, Windows MinorNdisVersion = 20 12974973524359: XenNet --> XenNet_SetOptions 12974973524359: XenNet <-- XenNet_SetOptions 12974973524359: XenNet <-- DriverEntry 12974973524359: XenPCI --> XenPciPdo_EvtDeviceWdmIrpPreprocess_START_DEVICE 12974973524375: XenPCI device/vif/0 12974973524375: XenPCI CmResourceTypeMemory (0) 12974973524375: XenPCI Start = f2000000, Length = 0 12974973524375: XenPCI pfn[0] = 0001afaf 12974973524375: XenPCI New Start = 000000001afaf000, Length = 4096 12974973524375: XenPCI CmResourceTypeMemory (1) 12974973524390: XenPCI Start = f2000001, Length = 0 12974973524390: XenPCI <-- XenPciPdo_EvtDeviceWdmIrpPreprocess_START_DEVICE 12974973524390: XenPCI --> XenPciPdo_EvtDevicePrepareHardware 12974973524390: XenPCI <-- XenPciPdo_EvtDevicePrepareHardware 12974973524390: XenPCI --> XenPciPdo_EvtDeviceD0Entry 12974973524390: XenPCI path = device/vif/0 12974973524406: XenPCI WdfPowerDeviceD3Final 12974973524406: XenPCI --> XenPci_GetBackendAndAddWatch 12974973524406: XenPCI <-- XenPci_GetBackendAndAddWatch 12974973524406: XenPCI --> XenPci_UpdateBackendState 12974973524421: XenPCI --> XenConfig_InitConfigPage 12974973524421: XenPCI Backend State Changed to InitWait 12974973524421: XenPCI fdo_driver_object = FFFFFA8001BB7060 12974973524421: XenPCI <-- XenPci_UpdateBackendState 12974973524421: XenPCI fdo_driver_extension = 0000000000000000 12974973524421: XenPCI fdo_driver_object = FFFFFA8000F93DE0 12974973524437: XenPCI fdo_driver_extension = 0000000000000000 12974973524437: XenPCI <-- XenConfig_InitConfigPage 12974973524437: XenPCI --> XenPci_XenConfigDeviceSpecifyBuffers 12974973524437: XenPCI --> XenPci_ChangeFrontendStateMap 12974973524437: XenPCI <-- XenPci_ChangeFrontendStateMap 12974973524453: XenPCI --> XenPci_ChangeFrontendStateMap 12974973524453: XenPCI <-- XenPci_ChangeFrontendStateMap 12974973524453: XenPCI <-- XenPci_XenConfigDeviceSpecifyBuffers 12974973524453: XenPCI <-- XenPciPdo_EvtDeviceD0Entry 12974973524468: XenNet --> XenNet_Initialize 12974973524468: XenNet XEN_INIT_TYPE_13 12974973524468: XenNet XEN_INIT_TYPE_VECTORS 12974973524468: XenNet XEN_INIT_TYPE_DEVICE_STATE - 000000000137F5D0 12974973524468: ScatterGather = 1 12974973524468: LargeSendOffload = 61440 12974973524500: LargeSendOffloadRxSplitMTU = 1 12974973524500: ChecksumOffload = 1 12974973524500: MTU = 1500 12974973524515: Could not read NetworkAddress value (c0000001) or value is invalid 12974973524515: XenNet --> XenNet_D0Entry 12974973524515: XenPCI --> XenPci_XenConfigDeviceSpecifyBuffers 12974973524515: XenPCI XEN_INIT_TYPE_RING - tx-ring-ref = FFFFFA8001BBC000 12974973524515: XenPCI XEN_INIT_TYPE_RING - tx-ring-ref = 16380 12974973524531: XenPCI XEN_INIT_TYPE_RING - rx-ring-ref = FFFFFA8001BBD000 12974973524546: XenPCI --> XenPci_DeviceWatchHandler 12974973524562: XenPCI XEN_INIT_TYPE_RING - rx-ring-ref = 16379 12974973524562: XenPCI <-- XenPci_DeviceWatchHandler 12974973524562: XenPCI XEN_INIT_TYPE_EVENT_CHANNEL - event-channel = 12 12974973524562: XenPCI --> XenPci_DeviceWatchHandler 12974973524562: XenPCI --> EvtChn_Bind 12974973524562: XenPCI <-- XenPci_DeviceWatchHandler 12974973524562: XenPCI <-- EvtChn_Bind 12974973524578: XenPCI --> XenPci_DeviceWatchHandler 12974973524578: XenPCI <-- XenPci_DeviceWatchHandler 12974973524578: XenPCI --> XenPci_ChangeFrontendStateMap 12974973524578: XenPCI --> XenPci_DeviceWatchHandler 12974973524578: XenPCI <-- XenPci_ChangeFrontendStateMap 12974973524578: XenPCI <-- XenPci_DeviceWatchHandler 12974973524578: XenPCI --> XenPci_ChangeFrontendStateMap 12974973524578: XenPCI --> XenPci_DeviceWatchHandler 12974973524578: XenPCI --> XenPci_ChangeFrontendState 12974973524578: XenPCI <-- XenPci_DeviceWatchHandler 12974973524593: XenPCI --> XenPci_DeviceWatchHandler 12974973524593: XenPCI <-- XenPci_DeviceWatchHandler 12974973524593: XenPCI --> XenPci_DeviceWatchHandler 12974973524593: XenPCI <-- XenPci_DeviceWatchHandler 12974973524593: XenPCI --> XenPci_DeviceWatchHandler 12974973524593: XenPCI <-- XenPci_DeviceWatchHandler 12974973524593: XenPCI --> XenPci_DeviceWatchHandler 12974973524593: XenPCI <-- XenPci_DeviceWatchHandler 12974973524593: XenPCI --> XenPci_UpdateBackendState 12974973524593: XenPCI Backend State Changed to Connected 12974973524593: XenPCI <-- XenPci_UpdateBackendState 12974973524593: XenPCI <-- XenPci_ChangeFrontendState 12974973524609: XenPCI <-- XenPci_ChangeFrontendStateMap 12974973524609: XenPCI <-- XenPci_XenConfigDeviceSpecifyBuffers 12974973524609: XenNet --> XenNet_ConnectBackend 12974973524609: XenNet XEN_INIT_TYPE_13 12974973524609: XenNet XEN_INIT_TYPE_VECTORS 12974973524609: XenNet XEN_INIT_TYPE_DEVICE_STATE - 000000000137F5D0 12974973524609: XenNet XEN_INIT_TYPE_RING - tx-ring-ref = FFFFFA8001BBC000 12974973524609: XenNet XEN_INIT_TYPE_RING - rx-ring-ref = FFFFFA8001BBD000 12974973524609: XenNet XEN_INIT_TYPE_EVENT_CHANNEL - event-channel = 12 12974973524609: XenNet XEN_INIT_TYPE_READ_STRING - mac = 00:16:3e:00:17:b9 12974973524609: XenNet XEN_INIT_TYPE_READ_STRING - feature-sg = 1 12974973524625: XenNet XEN_INIT_TYPE_READ_STRING - feature-gso-tcpv4 = 1 12974973524625: XenNet XEN_INIT_TYPE_17 12974973524625: XenNet <-- XenNet_ConnectBackend 12974973524625: XenNet --> XenNet_RxInit 12974973524625: XenNet <-- XenNet_RxInit 12974973524625: XenNet <-- XenNet_D0Entry 12974973524640: XenNet Supporting 00010102 (OID_GEN_HARDWARE_STATUS) get only 4 bytes 12974973524640: XenNet Supporting 00010108 (OID_GEN_TRANSMIT_BUFFER_SPACE) get only 4 bytes 12974973524640: XenNet Supporting 00010109 (OID_GEN_RECEIVE_BUFFER_SPACE) get only 4 bytes 12974973524640: XenNet Supporting 0001010a (OID_GEN_TRANSMIT_BLOCK_SIZE) get only 4 bytes 12974973524640: XenNet Supporting 0001010b (OID_GEN_RECEIVE_BLOCK_SIZE) get only 4 bytes 12974973524640: XenNet Supporting 0001010c (OID_GEN_VENDOR_ID) get only 4 bytes 12974973524656: XenNet Supporting 0001010d (OID_GEN_VENDOR_DESCRIPTION) get only 10 bytes 12974973524656: XenNet Supporting 00010116 (OID_GEN_VENDOR_DRIVER_VERSION) get only 4 bytes 12974973524656: XenNet Supporting 0001010e (OID_GEN_CURRENT_PACKET_FILTER) get/set 4 bytes 12974973524656: XenNet Supporting 0001010f (OID_GEN_CURRENT_LOOKAHEAD) get/set 4 bytes 12974973524656: XenNet Supporting 00010111 (OID_GEN_MAXIMUM_TOTAL_SIZE) get only 4 bytes 12974973524656: XenNet Supporting 00010208 (OID_GEN_LINK_PARAMETERS) set only 32 bytes 12974973524656: XenNet Supporting 00010209 (OID_GEN_INTERRUPT_MODERATION) get/set 12 bytes 12974973524671: XenNet Supporting 00010115 (OID_GEN_MAXIMUM_SEND_PACKETS) get only 4 bytes 12974973524671: XenNet Supporting 00010103 (OID_GEN_MEDIA_SUPPORTED) get only 4 bytes 12974973524671: XenNet Supporting 00010104 (OID_GEN_MEDIA_IN_USE) get only 4 bytes 12974973524671: XenNet Supporting 00010105 (OID_GEN_MAXIMUM_LOOKAHEAD) get only 4 bytes 12974973524671: XenNet Supporting 00010118 (OID_GEN_NETWORK_LAYER_ADDRESSES) set only 6 bytes 12974973524671: XenNet Supporting 0001021a (OID_GEN_MACHINE_NAME) set only 0 bytes 12974973524687: XenNet Supporting 0101010a (OID_OFFLOAD_ENCAPSULATION) set only 28 bytes 12974973524687: XenNet Supporting fd010101 (OID_PNP_SET_POWER) set only 4 bytes 12974973524687: XenNet Supporting 00020101 (OID_GEN_XMIT_OK) get only 0 bytes 12974973524687: XenNet Supporting 00020102 (OID_GEN_RCV_OK) get only 0 bytes 12974973524687: XenNet Supporting 00020103 (OID_GEN_XMIT_ERROR) get only 0 bytes 12974973524703: XenNet Supporting 00020104 (OID_GEN_RCV_ERROR) get only 0 bytes 12974973524703: XenNet Supporting 00020105 (OID_GEN_RCV_NO_BUFFER) get only 0 bytes 12974973524703: XenNet Supporting 01020101 (OID_802_3_RCV_ERROR_ALIGNMENT) get only 0 bytes 12974973524703: XenNet Supporting 01020102 (OID_802_3_XMIT_ONE_COLLISION) get only 0 bytes 12974973524703: XenNet Supporting 01020103 (OID_802_3_XMIT_MORE_COLLISIONS) get only 0 bytes 12974973524703: XenNet Supporting fc010209 (OID_IP4_OFFLOAD_STATS) none 0 bytes 12974973524718: XenNet Supporting fc01020a (OID_IP6_OFFLOAD_STATS) none 0 bytes 12974973524718: XenNet Supporting 00020106 (OID_GEN_STATISTICS) get only 152 bytes 12974973524718: XenNet Supporting 01010101 (OID_802_3_PERMANENT_ADDRESS) get only 6 bytes 12974973524718: XenNet Supporting 01010102 (OID_802_3_CURRENT_ADDRESS) get only 6 bytes 12974973524718: XenNet Supporting 01010103 (OID_802_3_MULTICAST_LIST) get/set 0 bytes 12974973524734: XenNet Supporting 01010104 (OID_802_3_MAXIMUM_LIST_SIZE) get only 4 bytes 12974973524734: XenNet name = minint-ps2nl91 12974973524734: XenNet --> XenNet_Restart 12974973524734: XenNet <-- XenNet_Restart 12974973524734: XenNet --> XenNet_DevicePnPEventNotify 12974973524734: XenNet NdisDevicePnPEventPowerProfileChanged 12974973524734: XenNet <-- XenNet_DevicePnPEventNotify 12974973524734: XenNet Set OID_GEN_CURRENT_LOOKAHEAD 62 (FFFFFA8001BB9000) 12974973524750: XenNet NDIS_PACKET_TYPE_DIRECTED 12974973524750: XenNet NDIS_PACKET_TYPE_MULTICAST 12974973524750: XenNet Unsupported OID 00010117 12974973524750: XenNet Unknown Encapsulation Type 0 12974973524750: XenNet Unknown Encapsulation Type 0 12974973524781: XenNet Set OID_GEN_CURRENT_LOOKAHEAD 82 (FFFFFA8001BB9000) 12974973524781: XenNet NDIS_PACKET_TYPE_DIRECTED 12974973524796: XenNet NDIS_PACKET_TYPE_MULTICAST 12974973524796: XenNet NDIS_PACKET_TYPE_BROADCAST 12974973524796: XenNet IPv4.Enabled = NDIS_OFFLOAD_SET_ON 12974973524796: XenNet IPv4.HeaderSize = 14 12974973524796: XenNet IPv6.EncapsulationType = 0 12974973524796: XenNet IPv6.Enabled = NDIS_OFFLOAD_SET_OFF 12974973524812: XenNet IPv6.HeaderSize = 0 12974973534531: XenNet AddressType = 2 12974973534531: XenNet AddressCount = 1 12974973534531: XenNet Address[0].Type = NDIS_PROTOCOL_ID_TCP_IP 12974973534531: XenNet Address[0].Length = 16 12974973534531: XenNet Address[0].in_addr = 169.254.239.84 12974973586906: XenPCI --> XenPci_EvtDeviceFileCreate 12974973586921: XenPCI --> XenBus_DeviceFileInit 12974973586921: XenPCI <-- XenBus_DeviceFileInit 12974973586921: XenPCI <-- XenPci_EvtDeviceFileCreate 12974973586921: XenPCI --> XenPci_EvtIoDefault 12974973586921: XenPCI --> XenBus_EvtIoWrite 12974973586921: XenPCI 36 bytes of write buffer remaining 12974973586921: XenPCI completing request with length 36 12974973586921: XenPCI <-- XenBus_EvtIoWrite 12974973586921: XenPCI <-- XenPci_EvtIoDefault 12974973586921: XenPCI --> XenPci_EvtIoDefault 12974973586921: XenPCI --> XenBus_EvtIoRead 12974973586921: XenPCI found pending read 12974973586937: XenPCI <-- XenBus_ProcessReadRequest 12974973586937: XenPCI <-- XenBus_EvtIoRead 12974973586937: XenPCI <-- XenPci_EvtIoDefault 12974973586937: XenPCI --> XenPci_EvtFileCleanup 12974973586937: XenPCI --> XenBus_EvtFileCleanup 12974973586937: XenPCI <-- XenBus_EvtFileCleanup 12974973586937: XenPCI <-- XenPci_EvtFileCleanup 12974973586937: XenPCI --> XenPci_EvtFileClose 12974973586937: XenPCI --> XenBus_EvtFileClose 12974973586937: XenPCI <-- XenBus_EvtFileClose 12974973586937: XenPCI <-- XenPci_EvtFileClose 12974973591531: XenNet AddressType = 2 12974973591531: XenNet AddressCount = 1 12974973591531: XenNet Address[0].Type = NDIS_PROTOCOL_ID_TCP_IP 12974973591531: XenNet Address[0].Length = 16 12974973591531: XenNet Address[0].in_addr = 62.76.47.68 12974973591531: XenNet AddressType = 2 12974973591531: XenNet AddressCount = 1 12974973591531: XenNet Address[0].Type = NDIS_PROTOCOL_ID_TCP_IP 12974973591546: XenNet Address[0].Length = 16 12974973591546: XenNet Address[0].in_addr = 62.76.47.68 12974973604156: XenVbd SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 63, allocation_length = 192 12974973604156: XenVbd SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 63, allocation_length = 192 12974973604156: XenVbd SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 63, allocation_length = 192 12974973612640: XenVbd SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 63, allocation_length = 192 12974973613343: XenVbd SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 63, allocation_length = 192 12974973613359: XenVbd SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 63, allocation_length = 192 12974973613359: XenVbd SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 63, allocation_length = 192 12974973613390: XenVbd SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 63, allocation_length = 192 12974973613453: XenVbd SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 63, allocation_length = 192 12974973613468: XenVbd SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 63, allocation_length = 192 12974973613484: XenVbd SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 63, allocation_length = 192 12974973613484: XenVbd SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 63, allocation_length = 192 12974973613500: XenVbd SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 63, allocation_length = 192 12974973613531: XenVbd SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 63, allocation_length = 192 12974973613812: XenVbd SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 63, allocation_length = 192 12974973613828: XenVbd SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 63, allocation_length = 192 12974973613843: XenVbd SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 63, allocation_length = 192 12974973613859: XenVbd SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 63, allocation_length = 192 12974973613875: XenVbd SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 63, allocation_length = 192 12974973613875: XenVbd SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 63, allocation_length = 192 12974973613890: XenVbd SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 63, allocation_length = 192 12974973613906: XenVbd SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 63, allocation_length = 192 12974973613906: XenVbd SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 63, allocation_length = 192 12974973613921: XenVbd SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 63, allocation_length = 192 12974973613921: XenVbd SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 63, allocation_length = 192 12974973613937: XenVbd SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 63, allocation_length = 192 12974973613937: XenVbd SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 63, allocation_length = 192 12974973613953: XenVbd SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 63, allocation_length = 192 12974973613968: XenVbd SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 63, allocation_length = 192 12974973613984: XenVbd SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 63, allocation_length = 192 12974973613984: XenVbd SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 63, allocation_length = 192 12974973613984: XenVbd SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 63, allocation_length = 192 12974973613984: XenVbd SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 63, allocation_length = 192 12974973614000: XenVbd SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 63, allocation_length = 192 12974973614000: XenVbd SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 63, allocation_length = 192 12974973614015: XenVbd SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 63, allocation_length = 192 12974973617375: XenVbd SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 63, allocation_length = 192 12974973617375: XenVbd SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 63, allocation_length = 192 12974973618406: XenVbd SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 63, allocation_length = 192 12974973629578: XenVbd SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 63, allocation_length = 192 12974973629578: XenVbd SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 63, allocation_length = 192 12974973629593: XenVbd SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 63, allocation_length = 192 12974973629593: XenVbd SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 63, allocation_length = 192 12974973629718: XenVbd SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 63, allocation_length = 192 12974973629750: XenVbd SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 63, allocation_length = 192 12974973629765: XenVbd SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 63, allocation_length = 192 12974973629828: XenVbd SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 63, allocation_length = 192 12974973629828: XenVbd SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 63, allocation_length = 192 12974973629843: XenVbd SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 63, allocation_length = 192 12974973629843: XenVbd SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 63, allocation_length = 192 12974973635703: XenVbd Inactive srb->Function = 00000000 12974973635703: XenVbd Inactive srb->Function = 00000000 12974973635703: XenVbd Inactive srb->Function = 00000000 12974973635703: XenVbd Inactive srb->Function = 00000000 12974973635703: XenVbd Inactive srb->Function = 00000000 12974973635703: XenVbd Inactive srb->Function = 00000000 12974973635718: XenVbd Inactive srb->Function = 00000000 12974973635718: XenVbd Inactive srb->Function = 00000000 12974973635718: XenVbd Unhandled EXECUTE_SCSI Command = A0 12974973635718: XenVbd EXECUTE_SCSI Command = A0 returned error 00 12974973635718: XenVbd --- HwStorStartIo (Out of bounds - PathId = 0, TargetId = 1, Lun = 0) 12974973635718: XenVbd --- HwStorStartIo (Out of bounds - PathId = 0, TargetId = 1, Lun = 0) 12974973635734: XenVbd Inactive srb->Function = 00000000 12974973635734: XenVbd Inactive srb->Function = 00000000 12974973635734: XenVbd Inactive srb->Function = 00000000 12974973635734: XenVbd Inactive srb->Function = 00000000 12974973640703: XenVbd SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 63, allocation_length = 192 12974973648015: XenVbd Inactive srb->Function = 00000000 12974973648015: XenVbd Inactive srb->Function = 00000000 12974973648015: XenVbd Inactive srb->Function = 00000000 12974973648015: XenVbd Inactive srb->Function = 00000000 12974973648015: XenVbd Unhandled EXECUTE_SCSI Command = A0 12974973648015: XenVbd EXECUTE_SCSI Command = A0 returned error 00 12974973648015: XenVbd --- HwStorStartIo (Out of bounds - PathId = 0, TargetId = 1, Lun = 0) 12974973648015: XenVbd --- HwStorStartIo (Out of bounds - PathId = 0, TargetId = 1, Lun = 0) 12974973648015: XenVbd Inactive srb->Function = 00000000 12974973648031: XenVbd Inactive srb->Function = 00000000 12974973648031: XenVbd Inactive srb->Function = 00000000 12974973648031: XenVbd Inactive srb->Function = 00000000 12974973652000: XenVbd SCSIOP_MODE_SENSE llbaa = 0, dbd = 0, page_code = 63, allocation_length = 192 -- Vasiliy Tolstov, Clodo.ru e-mail: v.tolstov@selfip.ru jabber: vase@selfip.ru
Hi James, I used "http://www.heise.de/download/as-ssd-benchmark.html" (sorry - german website), but i remember similar results with the famous "HD Tune Pro" tool... Nowhere here DRBD is involved - sorry; the disk line refers to a phy lvm disk which is directly on a block device (ssd). But i can test with debug build if you still think this (what?) is an issue here - tell me if you want to see that! Greetings - and happy Easter! Tobias Am 06.04.2012 12:56, schrieb James Harper:>> glad you ask - because just yesterday i re-tested the 357-version of the >> drivers under Windows7 64bit HVM guest - here are the results: >> >> (everyting in mb/s) >> >> W/O gplpv-drivers and WITH pci-passthrough: >> >> Seq. reading: 311.8 >> Seq. writing: 106.3 >> 4k reading: 10.2 >> 4k writing: 9.3 >> 4k64thread reading: 11.1 >> 4k64threads writing: 10.9 >> >> >> WITH gplpv-drivers and WITH pci-passthrough: >> >> Seq. reading: 98.8 >> Seq. writing: 31.6 >> 4k reading: 12.0 >> 4k writing: 19.3 >> 4k64thread reading: 15.4 >> 4k64threads writing: 29.6 >> >> >> WITH gplpv-drivers and WITHOUT pci-passthrough: >> >> Seq. reading: 104.4 >> Seq. writing: 85.2 >> 4k reading: 12.7 >> 4k writing: 20.4 >> 4k64thread reading: 16.6 >> 4k64threads writing: 32.6 >> >> >> Strange thing is, that even without pci-passthrough the performance with >> gplpv is''nt that much better compared to w/o gplpv but with pci-passthrough >> - well it is overall a bit better, but just a bit, and seq. read performance is >> much worse... >> i haven''t made a test without gplpv and without passthrough at the same >> time - tell me if you want to see how that performs. >> >> Greetings! >> Tobias >> >> P.S.: i''m using phy backend pointing to a LVM device on an SSD for this tests. >> > What are you testing this with? I just ran some tests with iometer under 2008R2 and it reminded me of something... DRBD *hates* having outstanding writes to the same block, and complains about it, so gplpv serialises such requests (stalling the queue until the first request is complete). This almost never happens in production but iometer sends such requests frequently, which will significantly impact performance. > > You can test with the debug build to see if this is happening with whatever you are testing with - you''ll see messages like "Concurrent outstanding write detected". Be aware though that qemu will rate limit writes to the debug log so if it happens a lot (like under iometer) it will slow to a crawl. > > James >
Hi James, just FYI: since i updated my nearly one-year old xen-unstable checkout, it turned out that my strange GPL-PV Performance issue went away: With (gplpv_Vista2008x64_0.11.0.357.msi) i get much better performance with GPLPV than without - regardless of PCI-Passthrough. What i observed though: I get about exactly "half" the performance (Disk-IO) in my PV-HVM than i get in my Dom0: In Dom0 i read/write with about 300mb/s , in DomU its about 150mb/s; Also (but not exactly messured) i noticed double the RTT value when pinging the DomU in comparsion to the RTT when pinging Dom0; I wonder what it makes perform more or less exactly "half" as Dom0 ? Greetings Tobias Am Sonntag, 8. April 2012, 15:44:37 schrieb Tobias Geiger:> Hi James, > > I used "http://www.heise.de/download/as-ssd-benchmark.html" (sorry - > german website), but i remember similar results with the famous "HD Tune > Pro" tool... > > Nowhere here DRBD is involved - sorry; the disk line refers to a phy lvm > disk which is directly on a block device (ssd). > > But i can test with debug build if you still think this (what?) is an > issue here - tell me if you want to see that! > > Greetings - and happy Easter! > Tobias > > Am 06.04.2012 12:56, schrieb James Harper: > >> glad you ask - because just yesterday i re-tested the 357-version of the > >> drivers under Windows7 64bit HVM guest - here are the results: > >> > >> (everyting in mb/s) > >> > >> W/O gplpv-drivers and WITH pci-passthrough: > >> > >> Seq. reading: 311.8 > >> Seq. writing: 106.3 > >> 4k reading: 10.2 > >> 4k writing: 9.3 > >> 4k64thread reading: 11.1 > >> 4k64threads writing: 10.9 > >> > >> > >> WITH gplpv-drivers and WITH pci-passthrough: > >> > >> Seq. reading: 98.8 > >> Seq. writing: 31.6 > >> 4k reading: 12.0 > >> 4k writing: 19.3 > >> 4k64thread reading: 15.4 > >> 4k64threads writing: 29.6 > >> > >> > >> WITH gplpv-drivers and WITHOUT pci-passthrough: > >> > >> Seq. reading: 104.4 > >> Seq. writing: 85.2 > >> 4k reading: 12.7 > >> 4k writing: 20.4 > >> 4k64thread reading: 16.6 > >> 4k64threads writing: 32.6 > >> > >> > >> Strange thing is, that even without pci-passthrough the performance with > >> gplpv is''nt that much better compared to w/o gplpv but with > >> pci-passthrough - well it is overall a bit better, but just a bit, and > >> seq. read performance is much worse... > >> i haven''t made a test without gplpv and without passthrough at the same > >> time - tell me if you want to see how that performs. > >> > >> Greetings! > >> Tobias > >> > >> P.S.: i''m using phy backend pointing to a LVM device on an SSD for this > >> tests. > > > > What are you testing this with? I just ran some tests with iometer under > > 2008R2 and it reminded me of something... DRBD *hates* having > > outstanding writes to the same block, and complains about it, so gplpv > > serialises such requests (stalling the queue until the first request is > > complete). This almost never happens in production but iometer sends > > such requests frequently, which will significantly impact performance. > > > > You can test with the debug build to see if this is happening with > > whatever you are testing with - you''ll see messages like "Concurrent > > outstanding write detected". Be aware though that qemu will rate limit > > writes to the debug log so if it happens a lot (like under iometer) it > > will slow to a crawl. > > > > James > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel