Quantcast
Channel: Proxmox Support Forum
Viewing all articles
Browse latest Browse all 170561

MP-BIOS bug: 8254 timer not connected to IO-APIC ???????

$
0
0
I am getting this message on the console when I start some guests:

ACPI: Core revision 20060707
Kernel panic - not syncing: IO-APIC + timer doesn't work! Try using the 'noapic' kernel parameter.


I have transfered (backup-restore) two KVMs from one server to another and on the "new" server when I start each of the KVMs I am getting the above error.
I have searched the forums and some discussions relate to speed that KVMs are started when the node server starts...but here we are talking a about a running node. I never had this problem with those guest when they were on the other node.


If I STOP and START the KVMs (each one individually) its happening again but after a few times it works.
What is causing this? :confused:


--
root@prx-a:~# pveversion -v
proxmox-ve-2.6.32: 3.1-121 (running kernel: 2.6.32-27-pve)
pve-manager: 3.1-43 (running version: 3.1-43/1d4b0dfb)
pve-kernel-2.6.32-27-pve: 2.6.32-121
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
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.5-1
pve-cluster: 3.0-12
qemu-server: 3.1-15
pve-firmware: 1.1-2
libpve-common-perl: 3.0-13
libpve-access-control: 3.0-11
libpve-storage-perl: 3.0-19
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-6
vzctl: 4.0-1pve4
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.7-4
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.2-1
root@prx-a:~#
--


Nikole

Viewing all articles
Browse latest Browse all 170561

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>