Hi,
In the past, I have install esx 3.01 on workstation 6.0 by following the extrainvt document.
Now, it does not work and I have the error " The install was unable to find any supported network devices.
Press " ok" to reboot your system.
Can guru advise?
Tks
I assume you have re-posted this to make it a question?
Please see my previous post to you.
Rgds,
Doug.
Hi Chris, I've deleted your original post. Here was Doug's reply to that post
Dave Mishchenko
VMTN Communities User Moderator
-
My colleague had a similar issue with Workstation 6.02 and ESX 3.0.1. He had to manually edit the .vmx file of the VM and change the network card to be e1000 instead of vmxnet to get it to work.
Hope this helps.
Doug.
Hi,
I've install sucessfully on version 6.0. Now I'm trying on workstation 6.02 and it is a different problem.
In version 6.0, you can change the vlance to e1000 but in 6.02 there is no such type when you create. Even I try to put it inside manually by
following extrainvt, it does not work
Kindly advise.
Tks
Can you post the contents of your VMX file?
Hi Guru,
Below is Original - Before Modification and After modification. Attach is the modification .vmx files. Thank You for your assistance
ORIGINAL - BEFORE MODIFICATION
config.version = "8"
virtualHW.version = "4"
scsi0.present = "TRUE"
scsi0.virtualDev = "lsilogic"
memsize = "512"
scsi0:0.present = "TRUE"
scsi0:0.fileName = "ESX35.vmdk"
ide1:0.present = "TRUE"
ide1:0.fileName = "H:\ISO\vmware\esx-3.5.0-64607.iso"
ide1:0.deviceType = "cdrom-image"
floppy0.autodetect = "TRUE"
ethernet0.present = "TRUE"
ethernet0.wakeOnPcktRcv = "FALSE"
svga.autodetect = "TRUE"
mks.keyboardFilter = "allow"
displayName = "ESX35"
guestOS = "redhat"
nvram = "Red Hat Linux.nvram"
deploymentPlatform = "windows"
virtualHW.productCompatibility = "esx"
tools.upgrade.policy = "useGlobal"
ide1:0.autodetect = "TRUE"
floppy0.fileName = "A:"
extendedConfigFile = "Red Hat Linux.vmxf"
floppy0.present = "FALSE"
After modification to the .vmx file
config.version = "8"
virtualHW.version = "4"
scsi0.present = "TRUE"
scsi0.virtualDev = "lsilogic"
memsize = "512"
scsi0:0.present = "TRUE"
scsi0:0.fileName = "ESX35.vmdk"
ide1:0.present = "TRUE"
ide1:0.fileName = "H:\ISO\vmware\esx-3.5.0-64607.iso"
ide1:0.deviceType = "cdrom-image"
floppy0.autodetect = "TRUE"
ethernet0.present = "TRUE"
ethernet0.virtualDev = "vlance"
ethernet0.connectionType = "bridged"
ethernet0.addressType= "generated"
ethernet0.wakeOnPcktRcv = "FALSE"
svga.autodetect = "TRUE"
mks.keyboardFilter = "allow"
displayName = "ESX35"
guestOS = "redhat"
nvram = "Red Hat Linux.nvram"
deploymentPlatform = "windows"
virtualHW.productCompatibility = "esx"
tools.upgrade.policy = "useGlobal"
ide1:0.autodetect = "TRUE"
floppy0.fileName = "A:"
extendedConfigFile = "Red Hat Linux.vmxf"
floppy0.present = "FALSE"
monitor_control.restrict_backdoor = TRUE
monitor_control.vt32 = TRUE
ethernet0.generatedAddress = "00:0c:29:f4:fa:b1"
uuid.location = "56 4d 16 a2 25 e3 74 4d-31 17 4b 3d 50 f4 fa b1"
uuid.bios = "56 4d 16 a2 25 e3 74 4d-31 17 4b 3d 50 f4 fa b1"
scsi0:0.redo = ""
ethernet0.generatedAddressOffset = "0"
Hi,
When I power on the esx it changes from ethernet0.virtualDev = "e1000" to the following
ethernet0.virtualDev = "vlance"
Anyone able to get esx 3.5 working on 6.02?
Kindly advise.
Thanks
Hi Chris, are you closing Workstation before you edit the VMX. I think that may be a factor in it getting changed back. I also user Other \ Other as the OS choice when I setup the VM.
Chris,
This may or may not help, but I have ESX 3.5 running succesfully on Workstation 6.0.2.
I didn't do a fresh install, though. I updated existing ESX 3.0.2 installs. I didn't need to change the .vmx file.
When I did the initial install of 3.0.2, I also initially had the problem with Workstation undoing changes I'd made to the vmx file. How I got around that was, once I had made the required changes, I shut down Workstation and restarted it. I then found the changes would stay.
Hope this helps.
Shane
Hi Shane,
Just to be sure, can you power on VMs? ESX 3.5 runs on my workstation 6.02 as well, right up to the point where I try to start a VM... If it does work on your end, it would be worthwhile to install ESX 3.02 and then upgrade to 3.5 to see if that does work...
The ultimate test would be, if you installed another ESX host on your workstation, but then directly version 3.5. You should have the strange behaviour that one ESX 3.5 host can, and the other cannot power on VMs...
Erik,
Haven't tried yet. Only did the upgrade yesterday and then ran out of time.
Will let you know when I've had a go.
Shane