1 7 8 9 10 11 Previous Next 268 Replies Latest reply on Mar 13, 2009 7:11 AM by satish.lx Go to original post
      • 120. Re: for AMD-V
        oreeh Guru

        When your NIC setting changes back try the following:

        remove the VM from inventory

        modify the VMX

        add the VM to the inventory

        • 121. Re: for AMD-V
          VirtualKenneth Master
          vExpert

          Removing from inventory didn't do the trick for me, I had to remove, shutdown WS, start WS and re-add.

          So this problem is solved, but the other one isn't

          • 122. Re: for AMD-V
            VirtualKenneth Master
            vExpert

            I'm going to retry as well tomorrow (disable the VT) just to check if the error will disappear.

            • 123. Re: for AMD-V
              oreeh Guru

              I guess there's something wrong with your VM configuration / the VMX file.

              • 124. Re: for AMD-V
                VirtualKenneth Master
                vExpert

                I got it running now somehow.

                This is what I've changed:

                 

                1) Used notepad (instead of VIM to edit the .vmx file)

                2) Ejected my Sierra Wireless Edge card (with this card inserted I noticed that I have other network problems as well)

                3) Assigned more memory to the kernel

                 

                I'm unsure what has fixed it, will try to determine that later on.

                • 125. Re: for AMD-V
                  oreeh Guru

                  1) Used notepad (instead of VIM to edit the .vmx file)

                   

                  doesn't matter (I always use VIM)

                   

                  2) Ejected my Sierra Wireless Edge card (with this card inserted I noticed that I have other network problems as well)

                  3) Assigned more memory to the kernel

                   

                  if you had less than 1GB configured this is at least part of the issue

                  • 126. Re: for AMD-V
                    MayurPatel Expert

                    Folks,

                     

                    After the problems I was having with the hardware I have on which I was testing I decided to give up until I had something more modern and didn't realise how popular this thread has become. Sorry for not answering some of the questions put to me.

                     

                    Today I managed to get hold of a HPdc7700 desktop computer which has a T6300 Intel Dual Core CPU.

                     

                    I can confirm that the error message that I was earlier getting with my non-dual core CPU machine ie. VMware VMkernel authorisation daemon, Warning: date....error:md5 signature mismatch. Running vmkernel built on -Unknown- (vs.vmkload_app built on Sept 26 2006 00:00:01)[/b]  was due to the fact I was running this on my P4 2.5GHz Cerelon which is not dual core. I was also thinking my ISO might be corrupt but this was not the case as I have used the same ISO ESX image to build and did not receive this error on different hardware.

                     

                    I then moved the installation on my even older P3-1GHz machine which has 2 CPUs and I use this as a ESX host for my lab. On this machine the startup of VI3 went smoothly without any errors but it took 3hrs to display the console screen and it was not useable.

                     

                    This indicates the Guest ESX machine needs to have atleast 2 physical or logical CPU's in order to load successfully.

                     

                    Today I tested this on the T6300 dual core desktop machine and had to configure the "monitor_control.vt32" setting to "FALSE" because the BIOS does not enable the VT support although the CPU supports it and I managed to load ESX troublefree without any errors but it took a while (20mins) to display the console screen.

                     

                    One thing I noted, the XP deskop on which the Workstation 6 is running this guest is maxing out 100% both logical CPU's without running any VM's.

                     

                    I think this is where VT support is a must!

                     

                    My goal is to purchase an affordable laptop computer on which I can run a couple of ESX hosts and VC along with a couple of VM's.

                     

                    I have been searching around and found that many dual core laptops and desktops with VT supported CPU's do not have this feature enable in the bios.

                     

                    Below is the working VMX config that I used.

                     

                    guestOS = "redhat"

                    displayName = "ESX301"

                    deploymentPlatform = "windows"

                    numvcpus = "2"

                    nvram = "ESX.nvram"

                    config.version = "8"

                    virtualHW.version = "4"

                    scsi0.present = "True"

                    scsi0.virtualDev = "lsilogic"

                    scsi0.pciSlotNumber = "-1"

                    memsize = "512"

                    scsi0:0.present = "True"

                    scsi0:0.filename = "ESX301.vmdk"

                    scsi0:0.redo = ""

                    ide1:0.autodetect = "TRUE"

                    ide1:0.present = "TRUE"

                    ide1:0.devicetype = "cdrom-image"

                    ide1:0.filename = "C:\wks\esx-3.0.1-32039.iso"

                    floppy0.autodetect = "True"

                    floppy0.filename = "A:"

                    floppy0.startConnected = "FALSE"

                    ethernet0.present = "TRUE"

                    ethernet0.connectionType = "hostonly"

                    ethernet0.addressType = "generated"

                    ethernet0.generatedAddressOffset = "0"

                    ethernet0.virtualDev = "e1000"

                    ethernet0.wakeOnPcktRcv = "FALSE"

                    uuid.action = "Create"

                    monitor_control.restrict_backdoor = "TRUE"

                    monitor_control.vt32 = "[b]FALSE[/b]" (only enable this if VT is enabled in BIOS)[/i]virtualHW.productCompatibility = "hosted"

                    tools.upgrade.policy = "manual"

                    isolation.tools.hgfs.disable = "TRUE"

                    tools.remindInstall = "TRUE"

                     

                    Hope this helps.

                    • 127. Re: for AMD-V
                      oreeh Guru

                      I think this is where VT support is a must!

                       

                      Yepp !

                      Without VT it is awfully slow and nearly unusable.

                      To do something "useful" you should also increase the memory size.

                      Otherwise you won't have memory for a VM inside the ESX VM.

                      • 128. Re: for AMD-V
                        MayurPatel Expert

                        I have just configured the guest with 1GB of ram but still takes quite a long while just to load.

                         

                        Without VT there is little point using it.

                        • 129. Re: HPdc7700 Bios
                          mikelane Expert

                          The HPdc7700 does have an option for VT in the Bios it's just not in a logical location - from memory i think it is under Operating System option - just hunt around and you will find that it is there - it is on my HPdc7700.

                          • 130. VMWare Server inside VMWare Server
                            veshi Lurker

                            This is slightly off topic but I thought that it made sense to ask it here.  I'm trying to run VMWare Server inside of VMWare server to do some NAT testing.  I'm able to install fine, but I get the "You may not power on a virtual machine in a virtual machine." error when trying to start an image.

                             

                            I'm not sure which parameters are available for VMWare server, but I've tried the following in my vmx:

                             

                            guestOS = "other 32-bit"

                            ethernet0.virtualDev = "e1000"

                            monitor_control.restrict_backdoor = TRUE

                            monitor_control.vt32 = TRUE

                             

                            Any hints?

                            • 131. Re: VMWare Server inside VMWare Server
                              oreeh Guru

                              monitor_control.vt32 = TRUE

                               

                              not supported in VMware Server

                               

                              You probably need some more of the isolation.* parameters - don't ask me which since I don't know.

                              • 132. Re: VMWare Server inside VMWare Server
                                ksc Expert
                                VMware Employees

                                "isolation.tools.getversion.disable = true" should get past the check - outside of that, I'd strongly suggest not installing Tools in EITHER VM.

                                 

                                Server's codebase is somewhat older - it's roughly ws5.5.1.  The vt32 option should still work there (ws55 supported VT), but performance will be terrible.  If you aren't able to use Workstation, I'd suggest running Player 2.0 as the VT layer, since it's more modern and supports these options better.

                                • 133. Re: VMWare Server inside VMWare Server
                                  oreeh Guru

                                  Thanks for the info.

                                   

                                  The vt32 option should still work there (ws55 supported VT)

                                   

                                  Does this mean that in theory you could run ESX as a WS55 VM too?

                                  • 134. Re: HPdc7700 Bios
                                    MayurPatel Expert

                                    I am sure I flicked thru every menu item. The model I was testing on is the ultra-slim. I also read thru the user advanced guide to see if this option was available but couldn't find it there.

                                     

                                    I will check again now that you have mentioned that it could be hidden in one of the menu's.

                                     

                                    I must mention that there is a password set on the machine I am testing on, and although I don't have the BIOS password as this is from a batch of machines ordered by the corporate for our POC environment.  I am pressing return 3 times and it lets me into the BIOS. It may be because I don't have the password I am not seeing the advanced settings.

                                     

                                    I have access to the latest DL380G5 server class machines on which I could test but I  it would not give me the feel of what it would be like using it on a ordinary desktop/laptop computer.

                                     

                                    What would be nice is to create a list of Laptop and desktop computers which can run ESX properly in a VM as people experiment this functionality.

                                    1 7 8 9 10 11 Previous Next