migration debian vmware -> Proxmox

[tsaenger]

Hello,
i migrated my debian from vmware Server 2.0 to proxmox successfully.
My problem is at the moment, that i can not see in my proxmox VM-List how much CPU and HDD is in use. Its only display how much memory use.
Has somebody an idea who to fix it?

Thanks a lot

Tobias

 

[tom]

pls provide a screenshot.

 

[tsaenger]

Hi,

here you are.





Thanks a lot

Tobias

 

[tom]

so you are using containers and not KVM guests? how did you migrate, in detail?

 

[tsaenger]

hi tom,

i used this tutorial:
http://howtoforge.com/how-to-convert-physical-systems-and-xen-vms-into-openvz-containers-debian-etch

after that i did:

[B] Move OpenVZ containers to Proxmox VE[/B]

 You can move existing OpenVZ containers (container=VE=VPS) with vzmigrate or vzdump: 
 
[LIST]
[*] Use vzmigrate offline migration to move your container to Proxmox VE
[*] Use vzdump to restore from a backup
[/LIST]
 After you moved your container you need to add the following line to the corresponding config file (see /etc/vz/conf/xyz.conf): 
 nano /etc/vz/conf/xyz.conf Add/edit the following line: 
 ORIGIN_SAMPLE="pve.auto" Now you can manage resource settings on the Proxmox VE management interface

thanks for help

tobias

 

[tom]

did you followed this? http://pve.proxmox.com/wiki/Migration_of_servers_to_Proxmox_VE#Move_OpenVZ_containers_to_Proxmox_VE

after you added the pve-auto just edit some parameter on the web gui (disk size or ram) and click save. better now?

 

[tsaenger]

hi tom,

yes i changed the hdd and ram values.
It worked fine.

Tobias

 

[tom]

so the issue is solved?

 

[tsaenger]

Hi tom,

no i changed the settings at the beginning (2 days ago). The problem still exists.

TObias

 

[tom]

post one of your openvz config files.
and post the output of 'pveverson -v' - I assume you are already using the latest versions?

 

[tsaenger]

212.conf

ONBOOT="yes"

# UBC parameters (in form of barrier:limit)
KMEMSIZE="14372700:14790164"
LOCKEDPAGES="262144:262144"
PRIVVMPAGES="393216:405716"
SHMPAGES="21504:21504"
NUMPROC="240:240"
PHYSPAGES="0:9223372036854775807"
VMGUARPAGES="393216:9223372036854775807"
OOMGUARPAGES="393216:9223372036854775807"
NUMTCPSOCK="360:360"
NUMFLOCK="188:206"
NUMPTY="16:16"
NUMSIGINFO="256:256"
TCPSNDBUF="1720320:2703360"
TCPRCVBUF="1720320:2703360"
OTHERSOCKBUF="1126080:2097152"
DGRAMRCVBUF="262144:262144"
NUMOTHERSOCK="360:360"
DCACHESIZE="3409920:3624960"
NUMFILE="9312:9312"
AVNUMPROC="180:180"
NUMIPTENT="128:128"

# Disk quota parameters (in form of softlimit:hardlimit)
DISKSPACE="41943040:46137344"
DISKINODES="8000000:8800000"
QUOTATIME="0"
# CPU fair sheduler parameter
CPUUNITS="1000"
ORIGIN_SAMPLE="pve.auto"
OSTEMPLATE="debian-5.0-standard_5.0-2"
CPUS="1"
IP_ADDRESS="10.16.0.229"
HOSTNAME="webserver.xxz.de"
NAMESERVER="10.16.0.227"
SEARCHDOMAIN="xyz.de"

vm:/etc/vz/conf# pveversion -v

