Convert VirtualBox VM to ProxMox VE

June 24, 2022 by Rumi

On the VirtualBox host, launch VirtualBox
Right click the VM to convert > Settings
Select Storage from the left navigation
Click the virtual hard disk and copy the Location value for the full path of the disk to the clipboard
Right click on the Start menu > Run > type cmd.exe > Press Enter

Enter the following commands in the command prompt

# change directory to VirtualBox installation
cd %programfiles%\Oracle\VirtualBox
# convert the .vdi to raw .img
VBoxManage clonehd --format RAW "pasted\full\path\to.vdi" "pasted\full\path\to.raw"

Once the .vdi to .raw conversion completes, open a web browser and navigate to the ProxMox web UI https://ProxMoxDNSorIP:8006/
Click the Create VM button at the top right
On the General tab, enter a VM Name and note the VM ID generated > click Next
On the OS tab select Do not use any media and set the Guest OS > click Next
On the System tab click Next
On the Hard Disk tab set the Disk size to 0.001 > click Next
On the CPU tab set the number of CPUs > click Next
On the Memory tab set the amount of memory to allocate in MiB > click Next
On the Network tab click Next
On the Confirm tab review the settings and click Finish
Select the newly created VM from the left navigation panel > Hardware
Click the Hard Disk to select it
Click the Detach button to detach the hard disk from the VM
Click the Unused disk
Click the Remove button to permanently delete it
Download WinSCP Download
Extract WinSCP and run the executable
Connect to the ProxMox IP server via WinSCP
Copy the VirtualBox created .raw file to a location on the ProxMox server that has enough free disk space, /root for example
Back in the browser, open the ProxMox host Shell

Run the following command to import the raw disk, modify the .raw file name and VM ID noted earlier

# import the raw disk
# usage:
# qm importdisk <VM ID> /root/<source disk file>.raw <destination storage pool name>
qm importdisk 100 vbox.raw HDD_500GB --format qcow2

Once the disk import completes, select the target VM from the left navigation menu > Hardware
Double click the Unused Disk > Click the Add button
Select Options from the left navigation sub-menu
Double click Boot Order
Check the Enabled box next to the hard disk
Drag the Hard disk up in the boot order as needed, typically below the CD-ROM device
Click OK
Click the Start button in the top right of the screen
Click the Console link to watch the boot process

Src:

https://i12bretro.github.io/tutorials/0295.html

Install Proxmox VE 7 on Debian 11 (Bullseye)

December 16, 2021 by Rumi

In this guide, we will cover a step-by-step installation of Proxmox VE 7 virtualization software on Debian 11 (Bullseye) Linux system. It’s recommended to deploy Proxmox VE server from a Bare-metal_ISO_Installer, but it’s sometimes inevitable to deploy it on a running instance of Debian 11 (Bullseye) server.

Setup Pre-requisites

For the installation of Proxmox VE 7 on Debian 11 (Bullseye), you need the following requirements to be met;

A running instance of Debian Bullseye
A 64-bit processor with support for the Intel 64 or AMD64 CPU extensions.
Access to Debian server terminal as root or standard user with sudo
Server needs internet access
Enough hardware resources to be used in Virtualizing other operating systems

Continue reading “Install Proxmox VE 7 on Debian 11 (Bullseye)” »

Proxmox VM auto start VM after found in shutdown state

July 30, 2021 by Rumi

I was having this strange issue, where a running busy VM stopeed all of a sudden due to high CPU or Memory overload issue. So manually had to start everythime. In order to avoid this, created a small script to start the VM in case if it’s down.

#!/bin/bash

# Set environment
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

su -

if [[ $(qm status 101) = *"status: stopped"* ]];
then
echo `qm start 101`
fi

Proxmox Communication Failure (0) Cluster Node on WebGUI

May 21, 2021 by Rumi

Was getting “Communication Failure (0) Cluster Node” Applied the following command on the faulty node-

pvecm updatecerts

