Tag Archives: vmware

VMware reported an error after installing docker

Problem: after installing docker and opening VMware, an error is reported

Problem tip: VMware Workstation is incompatible with device/credential guard

Scheme:

Close hypervisorlaunchtype

Execution steps:

1. Open PowerShell as administrator

2. Operation command:

bcdedit /set hypervisorlaunchtype off

PS: if you want to restart:

bcdedit /set hypervisorlaunchtype auto

Explain

The Bcdedit/set command sets the startup item option value in the windows boot configuration data file (BCD)

Format Bcdedit/set [{ID}] datatype value

Hypervisordebug [on | off]
controls whether the hypervisor debugger is enabled

Reference

https://docs.microsoft.com/zh-cn/windows-hardware/drivers/devtest/bcdedit–set

VMware Error: cannot find a valid peer process to connect to! [How to Solve]

There is no universal solution to such a problem. When I encounter it, I would like to share with you my experience in solving this problem. And repeat the possible situation, for everyone to use

Analyze the possible solutions

1. Find vmware-vmx.exe in the task manager, restart the virtual machine, and then start it

Verified: there is no such process, so no

2. Clear the. Lck file in the virtual machine directory, and then start peer process. The startup mode is: Net start vmx86 in DOS

Prompt, should use the administrator mode to run, if you want to crack Windows administrator permissions, please do Niang

Verified: there is no. Lck file in my virtual machine directory. After typing in the command, restart the virtual machine, the problem remains, so no

3. Execute net user in DOS to check whether it has been added correctly_ vmware_ If there is no user, it means that the system has enabled the password policy. You can use net user username {password | *}/add to add a new user

After verification: after net user is called, there is only one local administrator user, so try to add a net user_ vmware_ Fuchao/add, where the user name is_ vmware_ The password is Fuchao. After adding, restart the virtual machine. The problem remains, so no

4. What is given here is similar to the first method, but it only uses the instruction method, and class C goes to the doctor randomly. Continue to try: enter taskkill/im vmware-vmx.exe in DOS, then clear the. Lck file in the virtual machine directory, and finally restart the vmx86 service: enter two instructions in DOS

net stop vmx86

net start vmx 86

Verified: finally found. Lck file, indeed, is a folder, all deleted. Restart vmx86. Open VMware, the problem remains the same!!! It’s getting restless! It’s better to restart the machine first

************Eager to solve the problem, look here**************

5. I suddenly found that the scenario description in a solution is similar to mine: the virtual machine was forced to shut down when it was forced to shut down, resulting in the failure to boot correctly when the virtual machine was restarted. In this article, we fiercely attack the blog of Chinese people. We can only focus on it. Can we solve the problem if we can solve it?What’s the use of being so lofty??I don’t understand

However, the technology still has no national boundaries. As mentioned in the article, delete the cache file. VMSs of the virtual machine for restoring, and then restart the virtual machine to solve the problem

 

Centos7 vmware Install Error: C header files matching your running kernel were not found.

C header files matching your running kernel were not found when installing VMware in centos7

02 OCT 2015 06:48:45jcxch number of readings: 3812

When installing VMware 11.0 in CentOS 7

1. Install gcc compiler first, because some files need to be compiled when installing VMware. If the system does not install GCC, you will be prompted to install GCC. Just use Yum install GCC

2. C header files matching your running kernel were not found. Refer to your distribution’s documentation for installation instruction. The general meaning is that there are no C header files and other files found in the current kernel. If there is such a problem that the development package of the corresponding kernel is not installed, you need to solve it by Yum install kernel devel or download the corresponding RPM package for installation

[Solved] VMware Modify network.service Error: LSB: Bring up/down networking

modify the network configuration: VIM/etc/sysconfig/network scripts/ifcfg-ens32

TYPE="Ethernet"
#BOOTPROTO="dhcp"
DEFROUTE="yes"
PEERDNS="yes"
PEERROUTES="yes"
IPV4_FAILURE_FATAL="no"
IPV6INIT="yes"
IPV6_AUTOCONF="yes"
IPV6_DEFROUTE="yes"
IPV6_PEERDNS="yes"
IPV6_PEERROUTES="yes"
IPV6_FAILURE_FATAL="no"
NAME="eno16777728"
UUID="47be0836-29b3-4ae8-8c41-8ba96a7cb0f8"
DEVICE="ens32"
ONBOOT="yes"

