Hi everyone
1- Do we have to use VXLAN in the NSX?
and
2- when do we use VXLAN?
thanks a lot
↧
VXLAN in NSX
↧
no sound on vm
VMware® Workstation 15.5.2 build-15785246. There are some virtual machines with Windows and Linux. No sound on Linux machines.
Log error:
vcpu-1| I125: Msg_Post: Warning
vcpu-1| I125: [msg.sound.defaultbadwaveopen] The default sound device cannot be opened:
vcpu-1| I125+ Undefined external error.
vcpu-1| I125: [msg.pciSound.HostOpenDspChannelFailed] Sound will be disconnected.
How to fix?
↧
↧
Re: VXLAN in NSX
VXLAN provides the capability to create isolated, multi-tenant broadcast domains across data center fabrics, and enables us to create elastic, logical networks that span physical network boundaries . Basically It encapsulates original packets into a new header (VXLAN), however from a workload perspective you won't see any difference. It's not mandatory to use VXLAN in a NSX design. I would suggest go through NSX documentation and Network and Security Virtualization Software Platform - NSX | VMware to know about various uses cases and design aspects.
↧
Re: no sound on vm
↧
Logical Switch
1- Do we have to use a logical switch?
2- what are Differences between a logical switch and a port group?
3- If we have to create logical switches, what do we do with the previous port groups that exist on VDS?
4- Can we use a port group as a logical switch?
↧
↧
Re: The file specified is not a virtual disk
hi AP,
i am new to Vmware and I am having the same issue that you helped resolve for another users on this site. i was hoping you can help me as well? i read your response but am new and could not make much of it, for now.
am actually having 2 problems but lets starts with this one
regards
and yeah , happy Easter .
↧
Re: Не удается отредактировать USB-устройства на перенесенной ВМ - ESXi 6.5
Не рискнул удаленно ставить патчи - если что-то пойдет не так - сервер просто нечем будет сейчас подменить - офис закрыт на карантин. Что странно и вряд ли, как мне кажется, связано с версией релиза хоста - вот создаешь машину на базе любой Windows - нормально устанавливается, сеть определяется, все нормально. Стоит только добавить USB-контроллер (неважно, 2.0 или 3.0) и навесить на него любое устройство - машина при старте вешает весь Веб-интефейс и тупит так, пока ее принудительно не выключишь. Во всяком случае, я не смог дождаться загрузки такой машины. И даже если зайти в конфигурацию и попытаться удалить USB-устройство - оно вроде как удалится, но останется на месте. Не решается никак. Только сносом такой машины. Ранее такого бага не было. Ну не могут же все USB-устройства сразу на всех портах начать глючить?
Updated: Вывод команды lsusb:
Bus 003 Device 007: ID 0557:2419 ATEN International Co., Ltd
Bus 003 Device 006: ID 0557:7000 ATEN International Co., Ltd Hub
Bus 003 Device 005: ID 0a89:0003
Bus 003 Device 004: ID 1058:25e7 Western Digital Technologies, Inc.
Bus 003 Device 002: ID 8087:8002 Intel Corp.
Bus 002 Device 002: ID 8087:800a Intel Corp.
Bus 003 Device 001: ID 0e0f:8002 VMware, Inc.
Bus 002 Device 001: ID 0e0f:8002 VMware, Inc.
Bus 001 Device 001: ID 0e0f:8003 VMware, Inc.
Видно, что отсутствует ID на порту с флешкой. То есть она вышла из строя?
↧
Re: SRM Placeholder Datastores
It depend on how your Storage provide shared LUNs to all clusters. Example: You have 10 clusters and each set of clusters esxi hosts having different storage group from storage side to provide luns to cluster. I Would suggest you to create placeholder Datastore on cluster wise if you want specific prod cluster vms to be protect to specific cluster at DR site.
↧
Re: VMFS and VMFSL in ESXi 7 - what is the difference ?
Is this link may help you.Virtual Maestro: Disk partition layout for ESXi in vSphere 7
↧
↧
Re: Logical Switch
It may help you if you talking about NSX and VDS. Logical Switch vs Distributed Switch
↧
Inclusión driver en ISO ESXi 7.0 usando ESXi-Customizer
He modificado la versión 2.6.0 del script ESXi-Customizer-PS para incluir la versión 7.0. Y he renombrado la versión a la 2.7.0
Al añadir el driver net -6168 me da un error en la inclusión del driver que no se como solucionar. El error es el siguiente:
PS D:\intercambios> .\ESXi-Customizer-PS-v2.7.0.ps1 -v70 -load net-r8168
This is ESXi-Customizer-PS Version 2.7.0 (visit https://ESXi-Customizer-PS.v-front.de for more information!)
(Call with -help for instructions)
Logging to C:\Users\Jesus\AppData\Local\Temp\ESXi-Customizer-PS-6020.log ...
Running with PowerShell version 5.1 and VMware PowerCLI version 12.0.0.15939655
Connecting the VMware ESXi Online depot ... [OK]
Getting Imageprofiles, please wait ... [OK]
Using Imageprofile ESXi-7.0.0-15843807-standard ...
(dated 03/16/2020 10:48:54, AcceptanceLevel: PartnerSupported,
The general availability release of VMware ESXi Server 7.0.0 brings whole new levels of virtualization performance to datacenters and enterprises.)
Load additional VIBs from Online depots ...
Add VIB net-r8168 8.013.00-3vmw.510.0.0.799733 [OK, added]
Exporting the Imageprofile to 'D:\intercambios\ESXi-7.0.0-15843807-standard-customized.iso'. Please be patient ...
ADVERTENCIA: The image profile fails validation. The ISO / Offline Bundle will still be generated but may contain
errors and may not boot or be functional. Errors:
ADVERTENCIA: VIB VMware_bootbank_net-r8168_8.013.00-3vmw.510.0.0.799733 requires com.vmware.driverAPI-9.2.1.0, but
the requirement cannot be satisfied within the ImageProfile. However, additional VIB(s)
VMware_bootbank_misc-drivers_5.5.0-3.78.3248547, VMware_bootbank_misc-drivers_5.5.0-1.28.1892794,
VMware_bootbank_misc-drivers_5.1.0-3.50.2323236, VMware_bootbank_misc-drivers_5.5.0-2.33.2068190,
VMware_bootbank_misc-drivers_5.5.0-2.54.2403361, VMware_bootbank_misc-drivers_6.0.0-3.79.6921384,
VMware_bootbank_misc-drivers_6.0.0-0.11.2809209, VMware_bootbank_misc-drivers_6.0.0-3.69.5572656,
VMware_bootbank_misc-drivers_5.1.0-1.12.1065491, VMware_bootbank_misc-drivers_5.1.0-1.20.1312873,
VMware_bootbank_misc-drivers_5.5.0-3.68.3029944, VMware_bootbank_misc-drivers_6.0.0-1.26.3380124,
VMware_bootbank_misc-drivers_6.0.0-3.129.14513180, VMware_bootbank_misc-drivers_6.0.0-3.57.5050593,
VMware_bootbank_misc-drivers_6.0.0-2.34.3620759, VMware_bootbank_misc-drivers_5.5.0-3.89.4179633,
VMW_bootbank_shim-vmklinux-9-2-1-0_6.5.0-0.0.4564106, VMware_bootbank_misc-drivers_6.0.0-2.43.4192238,
VMware_bootbank_misc-drivers_5.5.0-2.39.2143827, VMware_bootbank_misc-drivers_5.1.0-1.16.1157734,
VMware_bootbank_misc-drivers_6.0.0-3.104.9919195, VMware_bootbank_misc-drivers_6.0.0-2.52.4600944,
VMware_bootbank_misc-drivers_5.5.0-3.95.4345813, VMware_bootbank_misc-drivers_6.0.0-3.96.9239799,
VMware_bootbank_misc-drivers_5.1.0-0.0.799733, VMware_bootbank_misc-drivers_5.1.0-2.23.1483097,
VMware_bootbank_misc-drivers_5.5.0-0.0.1331820, VMware_bootbank_misc-drivers_5.1.0-2.44.2191751,
VMware_bootbank_misc-drivers_5.1.0-3.55.2583090, VMware_bootbank_misc-drivers_5.1.0-1.19.1312874,
VMware_bootbank_misc-drivers_5.5.0-0.7.1474526, VMware_bootbank_misc-drivers_6.0.0-0.0.2494585,
VMW_bootbank_shim-vmklinux-9-2-1-0_6.7.0-0.0.8169922, VMware_bootbank_misc-drivers_6.0.0-1.17.3029758,
VMware_bootbank_misc-drivers_5.5.0-2.62.2718055, VMware_bootbank_misc-drivers_6.0.0-3.107.10474991 from depot can
satisfy this requirement.
ADVERTENCIA: VIB VMware_bootbank_net-r8168_8.013.00-3vmw.510.0.0.799733 requires vmkapi_2_1_0_0, but the requirement
cannot be satisfied within the ImageProfile. However, additional VIB(s) VMware_bootbank_esx-base_5.5.0-3.71.3116895,
VMware_bootbank_esx-base_5.5.0-2.42.2302651, VMware_bootbank_esx-base_5.5.0-2.33.2068190,
VMware_bootbank_esx-base_5.1.0-2.27.1743201, VMware_bootbank_esx-base_6.5.0-1.33.7273056,
VMware_bootbank_esx-base_5.1.0-0.10.1021289, VMware_bootbank_esx-base_6.5.0-2.54.8935087,
VMware_bootbank_esx-base_6.5.0-0.15.5224529, VMware_bootbank_esx-base_5.5.0-3.68.3029944,
VMware_bootbank_esx-base_6.0.0-2.37.3825889, VMware_bootbank_esx-base_6.5.0-1.47.8285314,
VMware_bootbank_esx-base_6.0.0-1.29.3568940, VMware_bootbank_esx-base_6.0.0-3.96.9239799,
VMware_bootbank_esx-base_5.5.0-3.117.8934887, VMware_bootbank_esx-base_6.0.0-3.87.8934903,
VMware_bootbank_esx-base_6.5.0-0.19.5310538, VMware_bootbank_esx-base_5.1.0-2.35.2000251,
VMware_bootbank_esx-base_6.0.0-3.76.6856897, VMware_bootbank_esx-base_6.5.0-3.108.14990892,
VMware_bootbank_esx-base_6.0.0-2.49.4558694, VMware_bootbank_esx-base_5.5.0-3.100.4722766,
VMware_bootbank_esx-base_5.1.0-2.26.1612806, VMware_bootbank_esx-base_5.5.0-2.65.3029837,
VMware_bootbank_esx-base_5.5.0-3.107.7618464, VMware_bootbank_esx-base_5.5.0-0.15.1746974,
VMware_bootbank_esx-base_6.5.0-2.75.10884925, VMware_bootbank_esx-base_6.0.0-3.66.5485776,
VMware_bootbank_esx-base_5.5.0-1.18.1881737, VMware_bootbank_esx-base_6.5.0-2.67.10719125,
VMware_bootbank_esx-base_5.5.0-3.101.5230635, VMware_bootbank_esx-base_6.5.0-0.0.4564106,
VMware_bootbank_esx-base_6.0.0-3.84.7967664, VMware_bootbank_esx-base_5.1.0-1.20.1312873,
VMware_bootbank_esx-base_5.5.0-3.124.9919047, VMware_bootbank_esx-base_6.5.0-3.116.15256468,
VMware_bootbank_esx-base_5.1.0-3.85.3872664, VMware_bootbank_esx-base_6.0.0-3.100.9313334,
VMware_bootbank_esx-base_5.5.0-3.97.4756874, VMware_bootbank_esx-base_6.5.0-1.41.7967591,
VMware_bootbank_esx-base_6.5.0-0.23.5969300, VMware_bootbank_esx-base_5.5.0-2.39.2143827,
VMware_bootbank_esx-base_5.1.0-1.16.1157734, VMware_bootbank_esx-base_5.5.0-0.14.1598313,
VMware_bootbank_esx-base_6.0.0-2.40.4179598, VMware_bootbank_esx-base_6.0.0-2.46.4510822,
VMware_bootbank_esx-base_6.5.0-2.79.11925212, VMware_bootbank_esx-base_5.5.0-1.30.1980513,
VMware_bootbank_esx-base_5.5.0-2.59.2702869, VMware_bootbank_esx-base_6.0.0-3.93.9239792,
VMware_bootbank_esx-base_6.0.0-2.54.5047589, VMware_bootbank_esx-base_5.1.0-0.11.1063671,
VMware_bootbank_esx-base_5.1.0-2.29.1900470, VMware_bootbank_esx-base_5.5.0-3.84.3568722,
VMware_bootbank_esx-base_5.1.0-1.12.1065491, VMware_bootbank_esx-base_5.5.0-3.106.6480324,
VMware_bootbank_esx-base_5.5.0-3.114.7967571, VMware_bootbank_esx-base_6.0.0-0.5.2615704,
VMware_bootbank_esx-base_6.0.0-1.31.3568943, VMware_bootbank_esx-base_5.5.0-3.120.9313066,
VMware_bootbank_esx-base_6.0.0-1.22.3247720, VMware_bootbank_esx-base_6.0.0-2.34.3620759,
VMware_bootbank_esx-base_5.5.0-3.75.3247226, VMware_bootbank_esx-base_5.1.0-1.22.1472666,
VMware_bootbank_esx-base_6.0.0-1.17.3029758, VMware_bootbank_esx-base_5.1.0-3.52.2575044,
VMware_bootbank_esx-base_5.1.0-2.32.1904929, VMware_bootbank_esx-base_5.5.0-3.78.3248547,
VMware_bootbank_esx-base_6.0.0-3.145.15517548, VMware_bootbank_esx-base_5.1.0-0.0.799733,
VMware_bootbank_esx-base_5.1.0-2.28.1743533, VMware_bootbank_esx-base_5.5.0-0.0.1331820,
VMware_bootbank_esx-base_5.5.0-0.8.1474528, VMware_bootbank_esx-base_6.5.0-3.105.14874964,
VMware_bootbank_esx-base_5.1.0-0.5.838463, VMware_bootbank_esx-base_5.5.0-3.92.4345810,
VMware_bootbank_esx-base_6.0.0-3.116.13635687, VMware_bootbank_esx-base_6.5.0-1.26.5969303,
VMware_bootbank_esx-base_5.1.0-0.8.911593, VMware_bootbank_esx-base_6.0.0-1.26.3380124,
VMware_bootbank_esx-base_6.5.0-2.83.13004031, VMware_bootbank_esx-base_6.0.0-3.57.5050593,
VMware_bootbank_esx-base_5.1.0-1.13.1117900, VMware_bootbank_esx-base_5.1.0-3.57.3021178,
VMware_bootbank_esx-base_5.1.0-3.55.2583090, VMware_bootbank_esx-base_5.1.0-1.19.1312874,
VMware_bootbank_esx-base_6.0.0-3.110.10719132, VMware_bootbank_esx-base_6.5.0-3.120.15256549,
VMware_bootbank_esx-base_5.5.0-2.58.2638301, VMware_bootbank_esx-base_5.5.0-3.89.4179633,
VMware_bootbank_esx-base_5.1.0-2.23.1483097, VMware_bootbank_esx-base_6.5.0-3.101.14320405,
VMware_bootbank_esx-base_6.0.0-0.11.2809209, VMware_bootbank_esx-base_6.0.0-3.72.6765062,
VMware_bootbank_esx-base_5.5.0-1.16.1746018, VMware_bootbank_esx-base_5.5.0-1.15.1623387,
VMware_bootbank_esx-base_6.0.0-3.125.14475122, VMware_bootbank_esx-base_5.5.0-2.51.2352327,
VMware_bootbank_esx-base_5.5.0-2.54.2403361, VMware_bootbank_esx-base_5.5.0-3.103.6480267,
VMware_bootbank_esx-base_5.1.0-2.47.2323231, VMware_bootbank_esx-base_5.1.0-3.50.2323236,
VMware_bootbank_esx-base_6.0.0-2.52.4600944, VMware_bootbank_esx-base_6.5.0-2.92.13873656,
VMware_bootbank_esx-base_6.0.0-3.138.15169789, VMware_bootbank_esx-base_5.5.0-1.28.1892794,
VMware_bootbank_esx-base_6.0.0-3.107.10474991, VMware_bootbank_esx-base_5.1.0-1.15.1142907,
VMware_bootbank_esx-base_6.0.0-1.20.3073146, VMware_bootbank_esx-base_5.1.0-0.9.914609,
VMware_bootbank_esx-base_6.5.0-2.57.9298722, VMware_bootbank_esx-base_6.5.0-2.50.8294253,
VMware_bootbank_esx-base_6.5.0-2.71.10868328, VMware_bootbank_esx-base_5.5.0-2.36.2093874,
VMware_bootbank_esx-base_6.5.0-0.14.5146846, VMware_bootbank_esx-base_6.0.0-3.69.5572656,
VMware_bootbank_esx-base_5.5.0-3.86.4179631, VMware_bootbank_esx-base_5.5.0-1.25.1892623,
VMware_bootbank_esx-base_6.0.0-2.43.4192238, VMware_bootbank_esx-base_6.0.0-3.79.6921384,
VMware_bootbank_esx-base_6.0.0-0.14.3017641, VMware_bootbank_esx-base_6.0.0-1.23.3341439,
VMware_bootbank_esx-base_6.0.0-3.58.5224934, VMware_bootbank_esx-base_6.5.0-0.11.5146843,
VMware_bootbank_esx-base_6.5.0-1.29.6765664, VMware_bootbank_esx-base_6.0.0-0.0.2494585,
VMware_bootbank_esx-base_5.1.0-2.41.2191354, VMware_bootbank_esx-base_5.5.0-3.95.4345813,
VMware_bootbank_esx-base_5.1.0-2.44.2191751, VMware_bootbank_esx-base_6.5.0-0.9.4887370,
VMware_bootbank_esx-base_6.0.0-0.6.2715440, VMware_bootbank_esx-base_5.1.0-3.60.3070626,
VMware_bootbank_esx-base_6.0.0-3.129.14513180, VMware_bootbank_esx-base_6.5.0-3.96.13932383,
VMware_bootbank_esx-base_6.5.0-3.111.15177306, VMware_bootbank_esx-base_6.5.0-2.88.13635690,
VMware_bootbank_esx-base_5.5.0-2.62.2718055, VMware_bootbank_esx-base_5.5.0-0.7.1474526,
VMware_bootbank_esx-base_6.5.0-1.36.7388607, VMware_bootbank_esx-base_5.5.0-2.55.2456374,
VMware_bootbank_esx-base_6.0.0-3.113.13003896, VMware_bootbank_esx-base_6.0.0-0.8.2809111,
VMware_bootbank_esx-base_6.0.0-3.135.15018929, VMware_bootbank_esx-base_6.5.0-2.64.10390116,
VMware_bootbank_esx-base_5.5.0-3.81.3343343, VMware_bootbank_esx-base_6.5.0-2.61.10175896,
VMware_bootbank_esx-base_5.1.0-3.82.3872638 from depot can satisfy this requirement.
An unexpected error occured:
[WinError 10054] Se ha forzado la interrupci??n de una conexi??n existente por el host remoto
If requesting support please be sure to include the log file
C:\Users\User\AppData\Local\Temp\ESXi-Customizer-PS-6020.log
PS D:\intercambios>
↧
Re: The file specified is not a virtual disk
Welcome to the Community,
issues like this may look similar, but are often very different.
Did something happen that may have caused the issue?
To start with, please run dir *.* /one > filelist.txt in the VM's folder, compress/zip filelist.txt, *.vmx, *.vmsd, *.log, and attach the resulting .zip archive to your next reply.
André
Moderator note: I branched your reply to a 7 years old discussion to a new one.
↧
Intel Turbo Boost on ESXi/vSphere6.7 With 2xE52630v2 In Dell R720
Hi,
I have a Dell R720 with a pair of Intel Xeon E5-2630v2s. They have a base speed of 2.6GHz and a max turbo clock of 3.1Ghz. IDRAC shows Intel turbo boost as enabled. However vSphere web client says CPU total power is 31.19 GHz, which when divided by the core count (12) returns 2.6GHz. Furthermore, all VMs show 2.6GHz under both load and idle. How can I ensure that turbo is enabled as some of my VMs really need that extra clock for some gaming servers we are hosting for the next few months.
Many thanks in advance,
James Conway
t: 07775268635
↧
↧
Re: How to upgrade VCSA 6.5 U3h (build 15679215) to 6.7
I'm in the same boat with some of my cusomer's environments. Options are basically to wait for a supported v6.7 update/patch, or to go to v7.0 after verifying that this is a supported upgrade path, and that any 3rd party tools support that version as well.
André
↧
Re: VMFS and VMFSL in ESXi 7 - what is the difference ?
VMFSL (VMFS-Local) is actually not new. IIR it was first introduced with vSAN, and one of the main differences it that it is sues as a local file system, i.e. only accessed by a single host, and therefore doesn't require the same locking mechanisms as a shred file system.
What I can't tell you, is why VMware decided to consume up to 120GB disk space for the VMFSL partition for new installation, and doesn't allow to create VMs on it. Well, sure the files in that partition should be protected from accidental modifications, but still, why 120GB?
André
↧
security advice
vmware reported security advice. I use vcenter 6.5 u2 and esxi 6.5 u2. Do I need to make any updates or changes to the infrastructure I use?
↧
Re: The system cannot find the file specified.
Welcome to the Community,
one of the files "...-000007-s007.vmdk" is missing. Unless you have a backup, you may try to replace it with a copy of "-000007-s016.vmdk". This won't of course bring back missing data, but should allow to open the virtual disk, to access, and backup important data.
Note: Before powering on the VM after replacing the missing file, please create another snapshot, so that you can always revert to the current state if required!
André
↧
↧
Re: security advice
You posted a link to the article so I assumed you read it, but apparently not.
↧
Re: security advice
I'm sorry. I couldn't understand exactly what I needed and I wanted to make sure. so I don't need to take any action or any update on my VMware infrastructure. is not it?
vCenter 6.5 systems are not affected.
thanks for helping.
↧
Re: VMFS and VMFSL in ESXi 7 - what is the difference ?
This is a topic I am curious about
↧