Issue starting a VM !

  • Thread starter Thread starter DJPz
  • Start date Start date
D

DJPz

Guest
Hi everyone,

I'm having an issue starting a VM, and I don't understand why o_0'

I created the VM on this VPS:

# pveversion -v
pve-manager: 1.5-10 (pve-manager/1.5/4822)
running kernel: 2.6.24-11-pve
proxmox-ve-2.6.24: 1.5-23
pve-kernel-2.6.24-11-pve: 2.6.24-23
pve-kernel-2.6.24-7-pve: 2.6.24-11
qemu-server: 1.1-16
pve-firmware: 1.0-5
libpve-storage-perl: 1.0-13
vncterm: 0.9-2
vzctl: 3.0.23-1pve11
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.12.4-1

# file /sbin/init
/sbin/init: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.8, stripped

# file /var/lib/vz/private/104/sbin/init
/var/lib/vz/private/104/sbin/init: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.15, stripped

# uname -a
Linux proxmox4 2.6.24-11-pve #1 SMP PREEMPT Fri May 14 09:28:08 CEST 2010 x86_64 GNU/Linux


Then I create a dump (vzdump) and restore the dump using vzrestore on this VPS using ID 110:
# pveversion -v
pve-manager: 1.6-2 (pve-manager/1.6/5087)
running kernel: 2.6.18-2-pve
proxmox-ve-2.6.18: 1.5-5
pve-kernel-2.6.18-2-pve: 2.6.18-5
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-2.6.18: 0.9.1-6

# file /sbin/init
/sbin/init: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.8, stripped

# file /var/lib/vz/private/110/sbin/init
/var/lib/vz/private/110/sbin/init: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.8, stripped

# uname -a
Linux proxmox6 2.6.18-2-pve #1 SMP Mon Feb 1 10:45:26 CET 2010 x86_64 GNU/Linux

When starting on this second VPS (2.6.18), i got :
# vzctl start 110
Starting container ...
Container is mounted
Setting CPU units: 1000
Setting CPUs: 4
Set hostname: XXXXX
Configure veth devices: veth106.0
Adding interface veth106.0 to bridge vmbr0 on CT0 for CT110
/usr/sbin/vznetaddbr: line 34: /proc/sys/net/ipv4/conf/veth106.0/proxy_arp: No such file or directory
/usr/sbin/vznetaddbr: line 35: /proc/sys/net/ipv4/conf/veth106.0/forwarding: No such file or directory
Unable to start init, probably incorrect template
Container start failed
Stopping container ...
Container was stopped
Container is unmounted

Any idea ?
Are VM created under 2.6.24 not compatible with 2.6.18 ??

Thanks,
DJPz
 
dietmar said:
Please can you test with more recent kernels?
Click to expand...

Hi dietmar,

How can I do that : apt-get upgrade on my second VPS ? Or dist-upgrade ?
Or apt-get install pve-kernel-2.6.18-3-pve ?

Many thanks for your answer,
 
Last edited by a moderator:
DJPz said:
Hi dietmar,

How can I do that : apt-get upgrade on my second VPS ? Or dist-upgrade ?
Or apt-get install pve-kernel-2.6.18-3-pve ?

Many thanks for your answer,
Click to expand...
Just FIY:
# apt-get install pve-kernel-2.6.18-3-pve
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
pve-kernel-2.6.18-3-pve
0 upgraded, 1 newly installed, 0 to remove and 32 not upgraded.
Need to get 32.6MB of archives.
After this operation, 0B of additional disk space will be used.
Err http://download.proxmox.com lenny/pve pve-kernel-2.6.18-3-pve 2.6.18-6
404 Not Found
Failed to fetch http://download.proxmox.com/debian/...64/pve-kernel-2.6.18-3-pve_2.6.18-6_amd64.deb 404 Not Found
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

even with #apt-get update before.

I can see pve-headers-2.6.18-4-pve_2.6.18-10_amd64.deb on repository but not 2.6.18-3. So I need to do a dist-upgrade or smth ? (And so migrating to 1.7 ?)
 
tom said:
take a look on the documentation - how to upgrade!
See http://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_to_1.7

you need to select a kernel branch and then you need to install the right virtual package.
Click to expand...

Hi tom,

Thanks for your answer but I've been looking for a way to run my VM without upgrade to proxmox 1.7 since all my PVS are in 1.6...

