I am running the latest proxmox on an Intel SR2600UR with two Xeon E5520. It shows up as 16 cores in proxmox so the HT should be supported correctly.
Proxmox installs without any trouble. However I have had some trouble with kvm machines hanging or going into pause randomly (another thread on this forum). It seemed related to multicore kvm's. Single core KVMs have been running fine. Unfortunately I have not had time to dig deeper into whether there is a problem or not. At the moment we mostly use OpenVZ machines which run very stable.
Someone writes about kernel 2.6.31-rc6 solving the problem. Are the 2.6.31 KVM patches backported to Proxmox 1.4?
Is there a safe way to downgrade again if it does not work correctly? The server is used for production now, but we are only dependent on openVZ machines.
Nov 17 18:16:03 jango kernel: ioctl32(mount:5639): Unknown cmd fd(3) cmd(80041272){t:12;sz:4} arg(bfee8798) on /
Nov 17 18:16:03 jango kernel: ioctl32(mount:5639): Unknown cmd fd(3) cmd(00001260){t:12;sz:0} arg(bfee87a0) on /
Nov 17 18:16:03 jango kernel: ioctl32(mount:5639): Unknown cmd fd(3) cmd(801c0204){t:02;sz:28} arg(bfee877c) on /
Nov 17 18:16:03 jango kernel: ioctl32(mount:5639): Unknown cmd fd(3) cmd(80041272){t:12;sz:4} arg(bfee8798) on /
Nov 17 18:16:03 jango kernel: ioctl32(mount:5639): Unknown cmd fd(3) cmd(00001260){t:12;sz:0} arg(bfee87a0) on /
Nov 17 18:16:03 jango kernel: ioctl32(mount:5639): Unknown cmd fd(3) cmd(801c0204){t:02;sz:28} arg(bfee877c) on /
I loaded the new kernel and it seems ok so far. I'll try put some stress on it tomorrow.
I noticed the following when starting OpenVZ machines:
But it also showed up in the previous 2.6.24-8 kernel. I'll post the results of stress testing as soon as possible.Code:Nov 17 18:16:03 jango kernel: ioctl32(mount:5639): Unknown cmd fd(3) cmd(80041272){t:12;sz:4} arg(bfee8798) on / Nov 17 18:16:03 jango kernel: ioctl32(mount:5639): Unknown cmd fd(3) cmd(00001260){t:12;sz:0} arg(bfee87a0) on / Nov 17 18:16:03 jango kernel: ioctl32(mount:5639): Unknown cmd fd(3) cmd(801c0204){t:02;sz:28} arg(bfee877c) on / Nov 17 18:16:03 jango kernel: ioctl32(mount:5639): Unknown cmd fd(3) cmd(80041272){t:12;sz:4} arg(bfee8798) on / Nov 17 18:16:03 jango kernel: ioctl32(mount:5639): Unknown cmd fd(3) cmd(00001260){t:12;sz:0} arg(bfee87a0) on / Nov 17 18:16:03 jango kernel: ioctl32(mount:5639): Unknown cmd fd(3) cmd(801c0204){t:02;sz:28} arg(bfee877c) on /
you can ignore this well known but harmless bug.
Hi Tom,
And about my problem with live migration AMD 2 cpus in guest ? I tested this new kernel and the problem still the same.
First test results:
VMs:
2x Ubuntu 8.04 server i386
2GB RAM, IDE, raw-file, rtl8139, 1 socket, 4 cores
So far so good, 10 hours of intensive compiling on both machines without any trouble. Continuing the tests for the rest of the week. I'll raise the load by adding two extra machines when we are not using the server during the weekend.
We use essential cookies to make this site work, and optional cookies to enhance your experience.