Features/Questions coming from Vmware Server 2.0

Trimmings

Well-Known Member
Nov 5, 2012
55
0
46
A few questions/things I've noticed coming from Vmware Server 2.0

1) Vmware Server allowed hibernate to disk in the server. I notice proxmox has a suspend button, but this only seems to freeze the KVM host. Is it possible to send the host via ACPI, keyboard or otherwise a 'sleep' or 'hibernate' request as you do a shutdown request? This would be very handy, as I can see right now to properly hibernate to disk I'll need to log onto each host to do this.
2) Right now I'm just using vmdk files (which, by the way is awesome as it makes migration easier and customers happier that their data is still in the same format) but I notice when I put files into the directory of the host (eg 101) they do not show up. I can refresh the web page and it still doesn't happen. The only way I've seen to do this (apart from I imagine doing a reboot of the server) is to add a new drive, delete it, then it comes up in 'unused disks' and replace that file with the file I want. Surely there is a better way? A refresh button would be great.

Lastly, this isn't a biggie but the ability to hotswap disks from/to the hosts in Vmware was awesome - I read someone say that this had to go thru the BIOS, surely using the SCSI interface hotswap should be technically possible? Is this a KVM limitation?

Cheers
 
The only way I've seen to do this (apart from I imagine doing a reboot of the server) is to add a new drive, delete it, then it comes up in 'unused disks' and replace that file with the file I want. Surely there is a better way? A refresh button would be great.

# qm rescan <vmid>

Lastly, this isn't a biggie but the ability to hotswap disks from/to the hosts in Vmware was awesome - I read someone say that this had to go thru the BIOS, surely using the SCSI interface hotswap should be technically possible? Is this a KVM limitation?

Our hostswap support is still experimental, sorry.
 
Tried that, nope it errors like this?

root@proxmox1:~# qm rescan 100
400 wrong number of arguments
qm rescan [OPTIONS]
 
It accepts this command, but no effect. This will be quite a pain since I'll be migrating a bunch of images for testing :/

p.s. This is actually quite unfortunate because I can't give any of the files/drives meaningful names.

try the following.

# qm rescan --vmid 100
 
Last edited:
Never tried qm rescan, yesterday I did editing the <VMID>.conf and adding at the bottom something like
Code:
unused0: local:204/vm-204-disk-1.qcow2
but sure a refresh button would be much better.
Ah, maybe your VM file is not named correctly? do you use the vm-<VMID>-disk-<n>.<extension> format? (just a guess)
 
Win! Editing the file works great to add offline drives (assuming the vm is off at the time lol), I can even retain meaningful file names. I won't be using the add disk function due to this, I'd far perfer to have meaningful disk image file names than something nondescriptive in any case, this is just basic function in my opinion.

Never tried qm rescan, yesterday I did editing the <VMID>.conf and adding at the bottom something like
Code:
unused0: local:204/vm-204-disk-1.qcow2
but sure a refresh button would be much better.
Ah, maybe your VM file is not named correctly? do you use the vm-<VMID>-disk-<n>.<extension> format? (just a guess)
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!