My Proxmox 4.1 wouldn’t reboot. A quick look at the logs showed this was caused by the watchdog. My Supermicro (like HP) uses an IPMI hardware watchdog, but the Proxmox default is softdog.
In fact, by default, Proxmox disables loading of the ipmi_watchdog kernel module. And if you remove it from their blacklist, they just overwrite on the next update.
The fix is to uncomment the ipmi_watchdog line in /etc/default/pve-ha-manager, like so:
# select watchdog module (default is softdog)
After you reboot, you should see ipmi_watchdog output by lsmod.
Adding existing logical volumes to the list of virtual disks is non-obvious.
First add the VG to Proxmox using the “Storage|Add” UI. Once done, adding existing LV to Proxmox must be done via LVM command line tools.
A logical volume needs to have the correct naming, and (surprise!) an LVM tag set. For the correct tag (and LV name) format, use the UI to create a sample volume (VM|Hardware|Add|Hard Disk).
Note: LV names must fit a certain pattern. However, names like this seem to work: vm-110-timemachine.
The example below shows a pre-existing LV (vg1/vm-110-disk-2) without the “pve-vm-110” tag Proxmox requires.
Subsequent steps add the tag, after which the volume appears in Proxmox.
# lvs -o vg_name,lv_name,lv_tags
VG LV LV Tags
vg0 vm-110-disk-1 pve-vm-110
vg0 vm-110-disk-2 pve-vm-110
vg1 vm-110-disk-1 pve-vm-110
To see LV tags:
# lvs @pve-vm-110
LV VG Attr LSize Pool Origin Data% Move Log Copy% Convert
vm-110-disk-1 vg0 -wi-ao--- 500.00g
vm-110-disk-2 vg0 -wi-ao--- 750.00g
vm-110-disk-1 vg1 -wi-ao--- 750.00g
To add missing tags:
# lvchange --addtag pve-vm-110 /dev/vg1/vm-110-disk-2
Refresh the Proxmox Storage UI to see the new LV.