proxmox 2.0 VM hanfs at boot with 100% cpu when VM has 3 virtio NICs

uriella_superstar

New Member
Apr 19, 2012
4
0
1
hello out there
while testing proxmox 2.0 we have got a strange issue:

This is our Test VM:
---------------------------------------------------------------
- Linux 2.6 (Ubuntu 10.04 LTS)
- 3x NIC (virtio)
- 1x HDD 20GB (virtio)
- 1 CPU
- 512 MB RAM
---------------------------------------------------------------
bootdisk: virtio0
cores: 1
ide1: local:iso/ubuntu-10.04.1-server-amd64.iso,media=cdrom
memory: 512
name: test32
net0: virtio=EE:15:58:C1:74:C3,bridge=vmbr0
net1: virtio=C2:08:1B:CC:A8:B7,bridge=vmbr1
net2: virtio=26:32:FC:15:7A:8F,bridge=vmbr2
ostype: l26
sockets: 1
virtio0: local:100/vm-100-disk-1.raw
---------------------------------------------------------------

This is our Proxmox Server:
---------------------------------------------------------------
pve-manager: 2.0-59 (pve-manager/2.0/18400f07)
running kernel: 2.6.32-11-pve
proxmox-ve-2.6.32: 2.0-66
pve-kernel-2.6.32-11-pve: 2.6.32-66
lvm2: 2.02.88-2pve2
clvm: 2.02.88-2pve2
corosync-pve: 1.4.3-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.8-3
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.7-2
pve-cluster: 1.0-26
qemu-server: 2.0-38
pve-firmware: 1.0-15
libpve-common-perl: 1.0-26
libpve-access-control: 1.0-18
libpve-storage-perl: 2.0-17
vncterm: 1.0-2
vzctl: 3.0.30-2pve2
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 1.0-9
ksm-control-daemon: 1.1-1

AND THIS IS THE PROBLEM:
---------------------------------------------------------------
- VM is hanging after boot with 100% cpu
- there is no special output at the VM console (as far as I can see :)

STRANGE IS:
---------------------------------------------------------------
- If we remove one NIC and reboot .... IT WORKS
- If we change one NIC type from virtio to rtl8139 ... IT WORKS
- We where able to reporduce the problem on multiple servers which where working fine with Proxmox 1.9???!!!

does anybody knows this problem?

tnx a lot

chris
 
hi udo
tnx for the fast reply.

I also guess, this is our problem.

As far as I can see, there is nothing that I can help at the moment.

We reporduced the problem with:
- CentOS 6.2 x64
- Ubuntu 10.04 LTS x64
- Ubuntu 11.10 i386
- Ubuntu 11.10 x64
- Ubuntut 12.04 LTS

tnx a lot for the help

chris