BSOD when starting two VMs in Virtual Server
Sebastian G.
Core Duo 2.2 GHz, 4 GB RAM, PAE mode + NoExecuteAlwaysOn + UsePmTimer
BUGCHECK 0x8e KERNEL_MODE_EXCEPTION_NOT_HANDLED (0xc000001d, ..., ... , 0x0)
in VMM.SYS (DateStamp 4655F4A1) at Base+257D6
The memory address of the access could be valid, but I don't know for sure
since I got no coredump.
It occured when I started two VMs which are configured to run on the same
disk image, but with undo discs into different files. This has already been
running fine, tough I had never started them almost simultaneously before.
Most likely not due to third party drivers, since almost all of them are
disabled and have been tested under Driver Verifier with highest settings,
as well as with the checked build of kernel + HAL + drivers and the Driver
Patch Exerciser tool with full HCT test set.
Any ideas?
Sebastian G.
> Virtual Server 2005 R2 SP1 on Windows Server 2003 SP2 and all updates, Intel
> Core Duo 2.2 GHz, 4 GB RAM, PAE mode + NoExecuteAlwaysOn + UsePmTimer
>
> BUGCHECK 0x8e KERNEL_MODE_EXCEPTION_NOT_HANDLED (0xc000001d, ..., ... , 0x0)
> in VMM.SYS (DateStamp 4655F4A1) at Base+257D6
0xc000001d is STATUS_ILLEGAL_INSTRUCTION, and at this code location this is
actually the case. Still don't know how it got there.
Ryan Sokolowski [MVP]
--
Ryan Sokolowski
MVP - Clustering
MCSE, CCNA, CCDA, BCFP
"Sebastian G." <se...@seppig.de> wrote in message
news:67adbtF...@mid.dfncis.de...
Sebastian G.
> What is the disk type and speed that you're running against?
I don't quite understand what you mean, but it emulates plain IDE disks,
since the configuration has to be portable with Virtual PC. On the host it's
a high speed SATA drive with sufficient free adjecent space, so the virtual
disks can easily read and write at a rate of 60 MB/s.