I have a CentOS 7 VM (64 bit) running off a VMWare Fusion 8.5.10 on High Sierra. I recently moved the contents of an old mac-book to a new one. I initially had some problems with ens33 being listed and no eth0 being found, which I resolved after make changes to my grub conf. However, I never got an IP Address assigned to eth0. The contents of /etc/sysconfig/network-scripts/ifcfg-eth0 #HWADDR=00:50:56:26:22:EE TYPE=Ethernet PROXY_METHOD=none BROWSER_ONLY=no BOOTPROTO=dhcp DEFROUTE=yes IPV4_FAILURE_FATAL=no IPV6INIT=yes IPV6_AUTOCONF=yes IPV6_DEFROUTE=yes IPV6_FAILURE_FATAL=no IPV6_ADDR_GEN_MODE=stable-privacy NAME=eth0 DEVICE=eth0 #UUID=e82482f2-90e1-4c54-829f-a2c59931282e ONBOOT=yes #UUID=5fb06bd0-0bb0-7ffb-45f1-d6edd65f3e03 UUID=5fb06bd0-0bb0-7ffb-45f1-d6edd65f3e03 I have tried with 'HWADDR' uncommented but to no avail. The command ifup eth0 fails with the error Error: Connection activation failed: No suitable device found for this connection. On my host system, I have a vmnet2 custom network configured. It would be great if I can get this issue resolved. The VM was working perfectly fine on my old mac and the problem really started after moving the machine as part of the mac data migration.

I cannot login my Ubuntu12.04 (which is VM running on OSX using VMWARE FUSION 6) because I have changed permission of /tmp for some purpose before rebooting the machine. Thus I tried to boot Ubuntu in recovery mode by pressing shift key while booting the machine (in order to change the permission of /tmp), but it was not possible because no grub screen appears while booting. How can I get into recovery mode if grub does not appear?

