As Windows Pro only supports 2 CPU sockets, after added 4 cores in VMware Fusion, the OS is still shown as 2 vCPU. To avoid this is, need to change cpuid.coresPerSocket to handle more than 2 cores.
In .vmx file change following parameter, numvcpus is the total number of cores, which can be changed in GUI. cpuid.coresPerSocket should be changed to half of numvcpus.
numvcpus = "4"
cpuid.coresPerSocket = "2"This is to describe how to convert Ubuntu VM to Proxmox.
Following hardware options can be considered
sata0 to be considered for disk)disk_image_file<mac_address> (This is default for VMware, can use other type too)Convert the VMware disk to Proxmox disk and attach the disk to new VM
qm importdisk 121 ubuntu.vmdk pool240ssd --format qcow2Attach the disk as sata0.
After boot up system show a GUI error screen, press Contrl + Alt + F3 to switch to console mode.
Note: Press Shift to active Grub Menu if required
Find out new network interface UUID
nmcli connChange NetworkManager file name
cd /etc/NetworkManager/system-connections
mv Wired\ connection\ 1-<old_uuid>.nmconnection Wired\ connection\ 1-<new_uuid>.nmconnectionUpdate nmconnection file
[connection]
id=<new_interface_name>
uuid=<new_uuid>
type=ethernet
autoconnect-priority=-999
interface-name=<new_interface_name>
permissions=
timestamp=1628151710
[ethernet]
mac-address-blacklist=
[ipv4]
address1=192.168.1.232/24,192.168.1.254
dns=192.168.1.250;8.8.8.8;
dns-search=
method=manual
[ipv6]
addr-gen-mode=stable-privacy
dns-search=
method=disabled
[proxy]After boot, only a white screen with error message appears, this was fixed by running apt update and upgrade
First, update /etc/apt/sources.list file, replace all repo URL to old-releases.ubuntu.com
Then run following commands
apt update
apt upgrade -yThis is to describe how to convert Oracle Linux 7.9 to Proxmox.
Following hardware options can be considered
sata0 to be considered for disk)disk_image_file<mac_address> (This is default for VMware, can use other type too)Convert the VMware disk to Proxmox disk and attach the disk to new VM
qm importdisk 121 oracle18c.vmdk pool240ssd --format qcow2Attach the disk as sata0.
Select item Oracle Linux Server (0-rescue-ed95572bd80641d79f83cd91e03c0283 with Linux) 7.9 from Grub menu to boot into rescue mode.
Note: Tried other option, all got error and unable to boot
Login as valid user, then find out the kernel to be used
rpm -q -a | grep kernel | sortGot following list
kernel-3.10.0-1160.25.1.el7.x86_64
kernel-3.10.0-1160.36.2.el7.x86_64
kernel-3.10.0-1160.el7.x86_64
kernel-tools-3.10.0-1160.36.2.el7.x86_64
kernel-tools-libs-3.10.0-1160.36.2.el7.x86_64
kernel-uek-5.4.17-2102.203.6.el7uek.x86_64
kernel-uek-5.4.17-2102.204.4.2.el7uek.x86_64
kernel-uek-5.4.17-2102.204.4.4.el7uek.x86_64Choose the latest one, which is also Unbreakable Enterprise Kernel
Find scripts in Kernel package
rpm -q kernel-uek-5.4.17-2102.204.4.4.el7uek.x86_64 --scriptsFollowing posttrans scriptlet shown
...
posttrans scriptlet (using /bin/sh):
/usr/sbin/new-kernel-pkg --package kernel --mkinitrd --dracut --depmod --update 5.4.17-2102.204.4.4.el7uek.x86_64 || exit $?
/usr/sbin/new-kernel-pkg --package kernel --rpmposttrans 5.4.17-2102.204.4.4.el7uek.x86_64 || exit $?
...Run above commands to rebuild Grub files, then reboot the system to the menu with kernel recreated.
Note: The error Unable to open file: /etc/keys/x509_ima.der (-2) can be ignored
You can reconfigure network interface the same as VMware, this is to avoid reconfiguration of network settings
Check VMWare vmx file to find disk type, then set the same in Proxmox
ethernet0.virtualDev = "vmxnet3"You can change Mac Address using the value in VMWare configuration
ethernet0.generatedAddress = "00:11c:22:33:44:55"Find out the interface in /etc/sysconfig/network-scripts as below.
/etc/sysconfig/network-scripts/ifcfg-ens192The interface name is ifcfg-ens192
Create the file /etc/udev/rules.d/70-custom-ifnames.rules with the following contents:
SUBSYSTEM=="net",ACTION=="add",ATTR{address}=="00:11:22:33:44:55",ATTR{type}=="1",NAME="ens192"Then reboot the server, then check the Interface and IP address using ip a command.
Run following command to convert vmdk to qcow2
qm importdisk <VM_ID> <Virtual Disk>.vmdk <storage> --format qcow2Here, VM_ID is a number. After completed a newly created disk appears in VM
Double click the newly created disk, then select VirtIO Block device.
Select Write Back as cache method
Double click the newly created disk, then select SATA device.
Select Write Back as cache method
apt remove --auto-remove open-vm-tools
apt remove --auto-remove xserver-xorg-video-vmware
apt purge open-vm-tools
apt purge open-vm-tools-desktopyum remove open-vm-tools open-vm-tools-desktopTwo ESXi servers, for example esx01 and esx02.
The CPU of both esx01 and esx02 are same family.
Both esx01 and esx02 are having same shared storage.
Configure NFS or iSCSI in both ESXi servers.
Access storage, and check Hosts tab, both ESXi servers should be in the list.
Add VMkernel Network Adapter with vMotion service, can be on an existing standard switch.
VMware Tutorial No.45 | VMware vMotion Step by Step |vMotion in VMware 6.7 |vSphere vMotion GOVMLAB
Fusion reports error, and it can not connect to USB drive to boot.
Fusion does not support USB adapters for connecting displays to your virtual machines.
Note: I haven't tried to change UEFI mode to BIOS mode, maybe this is the cause.
Unable to connect a USB device to a virtual machine (2118442)
USB Device not detected by the virtual machine (57195)
Configuring the USB Controller and Connecting USB Devices
After Attempt 1 created, Reset (restart) Raspberry Pi. Now, in Boot Manager, should see UEFI SYNOLOGY iSCSI Storage.
After installation completed, take out ESXi installation USB, then another reset is required,
Most likely is the iSCSI configuration wrong.
After installation complete, suddenly cannot boot into any destination, and just show error Synchronous Exception.
End up, I have to recopy UEFI image into micro SD card, redo iSCSI configuration. Luckily the iSCSI has no issue, which contains installed ESXi image.
Boot ESXi-Arm Fling on a Raspberry Pi 4 Using ISCSI
Raspberry Pi 4 UEFI Firmware Images
ESXi on Arm 10/22 更新
Raspberry Pi 4 Model B 8GBにESXi for ARM 7.0.0をインストール
Synchronous Exception at 0x00000000371013D8 #97