pve-manager: 1.6-2 (pve-manager/1.6/5087)
running kernel: 2.6.32-4-pve
proxmox-ve-2.6.32: 1.6-19
pve-kernel-2.6.32-4-pve: 2.6.32-19
qemu-server: 1.1-18
pve-firmware: 1.0-8
libpve-storage-perl: 1.0-14
vncterm: 0.9-2
vzctl: 3.0.24-1pve4
vzdump: 1.2-7
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.12.5-1
ksm-control-daemon: 1.0-4

Tobias

 

[svenr]

sometimes after migrating to openvz, proxmox was showing wrong values for quota, but this was working correct after stopping the vm, dropping the quota with vzquota and restarting the vm. maybe this is working here too


Sven

 

[tsaenger]

Hello,

after i did:

vzquota drop 101

my system will not start again.

I get this error at my host-log:

Nov 23 11:53:55 vm pvedaemon[13443]: starting VM 101 on node 0 (localhost)
Nov 23 11:53:55 vm pvedaemon[13443]: VM 101 start failed -

My 101.conf looks like this:

# PVE default config for 256MB RAM

ONBOOT="yes"

# Primary parameters
NUMPROC="1024:1024"
NUMTCPSOCK="9223372036854775807:9223372036854775807"
NUMOTHERSOCK="9223372036854775807:9223372036854775807"
VMGUARPAGES="262144:9223372036854775807"

# Secondary parameters
KMEMSIZE="9223372036854775807:9223372036854775807"
OOMGUARPAGES="262144:9223372036854775807"
PRIVVMPAGES="262144:274644"
TCPSNDBUF="9223372036854775807:9223372036854775807"
TCPRCVBUF="9223372036854775807:9223372036854775807"
OTHERSOCKBUF="9223372036854775807:9223372036854775807"
DGRAMRCVBUF="9223372036854775807:9223372036854775807"

# Auxiliary parameters
NUMFILE="9223372036854775807:9223372036854775807"
NUMFLOCK="9223372036854775807:9223372036854775807"
NUMPTY="255:255"
NUMSIGINFO="1024:1024"
DCACHESIZE="9223372036854775807:9223372036854775807"
LOCKEDPAGES="131072:131072"
SHMPAGES="9223372036854775807:9223372036854775807"
NUMIPTENT="9223372036854775807:9223372036854775807"
PHYSPAGES="0:9223372036854775807"

# Disk quota parameters
DISKSPACE="20971520:23068672"
DISKINODES="4000000:4400000"
QUOTATIME="0"
QUOTAUGIDLIMIT="0"

# CPU fair sheduler parameter
CPUUNITS="1000"
CPUS="1"
VE_ROOT="/var/lib/vz/root/$VEID"
VE_PRIVATE="/var/lib/vz/private/$VEID"
OSTEMPLATE="debian-5.0-standard_5.0-2_i386"
ORIGIN_SAMPLE="pve.auto"
IP_ADDRESS="10.16.0.249"
HOSTNAME="name.tld.de"
NAMESERVER="10.16.0.227"
SEARCHDOMAIN="tld.de"

how can i sove this?

Thanks for help.

Tobias

 

[tom]

any more info if you start the container from the commandline?

vzctl start 101

 

[tsaenger]

Hi tom,

yes:

Starting container ...
Initializing quota ...
vzquota : (error) Quota is running, stop it first

but:

vm:/etc/vz/conf# vzquota show 101
vzquota : (error) Can't open quota file for id 101, maybe you need to reinitialize quota: No such file or directory
vzquota : (error) Quota file must exist for show command
vm:/etc/vz/conf# vzquota drop 101
vzquota : (error) Can't open quota file for id 101, maybe you need to reinitialize quota: No such file or directory

What can i do?

Thanks

Tobias

 

[tom]

See http://forum.proxmox.com/threads/2028-vzquota-Can-t-open-quota-file

 

[tsaenger]

Hi Tom,

thanks for the link.
my Container starts again.
But the view about my containers shows me again: 0KB in user HDD ans 0% use of CPU.

What could it be?

Thanks
Tobias