Windows Terminal Server 2008 unusably slow after upgrade from 3.2.4 and databases getting corrupted

[ToddAndMargo]

Hi All,

This bug is being reported as critical as it corrupted one of my customers databases.

Host: Motherboard: Supermicro X8SAX Processor: x5650 (6 hard cores costing $1,200.00) Memory: 12 GB OS: CentOS 5.5 x64

Guest: Windows Terminal Server 2008 x32, Service Pack 2

VM: VBox 3.2.10

Before I get started, please note that bug 6928 was a Nested Paging bug and does not apply to this bug. The bug I am now reporting was uncovered while working on 6928.

On 2010-09-15 under bug 6928, I reported that when I upgrade from 3.2.4 to 3.2.8, with one software processor, that my Windows Terminal Server 2008 slowed to an excruciating crawl. I then reverted to 3.1.8 and got back to normal, still on one software processor.

On 10-18-2010 on bug 6928, I upgraded from 3.1.8 to 3.2.10 and from one soft processor to four hardware cores. The good news in that bug 6928 is fixed. The CPU storm is gone. But the massive slow down when I tried upgrading from 3.2.4 to 3.2.8 is still there. And it does not matter if you are using a single soft processor or multiple hard processors.

Note that Windows Terminal Server 2003, x32 worked beautifully under bug 6928's 3.2.10 patch. So, this bug is confined to Windows Terminal Server 2008 x32, SP2.

Also, in my 10-18-2010 testing of 3.2.10 on my Windows Terminal Server 2008 x32, SP2, a customer's database got corrupted. The report from the customer was that his program slowed down so excruciatingly slow that the whole thing eventually seized up. (I restored his database to Saturday night's snapshot. Fortunately, he did not use the server on Sunday.)

Please correct this bug as soon as possible. My Windows Terminal Server 2008 x32, SP2 is highly impacted, being relegated to one soft processor, and my customers are being poorly served. It would also be nice to FINALLY start being able to use my $1,200.00 processor.

I have attached both the 3.1.8 and the 3.2.10 XML files.

Please let me know if I can be of assistance in resolving this bug.

Many thanks, -T

[ToddAndMargo]

3.1.8, one soft core, works correctly

[ToddAndMargo]

3.2.10, 4 hard cores, very very slow

[ToddAndMargo]

log files. 3.2.10 is probably .2 and .3