Force Stop Proxmox LXC

November 21, 2020 by Rumi

First try to unlock the pct (assuming your troubled container is 101):

pct unlock 101

if it works just stop and start again the vm. if it does’nt work (my case) try to stop with this

lxc-stop --name 101

if it’s does’nt work (my case) you can force stop with kill command

ps ax | grep lxc

then kill the process with your id (101 for me) kill pid (replace pid by the process name). After that you can just launch again you’r vm

Remove Proxmox Subscription Notice

November 1, 2020 by Rumi

Copy and paste following command to the terminal

(6.1 and up)

sed -i.backup "s/data.status !== 'Active'/false/g" /usr/share/javascript/proxmox-widget-toolkit/proxmoxlib.js && systemctl restart pveproxy.service

(6.2-11 and up)

sed -i.backup -z "s/res === null || res === undefined || \!res || res\n\t\t\t.false/false/g" /usr/share/javascript/proxmox-widget-toolkit/proxmoxlib.js && systemctl restart pveproxy.service

(6.2-12 and up) Continue reading “Remove Proxmox Subscription Notice” »

Remove Node from Proxmox Cluster

September 9, 2020 by Rumi

Step 1 : Migrate all VMs to another active node

Migrate all VMs to another active node. You can use the live migration feature if you have a shared storage or offline migration if you only have local storage.

Step 2 : Display all active nodes

Display all active nodes in order identify the name of the node you want to remove Continue reading “Remove Node from Proxmox Cluster” »

Fix Proxmox (PVE) “can’t lock file ‘/var/lock/qemu-server/lock-xxx.conf’ – got timeout” (Proxmox can’t shutdown/stop virtual machine) (Proxmox kill/force stop virtual machine)

August 14, 2020 by Rumi

The Issue

When trying to “Stop” or “Shutdown” virtual machine from Proxmox (PVE) web gui, the “Cluster log” shows

end task UPID:pve:xxxxxxxx:xxxxxxxx:xxxxxxx:qmstop:xxx:root@pam: can’t lock file ‘/var/lock/qemu-server/lock-xxx.conf’ -got timeout
end task UPID:pve:xxxxxxxx:xxxxxxxx:xxxxxxx:qmreboot:xxx:root@pam: VM quit/powerdown failed

The Fix

We can manually delete the lock from following path

/run/lock/qemu-server

# The file will be
/run/lock/qemu-server/lock-100.conf
/run/lock/qemu-server/lock-102.conf
...

Make sure only delete the correct one!

You can also do it using script from this site-

https://dannyda.com/2020/05/11/how-to-fix-proxmox-pve-cant-lock-file-var-lock-qemu-server-lock-xxx-conf-got-timeout-proxmox-cant-shutdown-virtual-machine/

Reclaim disk space from a sparse image file qcow2/ vmdk

July 23, 2020 by Rumi

Sparse disk image formats such as qcow2 only consume the physical disk space which they need. For example, if a guest is given a qcow2 image with a size of 100GB but has only written to 10GB then only 10GB of physical disk space will be used. There is some slight overhead associated, so the above example may not be strictly true, but you get the idea.

Sparse disk image files allow you to over allocate virtual disk space – this means that you could allocate 5 virtual machines 100GB of disk space, even if you only have 300GB of physical disk space. If all the guests need 100% of their 100GB disk space then you will have a problem. If you use over allocation of disk space you will need to monitor the physical disk usage very carefully.

There is another problem with sparse disk formats, they don’t automatically shrink. Let’s say you fill 100GB of a sparse disk (we know this will roughly consume 100GB of physical disk space) and then delete some files so that you are only using 50GB. The physical disk space used should be 50GB, right? Wrong. Because the disk image doesn’t shrink, it will always be 100GB on the file system even if the guest is now using less. The below steps will detail how to get round this issue. Continue reading “Reclaim disk space from a sparse image file qcow2/ vmdk” »

Bots!

Brain's Workbench

Tag Archives: Proxmox