Problems with ESXi 4.1 on an ML370

Similar Questions

• Strange problem with ESXI 4 e1000 windows 2003

  Hello

  I have a problem with ESXi all my vm will not have access to the Internet with the default E1000 network card...

  I can ping google or any other machine, but not access with ie/firefox. If I set up the virtual machine with vmXnet 3 it work perfect.

  Given that I'm about to convert a win 2000 Server and vmxnet is not supported on this operating system, I'm looking for a solution

  My dns are ok tried with the dns domain by default and open dns

  I can ping google but failed to load the web page

  I can ping my file server, but can not access to search for the file.

  Anyone with an idea.

  Thank you

  Is there a drawback using series vmxnet on all my virtual machine?

  No.... If you have installed VMware tools

  André

• Having problems with ESXi/vSphere Client Network

  First of all, I apologize if it's thread is in the wrong section.

  I recently installed ESXi v6.0.0 in VMware Workstation 12.0 trying to familiarize myself with ESXi as I recently graduated and I forgot most of what I learned from the class I took.

  Then, ESXi installed smoothly and was very painless.

  Then, I tried to create a virtual machine. It's when things are messy. I can't understand why, but I don't get any network connectivity after obtaining a DHCP address to all within the virtual machine, in addition to being able to ping the host ESXi itself.

  First of all, networking is like so:

  10.10.10.1 router/gateway

  10.10.10.254 DHCP, DNS, server, VMware Workstation files 12

  10.10.10.250 ESXi host

  10.10.10.244 ESXi reviews - Windows 7

  Googles DNS 8.8.8.8

  VMware workstation 12:

  AMD FX-8350

  Intel Corporation 82574L Gigabit Network Connection

  NVIDIA Corporation GF119 [GeForce GT 520] (rev a1) - However, not allowed to work with VMware VMware or xvnc throws a fit to this topic

  ESXi host

  Images: 2015-10-04_21-13 - 57.png, 2015-10-04_21-14 - 34.png

  The vSwitch has the following properties:

  Image: 2015-10-04_21-19 - 38.png

  
  

  And the following then occurs on the ESXi prompt:

  Images:,2015-10-04_21-01 - 58.png, 2015-10-04_21-03 - 32.png

  
  

  I can't really understand what the problem is, or what is happening. Yes, I could set up an internal network of the virtual machine with a firewall and what not, but I was hoping that there would already network connectivity while I wouldn't do. Also, is it possible to make attachments online?

  
  

  Thanks for all their help
  

  This could be a problem of permission on the host vmnet adapter, see http://kb.vmware.com/kb/287.

  André

• Debian Wheezy 7 - iSCSI / LIO problem with ESXi 5.0

  Hi all

  I had a Debian Wheezy on a HP ML310e server. This server should be used as an iSCSI - storage server.

  Unfortunately I am not able to connect my 5.0 with LIO iSCSI target ESX servers.

  I used the implementation of LIO (targetcli) for iSCSI and I used the official installation manual Linux target SCSI - ISCSI.

  I know that the discovery of the Portal works, because when I enter the IP Address of storage in the dynamic discovery, the two portals of storage can be found. BUT any new features.

  I disabled the CHAP authentication, because I thought that it might have to do with it, but still no go.

  My Windows 2003 R2 64 bit backup server can connect without a problem.

  I have a feeling it's something small, but unfortunately I can't find any debugging or a newspaper for the login process.

  Here is some info on my system:

  4 ESXi 5.0 x 623860 mit vCenter 5.0.0 623373

  HP ML310e as a storage server with:

  Debian GNU/Linux 7

  Linux avaNAS 3.2.0 - 4-amd64 SMP 3.2.46 - 1 + deb7u1 x86_64 GNU/Linux Debian #1

  [INFO] 2013-11-10 01:44:39 Using configshell version 1.1

  [INFO] 2013-11-10 01:44:39 Using rtslib version 2.1

  [INFO] 2013-11-10 01:44:39 using targetcli version 2.0rc1

  Is attached a screenshot of the current configuration of the TargetCLI.

  Thank you very much for your help!

  See you soon,.

  Alex

  Hi all

  Sorry for the late reply.

  I found a problem with MTU 9000.

  One of the switches does not 9000 MTU packet transport.

  After changing the MTU to 1500, everything works like a charm.

  See you soon,.

  Alex

