CarltonR Tracker

Re: Windows Server 2003 Entrprise R2 random BSoD

CarltonR — Fri, 27 Oct 2023 10:14:15 GMT

@wxlmalanis wrote: . . . I installed Windows Server 2003 R2 Enterprise 23 bit . . .

Running a '23 bit' operating system might be a issue !

On a more serious note:

- is the Win Svr 2003 Ent x32 source image legitimate and verifiable, i.e. checksum validated

- how much memory resources have you allocated to the VM

- have you tried to install the x64 version ?

As a starting point may I suggest searching this forum for the 0x0000007F error, as there is plethora of invaluable information regards this . . . starting with Windows 2003 bluescreen

Note: On a cautionary note, as this operating system is unsupported, It may be unwise to present it to an 'open' network.

Re: Laptop Lid Power Settings in VM

CarltonR — Wed, 18 Oct 2023 20:23:52 GMT

Refer . . .

Make a Virtual Machine Think it's a Laptop

Re: Static IP

CarltonR — Fri, 06 Oct 2023 15:06:50 GMT

Somewhat confusing . . .

- when you say "static IP address with the exact same details" would that include the DHCP allocated IP address of the new server. This IP address should be outside of the DHCP allocated range, but within the same subnet.

- Just to clarify, is this 'new server' a VMware Workstation Host or a VM ?

Re: Clipboard does not work in built-in VNC in VMware Workstation Pro.

CarltonR — Wed, 04 Oct 2023 20:36:34 GMT

I assume that when you say 'built-in' you mean 'VM > Settings, Options tab and select VNC Connections'.

If this is the case then the following restrictions apply:

When you use a VNC client to connect to a virtual machine, some features do not work or are not available.

You cannot take or revert to snapshots.
You cannot power on, power off, suspend, or resume the virtual machine. You can shut down the guest operating system. Shutting down might power off the virtual machine.
You cannot copy and paste text between the host system and the guest operating system.
You cannot change virtual machine settings.
Remote display does not work well if you are also using the 3D feature.

