Last night I had a little battle with one of my Windows XP machines that I recently had P2V.
However for some reason there was something wrong with the USB driver, 
when I open the Device Manager I saw two unknown devices both from VMware, this is very weird because I have the VMware Tools installed and it is working just fine except it couldn’t find the correct driver.
So I open the device and tried to update the driver and point it to the VMware Tools folder in the Program Files directory, 
but unfortunately Windows was unable to find the correct driver 
Read more…
Sometimes you have a nice colleague who is moving a Virtual Machine from one datacenter to another, however if this Virtual Machine have a RDM connected to it, and the storage is not linked to each other you would end up with an extra VMDK, that once was a RDM .
Okay so far my frustration 
(just kidding here) but It would be nice if VMware would have shown a big information message, that indicate that the RDM will be converted to a VMDK when an Admin is doing something like mentioned here above, because not every administrator is aware what he is doing.
S
Now lets take a look at how we can fix this, because we end up with quite a large VMDK file of around 450 GB, and because we only have a few VMFS datastores of approximately 500 GB each, this is not a great situation.
Read more…
Because we just upgraded the environment to vSphere 4.1 it was a bit suspicious that suddenly we have a number of VMs that where generating blue screens.
In a early stage the symptoms were just application errors especially Java related, and after a few minutes it ends up in a blue screen, after a reboot the sequence started all over again.
Read more…
After a P2V migration, I see there was an error in the eventlog with the
description “The following boot-start or system-start driver(s) failed to load: vmscsi” the Virtual Machines is just working fine so it’s not a big issue but I just don’t like errors
A quick search in the Device Manager finds out that indeed there’s one driver called “vmscsi” that gives a error (yes it’s a old KB, but I just want to share my expierience with you guys).
Luckily VMware have created a KB article that fixed this issue.
The solution is very simple open Device Manager and click on View and Show hidden devices. Next open Non-Plug and Play Drivers right click on vmscsi and choose Uninstall. After a reboot the error should disappear.