• Problem with ESXi crashing on

  Hi all, looking for a few tips, recently did an upgrade to vCenter 5.0 to 5.5 all seem to go well. So next i deployed ESXi 5.5 to a host of test (HP Proliant DL360 G5) using the custom HP, once again the upgrade image seems fine, I have now a mixture of 2 x 5.0 hosts and 1 x 5.5 host in my environment. Now, the problems I have are:

  1. I can see is more monitoring equipment in the vCenter on my 5.0 hosts, I get an error, "the service of monitoring equipment is not available on this host or does not" tried restarting the service of the CIM on the hosts but no chance, not yet been able to reboot the host. I will modernize these hosts to 5.5 Finally so I hope it's a compatibility problem between the vCenter in 5.5 and 5.0 hosts. My reasoning for this is that on my test host that I've updated to 5.5, I can see hardware monitoring and reporting works OK - with 1 exception which I elaborate on below...

  2. after my upgrade to 5.5 on my test host computer although the hardware monitoring works after every reboot of the CIM service host seems down, a few minutes storage components of my screen (storage and battery) server in the status tab of the hardware, but shortly after they both disappear If I go into the security profile and restart the service of the CIM on the host, and then click on "Update", under the condition of the equipment, the two batteries and storage return under supervision and as far as I can see that they stay there until the host is restarted, and the cycle starts again. I installed the last HP Offline bundles on the host.

  3. my biggest problem though is the following. After my upgrade to 5.5 on my test server, everything seems to work very well. However, it is the second morning in a row (had 5.5 running since Tuesday this week) that I came into the Office to find that my 5.5 test host is disconnected in my vCenter server, when it was connected and managed until I left the night before. I can not AT ALL on the host without having to reboot it completely. I tried:

  • SSH to the host
  • Live Console
  • Remove and readd in vCenter
  • client vSphere for vCenter Server
  • vSphere Client directly to the host
  • vCenter Webclient

  Whenever he gives me the different errors that my credentials are not valid or that the user name or password is incorrect, I use root credentials I know are correct, and if I reboot the host then I can connect to the host using one of the above methods using the same credentials I use now. Yesterday, I was able to connect to the host using the client vSphere that allows me to put it in maintenance mode and it reboot, this morning but my only option is a hard reset on the server.

  My VM on the host are available I can ping and RDP for them and they have full network access, but I can't manage the host on which they are sitting on. This isn't a problem now in my test configuration, but I won't go live until I've been overcome these bugs. The host responds to the Ping and the console directly on the face seems to be running and not crashed.

  I'm relatively new to ESX on this scale, so any advice would be warmly received.

  Thank you.

  OK, I added a little more memory for the machine and another CPU, I had lying around and this solved my most problem machines to crash on.

  Also a restart of the other guests brought material followed back to life and the upgrade to 5.5 worked well on other machines with all the existing monitoring equipment.

  So it seems that some issues were down to compatibility were 'other' allocation of resources.

• Problems with ESXi 5.1 and 5.0 in a WS9 EFI - VM

  Hello Jim

  I'm testing ESXi LiveCDs to version 5.0 and 5.1.
  In the LiveCD, I use a state.tgz to enable SSH and ESXi-shell and set a password.
  The LiveCD works fine if I use them on WS 9 virtual machines with firmware = "bios".

  If I try the same CD in a virtual machine with the firmware = "efi" I am not able to get the network began.
  If I built a CD that does not use the state.tgz the network is fine.

  For now, I'm building the CD with different boot.cfgs for MBR and boot EFI.
  But I prefer to use the boot.cfg even with a state.tgz that works for both scenarios.

  I enclose the EFI - VM's vmx file and the state.tgz file.

  Great!

