Proxmox 3 fresh install, CT cannot start?

Netizen

Member
Aug 16, 2012
88
0
6
On a fresh install of Proxmox 3 the CT does not start. :( I am attaching a screenshot.
KVMs are OK.

Any ideas?
 

Attachments

  • CT Cannot Start.png
    CT Cannot Start.png
    40.3 KB · Views: 23
your log shows a starting CT. do a vzctl enter ...

the log show some unneeded operations, what is this for a template?
 
This CT was created from the default template centos-5-standard_5.8-1_i386 (downloaded from Proxmox it self...so nothing non-default here)

The log only shows:

Jun 3 16:31:23 server015 pvedaemon[32009]: <root@pam> starting task UPID:server015:000084E8:0005E66F:51ACB6CB:vzstart:101:root@pam:
Jun 3 16:31:23 server015 pvedaemon[34024]: starting CT 101: UPID:server015:000084E8:0005E66F:51ACB6CB:vzstart:101:root@pam:
Jun 3 16:31:23 server015 kernel: CT: 101: started
Jun 3 16:31:23 server015 pvedaemon[32009]: <root@pam> end task UPID:server015:000084E8:0005E66F:51ACB6CB:vzstart:101:root@pam: OK
---

so why isn't showing on console?
 
I did add
1:2345:respawn:/sbin/getty 38400 tty1

within the inittab of the CT... restarted the CT.. same thing.

When I shut it down it also shows more errors:

Jun 3 16:56:01 server015 pvedaemon[42823]: <root@pam> starting task UPID:server015:0000C0C3:000827F3:51ACBC91:vzshutdown:101:root@pam:
Jun 3 16:56:01 server015 pvedaemon[49347]: shutdown CT 101: UPID:server015:0000C0C3:000827F3:51ACBC91:vzshutdown:101:root@pam:
Jun 3 16:56:08 server015 kernel: VE101: no allowed mount options found for device 0:25
Jun 3 16:56:08 server015 kernel: proc: unrecognized mount option "relatime" or missing value
Jun 3 16:56:10 server015 kernel: CT: 101: stopped


It seems that installing Proxmox on top of a fresh wheezy is not that straight-forward as per this link: http://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Wheezy

:(
 
What is the output of

# pveversion -v

pve-manager: 3.0-20 (pve-manager/3.0/0428106c)
running kernel: 2.6.32-20-pve
proxmox-ve-2.6.32: 3.0-100
pve-kernel-2.6.32-20-pve: 2.6.32-100
lvm2: 2.02.95-pve3
clvm: 2.02.95-pve3
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.0-1
pve-cluster: 3.0-4
qemu-server: 3.0-15
pve-firmware: 1.0-22
libpve-common-perl: 3.0-4
libpve-access-control: 3.0-4
libpve-storage-perl: 3.0-6
vncterm: 1.1-3
vzctl: 4.0-1pve3
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-12
ksm-control-daemon: 1.1-1
 
Hello,

My server was up for 3 month! now, today when I was installing bugzilla, the CT virtual machine suddenly stopped! When I click on start, it says
Starting container ...
Container is mounted
Setting CPU units: 1000
Setting CPUs: 1
Configure veth devices: veth101.0
Adding interface veth101.0 to bridge vmbr0 on CT0 for CT101
Killing container ...
Unable to start init, probably incorrect template
Container start failed
Container was stopped
Container is unmounted
TASK ERROR: command 'vzctl start 101' failed: exit code 47

Can anyone help? everything is down because of this:(
 
Please open a new thread as your issue is not related to this one.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!