I’m trying to enable virtualization on my Windows 10 VM so I can use Docker WSL2.

Docker gives me this error:

“Please enable the Virtual Machine Platform Windows feature and ensure virtualization is enabled in the BIOS.”

When I enter the Windows 10 VM BIOS I don’t get the UEFI page, I get an old looking EFI page (image attached).

From here I cannot seem to enable virtualization.

My ESXI settings for the Windows 10 VM are set to:

Windows 10 VM:

    VM Options:

       Boot Options:

           EFI (selected)

           Enable UEFI secure boot (checked)

Any guidance on this would be much appreciated.

Hello there.

I am trying to create vmk intarfaces with New-VMHostNetworkAdapter cmlet, but gettin the error “DistributedVirtualSwitchInfo with id 50 02 5a 5c 8c fc 30 be-15 99 73 74 7d 87 b7 37′ does not exist.”

I’ve tried to specify vDS name in the cmdlet, tried to specify the variable, in which the switch object was stored (the result of Get-VirtualSwitch and Get-VDSwitch cmdlets), but still no luck.

Furthermore, the vDS key is the same, vCenter is complaining about:

PS C:Windowssystem32> $vswitch.key

50 02 5a 5c 8c fc 30 be-15 99 73 74 7d 87 b7 37

What is the problem?

I try to add a LUN as a new Datastore, provided from a HPE MSA 2040 SAS, using a HPE 241 SAS HBA to a vSphere 6.7 System.

The HW is a HPE Proliant 380 Gen9 Server. The MSA2040 is direct attached using SAS Controllers.

The LUN is available in the MSA Utility Software and shown in the “Add Datastore” Wizard as expected.

But during the “Add Datastore” procedure, I get the error “Cannot change the host configuration”.

Please find below the summary details of the “Add Datastore” Wizard:

General

Name: MSA2040VDISKA

Type: VMFS

Datastore size: 2.64 TB

Device and Formatting

Disk/LUN: HP Serial Attached SCSI Disk (naa.600c0ff0001e3b26fc879d5f01000000)

Partition Format: GPT

VMFS Version: VMFS 6

Block Size: 1 MB

Space Reclamation Granularity: 1 MB

Space Reclamation Priority Low: Deleted or unmapped blocks are reclaimed on the LUN at low priority

Looking to the device on the ESX Console, is not showing any existing partition on this LUN:

[root@HCDORDEVOPSENP1:~] partedUtil getptbl /vmfs/devices/disks/naa.600c0ff0001e3b26fc879d5f01000000

unknown

352571 255 63 5664055296

Does anyone know how to troubleshoot this error?

Is anyone may be able to help or point me to the root cause of this error?

Thank you in advance.

Kind regards Bernd

Hello friends,

I’m currently working on trying to migrating virtual machines to a new datacenter. Networks are identical (stretched) in both datacenters but we have to do a svmotion to move between them.

I’ve cobbled together a powercli script from various sources that basically imports today selected VM’s through a CSV, then cycles through it while spawning new Move-VM’s once the running sessions is under a predefined threshold. But, I’m running into issues with migrating systems that are on standard switches over to distributed switched. Port group names are all identical, so I figured I could just use the name element in the destinations port group. It seems to have worked ok on system with a single nic, but I started running into issues with multiple nics.

I ran across an article by Kyle Ruddy – Spotlight on the Move-VM Cmdlet including PowerCLI 6.5 Enhancements that showed you can pipe arrays. I also found an article that LucD was helping on which was more recent, move-vm script placing port groups on wrong adapters for VMs with multiple nics but have still been unable to resolve my issues.

Snipped of code for picking the network adapter:

      # Pick target port group based on source port group name. Cycle through for multiple network adapters

      $NetworkAdapter = Get-NetworkAdapter -vm $vm

      $targetpg = @()

      $NetworkAdapter.count | foreach-object {

      $targetpg += Get-VDPortgroup -name $NetworkAdapter.networkname

   }

Move VM command:

Move-VM -VM $vm `

      -Destination $DestinationHost `

      -NetworkAdapter $NetworkAdapter `

      -PortGroup $targetpg  `

      -Datastore (Get-DatastoreCluster -Name $DestinationDatastore | Get-Datastore | Sort-Object -Property FreeSpaceGB -Descending | Select -First 1) `

      -RunAsync -Confirm:$false

But when I am currently getting the following error:

Move-VM : 10/31/2020 2:12:56 PM Move-VM A specified parameter was not correct: RelocateSpec

At line:1 char:1

+ Move-VM -VM $vm `