• Problem with ESXi 4.0 with Allocation of disk on a virtual computer

  Hello Experts

  Physical server:

  HP DL 380 2 proc Intel Xeon 4 GB RAM

  6 x 146 GB HDD (with RAID5) = > total available capacity 650 GB

  Problem:

  I am creating a VM with OS = DEBIAN6

  When I allocate 300 GB HARD drive for the virtual machine, it gives me just 256GB.

  I don't understand the reason.

  I read that this could be linked to the BLOCK SIZE.

  What is your opinion? If so, how can I change the block size?

  Thanks in advance

  Options of your choice after.

  Block size of 1 MB = Max VMDK 256 GB

  2MB block size = Max VMDK 512 GB

  4MB block size = Max VMDK 1024 GB

  Block size of 8MB = Max VMDK 2048 GB

  First calculation of disk space when set up 2 MB to 512 GB.

• Problems with esxi 4.1 hosts about vcenter 5?

  I'm in a situation where I want to update my server vcenter V5, but am not able to upgrade all of my esxi 4.1-5 hosts.

  4.1 host will need licenses on the vcenter v5 v5 or will it take 4.1 license keys?

  You have to run for about 1 or 2 months before all the esx hosts can go to v5.

  Guests 4.x will continue to use the vSphere licenses 4. vCenter will require you a new license key for itself when you upgrade to 5, and ESXi hosts, you are upgrading will require licenses on vSphere 5.

• problem with esxi

  Hello

  I have a dedicated server with Intel Core 2 X 5650. I want to create three virtual machines:
  A machine with 10 hearts, one with 8 cores and the other with its four hearts.
  Unfortunately, I can go up to 8 cores / maximum machines. And when I create a virtual machine with 8 cores, I get the following error:

  (in french: the vsmp function is not licensed, of requires 8, 4)

  VSMP function is not approved, requires 8, 4

  How can I start a virtual machine with more than 4 cores?

  Thank you

  Hello and welcome to the forums.

  You will need to have company + licenses, in order to get 8 vCPUs.

  Good luck!

• Problem with ESXi 3.5 host or our iSCSI SAN

  Hello

  Last week, twice we came into work and notice that some virtual machines on a host somehow the bomb and break the connection or work habit and are turned off.  It happens with mutiple errors, but we are not sure if it's the host itself or iSCSI SAN is too connected a NETgear ReadyNAS.  All the vmdk and vmx VM files are on the SAN storage are loacted here for targets.  Your opinion on this if someone could help determine what may be the question, please, thank you?

  Welcome to the forums

  I edit your images and delete the business credentials. There is a security risk that you should not expose.

  Take a look at the following.

  http://communities.VMware.com/message/1333118#1333118

• Purple screen of death with ESXi 3.4 U4

  Hi all

  I lived I have a strange problem with esxi 3.5 U4. Yesterday morning I got the purple screen on one of my hosts esxi test, if anyone can give me any idea what this error means.

  on the host, it there was only one virtual machine running with ubuntu server on it. The thing I noticed is that my colleague, who install the ubuntu Server I forgot to install vmware tools. Can this be the cause of this error.

  After a reboot and the vmware tools install everything I work, but I don't know what was the problem in the first place, so I appreciate your responses.

  Kind regards

  Lyubo

  Hello

  Definitely check your hardware, here is a link to find some info on the purple screen and error codes:

  http://www.VI-Toolkit.com/wiki/index.php/Vmkerrcode

  --

  Wil

  _____________________________________________________

  Visit VMware developers at http://www.vi-toolkit.com wiki

• Problem with the start of VMware ESXi 5.0

  I just installed VMware ESXi 5.0 on a new Cisco UCS B200 series blade with two 300 GB hard drives configured in a RAID 1 mirror.  I went through and completed the installation of VMware ESXi 5.0 on this server.  When the installation is complete and the server restarted, he did not initiate the ESXi where I can change the IP address and VLAN.  Instead, I get this text string after the initial boot sequence that is shown in the attachment.  I have a guest who said Shell > do not know why I can not start correctly in ESXi 5.0.  Thank you!  Paul

  Hi Paul,.

  Looks like you boot to the EFI shell. What is the startup policy that you have configured on this server service profile? It should look like the one below.  If there is a problem with the boot order, you should be able to type "EXIT", then enter on the EFI shell to exit the prompt. If your startup is similar to the one below and you still experience this issue, try to downgrade and re - ack the blade.

  Let me know if it helps.

  