BOOTPROTO="static"
IPADDR=192.168.7.101
GATEWAY=192.168.7.2
METMASK=255.255.255.0
DNS1=8.8.8.8
DNS2=114.114.114.114

systemctl restart network.service

● network.service - LSB: Bring up/down networking
   Loaded: loaded (/etc/rc.d/init.d/network; bad; vendor preset: disabled)
   Active: failed (Result: exit-code) since Thu 2020-07-02 11:21:16 CST; 4min 26s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 1631 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=1/FAILURE)

Jul 02 11:21:16 node1 network[1631]: RTNETLINK answers: File exists
Jul 02 11:21:16 node1 network[1631]: RTNETLINK answers: File exists
Jul 02 11:21:16 node1 network[1631]: RTNETLINK answers: File exists
Jul 02 11:21:16 node1 network[1631]: RTNETLINK answers: File exists
Jul 02 11:21:16 node1 network[1631]: RTNETLINK answers: File exists
Jul 02 11:21:16 node1 network[1631]: RTNETLINK answers: File exists
Jul 02 11:21:16 node1 systemd[1]: network.service: control process exited, code=exited status=1
Jul 02 11:21:16 node1 systemd[1]: Failed to start LSB: Bring up/down networking.
Jul 02 11:21:16 node1 systemd[1]: Unit network.service entered failed state.
Jul 02 11:21:16 node1 systemd[1]: network.service failed.

journals -xe

