1 2 3 4 5 Previous Next 268 Replies Latest reply on Mar 13, 2009 7:11 AM by satish.lx Go to original post
      • 30. Re: Ability to run ESX as a Workstation guest
        frapposelli Enthusiast

        OK, so here we go:

         

        config.version = "8"

        virtualHW.version = "6"

        numvcpus = "2"

        scsi0.present = "TRUE"

        scsi0.virtualDev = "lsilogic"

        memsize = "768"

        scsi0:0.present = "TRUE"

        scsi0:0.fileName = "ESX3-cl2.vmdk"

        ide1:0.present = "TRUE"

        ide1:0.fileName = "F:\Users\frapposelli\Desktop\rusco\esx-3.0.1-32039-1.iso"

        ide1:0.deviceType = "cdrom-image"

        floppy0.autodetect = "TRUE"

        ethernet0.present = "TRUE"

        ethernet0.wakeOnPcktRcv = "FALSE"

        sound.present = "TRUE"

        sound.fileName = "-1"

        sound.autodetect = "TRUE"

        pciBridge0.present = "TRUE"

        mks.keyboardFilter = "allow"

        displayName = "ESX 1"

        guestOS = "vmkernel"

        nvram = "ESX 1.nvram"

        deploymentPlatform = "windows"

        virtualHW.productCompatibility = "hosted"

        tools.upgrade.policy = "useGlobal"

         

        floppy0.fileName = "A:"

         

        isolation.tools.hgfs.disable = "TRUE"

         

        ethernet0.addressType = "generated"

        uuid.location = "56 4d 3b f8 df 08 31 58-51 5e 1d ba 74 10 d6 38"

        uuid.bios = "56 4d 3b f8 df 08 31 58-51 5e 1d ba 74 10 d6 38"

        scsi0:0.redo = ""

        pciBridge0.pciSlotNumber = "17"

        scsi0.pciSlotNumber = "16"

        ethernet0.pciSlotNumber = "32"

        sound.pciSlotNumber = "33"

        ethernet0.generatedAddress = "00:0c:29:10:d6:38"

        ethernet0.generatedAddressOffset = "0"

        ethernet0.virtualDev = "e1000"

        tools.remindInstall = "TRUE"

        floppy0.startConnected = "FALSE"

         

        monitor_control.vt32 = "TRUE"

         

        ethernet0.connectionType = "hostonly"

         

        vmx.allowNested = "TRUE"

         

        isolation.tools.getPtrLocation.disable = "TRUE"

        isolation.tools.setPtrLocation.disable = "TRUE"

        isolation.tools.setVersion.disable = "TRUE"

        isolation.tools.getVersion.disable = "TRUE"

         

        monitor_control.disable_directexec = "TRUE"

        monitor_control.disable_chksimd = "TRUE"

        monitor_control.disable_ntreloc = "TRUE"

        monitor_control.disable_selfmod = "TRUE"

        monitor_control.disable_reloc = "TRUE"

        monitor_control.disable_btinout = "TRUE"

        monitor_control.disable_btmemspace = "TRUE"

        monitor_control.disable_btpriv = "TRUE"

        monitor_control.disable_btseg = "TRUE"

        /code

         

        this is my vmx file, obviously you'll find some settings that resemble my environment so you need to tweak some parameters, as today i've only tested this file with Workstation 6 (last build, beta 3) on a core 2 duo processor.

         

        let me know if it works for you.

         

        HTH,

        Fabio

        • 31. Re: Ability to run ESX as a Workstation guest
          DaveP Master

          You don't need all of those statements:

           

          checkpoint.vmState = ""

          config.version = "8"

          deploymentPlatform = "windows"

          displayName = "ESX301"

          ethernet0.addressType = "generated"

          ethernet0.connectionType = "hostonly"

          ethernet0.generatedAddress = "00:0c:29:31:7e:36"

          ethernet0.generatedAddressOffset = "0"

          ethernet0.pciSlotNumber = "32"

          ethernet0.present = "TRUE"

          ethernet0.virtualDev = "e1000"

          ethernet0.wakeOnPcktRcv = "FALSE"

          floppy0.autodetect = "TRUE"

          floppy0.fileName = "A:"

          floppy0.startConnected = "FALSE"

          guestOS = "other"

          ide0:0.fileName = "ESX.vmdk"

          ide0:0.present = "FALSE"

          ide0:0.redo = ""

          ide1:0.autodetect = "TRUE"

          ide1:0.deviceType = "cdrom-image"

          ide1:0.fileName = "D:\Virtual Machines\!Dave!\ESXVM\dave.iso"

          ide1:0.present = "TRUE"

          isolation.tools.hgfs.disable = "TRUE"

          memsize = "1024"

          mks.keyboardFilter = "allow"

          monitor_control.restrict_backdoor = TRUE

          monitor_control.vt32 = TRUE

          numvcpus = "2"

          nvram = "ESX.nvram"

          pciBridge0.pciSlotNumber = "17"

          pciBridge0.present = "TRUE"

          scsi0.pciSlotNumber = "16"

          scsi0.present = "TRUE"

          scsi0.virtualDev = "lsilogic"

          scsi0:0.fileName = "ESX.vmdk"

          scsi0:0.present = "TRUE"

          scsi0:0.redo = ""

          sound.autodetect = "TRUE"

          sound.fileName = "-1"

          sound.present = "FALSE"

          tools.remindInstall = "TRUE"

          tools.upgrade.policy = "useGlobal"

          uuid.bios = "56 4d 89 4e 92 48 ba ba-54 18 f0 43 c9 31 7e 36"

          uuid.location = "56 4d 89 4e 92 48 ba ba-54 18 f0 43 c9 31 7e 36"

          virtualHW.productCompatibility = "hosted"

          virtualHW.version = "6"

          /code

           

          The important ones are:

           

          ethernet0.virtualDev = "e1000"

          monitor_control.restrict_backdoor = TRUE

          monitor_control.vt32 = TRUE

          numvcpus = "2"

          scsi0.virtualDev = "lsilogic"

          /code

          • 32. Re: Ability to run ESX as a Workstation guest
            frapposelli Enthusiast

            Thanks, I was not aware of this parameter

             

            monitor_control.restrict_backdoor = TRUE

            /code

             

            Surely my vmx file was a bit overkill thanks for pointing out the necessary parameter.

             

            Fabio

            • 33. Re: Ability to run ESX as a Workstation guest
              DaveP Master

              It's OK I had the same as you, but someone from VMware kindly gave me the correct ones to use.

              • 34. Re: Ability to run ESX as a Workstation guest
                ihsurf Novice

                Fabio and Dave thanks, but using these settings did not change the results on my test system.  (Booting speed was not increased at all.  I was using WIn2k3 Server as my host with Workstation 6 with ESX as a the guest.)

                 

                On the same hardware i was attempting to use ESX in a VM I have ESX running natively with NFS and it works like a champ, so at least we can have labs with relatively cheap pc's.  This is a SN25P shuttle box AMD 64bit dual core.

                 

                Perhaps somebody else will have better luck with different hardware?  I guess i could try on my dualcore 2 mac while in windows?

                • 35. Re: Ability to run ESX as a Workstation guest
                  Champion

                  Your AMD host does not have Intel VT support, so 'monitor_control.vt32' has no effect.  You should have more success on your Mac.

                  • 36. Re: Ability to run ESX as a Workstation guest
                    ihsurf Novice

                    Sucess!!! This worked flawlessly on my core 2 duo macbook pro.  I first tried the settings in the .vmx file in Workstation 5.5.3, but this did not work when ESX attempted to boot it got stuck on the SCSI forever.

                     

                    I upgraded to the VMware 6 beta and ESX booted just fine.  I connected to the service console so everything seems okay.

                     

                    This is cool because now you can run ESX as a guest if you have the correct hardware and are using a beta build of VMware 6 workstation.  The bad news is i doubt this will work with the production code and the beta will expire...

                    • 37. Re: Ability to run ESX as a Workstation guest
                      DaveP Master

                      >> The bad news is i doubt this will work with the production code and the beta will expire...  <<

                       

                      Why do you say that? It may be undocumented and not supported but what basis do you say it will be removed? Many VMX parameters have been around for a long time, and don't forget VMware use this themselves.

                      • 38. Re: Ability to run ESX as a Workstation guest
                        DaveP Master

                        Quick follow up. Also ran hosted products inside a guest. Ran Player 1.0.3 with Windows XP guest inside a Windows XP guest on a Windows XP host!!!! The main thing to ensure is that the the guest you are using to host the other VMware product uses IDE drives and has the SCSI adapter removed.

                        • 39. Re: Ability to run ESX as a Workstation guest
                          RDPetruska Guru

                          Hey Dave - question on what settings you used to create the "ESX.vmdk" file you used in your above VM.  I see it's using LsiLogic... what's the size and type, though?

                           

                          Oh, in regards to guest within a guest - you can actually install the Fusion beta inside an OSX guest!  I guess since it's an illegal guest they didn't even bother putting the check in the installer. 

                          Of course I can't power on a guest in there - the BIOS screen never POSTs... but it's interesting to look at, anyway.

                          • 40. Re: Ability to run ESX as a Workstation guest
                            DaveP Master

                            Hi

                             

                            For testing is created a 10Gb LSILogic SCSI drive. You can't actually use anything else. Remember also need 2 CPUs and Intel E1000 in guest definition as well.

                             

                            Dave

                            • 41. Re: Ability to run ESX as a Workstation guest
                              tlyczko Master

                              Does this work with the new 42757 beta??

                              Thank you, Tom

                              • 42. Re: Ability to run ESX as a Workstation guest
                                russjar Enthusiast

                                for some reason my configuration file is defaulting to ethernet0.virtualDev = "vlance". I have set the option to ethernet0.virtualDev = "e1000" and when I start the virtual machine bang back at ethernet0.virtualDev = "vlance"... I don't know what is causing this.

                                 

                                here is the rest of my config file....

                                 

                                'checkpoint.vmState = ""

                                'deploymentPlatform = "windows"

                                displayName = "ESX"

                                 

                                monitor_control.restrict_backdoor = TRUE

                                monitor_control.vt32 = TRUE

                                 

                                config.version = "8"

                                virtualHW.version = "6"

                                numvcpus = "2"

                                 

                                scsi0.present = "TRUE"

                                scsi0.virtualDev = "lsilogic"

                                scsi0:0.redo = ""

                                scsi0.pciSlotNumber = "16"

                                scsi0:0.present = "TRUE"

                                scsi0:0.fileName = "ESX.vmdk"

                                 

                                memsize = "512"

                                 

                                ide1:0.present = "TRUE"

                                ide1:0.fileName = ""

                                ide1:0.deviceType = "cdrom-image"

                                ide1:0.autodetect = "TRUE"

                                 

                                floppy0.autodetect = "TRUE"

                                floppy0.startConnected = "FALSE"

                                floppy0.fileName = "A:"

                                 

                                ethernet0.present = "TRUE"

                                ethernet0.virtualDev = "vlance"

                                ethernet0.wakeOnPcktRcv = "FALSE"

                                ethernet0.pciSlotNumber = "32"

                                ethernet0.generatedAddress = "00:0c:29:99:f8:e9"

                                ethernet0.generatedAddressOffset = "0"

                                ethernet0.addressType = "generated"

                                pciBridge0.pciSlotNumber = "17"

                                 

                                sound.present = "TRUE"

                                sound.fileName = "-1"

                                sound.autodetect = "TRUE"

                                pciBridge0.present = "TRUE"

                                mks.keyboardFilter = "allow"

                                guestOS = "other"

                                nvram = "Other.nvram"

                                deploymentPlatform = "windows"

                                virtualHW.productCompatibility = "hosted"

                                tools.upgrade.policy = "useGlobal"

                                 

                                isolation.tools.hgfs.disable = "TRUE"

                                 

                                uuid.location = "56 4d f6 f6 60 dd f8 26-6a 66 47 cb 32 99 f8 e9"

                                uuid.bios = "56 4d f6 f6 60 dd f8 26-6a 66 47 cb 32 99 f8 e9"

                                 

                                sound.pciSlotNumber = "33"

                                sound.startConnected = "FALSE"

                                 

                                svga.autodetect = "TRUE"

                                 

                                snapshot.disabled = "TRUE"

                                snapshot.action = "keep"

                                 

                                Message was edited by:

                                        russjar

                                • 43. Re: Ability to run ESX as a Workstation guest
                                  Jae Ellers Master

                                  If you are running VC this will happen sometimes. 

                                   

                                  Shut down the machine, right click and remove from inventory.  Edit the vmx and then browse the datastore on a host, right click and register.

                                  • 44. Re: Ability to run ESX as a Workstation guest
                                    sdaeme Novice

                                    for some reason my configuration file is defaulting

                                    to ethernet0.virtualDev = "vlance". I have set the

                                    option to ethernet0.virtualDev = "e1000" and when I

                                    start the virtual machine bang back at

                                    ethernet0.virtualDev = "vlance"... I don't know what

                                    is causing this.

                                     

                                    I had the same problem

                                    remove the quest from the favorites then shutdown vmware workstation, edit the vmx file start vmware workstation open the vmx file and start the quest

                                    When booting you see hardware reconfiguration

                                    Then I works and also virtual center works

                                    1 2 3 4 5 Previous Next