0kB disk in Virtual Machines List

[pcravero]

Hi.
I'm running:

~# pveversion -v
pve-manager: 1.7-11 (pve-manager/1.7/5470)
running kernel: 2.6.32-4-pve
proxmox-ve-2.6.32: 1.7-30
pve-kernel-2.6.32-4-pve: 2.6.32-30
qemu-server: 1.1-28
pve-firmware: 1.0-10
libpve-storage-perl: 1.0-16
vncterm: 0.9-2
vzctl: 3.0.24-1pve4
vzdump: 1.2-10
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.13.0-3
ksm-control-daemon: 1.0-4

with KVM VMs hosted on LVM/iSCSI Group. I have been creating and destroying VMs, so VMIDs are being recycled. On #101 and #102 I've had a strange behavior.

#101 had a 16GB VIRTIO disk. Destroyed, re-created with an 8 GB disk... the CentOS 5.5 installer saw the original 16GB. On the web console in the global VM list - and only there - the disk was reported as 0kB. (BTW, it is "kB" and not "KB"). This was magically solved when I deleted the disk from the stopped VM, destroyed the VM and then created a new one: both reported allocated space and VM disk matched.


#102 has a 12,00GB IDE device and it is reported as 0kB (at https://x.x.x.x/vmlist/index.htm) while everywhere else I see the correct space. The w2k8r2 VM sees 12,00 GB. Other relevant output from the hosting node:

# lvdisplay -m
  --- Logical volume ---
  LV Name                /dev/proxmox/vm-102-disk-1
  VG Name                proxmox
  LV UUID                vuheih-qdxB-ksuZ-lj2y-gApw-dhSL-4LhnKP
  LV Write Access        read/write
  LV Status              available
  # open                 1
  LV Size                12.00 GB
  Current LE             3072
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           254:12

  --- Segments ---
  Logical extent 0 to 3071:
    Type                linear
    Physical volume     /dev/sdd
    Physical extents    30725 to 33796

# lvs -v
    Finding all logical volumes
  LV            VG      #Seg Attr   LSize  Maj Min KMaj KMin Origin Snap%  Move Copy%  Log Convert LV UUID
  vm-102-disk-1 proxmox    1 -wi-ao 12.00G  -1  -1 254  12                                         vuheih-qdxB-ksuZ-lj2y-gApw-dhSL-4LhnKP

# fdisk -l
Disk /dev/dm-12: 12.8 GB, 12884901888 bytes
255 heads, 63 sectors/track, 1566 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x79c01718

      Device Boot      Start         End      Blocks   Id  System
/dev/dm-12p1   *           1          13      102400    7  HPFS/NTFS
Partition 1 does not end on cylinder boundary.
/dev/dm-12p2              13        1567    12478464    7  HPFS/NTFS

# pvdisplay -m
  --- Physical volume ---
  PV Name               /dev/sdd
  VG Name               proxmox
  PV Size               279.00 GB / not usable 4.00 MB
  Allocatable           yes
  PE Size (KByte)       4096
  Total PE              71423
  Free PE               41210
  Allocated PE          30213
  PV UUID               f40EUI-YIBE-8zhp-jV9A-VaWp-8l9s-sKo3RR

  --- Physical Segments ---
[cut]
  Physical extent 30725 to 33796:
    Logical volume      /dev/proxmox/vm-102-disk-1
    Logical extents     0 to 3071
  Physical extent 33797 to 36356:
    Logical volume      /dev/proxmox/vm-108-disk-1
    Logical extents     0 to 2559
[cut]

I guess this is only a console bug since everything else seems to be working properly. Is there any test/patch/whatever I can try to help you trace and fix the issue?

Paolo

 

[dswartz]

As far as I can tell, virtio disks always seem to have this happen (e.g. size reported as 0).

 

[pcravero]

@dswartz, not really! I set virtio on all Linux VMs and it always seems to work, except if I am re-using a VMID (but not 100% sure about this, might be a coincidence)

See:

 

[dswartz]

Interesting. My proxmox is not handy right now, but I have a ubuntu KVM with 3 virtio disks. I will check on this when I get home and see what it says...

 

[qk4l]

I also have the same problem on some kvm hosts.

Note: In hardware tab all looks ok

pveversion -v
pve-manager: 1.7-11 (pve-manager/1.7/5470)
running kernel: 2.6.35-1-pve
proxmox-ve-2.6.35: 1.7-9
pve-kernel-2.6.35-1-pve: 2.6.35-9
qemu-server: 1.1-28
pve-firmware: 1.0-10
libpve-storage-perl: 1.0-16
vncterm: 0.9-2
vzctl: 3.0.24-1pve4
vzdump: 1.2-10
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.13.0-3
ksm-control-daemon: 1.0-4

 

[m.ardito]

i remember something similar on the old 1.5, it seems to me that it was related to the drives listed in the boot priority options... try resetting them
also i remember pve manager only seems to list the disk capacity of the _boot_ disk, no matter if you have others...
i'm not certain though

Marco

 

[qk4l]

i remember something similar on the old 1.5, it seems to me that it was related to the drives listed in the boot priority options... try resetting them
also i remember pve manager only seems to list the disk capacity of the _boot_ disk, no matter if you have others...
i'm not certain though
Marco

Yea! It`s work, thank you! =)

 

[pcravero]

Bingo!

For the records (and the less experienced in proxmox): modify /etc/qemu-server/<VMID>.conf .

Make the bootdisk: value match the actual disk label (ide0, scsi0, virtio0, ...).


Refresh the vmlist.htm page and the correct size is shown. Nothing has to be rebooted. Cool.

Paolo

 

[m.ardito]

Bingo!
For the records (and the less experienced in proxmox): modify /etc/qemu-server/<VMID>.conf .
Make the bootdisk: value match the actual disk label (ide0, scsi0, virtio0, ...).
Refresh the vmlist.htm page and the correct size is shown. Nothing has to be rebooted. Cool.
Paolo

Well, for the REALLY less experienced, reset the boot options from scratch using the web interface, and then "save"... ))

Of course under the hood pve modifies some files on your server...

Glad that it worked: my memory isn't too bad, after all...(im getting 45! )

Marco