Anyway, I tryed to do that but :
aptitude update > OK
aptitude safe-upgrade > OK except for pve-kernel-2.6.18-3-pve, which :
Err http://download.proxmox.com lenny/pve pve-kernel-2.6.18-3-pve 2.6.18-6
404 Not Found
Err http://download.proxmox.com lenny/pve proxmox-ve-2.6.18 1.6-6
404 Not Found
Failed to fetch http://download.proxmox.com/debian/...64/pve-kernel-2.6.18-3-pve_2.6.18-6_amd64.deb 404 Not Found
Failed to fetch http://download.proxmox.com/debian/dists/lenny/pve/binary-amd64/proxmox-ve-2.6.18_1.6-6_all.deb 404 Not Found
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

What can I do ? All other packages have been updated....

I checked my apt/source.list and all is OK...

DJPz
 
Ok... My mistake... Thanks for my proxy which cached apt-get requests....

Sorry for this, btw, i'll keep you updated about my VM...

DJPz
 
dietmar said:
Please can you test with more recent kernels?
Click to expand...
Re,

Ok done with kernel 2.6.18-4 but same issue.
# pveversion -v
pve-manager: 1.6-2 (pve-manager/1.6/5087)
running kernel: 2.6.18-4-pve
proxmox-ve-2.6.18: 1.5-5
pve-kernel-2.6.18-2-pve: 2.6.18-5
pve-kernel-2.6.18-4-pve: 2.6.18-10
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-2.6.18: 0.9.1-6


# vzctl start 110
Starting container ...
Container is mounted
Setting CPU units: 1000
Setting CPUs: 4
Set hostname: XXXX
Configure veth devices: veth106.0
Adding interface veth106.0 to bridge vmbr0 on CT0 for CT110
/usr/sbin/vznetaddbr: line 34: /proc/sys/net/ipv4/conf/veth106.0/proxy_arp: No such file or directory
/usr/sbin/vznetaddbr: line 35: /proc/sys/net/ipv4/conf/veth106.0/forwarding: No such file or directory
Unable to start init, probably incorrect template
Container start failed
Stopping container ...
Container was stopped
Container is unmounted

I really don't understand what the issue could be ...

DJPz
 
the virtual packages make sure that you got the right dependencies for your system. if you do not install the virtual package you will get a not-working mix.

