Questions[esx](ubuntu)

I've installed NTP and internal NTP server peer is stratum 2. But every time I reboot the server, the VM time is synced with ESX instead of ntp.

I did run ntpdate -s x.x.x.x and corrected it. But after reboot its hours behind again.

Why doesn't NTP handle it? I've enabled ntp and it starts up during boot but the time is always the esx time. I'm on Ubuntu 16.04.

Also timedatectl doesn't show NTP but systemd.timesyncd is displyed. systemd.timesyncd is disabled and stopped on the VM.

root@host001:~# timedatectl
                      Local time: Fri 2020-05-08 16:00:59 UTC
                  Universal time: Fri 2020-05-08 16:00:59 UTC
                        RTC time: Fri 2020-05-08 08:57:03
                       Time zone: UTC (UTC, +0000)
       System clock synchronized: no
systemd-timesyncd.service active: no
                 RTC in local TZ: no

I have networking issues with vmware workstation v15.5.2 on Ubuntu 18.04. I installed ESXi and Openstack on vmware worksation with NAT, Host-only and Bridged adapters each time, then I set up a vm inside the ESXi/Openstack VM, I could ping the Vm inside openstack/esxi to the Workstation vm where was installed ESXi and Openstack, the ping is also successful from host machine to the workstation VM, but impossible to ping either way between Host machine and VMs created inside Openstack/ESxi.

-Here's the strange part:

I did the exact same labs with the exact same config (mainly out-the-box installations) on WINDOWS 10 Vmware workstation v15.5.2, and the ping worked just fine for the 3 scenarios mentioned above.

So to summarize, the VMs created within an openstack/esxi VM can't reach outside of their parent VM, not even the different gateways of vmware workstation different network/adapter types

I tried to uninstall VMware workstation and install again but the problem remains. has anyone ever noticed this or is there an extra configuration to do on Ubuntu Vmware that is not needed on Windows? thank you.

Preface: I am running Ubuntu 16.04 (kernel 4.15.0) in an ESXi virtual machine (version 6.7), and using PCI passthrough for a GTX 1080Ti. I am attempting to install the CUDA 10.1 toolkit, with Nvidia-418 drivers. I have tried 384 as well, and using apt install nvidia-current. Same result every time.

When I finish the CUDA installation and restart the machine, I am stuck at the login screen and cannot get to the desktop. Every time I type in my password, the login manager disappears for a few seconds, then a black screen, and then I am prompted again to enter my password. I even specified in the Ubuntu install to "Log in automatically", yet I always hit the login screen post CUDA installation.

I need the desktop to work, with the Nvidia drivers, in order to run a specific piece of software.

What I have tried so far:

• Changing ESXi settings. I have tried using ESXi 6.7, 6.5, and 6.0. I have also specified "hypervisor.cpuid.v0 = false". Additionally, I have disabled secure boot, and changed the boot option settings from "BIOS" to "EFI". No change with any of these adjustments.
• Installing VMware tools on the host machine
• Restarting the lightdm service
• Reconfiguring X server via this guide. It is important to note when I followed the guide, I did get two displays that showed up. The "Device" section of the xorg.conf file had the right BusID, but did not have the right driver. I changed it from "noveau" to "nvidia". Still no results
• Installing and running gdm3
• Running startx from a tty session
• (Attempting to) connect to the desktop using VNC
• Adding "nomodeset noveau.modeset=0" to GRUB
• Installing CUDA using both the runfile and the .deb
• Adding +iglx to Xserver commands

Oddly enough, I am able to run nvidia-smi post installation and see the graphics card appear. Unfortunately, I am unable to run the software I need to test without a GUI, so running it from tty is not an option.

I am not sure what log files to post, but here is my .xsession-errors log:

Xsession-errors log

How should I proceed? I have been troubleshooting this issue for days and I have hit a wall. I cannot figure out what else to try.

Thank you!

I have a hpe blade system c3000 with 8 blades.

On a number of blades, right now 4, I run ESXi version 5.5

I can easily create virtual Windows Server / Windows 10 machines and get proper access to the Internet and the other network.

But this does not work with Ubuntu.

Have tried both VMXNET3 and E1000 as a network adapter in ESX, but the problem remains.

Has installed VmWare tools on the virtual computer running VMXNET3 without success.

Ubuntu with E1000 network adapter

Se images:

cat /etc/networking/interfaces, ifconfig -a, ping results

Ubuntu with VMXNET3 network adapter

See images:

cat /etc/networking/interfaces, ifconfig -a, ping

This problem with the network are the same on other linux dist, like Debian. (Debian fails during the installation, because no connection to the internet is OK)

No firewall active.

ufw status = inactive

So my questions are.

What should I use? E1000 or VMXNET3?

How do I get this is working.

(Ubuntu Server 14.04 och Ubuntu Server 18.04 Same results)

Virtual Switch: Switch image 1 , Switch image 2

I have a question regarding running Ubuntu 17.10 (with open-vm-tools) as a VM on ESXi. I installed ESXi on my PC then install Ubuntu 17.10 as my virtual machine. Below is a screenshot of my VM settings:

What my problem is, the ubuntu desktop will hang while:

1. Browsing some website using FireFox (I tried Chrome but same result). I'm not sure if that is randomly but I tried to restore all sessions, then desktop will hang again.
2. If I leave the machine idle, after a few hours the same will happen.
3. After this issue happens, even ping is not able to reach the VM.

Symptoms:

1. Cursor is working, but not able to click on anything.
2. The system clock is freezed on the hang time.
3. ping test to virtual machine will show not able to reach to host.

What I tried:

1. I tried to increase the total memory on VM settings, but it doesn't help.

2. I tried to cat the logs under /var/log/syslog but no luck, there is no error captured during that period. Please refer to below screenshot (I reboot the machine at 11AM).

   

Anyone knows more about this issue and how to solve it?