+ ~~~~~~~~~~~~~~~~~

+ CategoryInfo          : NotSpecified: (:) [Move-VM], VimException

+ FullyQualifiedErrorId : Core_BaseCmdlet_UnknownError,VMware.VimAutomation.ViCore.Cmdlets.Commands.MoveVM

I tried using the sdk method but never could get it to work with standard switch moves. 

Any insight or help would be much appreciated. Thanks!!

i just upgraded a fedora 32 guest to fedora 33.  the v32 guest was working flawlessly.  the in-place upgrade was smooth.  but the v33 guest is a *disaster*.  so many KDE programs fail or crash it is hard to decide what to report and to whom to report it.  it appears to be running plasma v5.19.  anyone else run into this problem?  i tried a gnome session but didn’t push it very hard.  i didn’t see any problems though. 

/mark

I have installed vSphere with Kubernetes according to the blog below.

http://darrylcauldwell.com/vsphere-k8s/

In my case everthing is running in nested ESXi.

All seems to be running fine in vCenter and NSX-T.

However I am not able to download the CLI Tools from the namespace with a browser.

With telnet I can see that something is listening on the ip-address and port 443 but that is all.

Also with curl I do not get a response.

The Administrator user has been given edit rights to the namespace.

Does anyone has a clue or a suggestion to look further into it?

i created new two vm with vcenter 6.6

and i turned on two vms.

but in vcenter,  vsphere web client show me  [a general system error occurred. connection refused]

so i tried again but failed.

Fortunately I could turn on the power manually in esxi.

So what is the cause of this problem and what is the solution?

Hi;

I am a Redhat newbie by ANY stretch of the imagination and I was given and accepted the challenge of virtualizing our existing RedHat installation (ver. 5.11)…YES I know it is super old…but the hardware is dying so it is more important to get it off there first….to that end; I used the VMware converter tool which seems to work fine until the very end   97%…and then it fails….I then boot up with “No Operating System found”…even a dummy like me realizes that it is looking for the grub loader in the boot partition but I am clearly too stupid to understand the myriad of ways that people are tossing around to deal with it….I have found numerous articles about the same thing…sort of….but I still have NO idea how to fix it.

I recently tried this but when I try to access the directory they are referring to with vim…there is nothing there…so that is yet another dead end.

VMware P2V Linux Conversion – The Essential Methods

FAILED: An error occurred during the conversion: ‘GrubInstaller::InstallGrub: /usr/lib/vmware-converter/installGrub.sh failed with return code: 0, and message: Installing GRUB1 on (hd0)… GNU GRUB version 0.97 (640K lower / 3072K upper memory) [ Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists the possible completions of a device/filename.] grub> root (hd0,0) Filesystem type is ext2fs, partition type 0x83 grub> setup (hd0) Checking if “/boot/grub/stage1” exists… no Checking if “/grub/stage1” exists… yes Checking if “/grub/stage2” exists… yes Checking if “/grub/e2fs_stage1_5” exists… yes Running “embed /grub/e2fs_stage1_5 (hd0)”… 15 sectors are embedded. succeeded Running “install /grub/stage1 (hd0) (hd0)1+15 p (hd0,0)/grub/stage2 /grub/grub.conf”… failed Error 6:

Mismatched or corrupt version of stage1/stage2 grub> ‘

Could someone PLEASE give me precise instruction on what I can do to fix this and explain it as if you were talking to a 10 year old?

Thank you!!

Hi,

When having multiple FC HBA adapters/ports connecting to SAN storage and you lose SAN datastore heartbeats/Lost access to storage messages.

Are these messages per HBA/port meaning if one of the paths is down these messages get logged and I/O traffic goes via other HBA/port?

Or for these messages to get logged there needs to be both HBA adapters/ports with connectivity issue to storage?

Are heartbeats sent from each HBA/port towards SAN storage?

Thanks

I have VMWare Workstation Workstation Player 16 installed and have been considering upgrading to Workstation 16 Pro. I can’t seem to find these questions answered on the FAQ or anything on the page.

If I go to into the Workstation Player > Help > Upgrade to VMWare Workstation Pro I get 3 options. New, Upgrade From Workstation Pro or Player 14 or Greater, Upgrade from Workstation 16 Player. Whats the difference and which one should I get? Im using Player 16 the Free version as it’s just for personal use. Which one

Second question is how long does this license last and what happens to my license if/when they move to version 17?