An administrator is upgrading an ESXi 3.5 host to ESXi 5.x with an intermediate upgrade to 4.0 using Update Manager. The host has a single Intel Xeon processor, 4GB of RAM, and a VMFS datastore on a private, SAN-attached LUN.
What might cause the upgrade to be unsuccessful?
A.
The ESXi host has 4GB RAM.
B.
The ESXi host has one processor.
C.
ESXi 3.5 is not supported for upgrade.
D.
Update Manager cannot upgrade a previously upgraded host.
According to this
“because of the size the /boot partition was allocated in ESX 3.x, these hosts cannot be migrated to ESXi 5. Any ESX 4.x hosts that had previously been upgraded from ESX 3.x will not have the required minimum 350 MB of space in the /boot partition. In these cases a fresh install is required. VUM 5.0 still supports the great patching capabilities for legacy 3.5 and 4 ESX/ESXi servers and upgrades for 4.x hosts.”
Ans C should be true
0
0
Both reasons, C and D, are valid. But that may not be the correct answer according to VMwares exam.
0
0
The section you quoted talks about upgrade ESX 3.5 hosts, not ESXi 3.5 hosts as the question specifies.
0
0
C. Is NOT a valid answer. The Question already stated an in-between upgrade to 4.0.
D. Is valid:
https://pubs.vmware.com/vsphere-55/index.jsp#com.vmware.vsphere.upgrade.doc/GUID-CD26D0E7-D18C-482F-88BC-69139BDEC0FB.html
4.x ESX host that was upgraded from ESX 3.x with a partition layout incompatible with ESXi 5.x
Not supported.
The VMFS partition cannot be preserved. Upgrading or migration is possible only if there is at most one VMFS partition on the disk that is being upgraded and the VMFS partition must start after sector 1843200. Perform a fresh installation. To keep virtual machines, migrate them to a different system.
0
0
B is correct
Page 19
http://pubs.vmware.com/vsphere-50/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-50-installation-setup-guide.pdf
0
0
host must have at least 2 cores.
0
0
Answer B is correct, yes.
But they should be more specific and NOT call it “has a single Intel Xeon processor”. This is missleading since a CPU and a Core is not allways the same 😉
0
0
B is incorrect because an Intel Xeon processor is a multi core processor, thus fulfilling the requirement of having 2 cores.
D is correct – Update Manager cannot upgrade a previously upgraded host.
0
0
A.
The ESXi host has 4GB RAM. – ok 2GB is minimum
B.
The ESXi host has one processor. – OK its a xeon and is multi core (2 core minimum)
C.
ESXi 3.5 is not supported for upgrade. – It does, 3.5 > 4.x is fine
D.
Update Manager cannot upgrade a previously upgraded host.
This is the problem, you can’t upgrade a 4.x to 5 if it started as a 3.5. A 4.x fresh to 5 is fine.
0
0
agree with Ryan, see
http://pubs.vmware.com/vsphere-50/index.jsp?topic=%2Fcom.vmware.vsphere.upgrade.doc_50%2FGUID-AA106086-E10D-456E-B0B9-340D3D1462C3.html
You cannot use Update Manager to upgrade a host to ESXi 5.0 if the host was previously upgraded from ESX 3.x to ESX 4.x. Such hosts do not have sufficient free space in the /boot partition to support the Update Manager upgrade process. This problem also affects some 4.x ESX hosts, even if they were not previously upgraded from ESX 3.x. Hosts must have more than 350MB of free space in the /boot partition to support the Update Manager upgrade process. If the host that you are upgrading does not have more than 350MB of free space in the /boot partition, use a scripted or interactive upgrade instead.
0
0
B is the correct answer as Mariac shared. Two CPUs.
0
0
Ryan is right, option D is correct.
0
0
http://pubs.vmware.com/vsphere-51/index.jsp?topic=%2Fcom.vmware.vsphere.upgrade.doc_50%2FGUID-AA106086-E10D-456E-B0B9-340D3D1462C3.html
To upgrade version 3.5 ESX or ESXi to ESXi 5.x, you must first upgrade version 3.5 ESX or ESXi to version 4.x ESX or ESXi. See the VMware vSphere 4.x documentation Web page for information about upgrading from version 3.5 ESX or ESXi 3.5 to version 4.x ESX or ESXi.
—vmware so which is it yes or no?
0
0
http://pubs.vmware.com/vsphere-50/index.jsp?topic=%2Fcom.vmware.vsphere.upgrade.doc_50%2FGUID-AA106086-E10D-456E-B0B9-340D3D1462C3.html
“You cannot use Update Manager to upgrade a host to ESXi 5.0 if the host was previously upgraded from ESX 3.x to ESX 4.x.”
0
0
TestKing VCP-510 engine 3.5.1 v22.0 exp July 9 2013
–An administrator is upgrading an ESX3.5 host to ESXi5.x with an intermediate upgrade to ESX 4.0 using Update Manager. The host has a single Intel Xeon processor, 4GB of RAM, and a VMFS datastore on a private, SAN-attached LUN. What might cause the upgrade to be unsuccessful?
–Answer D. ESX 3.5 is not supported by Update Manager?
0
0
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2004503
You cannot use VMware Update Manager to upgrade an ESX/ESXi 3.x host to ESXi 5.x. Also, you may not use VMware Update Manager to upgrade to ESXi 5.x if that host was upgraded from ESX 3.x to ESX 4.x at any time. These hosts do not have sufficient free space (50 MB) in the /boot partition to support the VMware Upgrade Manager upgrade process
0
0
C is the correct Answer which will cause Vum to fail the upgrade
0
0
B – There are MANY legacy Xeon Procs with only one Core >
http://en.wikipedia.org/wiki/List_of_Intel_Xeon_microprocessors
C – You cannot even scan esx3.5 with VUM 5.X .
D – Makes sense , but not if C is true 🙂
Hate this question , could C/D/E
0
0
C & D seem to be true, but you can 3.x->4.x->5.x without VUM
0
0