Jul 02 11:33:45 node1 systemd[1]: network.service failed.
Jul 02 11:33:45 node1 polkitd[705]: Unregistered Authentication Agent for unix-process:1803:35978 (system bus name :1.29, object path /org/freedesktop/Poli
Jul 02 11:35:59 node1 polkitd[705]: Registered Authentication Agent for unix-process:2069:49419 (system bus name :1.37 [/usr/bin/pkttyagent --notify-fd 5 -
Jul 02 11:35:59 node1 polkitd[705]: Unregistered Authentication Agent for unix-process:2069:49419 (system bus name :1.37, object path /org/freedesktop/Poli
Jul 02 11:36:06 node1 polkitd[705]: Registered Authentication Agent for unix-process:2081:50192 (system bus name :1.38 [/usr/bin/pkttyagent --notify-fd 5 -
Jul 02 11:36:06 node1 systemd[1]: Reloading.
Jul 02 11:36:06 node1 polkitd[705]: Unregistered Authentication Agent for unix-process:2081:50192 (system bus name :1.38, object path /org/freedesktop/Poli
Jul 02 11:36:12 node1 polkitd[705]: Registered Authentication Agent for unix-process:2106:50727 (system bus name :1.39 [/usr/bin/pkttyagent --notify-fd 5 -
Jul 02 11:36:12 node1 systemd[1]: Starting LSB: Bring up/down networking...
-- Subject: Unit network.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit network.service has begun starting up.
Jul 02 11:36:12 node1 network[2112]: Bringing up loopback interface:  [  OK  ]
Jul 02 11:36:12 node1 network[2112]: Bringing up interface eno16777728:  ERROR     : [/etc/sysconfig/network-scripts/ifup-eth] Device eno16777728 does not 
Jul 02 11:36:12 node1 /etc/sysconfig/network-scripts/ifup-eth[2239]: Device eno16777728 does not seem to be present, delaying initialization.
Jul 02 11:36:12 node1 network[2112]: [FAILED]
Jul 02 11:36:12 node1 network[2112]: Bringing up interface ens32:  ERROR     : [/etc/sysconfig/network-scripts/ifup-eth] Device eno16777728 does not seem t
Jul 02 11:36:12 node1 /etc/sysconfig/network-scripts/ifup-eth[2264]: Device eno16777728 does not seem to be present, delaying initialization.
Jul 02 11:36:12 node1 network[2112]: [FAILED]
Jul 02 11:36:12 node1 network[2112]: RTNETLINK answers: File exists
Jul 02 11:36:12 node1 network[2112]: RTNETLINK answers: File exists
Jul 02 11:36:12 node1 network[2112]: RTNETLINK answers: File exists
Jul 02 11:36:12 node1 network[2112]: RTNETLINK answers: File exists
Jul 02 11:36:12 node1 network[2112]: RTNETLINK answers: File exists
Jul 02 11:36:12 node1 network[2112]: RTNETLINK answers: File exists
Jul 02 11:36:12 node1 network[2112]: RTNETLINK answers: File exists
Jul 02 11:36:12 node1 network[2112]: RTNETLINK answers: File exists
Jul 02 11:36:12 node1 network[2112]: RTNETLINK answers: File exists
Jul 02 11:36:12 node1 systemd[1]: network.service: control process exited, code=exited status=1
Jul 02 11:36:12 node1 systemd[1]: Failed to start LSB: Bring up/down networking.
-- Subject: Unit network.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit network.service has failed.
-- 
-- The result is failed.
Jul 02 11:36:12 node1 systemd[1]: Unit network.service entered failed state.
Jul 02 11:36:12 node1 systemd[1]: network.service failed.
Jul 02 11:36:12 node1 polkitd[705]: Unregistered Authentication Agent for unix-process:2106:50727 (system bus name :1.39, object path /org/freedesktop/Poli

Solution:

ip addr to see if the driver is consistent with the NIC profile

cd /etc/sysconfig/network-scripts/

ls -l

mv /etc/sysconfig/network-scripts/ifcfg-eno16777728 /etc/sysconfig/network-scripts/ifcfg-ens32

Modify the configuration file vim /etc/sysconfig/network-scripts/ifcfg-ens32

reboot

Installation of VMware, Microsoft runtime DLL setup failed to complete the installation, solution

Geeks, please accept the hero post of 2021 Microsoft x Intel hacking contest>>>

when installing VMware, the Microsoft runtime DLL installation program failed to complete the installation. The solution is 0

Reference article:

(1) Installation of VMware, Microsoft runtime DLL setup failed to complete the installation, solution

(2) https://www.cnblogs.com/wxdblog/p/7091496.html

Let’s make a note.

The solution to the problem of “host SMBus controller not enabled” when Linux starts in VMWare

Why can’t you grab tickets when you travel on holiday?Reveal the key technology of 12306 how to ensure the ticket is not oversold>>>

the solution to the problem of “host SMBus controller not enabled” when Linux starts in VMWare

Reference article:

(1) The solution to the problem of “host SMBus controller not enabled” when Linux starts in VMWare

(2) https://www.cnblogs.com/wenchaoz/p/8982122.html

Let’s make a note.

About vCenter converter standalone 6.2 unable to connect to esxi 5.5

Error: a general system error occurred: SSL exception: error:14077102 :SSL routines:SSL23_ GET_ SERVER_ HELLO:unsupported protocol

This problem is because tls1.0 is disabled in the latest version of converter. The solution is to modify the configuration file related to converter to allow tls1.0.

1. Open the show and hide file function in Explorer

2. Backup and modify 12342272 to 56313856 in the following four files

C:\Program Files (x86)\VMware\VMware vCenter Converter Standalone\converter- client.xml

C:\ProgramData\VMware\VMware vCenter Converter Standalone\converter- agent.xml

C:\ProgramData\VMware\VMware vCenter Converter Standalone\converter- server.xml

C:\ProgramData\VMware\VMware vCenter Converter Standalone\converter- worker.xml

3. Restart the three services of VMware converter agent, VMware converter server and VMware converter worker

Supplement:

1. VCenter converter standalone is recognized as the best P2V software, and it is also the official recommended tool for virtual machine hardware level degradation

2. VCenter converter standalone can’t be accessed normally after installation. It’s very likely that the fault will appear on the failure of VMware convert server to start. After checking the windows log, the situation that converter can’t be used can be basically solved

3. The download address of vCenter converter standalone 6.2 is attached https://pan.baidu.com/s/1BDye0Tr4WhMPAa6WpZSYTw Extraction code: f88r

VMware Workstation and Device/Credential Guard are not compatible

VMware Workstation and Device/Credential Guard are not compatible. VMware Workstation can be run after disabling Device/Credential Guard. ” error might be familiar with the VMware workstation users.

I ran in to this problem while I was starting to use my VMware workstation 14 pro on Windows 10 and it was throwing this error when I’m booting up the Virtual Machine. Actually, it was giving the direct VMware Knowledge base article to follow the steps to resolve it. But I thought to write this up to help all those who look for a step guide to fix the error.

This was the appeared error message in my Virtual Machine.

VMware Workstation and Device/Credential Guard are not compatible. VMware Workstation can be run after disabling Device/Credential Guard. Please Visithttp://www.vmware.com/go/turnoff CG DGfor more details.

I had to disable the Device/Credential Guard in my local group policy and I opened a “run” prompt by pressingWin Key + Rand typed ”gpedit.msc” to open the local group policy editor.

Once it opened up the Local group policy editor, navigate to ”Local Computer Policy &> Computer Configuration &> Administrative Templates &> System &> Device Guard” and open the ”Turn on Virtualization Based Security” setting by double click on it.

Set the setting to ”Disabled

Opened a Command Prompt elevating the “Administrative Privileges” and run the below piece of command

1

2

3

4

5

6

7

8

mountvol X: /s

copy %WINDIR%\System32\SecConfig.efi X:\EFI\Microsoft\Boot\SecConfig.efi /Y

bcdedit /create {0cb3b571-2f2e-4343-a879-d86a476d7215} /d “DebugTool” /application osloader

bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} path “\EFI\Microsoft\Boot\SecConfig.efi”

bcdedit /set {bootmgr} bootsequence {0cb3b571-2f2e-4343-a879-d86a476d7215}

bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} loadoptions DISABLE-LSA-ISO,DISABLE-VBS

bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} device partition=X:

mountvol X: /d

This
X:should be an unused drive and if it is in use make sure to use another drive letter which is not in use.

Hyper-V role was not installed on my system, if it is installed make sure to disable it before you restart.

Rebooted the Computer and at the login screen it prompted to accept the change and pressed F3 and Operating system loaded without issues, after that my Virtual Machine started correctly.

5

1

4.6(92.73%)11votes

Ubuntu Resolution Change xrandr Failed to get size of gamma for output default

1.Questions

Version information description: Ubuntu 16.04 lts

After installing Ubuntu, resolution and display do not match . The xrandr command cannot give relevant information. So we tried different methods.

2.Xrandr — addnewmode

This is the most frequently answered method on stackoverflow

gtf 1920 1080 60

1920×1080 resolution, 60Hz refresh rate

So you get a modeline:

"1920x1080_60.00"  172.80  1920 2040 2248 2576  1080 1081 1084 1118  -HSync +Vsync

Copy this line and run it

xrandr --newmode "1920x1080_60.00" 172.80 1920 2040 2248 2576 1080 1081 1084 1118 -HSync +Vsync

Add one more:

xrandr --addmode VGA1 "1920x1080_60.00"

Here, vga1 can be HDM and others (have no idea about this)

Finally:

xrandr --output VGA1 --mode "1920x1080_60.00"

But their own is to run xrandr can not give a response, there are errors. So it doesn’t work.

3.xorg.conf

1 sudo vim /etc/xorg.conf

Copy the following:

Section "Monitor"
        Identifier   "Monitor0"
        VendorName   "Monitor Vendor"
        ModelName    "Monitor Model"
        HorizSync   28.0 - 70.0
        VertRefresh     56.0 - 75.0
EndSection


Section "Device"
        Identifier  "VMware SVGA"
        Driver      "vesa"
EndSection


Section "Screen"
        Identifier "Screen0"
        Device     "Card0"
        Monitor    "Monitor0"
        SubSection "Display"
                Viewport   0 0
                Depth     24
                Modes     "1920x1080_60.00"
        EndSubSection
EndSection

: WQ! (save)

Restart and it’s successful.

4.Postscript

You also see a way to change the grub startup file. But it didn’t work for me.