VMware Cloud Community
infra3
Enthusiast
Enthusiast

Error on Updating ESXi 6.0 to 6.7

getting Below error while doing online update , offline network adapter is not showing

[root@localhost:~] esxcli software profile update -p ESXi-6.7.0-20190802001-standard -d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml

[DependencyError]

VIB DEC_bootbank_net-tulip_1.1.15-1 requires vmkapi_2_1_0_0, but the requirement cannot be satisfied within the ImageProfile.

Please refer to the log file for more details.

Regards

Rajesh

0 Kudos
6 Replies
daphnissov
Immortal
Immortal

You're trying to upgrade ESXi which is installed on Hyper-V. This won't work. 6.0 is the only version that supports that hacked VIB you have there.

0 Kudos
tayfundeger
Hot Shot
Hot Shot

Can you remove the driver and try again?

--
Blog: https://www.tayfundeger.com
Twitter: https://www.twitter.com/tayfundeger

vBlogger, vExpert, Cisco Champions

Please, if this solution helped your problem, "Helpful" if it solves your problem "Correct Answer" to mark.
0 Kudos
infra3
Enthusiast
Enthusiast

its a nested vm on Hyper-V and can't remove the driver .

0 Kudos
tayfundeger
Hot Shot
Hot Shot

This is a driver on VMware's black list. So you can't find it and run it. The operation you have already done is not supported.

--
Blog: https://www.tayfundeger.com
Twitter: https://www.twitter.com/tayfundeger

vBlogger, vExpert, Cisco Champions

Please, if this solution helped your problem, "Helpful" if it solves your problem "Correct Answer" to mark.
0 Kudos
marietto2008
Enthusiast
Enthusiast

I'm still a newbie of the vmware products. But I want to learn. I'm trying to customize a VMware ESXi image adding the tulip driver inside the ESXi-7.0.0-15843807-standard iso image file because I want to install it in a Hyper-V VM. I've got the same error appeared here. I would like to know the reasons why it has been blacklisted. thanks.

0 Kudos
a_p_
Leadership
Leadership

You've already got an answer at Re: Vmware ESXI within Hyper-v (server 2012) networking issue

Two ways to workaround this that I can think of, are that either MS provides an alternative virtual network adapter that's recognized by ESXi, or that someone re-writes the net-tulip driver to make it compatible with current ESXi versions.


André

0 Kudos