[https://docs.vmware.com/en/VMware-Workstation-Pro/17/com.vmware.ws.using.doc/GUID-FB23927B-98A0-45E9-BFAC-85152F14BCAC.html]

Re: when I try to start my Windows11 Pro VMs I get a message stating -This virtual machine is encryp

CarltonR — Tue, 03 Oct 2023 10:50:19 GMT

You might like to refer to these, for starters . . .

Windows 11 VM encrypted after password change on host (2023-09-21)

Unable to recover Windows 11 VM (2023-09-11)

What Password does a Win 11 VM need to run on a different host? (2022-09-04

Windows 11 VM asking for encryption key after host updates (2022-03-09)

What is the default encryption password for virtual TPM? (2022-07-19)

VM encrypted itself, don't know the password (2021-10-28)

Re: One guest vm is not auto starting

CarltonR — Sun, 01 Oct 2023 09:55:15 GMT

It would be useful if you could provided more information on what investigation, diagnostics, and research you have undertaken.

Re: Can't install ESXI 8.0 on HP ML350 (SAS disk not found)

CarltonR — Sun, 01 Oct 2023 15:42:53 GMT

Not sure if this is relevant in your case . . .

HPE Smart Array SR GEN10 Controller Remediation Guide

HPE received notification of a manufacturer firmware issue potentially affecting certain HPE Smart Array SR Gen10 controllers that require a firmware update to ensure the controllers continue to function properly. As part of our commitment to support our customers, and help simplify the firmware update process, HPE provides this dedicated Remediation Guide to ensure our customers have 24/7 access to the information and tools they need to both identify and quickly remediate potentially affected HPE Smart Array SR Gen10 controller firmware in real-time.

. . .

How Do I Resolve (Fix) the HPE Smart Array SR Gen10 Controller Issues?
HPE has developed the following remediation program to help customers identify and proactively update the firmware on potentially affected HPE Smart Array SR Gen10 controllers. HPE strongly recommends customers with potentially affected HPE Smart Array SR Gen10 controllers download and install the HPE Smart Array SR Gen10 Firmware Version 3.00 even for RAID configurations that are not specifically identified as potentially affected.

Access to HPE Smart Array SR Gen10 Controller Firmware Version 3.00, along with complete instructions on how to manage the remediation process, are provided in the platform specific HPE Customer Bulletins below:

HPE Server and Storage Customer Bulletin

HPE SimpliVity Customer Bulletin

Important Note
On HPE Gen10/Gen10 Plus platforms with certain HPE Smart Array SR Gen10 controllers, if controller firmware version 2.03 (or earlier) is updated to v2.62 (or later), logical drives may become inaccessible. This issue occurs when there are multiple SmartCache logical drives configured on a single SmartCache Array (512e SSD). For detailed information regarding how to regain access to logical drives and data, or the future Smart Array SR Gen10 controller firmware version that will resolve this issue, refer to the HPE Customer Bulletin.

[https://www.hpe.com/us/en/servers/server-storage/firmware-update-gen10-controllers.html]

Re: Can't install ESXI 8.0 on HP ML350 (SAS disk not found)

CarltonR — Sat, 30 Sep 2023 20:54:31 GMT

Out of curiosity have you referred to:

VMware Compatibility Guide [HPE Smart Array P408i-a SR Gen10]

https://www.vmware.com/resources/compatibility/detail.php?deviceCategory=vsanio&productid=41777

and

Solved: Re: HP Proliant ML350Gen10 no disk during installation

[note: some of the links in the solution have expired]

Re: Cannot boot ESXi host in nested

CarltonR — Sun, 17 Sep 2023 10:19:02 GMT

May I suggest that you search this forum as there is a plethora of information regarding the 'Virtualized Intel VT-x/EPT is not supported' error message.

Re: Workstation 17 Pro Error capacity mismatch for disk

CarltonR — Fri, 08 Sep 2023 09:35:42 GMT

Assuming that your moving from VirtualBox, then may I suggest referring to:

OVF format: import from VirtualBox-4.3 to VMware (VMware Technology Network)

Moving Virtual Machines Between VIrtualBox and VMware (morethanfootnotes.blogspot.com)

How to Migrate a VM from VirtualBox 4.3 to VMware Workstation 11 (eigenmagic)

Re: on-board bluetooth adatper is not working on guest

CarltonR — Wed, 06 Sep 2023 10:34:03 GMT

Did you follow the link provided previously . . . and is VMware Tools installed within the VM ?

setup VMware Tools in Linux, as sudo:

apt remove open-vm-tools-desktop open-vm-tools

apt install open-vm-tools-desktop open-vm-tools

Re: on-board bluetooth adatper is not working on guest

CarltonR — Wed, 06 Sep 2023 10:28:54 GMT

First things first, I'm assuming that the Host operating system is windows based, so:

- check the Device Manager for the Bluetooth device/s, make sure they are working and take note of the type;

- Within the VMware Workstation Virtual Machine Settings, check that the USB Controller is Present and setup correctly.

. . . then refer: Sharing Bluetooth devices with a virtual machine (2005315)

Re: Unable to install VMware Tools (several warning and error messages then guest windows 7 hung)

CarltonR — Mon, 04 Sep 2023 15:41:36 GMT

. . . either:

- copy the KB4474419 file you downloaded on the Win 11 Host to an external USB drive, once done, within VMware Player move the USB drive to the Win 7 VM, and copy/run.

- On the Win 7 VM download Microsoft

Microsoft Win 7 [x64] KB4474419

Microsoft Win 7 [x32] KB4474419

Note: Then suggest disabling the Win 7 VM's Network Interface, it's old, out-of-support, and vulnerable !

Re: Updated Host BIOS - Now All VM ask for password

CarltonR — Sat, 26 Aug 2023 10:16:34 GMT

Assuming that the only thing that was changed was the BIOS on the Host . . . then . . .

i. does the host have a TPM ?

ii. If so, then suggest verifying that within the BIOS, it's enabled.

iii. Confirm that it is available and working within Host [Win 11] Device Manager under Security devices - Trusted Platform Module 2.0

iv. would also suggest that you review the associated documentation for the 'BIOS' update, to confirm prerequisites and whether it included an TPM update.

v. When you say "default options were selected when setup" please expand.

Re: Use kvm utility to start in full screen on two monitors

CarltonR — Sat, 19 Aug 2023 09:50:26 GMT

Refer these articles:

Use Multiple Monitors for One Virtual Machine
https://docs.vmware.com/en/VMware-Workstation-Pro/17/com.vmware.ws.using.doc/GUID-E51CADFC-31C3-491F-92D9-C9C1D9615668.html

Use Multiple Monitors for One Virtual Machine in Workstation Player
https://docs.vmware.com/en/VMware-Workstation-Player-for-Windows/17.0/com.vmware.player.win.using.doc/GUID-59039700-F5A1-4A58-ADB0-6F6500ADC6C0.html

Limitations for Multiple Monitors
https://docs.vmware.com/en/VMware-Workstation-Player-for-Windows/17.0/com.vmware.player.win.using.doc/GUID-C1315BDC-324B-4D0B-8F05-F7B20B97076F.html

Re: How to determine which Network Addressing Authority identifier (NAA) is attach to which ESXi hos

CarltonR — Fri, 18 Aug 2023 20:56:17 GMT

May I suggest that you review the following articles and forum submission . . .

Identifying disks when working with VMware ESXi (1014953)
https://kb.vmware.com/s/article/1014953

Storage Device Names and Identifiers
https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.storage.doc/GUID-A36810F4-00EC-4EA8-A242-2A0DBBF56731.html

From NAA ID to get the Mapped Host information
https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/From-NAA-ID-to-get-the-Mapped-Host-information/td-p/1863334

Re: Wake on LAN not work

CarltonR — Wed, 09 Aug 2023 16:23:01 GMT

@drealine wrote: "I can't make a WOL if it's turnoff by ESX. Led ethernet still green and orange and use more consumption than excepted. While turn off by press button or disconnect and reconnect power plug, the WOL work again."

This is indeed an odd one as there appears to be two conditions, one where the NUC is powered off then on from 'cold' and the other when ESXi (I assume this is what you are using) is powered down.

This would indicate that the BIOS is using different 'configurations' for each case. Due to the lack of information on the Internet regards the workflow it not possible to determine what the differences are. The Intel e1000 is supported, but with the cavate that 'both the chipset and the OEM implementation must support wake-on-LAN so that the NIC supports it'. Also bearing in mind that ESXi is an enterprise system, so testing on PCs might not be a priority.

With this in mind you will have to, somehow, try and determine the differences between each of the two conditions. Due to this lack of detailed information, one way would be to try an force an error under varied conditions.

Requests:

- Provide ESXi version (including patches)
- NUC model and firmware version
- Provide a screen capture of the 'Secondary Power Settings' i.e. WOL

Suggest:

- Run the following on the ESXi console

list network adapters
esxcli network nic list

check if network adapter supports WOL and is it is enabled
esxcli network nic get -n vmnic0 | grep Wakeon

- Review the ESXi logs

- Although somewhat counter-intuitive, have you tried with the ESXi wake-on-lan turned 'off' . . . and note the response.

Re: Troubleshooting iSCSI

CarltonR — Tue, 08 Aug 2023 22:19:45 GMT

You outlined above that everything worked before the Meraki switches had their firmware updated, and that after the update only one of the ESXi servers was able to connect to the iSCSI target (Dell R730 server, Ubuntu 22.04.3 LTS). I would suggest that you focus on the switch/s . . .

Questions:

i. Could you confirm that it was only the switches firmware that was updated, and that none of, or any other parts of the infrastructure or configuration was changed (i.e. that switches swapped out, switches config, routing, cabling, and any config on the ESXi or iSCSI target were not changed in any way, what so ever) ?

ii. How many switches are involved, if more than one, which ESXi and iSCSI target is connected to which switch ?

iii. Is there only one iSCSI target for all of the four ESXi servers ?

iv. Are all of the switches at the same firmware version ?

v. Are all the switches the same make/model/version ?

vi. Have you reviewed the switches firmware version update notes to determine what was changed ?

vii. Are you using VLANs ?

viii. You mentioned that you spun up an 'older standalone ESXi 6.7' and a 'Windows Desktop' both of which could "also see the device". Would I be correct to assume that 'see the device' to mean that they could see the iSCSI target in question, and mount the storage ?

ix. How many network connections do the each of the ESXi servers have ?

x. How many network connections does the iSCSI target have ?

Suggest:

- I would suggest moving one of the ESXi's that cannot connect to iSCSI target to one of the switches network ports that you know is working (either the, ESXi that works after the switches firmware upgrade, ESXi 6.7 or Win Desktop (assuming 'viii' to be correct)).

- As an experiment, you could exclude the switches from the equation altogether and make an appropriate direct connection . . or alternatively via another type/make of switch.

Re: Troubleshooting iSCSI

CarltonR — Mon, 07 Aug 2023 20:44:15 GMT

Would suggest first validating the [Cisco] Meraki switches routing tables, etc., . . . also check ESXi vmkernel.log and syslog.log.

As to troubleshooting iSCSI, then these might be a good place to start:

Troubleshooting ESXi connectivity to iSCSI arrays using software initiators (1003952) 16/03/2021
https://kb.vmware.com/s/article/1003952

Troubleshooting ESX and ESXi connectivity to iSCSI arrays using hardware initiators (1003951) 23/09/2013
https://kb.vmware.com/s/article/1003951

Also, I'm sure that you've already been through this guide:

Best Practices for Configuring Networking with Software iSCSI
https://docs.vmware.com/en/VMware-vSphere/7.0/vsphere-esxi-vcenter-server-703-storage-guide.pdf

Re: No Internet connection through my REDHAT VM machine

CarltonR — Thu, 27 Jul 2023 14:25:09 GMT

I'm at a complete loss . . . this is the first time that you have mentioned anything about a customized VMnet8 setting ! ! !

This has been far from straightforward, particularly with unearthing relevant and consistent technical information in an effort to seek a solution. At every turn there have been unearthed surprises, including obscured, obfuscated, or removed information, making diagnoses somewhat tricky.

It appears that you may have a slightly bespoke setup, and that changes made to overcome perceived problems may have resulted in creating knock on effects. Unless you can put the setup back to a known good, then I would suggest getting another PC/laptop, set it up with a default install of VMware, and start over.