after upgrading from 1.4 beta 2 to 1.4 stable release all of my VMs don't work.
The setup is as follow:
LVM Group is named: VG-Compartido1 and is marked as shared
iscsi storage pool has "Use LUNS Directly" disabled.
All the VMs have their disks stored on the LVM Group (VG-Compartido1) with the default names provided by proxmox web-ui.
When I try to start machine 113 (just one of the machines) from the web ui, it simply doesn't do anything. If I run the command
I get the error: unable to parse volume ID 'VG-Compartido1:vm-106-disk-1'
It's word noting the VM has only one disk configured:
If I run from the command line the following:
I get the following:
If I change ide0: line on the config file of vmid 106 to
everything works, but of course, I lose migration capabilities.
And if I run
I get
but when trying to find path on filesystem of any of those devices with, for example:
I get again the error: unable to parse volume ID 'VG-Compartido1:vm-106-disk-1'
The contents of /etc/pve/storage.cfg is
The question, of course is: how can I fix this?.
And, how does pve (or qemu) know that (in this particular case) VG-Compartido1 is /dev/pve-compartido?
The setup is as follow:
1 Local storage pool which I don't use at all
1 iscsi pool used as base storage pool for
1 LVM Group storage pool
2 Directory storage pools I used before the new storage model. These 2 directories were 2 mountpoints for 2 iscsi disks manually configured. These pools are not really used anymore.
LVM Group is named: VG-Compartido1 and is marked as shared
iscsi storage pool has "Use LUNS Directly" disabled.
All the VMs have their disks stored on the LVM Group (VG-Compartido1) with the default names provided by proxmox web-ui.
When I try to start machine 113 (just one of the machines) from the web ui, it simply doesn't do anything. If I run the command
Code:
qm start 106It's word noting the VM has only one disk configured:
Code:
name: Caballo-Procesos-PDC
ide2: none,media=cdrom
sockets: 1
vlan0: rtl8139=E2:2C:FC:5D:00:0C
ostype: w2k3
memory: 4096
onboot: 1
cores: 2
boot: ca
freeze: 0
cpuunits: 1000
acpi: 1
kvm: 1
ide0: VG-Compartido1:vm-106-disk-1
bootdisk: ide0If I run from the command line the following:
Code:
pvesm list
Code:
Backups-PS5000-0 dir 0 1 16409832 4889808 30%
Imagenes-en-PS6000 dir 0 1 16409832 4889808 30%
VG-Compartido1 lvm 0 1 524296192 343932928 66%
iscsi-pv1 iscsi 0 1 0 0 100%
local dir 0 1 39349688 13076128 33%If I change ide0: line on the config file of vmid 106 to
Code:
ide0: /dev/pve-compartido/vm-106-disk-1And if I run
Code:
pvesm list --all
Code:
local:106/vm-106-disk.raw 106 raw 1969664
iscsi-pv1:0.0.0.scsi-36090a048508ab2c661adf4b3abd69e16 0 raw 524298240
VG-Compartido1:vm-101-disk-1 101 raw 83886080
VG-Compartido1:vm-102-disk-1 102 raw 36700160
VG-Compartido1:vm-106-disk-1 106 raw 23068672
VG-Compartido1:vm-112-disk-1 112 raw 37748736
VG-Compartido1:vm-112-disk-2 112 raw 158334976
VG-Compartido1:vm-113-disk-1 113 raw 2097152
VG-Compartido1:vm-113-disk-2 113 raw 2097152but when trying to find path on filesystem of any of those devices with, for example:
Code:
pvesm path VG-Compartido1:vm-106-disk-1The contents of /etc/pve/storage.cfg is
Code:
dir: local
path /var/lib/vz
content images,iso,vztmpl,rootdir
dir: Imagenes-en-PS6000
path /PS6000-proxmox-0
shared
content images
dir: Backups-PS5000-0
path /Backups-PS5000-0
shared
content backup
iscsi: iscsi-pv1
portal 172.26.0.3
target iqn.2001-05.com.equallogic:0-8a0906-c6b28a504-169ed6abb3f4ad61-promoxcompartido
content none
lvm: VG-Compartido1
vgname pve-compartido
shared
content imagesThe question, of course is: how can I fix this?.
And, how does pve (or qemu) know that (in this particular case) VG-Compartido1 is /dev/pve-compartido?