After install the program and execute vmPlayer request the kernel headers to recompile it (I guess), after that vmP install the virtual network device, at this point show an error. and the vmware-15092.log file is: 2015-03-27T22:51:28.154-06:00| vthread-4| I120: Preprocessed UTS_RELEASE, got value "3.19.1-201.fc21.x86_64". 2015-03-27T22:51:28.154-06:00| vthread-4| I120: The header path "/lib/modules/3.19.1-201.fc21.x86_64/build/include" for the kernel "3.19.1-201.fc21.x86_64" is valid. Whoohoo! 2015-03-27T22:51:28.158-06:00| vthread-4| I120: The GCC version matches the kernel GCC minor version like a glove. 2015-03-27T22:51:28.158-06:00| vthread-4| I120: Validating path "/lib/modules/3.19.1-201.fc21.x86_64/build/include" for kernel release "3.19.1-201.fc21.x86_64". 2015-03-27T22:51:28.158-06:00| vthread-4| I120: Failed to find /lib/modules/3.19.1-201.fc21.x86_64/build/include/linux/version.h 2015-03-27T22:51:28.158-06:00| vthread-4| I120: /lib/modules/3.19.1-201.fc21.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead. 2015-03-27T22:51:28.158-06:00| vthread-4| I120: using /usr/bin/gcc for preprocess check 2015-03-27T22:51:28.164-06:00| vthread-4| I120: Preprocessed UTS_RELEASE, got value "3.19.1-201.fc21.x86_64". 2015-03-27T22:51:28.164-06:00| vthread-4| I120: The header path "/lib/modules/3.19.1-201.fc21.x86_64/build/include" for the kernel "3.19.1-201.fc21.x86_64" is valid. Whoohoo! 2015-03-27T22:51:28.164-06:00| vthread-4| I120: Using temp dir "/tmp". 2015-03-27T22:51:28.165-06:00| vthread-4| I120: Obtaining info using the running kernel. 2015-03-27T22:51:28.165-06:00| vthread-4| I120: Setting header path for 3.19.1-201.fc21.x86_64 to "/lib/modules/3.19.1-201.fc21.x86_64/build/include". 2015-03-27T22:51:28.165-06:00| vthread-4| I120: Validating path "/lib/modules/3.19.1-201.fc21.x86_64/build/include" for kernel release "3.19.1-201.fc21.x86_64". 2015-03-27T22:51:28.165-06:00| vthread-4| I120: Failed to find /lib/modules/3.19.1-201.fc21.x86_64/build/include/linux/version.h 2015-03-27T22:51:28.165-06:00| vthread-4| I120: /lib/modules/3.19.1-201.fc21.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead. 2015-03-27T22:51:28.165-06:00| vthread-4| I120: using /usr/bin/gcc for preprocess check 2015-03-27T22:51:28.171-06:00| vthread-4| I120: Preprocessed UTS_RELEASE, got value "3.19.1-201.fc21.x86_64". 2015-03-27T22:51:28.171-06:00| vthread-4| I120: The header path "/lib/modules/3.19.1-201.fc21.x86_64/build/include" for the kernel "3.19.1-201.fc21.x86_64" is valid. Whoohoo! 2015-03-27T22:51:28.288-06:00| vthread-4| I120: found symbol version file /lib/modules/3.19.1-201.fc21.x86_64/build/Module.symvers 2015-03-27T22:51:28.288-06:00| vthread-4| I120: Reading symbol versions from /lib/modules/3.19.1-201.fc21.x86_64/build/Module.symvers. 2015-03-27T22:51:28.302-06:00| vthread-4| I120: Read 15286 symbol versions 2015-03-27T22:51:28.302-06:00| vthread-4| I120: Invoking modinfo on "vmnet". 2015-03-27T22:51:28.304-06:00| vthread-4| I120: "/sbin/modinfo" exited with status 256. 2015-03-27T22:51:28.381-06:00| vthread-4| I120: Setting destination path for vmnet to "/lib/modules/3.19.1-201.fc21.x86_64/misc/vmnet.ko". 2015-03-27T22:51:28.381-06:00| vthread-4| I120: Extracting the vmnet source from "/usr/lib/vmware/modules/source/vmnet.tar". 2015-03-27T22:51:28.385-06:00| vthread-4| I120: Successfully extracted the vmnet source. 2015-03-27T22:51:28.385-06:00| vthread-4| I120: Building module with command "/usr/bin/make -j4 -C /tmp/modconfig-3fL25O/vmnet-only auto-build HEADER_DIR=/lib/modules/3.19.1-201.fc21.x86_64/build/include CC=/usr/bin/gcc IS_GCC_3=no" 2015-03-27T22:51:29.709-06:00| vthread-4| W110: Failed to build vmnet. Failed to execute the build command. Now I don't know what to do, any idea?

I'm running ArchLinux in a virtual machine in VMWare. I've *open-vm-tools* installed but I'm unable to copy from macOS host and paste into Hyprland. How can I achieve this?

I recently installed **Debian 13 RC (trixie)** on VMWare using the net install image and during the installation I opted out the desktop environment. After the installation, I installed the gdm3 packages and rebooted to a black screen with a blinking underscore. For comparison, I repeated the exact same process on **Debian 12 (bookworm)** and was able to boot into the graphical interface without any problem. I'm using VMware Workstation 17 Pro, so I'm not sure if this is nvidia GPU related. I was wondering what would be the root cause of this issue. PS: I do notice that the dependencies for gdm3 packages for trixie and bookworm are slighly different.

I’m running Kali Linux, which is installed on a VMware virtual machine. I have been facing issues while trying to update and install packages using apt. The system shows errors related to connection timeouts when fetching packages from certain mirrors, and it also fails to locate some packages that should be available. **My command**

sudo apt update && sudo apt install -y \
  unzip zip curl git build-essential \
  cmake libusb-1.0-0-dev \
  adb lsb-release android-sdk-platform-tools-common \
  libxml2-utils

**Details of the problem:** The error messages:

