Highlighted
Contributor
Contributor

Base System Device problem esxi 4.1

Hi,

Running esxi 4.1 with vcenter 4.1.0. I recently converted (vmware converter 4.3.0) two Windows 2008 (not R2) 64 bit, none of them can identify the Base Device Driver.

From what I have found on google, it mostly seem to be a problem for some specific version of vmware fusion.

I tried to apply the same tricks; do an interactive vmware tools installation but that fail with error code 1935.

Googling that showed me I need some microsoft visual studio redistributional something, but that too failed with error 1935.

All windows R2 2008 went great, and I can't seem to find a bunch of other people who have the same problem.

Anyone know anything about this?

How can it be resolved?

If not solved, what impact will the lack of the base system device driver have?

Thanks,

19 Replies
Highlighted
Immortal
Immortal

base device driver ? - is that really the device description ?

you can disable unused PCI-bridges in the vmx to see if tyhat removes the device
how many of them do you find in devmgmt.msc ?

Do you need support with a recovery problem ? - call me via skype "sanbarrow"
0 Kudos
Highlighted
VMware Employee
VMware Employee

a source was IBM ? if yes you can try remove.

to virtual machine not is necesary

*Please, don't forget the awarding points for "helpful" and/or "correct" answers. *Por favor, não esqueça de atribuir os pontos se a resposta foi útil ou resolveu o problema.* Thank you/Obrigado
0 Kudos
Highlighted
Contributor
Contributor

Are you saying I get that because of some unused driver?

From what I can tell, vmware tools tries to install a driver for "Base System Device". See screenshot

0 Kudos
Highlighted
User Moderator
User Moderator

To find out for which device Windows requires drivers, open the device manager and find the "Hardware ID" of the device (Vendor string). The device should be listed under Other/Unknown devices.

André

0 Kudos
Highlighted
Immortal
Immortal

in most cases you can disable

pcibridge 1 - 7

pciBridge1.present = "false"

...

pciBridge7.present = "false"

Do you need support with a recovery problem ? - call me via skype "sanbarrow"
0 Kudos
Highlighted
Immortal
Immortal

also, do you have the VMware Tools taskbar icon hidden, otherwise from your screenshot it doesn't appear the tools are installed

0 Kudos
Highlighted
Contributor
Contributor

I disabled the pci bridges in the vmx and restarted, but the device still shows up in device manager.

Any other clues?

.encoding = "UTF-8"
config.version = "8"
virtualHW.version = "7"
pciBridge0.present = "false"
pciBridge4.present = "false"
pciBridge4.virtualDev = "pcieRootPort"
pciBridge4.functions = "8"
pciBridge5.present = "false"
pciBridge5.virtualDev = "pcieRootPort"
pciBridge5.functions = "8"
pciBridge6.present = "false"
pciBridge6.virtualDev = "pcieRootPort"
pciBridge6.functions = "8"
pciBridge7.present = "false"
pciBridge7.virtualDev = "pcieRootPort"
pciBridge7.functions = "8"
vmci0.present = "TRUE"
nvram = "vm02-test.nvram"
virtualHW.productCompatibility = "hosted"
powerType.powerOff = "soft"
powerType.powerOn = "hard"
powerType.suspend = "hard"
powerType.reset = "soft"
displayName = "vm02-test"
extendedConfigFile = "vm02-test.vmxf"
memsize = "2048"
ide0:0.present = "TRUE"
ide0:0.fileName = "vm02-test-000001.vmdk"
ide1:0.present = "TRUE"
ide1:0.clientDevice = "TRUE"
ide1:0.deviceType = "cdrom-raw"
ide1:0.startConnected = "FALSE"
ethernet0.present = "TRUE"
ethernet0.virtualDev = "e1000"
ethernet0.wakeOnPcktRcv = "FALSE"
ethernet0.networkName = "old6"
ethernet0.addressType = "vpx"
ethernet0.generatedAddress = "00:50:56:b7:00:6e"
ethernet1.present = "TRUE"
ethernet1.virtualDev = "e1000"
ethernet1.wakeOnPcktRcv = "FALSE"
ethernet1.networkName = "VM Network"
ethernet1.addressType = "vpx"
ethernet1.generatedAddress = "00:50:56:b7:00:6f"
chipset.onlineStandby = "FALSE"
disk.EnableUUID = "TRUE"
guestOS = "longhorn-64"
uuid.bios = "42 37 8c d7 89 d6 4f d7-31 dc db 87 e3 e4 89 f5"
vc.uuid = "50 37 12 f8 9e e0 7d 36-56 0d 41 e3 ed 81 63 e7"
floppy0.present = "FALSE"
vmci0.id = "-471561739"
uuid.location = "56 4d fd 59 e4 38 47 e4-c5 5a d3 28 60 95 e3 bd"
cleanShutdown = "FALSE"
migrate.hostlog = "./vm02-test-606c9ad1.hlog"
replay.supported = "FALSE"
sched.swap.derivedName = "/vmfs/volumes/4db86d72-07e84630-d4ea-f04da26ff0a8/vm02-test/vm02-test-606c9ad1.vswp"
ide0:0.redo = ""
pciBridge0.pciSlotNumber = "-1"
pciBridge4.pciSlotNumber = "-1"

