Proxmox 3.4 - Centos 6.7 - VM

[Bazcor]

Hi,

Do you know if exists any restriction to create VMs?

I am facing an issue related to the disk size... if the disk size is lower than 5G the machine after the instalation is booting and getting a Kernel Panic. I solved changing on grub at kernel line "selinux=0" at end. If I create a machine with 5G it is working perfectly after boot.

Any help it would be great.

Thanks in advance.

Bazcor

 

[tom]

works here. I just installed a CentOS-6.7-x86_64-LiveCD.iso on a 4 GB virtio disk.

post the output of:

> pveversion -v

and your VM config:

> qm config VMID

 

[Bazcor]

Sorry... I cannot paste my details due to I have a few posts and it is resolving some info as a link.

 

[Bazcor]

Let me paste a few posts in order to get the neccessary req. to paste my details...

 

[Bazcor]

root@pve:~# pveversion -v
proxmox-ve-2.6.32: 3.4-156 (running kernel: 2.6.32-39-pve)
pve-manager: 3.4-6 (running version: 3.4-6/102d4547)
pve-kernel-2.6.32-39-pve: 2.6.32-156
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-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.10-2
pve-cluster: 3.0-17
qemu-server: 3.4-6
pve-firmware: 1.1-4
libpve-common-perl: 3.0-24
libpve-access-control: 3.0-16
libpve-storage-perl: 3.0-33
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 2.2-10
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1
root@pve:~#

root@pve:~# qm config 700
bootdisk: sata0
cores: 1
ide2: local:iso/CentOS-6.7-x86_64-bin-DVD1.iso,media=cdrom
memory: 512
name: Centos67
net0: e1000=8E:E0:303:76:89,bridge=vmbr0
numa: 0
ostype: l26
sata0: local:700/vm-700-disk-1.qcow2,format=qcow2,size=3G
smbios1: uuid=3c62d72e-5ca9-44ae-af1b-3a37735299ad
sockets: 1
root@pve:~#

 

[Bazcor]

Console error is:

http://bazcor.sytes.net:40080/proxmox_error/error_proxmox.png

 

[Bazcor]

A detailed error is:

http://bazcor.sytes.net:40080/proxmox_error/error_proxmox2.png

If I follow the instructions related to add selinux=0 to kernel parameter in grub.conf file, next boot will work fine.

 

[tom]

root@pve:~# pveversion -v
...

you run an old version of 3.4, update to latest, see:
http://pve.proxmox.com/wiki/Downloads

root@pve:~# qm config 700
bootdisk: sata0
cores: 1
ide2: local:iso/CentOS-6.7-x86_64-bin-DVD1.iso,media=cdrom
memory: 512
name: Centos67
net0: e1000=8E:E0:303:76:89,bridge=vmbr0
numa: 0
ostype: l26
sata0: local:700/vm-700-disk-1.qcow2,format=qcow2,size=3G
smbios1: uuid=3c62d72e-5ca9-44ae-af1b-3a37735299ad
sockets: 1
root@pve:~#

for best performance, use virtio network and virtio disk.

 

[tom]

Console error is:

http://bazcor.sytes.net:40080/proxmox_error/error_proxmox.png

By using the same DVD ISO and settings, I tried the same in the lab and also on VMware Workstation - I got on both exactly the same kernel panic.

So the issue is not related to Proxmox VE, please report a bug to the Centos/Redhat team.

 

[Bazcor]

Hi Tom,

Thanks for your support.

To upgrade my current PROXMOX, do I have to purchase a subscription?

I will report the bug to Centos/RedHat Team.