Error: Failed to fetch http://mirror1.sox.rs/kali/kali/pool/main/a/android-platform-tools/android-libbase_34.0.5-12_amd64.deb   Could not connect to mirror1.sox.rs:80 (88.218.137.65), connection timed out
Error: Failed to fetch http://mirror1.sox.rs/kali/kali/pool/main/a/android-sdk-meta/android-sdk-platform-tools-common_28.0.2+12_all.deb   Unable to connect to mirror1.sox.rs:http:
Error: Failed to fetch http://mirror1.sox.rs/kali/kali/pool/main/g/gcc-defaults/g++_14.2.0-1_amd64.deb   Unable to connect to mirror1.sox.rs:http:
Error: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

**What I have checked so far:** My internet connection is active, and I can ping https://kali.org successfully. My /etc/apt/sources.list contains the default Kali Rolling repository:

deb http://http.kali.org/kali  kali-rolling main non-free non-free-firmware contrib

I tried the following: Ran sudo apt update multiple times, but the same errors occurred. And this:

sudo rm -rf /var/lib/apt/lists/*
sudo apt clean
sudo apt update

Suspect the VM might be trying to connect via IPv6, which could be causing unreachable network errors so I disabled it temporary

sudo sysctl -w net.ipv6.conf.all.disable_ipv6=1
sudo sysctl -w net.ipv6.conf.default.disable_ipv6=1

I am using a SUSE Linux Enterprise Desktop in a virtual environment with a VMware SVGA II Adapter. I need to rotate my screens using xrandr, but every time I try to do so, I get the following error:

xrandr: output Virtual1 cannot use rotation "left" reflection "none"

Here is some relevant information about my setup: - Graphics Adapter: VMware SVGA II Adapter (driver: vmwgfx) - Display Server: X11 (X.Org version 1.21.1.4) - Driver: vmwgfx (OpenGL v: 4.5 Mesa 22.3.5) - VM Environment: VMware VDI When I run inxi -G, it gives me:

Graphics:
  Device-1: VMware SVGA II Adapter driver: vmwgfx v: 2.20.0.0
  Display: x11 server: X.Org v: 1.21.1.4 driver: gpu: vmwgfx note: X driver n/a - try sudo/root
  API: OpenGL v: 4.5 Mesa 22.3.5 renderer: llvmpipe (LLVM 15.0.7 256 bits)

What I’ve tried: - Using xrandr to rotate the screen (xrandr --output Virtual1 --rotate left) - Checked for any VMware or SUSE settings that might enable screen rotation None of these have worked. Is there any way to enable screen rotation using xrandr or another tool while using the VMware SVGA II Adapter in a VDI environment? Any suggestions or workarounds would be greatly appreciated!

I installed Ubuntu 14.04 on VMware workstation version 10.0.0 on my Windows 7 machine. After installing I figured out that it doesn't have any sound so I checked the sound settings. All items seem to be at their default states and correct. Any suggestion to find the problem?

My system was running fine in a Virtual Machine until I ran a full system upgrade on June 2025. Now each time I try to **startx** the following error is logged in */var/log/Xorg.0.log*:

(EE) vmware(0): Unable to map mmio BAR. Invalid argument (22)
(EE) vmware(0): Unable to map frame buffer BAR. Invalid argument (22)
(EE)
(EE) Backtrace:
(EE) unw_get_proc_name failed: no unwind info found [-10]
(EE) ...
(EE) Segmentation fault at address 0x0

I'm using the *open-vm-tools* package and also tried installing *xf86-video-vmware*. Could a downgrade fix the problem? If so, how can I do it?