pciSlotNumber = "-1"
pciBridge6.pciSlotNumber = "-1"
pciBridge7.pciSlotNumber = "-1"
ethernet0.pciSlotNumber = "16"
ethernet1.pciSlotNumber = "17"
vmci0.pciSlotNumber = "18"
vmotion.checkpointFBSize = "4194304"
hostCPUID.0 = "0000000b756e65476c65746e49656e69"
hostCPUID.1 = "000206c220200800029ee3ffbfebfbff"
hostCPUID.80000001 = "0000000000000000000000012c100800"
guestCPUID.0 = "0000000b756e65476c65746e49656e69"
guestCPUID.1 = "000206c200010800829822030febfbff"
guestCPUID.80000001 = "00000000000000000000000128100800"
userCPUID.0 = "0000000b756e65476c65746e49656e69"
userCPUID.1 = "000206c220200800029822030febfbff"
userCPUID.80000001 = "00000000000000000000000128100800"
evcCompatibilityMode = "FALSE"
replay.filename = ""
tools.remindInstall = "TRUE"
ide1:0.fileName = "/usr/lib/vmware/isoimages/windows.iso"

0 Kudos
Highlighted
User Moderator
User Moderator

You didn't answer Troy's question on whether VMware Tools are installed yet. These tools provide drivers for the virtual hardware and other things. If the tools are installed please provide the hardware id's of the unknown devices.

André

0 Kudos
Highlighted
Contributor
Contributor

No, can't seem to get it right. During install of vmware tools, Im thrown a 1935 error.

* Followed some recomendations of making sure COM+ are running, running setup.exe of tools installer as opposed to autorun.exe.

* Further more one tip was to re-register mfc90.dll (or was it mvc90.dll?), but that couldnt be found.

* From that point, the recomendation was to install the Microsoft Visual C++ Redistributional pack, which too fail with 1935..

Kind of stuck here, I should probably open a separate thread for it.

0 Kudos
Highlighted
Contributor
Contributor

I had same issue when importing VM's from 3.5 to 4.1 and after reading forums i found. Making sure VM is recognized as the correct OS the correct tools where installed and and all drivers where installed.

Hope this helps

😉

0 Kudos
Highlighted
Enthusiast
Enthusiast

I had the same issue. Just point the hardware driver assistant to the following location :

C:\Program Files\Common Files\Drivers\vmci and the OS will install the driver.

--------- VMware Certified Professional 3/4
Highlighted
Immortal
Immortal

or disable vmci in the vmx-file

Do you need support with a recovery problem ? - call me via skype "sanbarrow"
0 Kudos
Highlighted
Immortal
Immortal

It is also important after a P2V to remove all hardware based software and devices.

Remove Hidden Devices
http://support.microsoft.com/kb/315539

-- David -- VMware Communities Moderator
0 Kudos
Highlighted
Contributor
Contributor

Just check your VM-Tools.

The "Base System Device" needs the VM-Tools Program Feature "VMCI Driver".

VM -> Guest -> Install / Uninstall VMTools

CD-Rom:

-> vmware tools.msi

-> vmware tools64.msi

Recommendation for new VMs (Templates,..): at first - uninstall this driver for better performance.

VMCI-Driver:

The Virtual Machine Communication Interface driver allows fast and efficient communication between virtual machines. Developers can write client-server applications to the VMCI Sock (vsock) interface to make use of the VMCI virtual device.

http://www.vmware.com/pdf/vmware-tools-cli.pdf

0 Kudos
Highlighted
Enthusiast
Enthusiast

Hello,

I am having this same issue after using converter standalone, to convert a Vista x64 machine.

I can not complete the install of the VM Tools because of it.

"Base System Device"

I examined the device drivers and it is pointing to hardware PCI\VEN_15AD&DEV_0740&SUBSYS_074015AD&REV_10

I tried the suggesions in the thread, even disabling the PCI and VMCI in the vmx file. But they keep switching back to TRUE after the VM starts.

I cleaned out all unused hidden drivers.

I tried manually installing "VMware Tools x64.msi" and when it is almost complete, it errors out with 25030 "Setup failed to load a kernal driver (vmrawdsk)" and rolls back.

What is the fix for this?

0 Kudos
Highlighted
Immortal
Immortal

remove the VM from the inventory before you disable vmci in the vmx-file.

Do you need support with a recovery problem ? - call me via skype "sanbarrow"
0 Kudos
Highlighted
Enthusiast
Enthusiast

That appears to have fixed it.

The VM started up, found the drivers it was looking; no more errors.

Thanks

0 Kudos
Highlighted
Contributor
Contributor

Well try beating that for simplicity. Thanks!

0 Kudos
Highlighted
Contributor
Contributor

Thanks! I had the same issue, and this solved my problem.

0 Kudos