>I've usually seen something like this when either a backup app or an
>antivirus program tries to scan the vhd's. It's best to exclude them
>from the scans.

>I'm seeing a lot of these inside my guests...
>
>Event Type: Warning
>Event Source: Disk
>Event Category: None
>Event ID: 51
>Date: 4/25/2007
>Time: 2:55:03 AM
>User: N/A
>Computer: SLAPPY
>Description:
>An error was detected on device \Device\Harddisk0\D during a paging
>operation.
>
>Running Virtual PC 2007, latest additions installed.
>
>I'm seeing this error with the VHDs placed on three physical drives, on
>two different controllers, and at least a few times when running the
>virtual machine on a second physical PC.
>
>I've also done a fresh install of the guest WinXP, and the problem
>continues.
>
>On the host I've run the manufacturer's diagnostics without any errors
>being reported (Including the destructive in depth testing)
>
>Am I missing anything obvious here?

>In message <(email address - cut out)> Robert Comer
><(email address - cut out)> wrote:
>
>>I've usually seen something like this when either a backup app or an
>>antivirus program tries to scan the vhd's. It's best to exclude them
>>from the scans.
>
>I have neither running on the host, or the guest... The closest I have
>is Vista' Shawdow Copies, but they're disabled on the drive on which I'm
>currently storing my VHD (and VMC&undo) files.

>If you have nothing trying to lock the VHD files then it sounds like a
>hardware problem of some kind unfortunately.
>
>Are the VHD's on an external drive by any chance?
>
>I've seen USB drives get funny like this at times, even when not
>running VM software.

>It sure sounds like something is interfering with VPC's ability to get
>to the VHD's...

>>I'm wondering if maybe something within the guest could be corrupt, so
>>even if I've resolved the host issue (moving off of the USB drive) it
>>might be sticking with me in the guest?
>
>I suppose it's possible, but I haven't seen anything like that.
>
>>I have a couple reinstalls scheduled anyway to build out a cleaner
>>"fresh install" image, but it's a longshot.
>
>It'll at least narrow down the problem no matter what happens. If it
>still does it, look only to the host, and if it does fix it, it's a
>problem with that one guest.

>In message <(email address - cut out)> Robert Comer
><(email address - cut out)> wrote:
>
>>If you have nothing trying to lock the VHD files then it sounds like a
>>hardware problem of some kind unfortunately.
>>
>>Are the VHD's on an external drive by any chance?
>>
>>I've seen USB drives get funny like this at times, even when not
>>running VM software.
>
>Normally yes I run my VHDs from an external/USB drive. However, for
>testing I moved the VM I spend most of my day using over to a local SATA
>drive, with the same results.
>
>I also moved it to a second SATA drive on a different controller, and
>still received the same errors.

>even if I've resolved the host issue (moving off of the USB drive) it
>might be sticking with me in the guest?
>I have a couple reinstalls scheduled anyway to build out a cleaner
>"fresh install" image, but it's a longshot.
>In message <(email address - cut out)> Robert Comer
><(email address - cut out)> wrote:
>
>>It sure sounds like something is interfering with VPC's ability to get
>>to the VHD's...
>
>Yeah -- I'm not sure what though, I don't have anything special or
>unique that interacts with the filesystem in any unique way.
>
>I'm wondering if maybe something within the guest could be corrupt, so
>even if I've resolved the host issue (moving off of the USB drive) it
>might be sticking with me in the guest?
>
>It's a long shot, but that's about all I can think of at this point.
>
>chkdsk and some diagnostics within the guest don't report any problems
>either -- I was able to run either Seagate or WD's diagnostics
>(Apologies, I don't recall which) which completed without any errors.
>
>I have a couple reinstalls scheduled anyway to build out a cleaner
>"fresh install" image, but it's a longshot.

>In message <(email address - cut out)> Robert Comer
><(email address - cut out)> wrote:
>
>>>I'm wondering if maybe something within the guest could be corrupt, so
>>>even if I've resolved the host issue (moving off of the USB drive) it
>>>might be sticking with me in the guest?
>>
>>I suppose it's possible, but I haven't seen anything like that.
>>
>>>I have a couple reinstalls scheduled anyway to build out a cleaner
>>>"fresh install" image, but it's a longshot.
>>
>>It'll at least narrow down the problem no matter what happens. If it
>>still does it, look only to the host, and if it does fix it, it's a
>>problem with that one guest.
>
>I'm not entirely sure, but it's about 99% certain that it happens when
>running my USB drive on my laptop too (with the same guest)
>It also happens in multiple guests, although I believe they all
>originated from the same base install (so if the base install was
>corrupt somehow, the fact that it happens in multiple guests isn't what
>I'd call surprising)

>In message <(email address - cut out)> DevilsPGD
><(email address - cut out)> wrote:
>
>>In message <(email address - cut out)> Robert Comer
>><(email address - cut out)> wrote:
>>
>>>>I'm wondering if maybe something within the guest could be corrupt, so
>>>>even if I've resolved the host issue (moving off of the USB drive) it
>>>>might be sticking with me in the guest?
>>>
>>>I suppose it's possible, but I haven't seen anything like that.
>>>
>>>>I have a couple reinstalls scheduled anyway to build out a cleaner
>>>>"fresh install" image, but it's a longshot.
>>>
>>>It'll at least narrow down the problem no matter what happens. If it
>>>still does it, look only to the host, and if it does fix it, it's a
>>>problem with that one guest.
>>
>>I'm not entirely sure, but it's about 99% certain that it happens when
>>running my USB drive on my laptop too (with the same guest)
>
>This is still unconfirmed, although I'm fairly sure.
>
>>It also happens in multiple guests, although I believe they all
>>originated from the same base install (so if the base install was
>>corrupt somehow, the fact that it happens in multiple guests isn't what
>>I'd call surprising)
>
>The problem is happening on WinXP and Windows 2000 guests, which
>confirms that it's not one defective image that got copied...
>
>I'll investigate running these guests on a different host, but I'm not
>sure where else to go if that yields the same problem.
>
>Can anyone suggest any diagnostic tools that might be useful to run on
>the host?
>
>FWIW, no similar errors (or any disk errors at all) in the last couple
>weeks worth of host event logs.

> I'm seeing a lot of these inside my guests...
>
> Event Type: Warning
> Event Source: Disk
> Event Category: None
> Event ID: 51
> Date: 4/25/2007
> Time: 2:55:03 AM
> User: N/A
> Computer: SLAPPY
> Description:
> An error was detected on device \Device\Harddisk0\D during a paging
> operation.
>
> Running Virtual PC 2007, latest additions installed.
>
> I'm seeing this error with the VHDs placed on three physical drives, on
> two different controllers, and at least a few times when running the
> virtual machine on a second physical PC.
>
> I've also done a fresh install of the guest WinXP, and the problem
> continues.
>
> On the host I've run the manufacturer's diagnostics without any errors
> being reported (Including the destructive in depth testing)
>
> Am I missing anything obvious here?
>
> --
> Just sit through this NRA meeting Marge, and if you still
> don't think guns are great then we'll argue some more.
> -- Homer Simpson