Refresh Items in "Storage List" and "Hardware", KVM import

[spdriver]

Hi,

I was migrating KVM guests from local Storage to a new Proxmox setup 1.5 with DRBD and a LVM Volumes now.

I had manually imported KVM disk files to my new setup with DRBD/LVM.

Configuration file was adapted to preserve the MAC address of my KVM guest (Windows Server 2008).

Was able to start the KVM guest successfully.


How can I refresh items in the GUI?

The GUI does not reflect items in Hardware TAB, size of the discs is shown with 0GB, but they have 24GB and 32GB really.

Other items in storage do not show up correctly when using "Browsing" the Backup, Local and LVM objects.
I was expecting the GUI to do similar refreshing of objects as an admin doing "ls" in a given directory...

Why is there no refreshing? Where to trigger this manually?


I am doing all this actions on a proxmox master of a two node cluster...

thanks.

 

[dietmar]

Where to trigger this manually?

Try to restart pvedaemon and apache:

# /etc/init.d/pvedaemon restart

and if this does not help

# /etc/init.d/apache2 restart

 

[whinpo]

the size of disk to 0 can be due to missing tags on the lv (depends how you've done the migration)
check :

# lvs -o lv_name,lv_tags

you should see something like :

neptune2:~# lvs -o lv_name,lv_tags
  LV                  LV Tags   
  Proxmox-Backup-disk           
  vm-101-disk-1       pve-vm-101
  vm-102-disk-1       pve-vm-102
  vm-103-disk-1       pve-vm-103

 

[spdriver]

Thank you, after learning something about LV tags now:
OK, I added the tags now with

lvchange --addtag pve-vm-901 /dev/mapper/drbdkvm-vm--901--disk--1
lvchange --addtag pve-vm-901 /dev/mapper/drbdkvm-vm--901--disk--2

Both LVs have the same tag now, they belong to a VM with ID 901, residing on a DRBD-mirrored Volume Group "drbdkvm".

Now these LogicalVolumes are showing up in the Storage view, now beeing visible with size value.
Before - without LV tags - they had not shown up in the Storage view.


In the Hardware tab of the 901 VM it is not refreshed, the disk are reading size 0GB as before.
Any hints?

In Vmware, one is able to do import of an formerly existing configuration file, just to make it an active, visible VM.

Where are the settings saved in Proxmox??

One answer is the above "Logical Volume Tag".

I have the VM's config file, the LV tags, and what else?




- Just for fun, I did a KVM migration from one node to master node in parallel to writing this posting here.
After the migration, the disk sizes are appearing in the Hardware tab of the VM!!

But, where is this information coming from? Where is it saved internally??


thanks!

 

[spdriver]

- - -

 

[dietmar]

In the Hardware tab of the 901 VM it is not refreshed, the disk are reading size 0GB as before.
Any hints?

Does it help when you stopt/start the VM?

In Vmware, one is able to do import of an formerly existing configuration file, just to make it an active, visible VM.

Where are the settings saved in Proxmox??

for KVM, config is stored in /etc/qemu-server/<vmid>.conf

The format is quite simple - see 'man qm'

The disk images are stored on the storage - see man 'pvesm'

But, where is this information coming from? Where is it saved internally??

The 'lvs' command provides that info for logical volumes.