• Problem with server Supermicro laboratory at home, ESXi sets in not as server restarts always

  Dear community,

  I'm having a problem that makes me nuts and I was wondering if you can help me with this.

  While trying to set up a laboratory at home (I think it's often referred to a "white box" system)? I don't get the operational ESXi installation. For three days, I was not able to install ESXi.

  Problem:

  ESXi 5.5U3 installation fails and immediately restarts the host until it starts doing anything... specific.

  Using IPMI my motherboard I recorded (and also attached) a video and tried to integrate it here:

  In case you don't see it please look at the attachment.

  For those who do not see the host starts and begins to extract the files in memory. When he goes to the grey-yellow screen it shows the following lines and then - BOOM - restarts the host and it again:

  Initialization of the moment...

  Initializing Scheduler...

  Initializing power management...

  the user successfully loaded.

  RESET

  I tried several options, such as the boot via USB, both internally and externally, to change between USB 2.0 or 3.0 port or IPMI ISO loading but nothing, all this goes down with the same problem or even f * cks up to my output video when you attach a file ISO storage KVM. Disabling USB legacy support also solves nothing and even had to reset the BIOS thereafter. Also to make sure that it is not related to the RAM, I changed the memory and tried with 8 or 16 GB or 32 GB full and also tried different banks, no change.

  It is the material that I use:

  • Supermicro X10SLL-F
  • Kit of UDUMM 240-pin ECC Kingston 32 GB (4 x 8 GB)
  • be quiet 400W power
  • SATA 250 GB HARD drive (or without)
  • Lexar 8 GB USB stick (formatted with Rufus) / anonymous 4 GB USB Stick

  As described above, nothing I tried quite fix it and I start to feel the distress of one.) "(ne pas pouvoir continuer et b.)" After spending a lot of money on things that don't work (and I'd rather not things).

  I know that, currently, this motherboard is not himself but factually have seen several blog posts of people who use this motherboard with success. Why am I the only one who can not do?

  Oh any by the way, the ESXi version is this: VMware-VMvisor-Installer - 5.5.0.update03 - 3116895.x86_64.iso

  I hope that someone out there is able to help me.

  Thank you in advance for your help!

  Believe it or not, it was the power supply.

  All those who try and random restarts as beds me days were due to the poor being quiet power, hopefully, at some point this will help everyone.

• Problem with RDM, Disc 3 to and ESXi 6

  Hello

  I followed this guide to my local 3 TB drive to work with ESXi 6.

  VMware KB: Raw Device Mapping for local storage

  But when I use the command

  vmkfstools - z/vmfs/devices/drives / < diskname > vmfs/volumes / < datastorename > / < vmfolder > / < vmname > hard

  I get this error.

  Unable to create the virtual disk: the destination file system does not support large files (12).

  Any advice on how to fix this?

  PROBLEM SOLVED!

  vmkfstools -z /vmfs/devices/disks/t10.ATA_____WDC_WD30EFRX2D68AX_________________________WD2DWMC1T1096 /vmfs/volumes/datastore1/3TBRDM.vmdk 
  

  I didn't understand that I had to add the datastore1 folder and put the hard file. I'm quite new to this kind of things.

• Big problem with installing ESXi 5.5 on Cisco UCS M200 B3

  Hello

  I have a problem with installing esxi 5.5 on SDcard mounted in Cisco UCS B200 m3.

  ESXi Show map SD but when to start partitioning I question (attachment).

  If I install ESXi on HDD I don't see SDcard (even from the console).

  Thanks for any help

  h

  Marcel

  Hello

  Thanks for the reply but SDcard are clear. map of are new directly from Cisco.

  The good news is that I found a solution. I install the old version of ESXi (5.5 U1) and everything works fine

  Concerning