if you want to stay at 1.6, just use the 1.6 repository in your sources.list (use 'pve1.6' instead of 'pve')
(see http://download.proxmox.com/debian/dists/lenny/)
 
And I just updated to 1.7 and same issue :
# pveversion -v
pve-manager: 1.7-10 (pve-manager/1.7/5323)
running kernel: 2.6.18-4-pve
proxmox-ve-2.6.18: 1.7-10
pve-kernel-2.6.18-2-pve: 2.6.18-5
pve-kernel-2.6.18-4-pve: 2.6.18-10
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-2.6.18: 0.9.1-10

# vzctl start 110
Starting container ...
Container is mounted
Setting CPU units: 1000
Setting CPUs: 4
Set hostname: xxx
Configure veth devices: veth106.0
Adding interface veth106.0 to bridge vmbr0 on CT0 for CT110
/usr/sbin/vznetaddbr: line 34: /proc/sys/net/ipv4/conf/veth106.0/proxy_arp: No such file or directory
/usr/sbin/vznetaddbr: line 35: /proc/sys/net/ipv4/conf/veth106.0/forwarding: No such file or directory
Unable to start init, probably incorrect template
Container start failed
Stopping container ...
Container was stopped
Container is unmounted

Even if I remove the vmbr0, i got the issue :
# vzctl start 110
Starting container ...
mkdir: cannot create directory `/mnt/110-soda/': File exists
Container is mounted
Setting CPU units: 1000
Setting CPUs: 4
Set hostname: xxx
Unable to start init, probably incorrect template
Container start failed
Stopping container ...
Container was stopped
Container is unmounted

Many thanks,
DJPz
 
Last edited by a moderator:
what OS template do use?
 
And, from the running VM (on the first VPS):
# uname -a
Linux kali 2.6.24-11-pve #1 SMP PREEMPT Fri May 14 09:28:08 CEST 2010 i686 GNU/Linux

DJPz
 
And same issue when upgrading second VPS to 2.6.24:
# uname -a
Linux proxmox6 2.6.24-12-pve #1 SMP PREEMPT Mon Sep 20 13:02:41 CEST 2010 x86_64 GNU/Linux

# vzctl start 110
Starting container ...
Container is mounted
Setting CPU units: 1000
Setting CPUs: 4
Set hostname: XXX
Configure veth devices: veth110.0
Adding interface veth110.0 to bridge vmbr0 on CT0 for CT110
Unable to start init, probably incorrect template
Container start failed
Stopping container ...
Container was stopped
Container is unmounted

:( I dont know why it doesn't work on that VPS while running and starting/stopping on first VPS o_0'
 
Does the 'private' container dir exists?

# grep VE_PRIVATE /etc/vz/conf/<vmid>.conf

That dir exists?
 
dietmar said:
Does the 'private' container dir exists?

# grep VE_PRIVATE /etc/vz/conf/<vmid>.conf

That dir exists?
Click to expand...
Yup :(

VE_PRIVATE="/var/lib/vz/private/$VEID"

# ls -lah /var/lib/vz/private/
total 48K
drwxr-xr-x 12 root root 4.0K Jan 24 16:17 .
drwxr-xr-x 9 root root 4.0K Jan 24 15:39 ..
drwxr-xr-x 20 root root 4.0K Oct 7 11:53 101
drwxr-xr-x 20 root root 4.0K Oct 7 15:26 102
drwxr-xr-x 20 root root 4.0K Oct 7 11:48 103
drwxr-xr-x 22 root root 4.0K Oct 7 13:47 104
drwxr-xr-x 22 root root 4.0K Oct 7 15:28 105
drwxr-xr-x 20 root root 4.0K Jan 24 14:05 106
drwxr-xr-x 19 root root 4.0K Jan 22 13:07 110
....

110 is here.

But, i think is succeeded started my VM on the second VPS, but from a rsync.

From first VPS : rsync -arvpz --numeric-ids --exclude /home/ . root@10.10.10.9:/vz/private/110/
# vzctl start 110
Starting container ...
Running: /usr/sbin/vzquota show 110
Running: /usr/sbin/vzquota on 110 -r 0 -b 31457380 -B 34603108 -i 6000100 -I 6600100 -e 0 -n 0 -s 0
Mounting root: /var/lib/vz/root/110 /var/lib/vz/private/110
Running: /etc/vz/conf/110.mount
Container is mounted
Set iptables mask 0x000017bf
Set features mask 0000000000000001/0000000000000001
Running container script: /etc/vz/dists/scripts/debian-add_ip.sh
Set personality 0x00000008
Setting CPU units: 1000
Setting CPUs: 4
Configuring meminfo: 1572864
Set hostname: xxxxx
Running container script: /etc/vz/dists/scripts/debian-set_hostname.sh
Set personality 0x00000008
Running container script: /etc/vz/dists/scripts/set_dns.sh
Set personality 0x00000008
File resolv.conf was modified
Setting quota ugidlimit: 0
Running container script: /etc/vz/dists/scripts/set_ugid_quota.sh
Set personality 0x00000008
Running: /usr/sbin/vzquota stat 110 -f
Running: /usr/sbin/vzquota stat 110 -f -t
Running: vzquota setlimit 110 -b 31457280 -B 34603008 -i 6000000 -I 6600000 -e 0 -n 0
Configure veth devices: veth110.0
Running: /usr/sbin/vznetcfg init veth veth110.0
Adding interface veth110.0 to bridge vmbr0 on CT0 for CT110
Container start in progress...
proxmox6:/var/lib/vz/private# vzctl enter 110
entered into CT 110
Set personality 0x00000008
Open /dev/pts/0
xxxx:/#

For now, it's OK to me, but i'll try it later from the dump...
FYI, I did on second VPS :
#chroot /vz/private/110/ /sbin/init
chroot: cannot run command `/sbin/init': Accessing a corrupted shared library

But now, i got :
#chroot /vz/private/110/ /sbin/init
Usage: init {-e VAR[=VAL] | [-t SECONDS] {0|1|2|3|4|5|6|S|s|Q|q|A|a|B|b|C|c|U|u}}

Many thanks for your answer, and i'll keep you updated about the (corrupted ?) vzdump...

DJPz
 
You must log in or register to reply here.
Top Bottom