I recently resized the hard drive of a VM from 150 GB to 500 GB in VMWare ESXi. After doing this, I used Gparted to effectively resize the partition of this image. Now all I have to do is to resize the file system, since it still shows the old value (as you can see from the output of df -h): Filesystem Size Used Avail Use% Mounted on /dev/mapper/owncloud--vg-root 157G 37G 112G 25% / udev 488M 4.0K 488M 1% /dev tmpfs 100M 240K 100M 1% /run none 5.0M 0 5.0M 0% /run/lock none 497M 0 497M 0% /run/shm /dev/sda1 236M 32M 192M 14% /boot However, running sudo resize2fs /dev/mapper/owncloud--vg-root returns this: resize2fs 1.42 (29-Nov-2011) The filesystem is already 41608192 blocks long. Nothing to do! Since Gparted says that my partition is /dev/sda5, I also tried running sudo resize2fs /dev/sda5, but in this case I got this: resize2fs 1.42 (29-Nov-2011) resize2fs: Device or resource busy while trying to open /dev/sda5 Couldn't find valid filesystem superblock. Finally, this is the output of pvs: PV VG Fmt Attr PSize PFree /dev/sda5 owncloud-vg lvm2 a- 499.76g 340.04g fdisk -l /dev/sda shows the correct amount of space. How can I resize the partition so that I can finally make the OS see 500 GB of hard drive?

After installing RHEL 8 with the required libraries and signed vmmon & vmnet, then imported the mok I am still unable to run a virtual machine in VMWare Workstation (the same goes for VMWare Player) This is how I am signing vmmon and vmnet: openssl req -new -x509 -newkey rsa:2048 -keyout VMWare.priv -outform DEF -out VMWare.der -nodes -days 36500 -subj "/CN=VMware/" /usr/src/kernels/$(uname -r)/scripts/sign-file sha256 ./VMWare.priv ./VMWare.der $(modinfo -n vmmon) /usr/src/kernels/$(uname -r)/scripts/sign-file sha256 ./VMWare.priv ./VMWare.der $(modinfo -n vmnet) mokutil --import VMWare.der I successfully import VMWare.der on reboot but I still get the following error: > Could not open /dev/vmmon: No such file or directory. Please make sure > that the kernel module `vmmon' is loaded. Thanks Graham Harris Update 1: I have reverted back to RHEL 7.8, updated, and signed the VMMON & VMNET files, got "Can't read private key", imported the MOK and the installation was borked. Update 2: On the boot screen the system says Red Hat Enterprise Linux Server (3.10.0-1127.e17.x86_64) 7.8 (Maipo) If I update to the latest that is when the system cannot get past the UEFI splash screen. Update 2 Switched back to RHEL 8, and after importing the MOK I run mokutil -l and the key is not found. However a recent search found this article on git MOK enrollment silently fails #105 Summary of the issue: > When writing MokList with EFI_VARIABLE_APPEND_WRITE, some HP laptops may just return EFI_SUCCESS without writing the content into the flash, so we have no way to detect if MokList is updated or not. Now we always read MokList first and write it back with the new content.

I'm currently working for a company with quite strict security measures. 90% of my work takes place on a Linux machine, but to access this machine I first have to connect to a VPN, access a Windows VDIs, and from this I can access the Linux server via Putty. This is fine for small tasks, but the majority of my work takes place on the shell this is slowing me down somewhat; I'm used to running multiple terminal windows and accessing servers via Emacs/Tramp. I'm wondering whether it's possible to access the remote Linux server using my local SSH via the VDI, but I'm out of my territory when it comes to this sort of thing. I believe I can use Putty on the Windows VDI to act as a proxy for getting onto the Linux system, but it's the step before that to access the VDI using SSH where I'm getting stuck. **Should it be possible? If so, what sort of google searches should I be making?** **Updated information:** - I'm using the built-in OS X VPN tool. - The linux server can only be accessed via a machine on the same network, which is why we have to connect to a VDI first. I believe I can use Putty to open a connection to the linux server and make it act as a proxy on whatever port I wish, I just need to tell SSH to a) use the VPN settings and b) connect to the VDI.

I am using an older laptop that is running Windows 10 (it came with Win8). I have installed Ubuntu on the laptop virtually, using VMware, but would like to access the files on the rest of the laptop (in the Windows partitions) especially those in my documents folders, on the C: and D: drives, from my Ubuntu. How can I do that? How can I cd to these drives/folders?

When using a VPN to connect to my Rocky Linux 9.3 server running on a virtual machine, my connection is randomly disconnected. After disconnection, I cannot reconnect for about one or two minutes, and the connection is refused. I have tried connecting from different computers on different networks, but the same error occurs. Only connections within the main network work (WinSCP from another Windows server to the Rocky Linux server remains stable). I am using pfSense as a firewall. I have already set the keep-alive connection parameters, but there is nothing suspicious in the server logs. I'm kind of running in the dark here. Some of the logs:

Knocking FTP port.
. 2024-08-21 11:35:02.610 FTP port did not open.
* 2024-08-21 11:35:02.693 (EFatal) Network error: Connection to "192.168.178.205" refused.
. 2024-08-21 11:35:06.189 Looking up host "192.168.178.205" for SSH connection
. 2024-08-21 11:35:06.189 Connecting to 192.168.178.205 port 22
. 2024-08-21 11:35:08.287 Failed to connect to 192.168.178.205: Network error: Connection refused
. 2024-08-21 11:35:08.287 Knocking FTP port.
. 2024-08-21 11:35:10.302 FTP port did not open.
* 2024-08-21 11:35:10.368 (EFatal) Network error: Connection to "192.168.178.205" refused.

/var/log/secure:

Aug 21 14:49:01 localhost sshd: Connection from 172.16.17.4 port 49860 on 192.168.178.205 port 22 rdomain ""
Aug 21 14:49:05 localhost sshd: Accepted password for woshi from 172.16.17.4 port 49860 ssh2
Aug 21 14:49:05 localhost sshd: Starting session: subsystem 'sftp' for woshi from 172.16.17.4 port 49860 id 0
Aug 21 14:49:30 localhost sshd: Connection from 172.16.17.4 port 49945 on 192.168.178.205 port 22 rdomain ""
Aug 21 14:49:58 localhost sshd: Accepted password for woshi from 172.16.17.4 port 49945 ssh2
Aug 21 14:49:58 localhost sshd: Starting session: shell on pts/1 for woshi from 172.16.17.4 port 49945 id 0
Aug 21 14:52:16 localhost sshd: Connection from 172.16.17.4 port 50512 on 192.168.178.205 port 22 rdomain ""
Aug 21 14:52:17 localhost sshd: Accepted password for woshi from 172.16.17.4 port 50512 ssh2
Aug 21 14:52:17 localhost sshd: Starting session: subsystem 'sftp' for woshi from 172.16.17.4 port 50512 id 0
Aug 21 14:53:23 localhost sshd: Connection from 172.16.17.4 port 50739 on 192.168.178.205 port 22 rdomain ""
Aug 21 14:53:23 localhost sshd: Accepted password for woshi from 172.16.17.4 port 50739 ssh2
Aug 21 14:53:24 localhost sshd: Starting session: shell for woshi from 172.16.17.4 port 50739 id 0
Aug 21 14:53:28 localhost sshd: Connection from 172.16.17.4 port 50757 on 192.168.178.205 port 22 rdomain ""
Aug 21 14:53:32 localhost sshd: Failed none for woshi from 172.16.17.4 port 50757 ssh2
Aug 21 14:53:59 localhost sshd: Accepted password for woshi from 172.16.17.4 port 50757 ssh2
Aug 21 14:54:00 localhost sshd: Starting session: shell on pts/0 for woshi from 172.16.17.4 port 50757 id 0
Aug 21 15:09:06 localhost sshd: Timeout, client not responding from user woshi 172.16.17.4 port 49860
Aug 21 15:11:30 localhost sshd: Timeout, client not responding from user woshi 172.16.17.4 port 49945
Aug 21 15:18:25 localhost sshd: Timeout, client not responding from user woshi 172.16.17.4 port 50739
Aug 21 15:21:18 localhost sshd: Timeout, client not responding from user woshi 172.16.17.4 port 50512
Aug 21 15:21:28 localhost sshd: Timeout, client not responding from user woshi 172.16.17.4 port 50757

**UPDATE:** So my network is managed by pfSense. I am connecting to that network over OpenVPN. My Rocky Linux server (target server) is on VmWare virtual machine.

I am trying to analyze a VMware memory dump from an AlmaLinux guest. I converted the snapshot to a core dump using vmss2core:

vmss2core-sb-8456865.exe -N vSRV1_Snapshot815.vmsn vSRV1_Snapshot815.vmem

Then, I installed the necessary tools for crash dump analysis:

sudo dnf install yum-utils -y
sudo dnf install kexec-tools crash gdb -y
sudo dnf debuginfo-install kernel-debuginfo-$(uname -r) -y

However, when I try to analyze the dump with crash, I get an error:

crash /usr/lib/debug/lib/modules/4.18.0-553.34.1.el8_10.x86_64/vmlinux /home2/memdump/vmss.core
crash: cannot resolve "p2m_top"

Any advice on how to properly analyze this dump or work around the p2m_top error? Thanks.

**Dear friends and college** we have VM machines with rhel 7.2 version - 3.10.0-327.el7.x86_64 we noticed about the following messages ( from /var/log/messages ) e1000 0000:02:01.0 eth0: Detected Tx Unit Hang#012 Tx Queue #012 TDH #012 TDT and from dmesg we get that [21519947.519425] e1000 0000:02:01.0 eth0: Detected Tx Unit Hang Tx Queue TDH TDT next_to_use next_to_clean buffer_info[next_to_clean] time_stamp next_to_watch jiffies next_to_watch.status [21519949.521583] e1000 0000:02:01.0 eth0: Detected Tx Unit Hang Tx Queue TDH TDT next_to_use next_to_clean buffer_info[next_to_clean] time_stamp next_to_watch jiffies next_to_watch.status [21519949.811366] e1000 0000:02:01.0 eth0: Reset adapter [21519949.855081] e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None we try to search the solution for the problem above and we see post about the following fixing set following in /etc/sysctl.conf, and reboot machine

pcie_aspm=offet

( https://serverfault.com/questions/193114/linux-e1000e-intel-networking-driver-problems-galore-where-do-i-start ) or ethtool -K eth0 tso off gso off or changed the network adapters tor VMNETX3. and so on .... so we are confuse about the right solution please advice what is the right approach for our problem ?

My LV should be around 135GB but I see it's only 74.5G. How to increase it without data loss as my SDA is 150 GB? I'm using VMware for virtualization

I have a very small VM running in a cloud with only 512 MB ram. I read, it is possible to use the video card as swap as descriped here : > Graphics cards contain a lot of very fast RAM, typically between 64 and 512 MB. With Linux, it's possible to use it as swap space, or even as RAM disk. Is it possible to use the virtual video card inside a VM also? So I could use more ram than I actually have to pay for? lspci -v output for the virtual video card: 00:0f.0 VGA compatible controller: VMware SVGA II Adapter (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: vmwgfx

I don't have access to the ESXi server. I don't have root access to any machine. Just a regular user. The current machine runs on VM and has Linux as its OS. Is there a way how to know the ESXi version? I have tried the below. Is there any alternate faster way? 1. Find the hypervisor used

systemd-detect-virt vmware

2. Since it is vmware, get more info on the vmware version

vmware-checkvm -h

VM's hw version is 4 VMware software version 6 (good) 3. Get the version info on vmware-toolbox-cmd

vmware-toolbox-cmd -v
    11.0.5.17716 (build-15389592)

4. Find the ESX version based on the mapping at the [website](https://packages.vmware.com/tools/versions) 11269 esx/6.7p02 16075168 11.0.5 15389592 11269 esx/7.0 15843807 11.0.5 15389592 Since in Step 2 indicated version 6, and there are two entries for 15389592, I conclude that the ESX version will be ESX/6.7p02 What is the alternate faster way - without relying on https://packages.vmware.com/tools/versions ?

I try to assign a private IP to VMware VMs (ubuntu) running on a macos host system. I try to achieve this by assigning a single bridge network to each VM. Connect Network Adapter options (inside VM settings) options I have are: - autodetect - wifi -eterhnet (not available, since I run on wifi) For whatever option I chose (autodetect, wifi) after restarting VM I keep getting the same IP on all VM when running the command: - hostname -i I have read this and that question, but I could not find the answer.