Is there any chance of getting a bootable iso image with this 2.6.35 kernel so I can install it? Or if someone can tell me a proceedure how I can get it onto the internal drive on the Mac Mini server I am testing Proxmox on? The current Mac Mini server won't boot a kernel prior to 2.6.35 so I can't simply user the 1.6 iso and upgrade the kernel package.
New Proxmox VE kernel branch 2.6.35 - with KSM support
- Thread starter martin
- Start date
That's fair enough. Can you suggest a method where I can boot from a 2.6.35 kernel say off a thumbdrive or some minimal CD and manually install proxmox then update the proxmox kernel that's installed to 2.6.35 and reboot?
My problem is the drive controller chip that handles the internal drives is not detected by the Proxmox 2.6.32 kernel so I need to boot of a 2.3.5 kernel somehow to do the install.
I don't have any recorded data to back this up, but it seems I have less disk throughput now than when I was using 2.6.32 a couple months ago.
While doing a vzdump and a qmrestore I/O Delays went up to 70%, I don't recall ever seeing it that high before.
If I remember correctly I used to be able to do 4x simultaneous qmrestores and be up near 50% with 2.6.32.
Now 1x vzdump with no compression is 20-35% delay.
I once had over a dozen VMs running and wouldn't reach 20%, now with only 4 running there's 5-10% while idling.
Recently I started recording pveperf values, I see very slight differences between them since the release of PVE 1.6.
I wish I had recorded last years.
Most recent pveperf:
Current versions:
===
As for the install woes faced by Erk, there's no 2.6.35 kernel in the Debian repos unless you're in 'experimental', and even the nightly iso installer builds don't include a version that far.
The new Ubuntu installer ships with 2.6.35, boots amazingly quick too, but I wouldn't trust a Debiabuntu Proxmox chimera.
While doing a vzdump and a qmrestore I/O Delays went up to 70%, I don't recall ever seeing it that high before.
If I remember correctly I used to be able to do 4x simultaneous qmrestores and be up near 50% with 2.6.32.
Now 1x vzdump with no compression is 20-35% delay.
I once had over a dozen VMs running and wouldn't reach 20%, now with only 4 running there's 5-10% while idling.
Recently I started recording pveperf values, I see very slight differences between them since the release of PVE 1.6.
I wish I had recorded last years.
Most recent pveperf:
Code:
CPU BOGOMIPS: 53200.22
REGEX/SECOND: 829505
HD SIZE: 94.49 GB (/dev/mapper/pve-root)
BUFFERED READS: 215.48 MB/sec
AVERAGE SEEK TIME: 9.04 ms
FSYNCS/SECOND: 2206.86
DNS EXT: 101.23 msCurrent versions:
Code:
pve-manager: 1.6-2 (pve-manager/1.6/5087)
running kernel: 2.6.35-1-pve
pve-kernel-2.6.32-4-pve: 2.6.32-19
pve-kernel-2.6.35-1-pve: 2.6.35-6
qemu-server: 1.1-18
pve-firmware: 1.0-9
libpve-storage-perl: 1.0-14
vncterm: 0.9-2
vzctl: 3.0.24-1pve4
vzdump: 1.2-7
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1===
As for the install woes faced by Erk, there's no 2.6.35 kernel in the Debian repos unless you're in 'experimental', and even the nightly iso installer builds don't include a version that far.
The new Ubuntu installer ships with 2.6.35, boots amazingly quick too, but I wouldn't trust a Debiabuntu Proxmox chimera.
Last edited:
Today I ran a few more for comparison's sake, they seem the same at least in this benchmarking method.
The CPUs are dual Xeon 5470 quad-core 3.33GHz:
pve-kernel-2.6.35-1, and irqbalance:
pve-kernel 2.6.32-4 +irqbalance:
I also noticed my load numbers hovering around 2.xx, whereas I remember .xx range- again, I'm without recorded data to compare to. doh!
The CPUs are dual Xeon 5470 quad-core 3.33GHz:
pve-kernel-2.6.35-1, and irqbalance:
Code:
pveperf
CPU BOGOMIPS: 53199.32
REGEX/SECOND: 797093
HD SIZE: 94.49 GB (/dev/mapper/pve-root)
BUFFERED READS: 242.62 MB/sec
AVERAGE SEEK TIME: 9.78 ms
FSYNCS/SECOND: 2769.47
DNS EXT: 110.03 ms
Bascule:~# pveperf
CPU BOGOMIPS: 53199.32
REGEX/SECOND: 832843
HD SIZE: 94.49 GB (/dev/mapper/pve-root)
BUFFERED READS: 178.86 MB/sec
AVERAGE SEEK TIME: 8.80 ms
FSYNCS/SECOND: 2150.29
DNS EXT: 121.10 ms
Bascule:~# pveperf
CPU BOGOMIPS: 53199.32
REGEX/SECOND: 833051
HD SIZE: 94.49 GB (/dev/mapper/pve-root)
BUFFERED READS: 223.62 MB/sec
AVERAGE SEEK TIME: 8.61 ms
FSYNCS/SECOND: 2507.56
DNS EXT: 95.27 ms
Bascule:~# pveperf
CPU BOGOMIPS: 53199.32
REGEX/SECOND: 838535
HD SIZE: 94.49 GB (/dev/mapper/pve-root)
BUFFERED READS: 235.32 MB/sec
AVERAGE SEEK TIME: 9.28 ms
FSYNCS/SECOND: 2615.14
DNS EXT: 124.11 ms
Bascule:~# pveperf
CPU BOGOMIPS: 53199.32
REGEX/SECOND: 846164
HD SIZE: 94.49 GB (/dev/mapper/pve-root)
BUFFERED READS: 227.76 MB/sec
AVERAGE SEEK TIME: 8.64 ms
FSYNCS/SECOND: 2432.49
DNS EXT: 109.19 ms
Code:
CPU BOGOMIPS: 53201.14
REGEX/SECOND: 839968
HD SIZE: 94.49 GB (/dev/mapper/pve-root)
BUFFERED READS: 226.12 MB/sec
AVERAGE SEEK TIME: 10.10 ms
FSYNCS/SECOND: 2828.87
DNS EXT: 92.20 ms
Bascule:~# pveperf
CPU BOGOMIPS: 53201.14
REGEX/SECOND: 854225
HD SIZE: 94.49 GB (/dev/mapper/pve-root)
BUFFERED READS: 225.59 MB/sec
AVERAGE SEEK TIME: 9.67 ms
FSYNCS/SECOND: 2986.26
DNS EXT: 112.33 ms
Bascule:~# pveperf
CPU BOGOMIPS: 53201.14
REGEX/SECOND: 851606
HD SIZE: 94.49 GB (/dev/mapper/pve-root)
BUFFERED READS: 226.34 MB/sec
AVERAGE SEEK TIME: 10.05 ms
FSYNCS/SECOND: 2347.66
DNS EXT: 115.65 ms
Bascule:~# pveperf
CPU BOGOMIPS: 53201.14
REGEX/SECOND: 846971
HD SIZE: 94.49 GB (/dev/mapper/pve-root)
BUFFERED READS: 224.86 MB/sec
AVERAGE SEEK TIME: 8.68 ms
FSYNCS/SECOND: 2687.54
DNS EXT: 100.07 msWell for my part, I've been running 2.6.35 from pvetest for two days now on a production environment (yeah I'm a risk taker) and so far so good.
Look forward to it entering stable when it's ready.
Can we get a confirmation off the Proxmox VE dev's that Proxmox VE 2.x will include LXC support and we can finally ditch this OpenVZ crap?
Look forward to it entering stable when it's ready.
Can we get a confirmation off the Proxmox VE dev's that Proxmox VE 2.x will include LXC support and we can finally ditch this OpenVZ crap?
When I downgrade from this to the 2.6.18 kernel, my network settings change.
I thought it was the Broadcom NetXtreme II drivers again, so I did what I did to make 2.6.35 work with them:
But it didn't help.
I'll have to come back to it later.
I thought it was the Broadcom NetXtreme II drivers again, so I did what I did to make 2.6.35 work with them:
Code:
#update-initramfs -c -t -k 2.6.18-4-pveBut it didn't help.
I'll have to come back to it later.
I'm currently unable to bring up the network using that kernel, see thread.
However I can type just fine, here are the pveperf values with 2.6.18-4-pve:
Code:
pveperf
CPU BOGOMIPS: 53200.06
REGEX/SECOND: 947756
HD SIZE: 94.49 GB (/dev/mapper/pve-root)
BUFFERED READS: 203.21 MB/sec
AVERAGE SEEK TIME: 8.46 ms
FSYNCS/SECOND: 2672.19
DNS EXT: 4000.68 ms
DNS INT: 3999.87 ms (sub.domain.suffix)
Bascule:~# pveperf
CPU BOGOMIPS: 53200.06
REGEX/SECOND: 951327
HD SIZE: 94.49 GB (/dev/mapper/pve-root)
BUFFERED READS: 214.53 MB/sec
AVERAGE SEEK TIME: 9.05 ms
FSYNCS/SECOND: 1612.59
DNS EXT: 4000.17ms
DNS INT: 3999.72 ms (sub.domain.suffix)
Bascule:~# pveperf
CPU BOGOMIPS: 53200.06
REGEX/SECOND: 946942
HD SIZE: 94.49 GB (/dev/mapper/pve-root)
BUFFERED READS: 226.24 MB/sec
AVERAGE SEEK TIME: 9.03 ms
FSYNCS/SECOND: 1690.94
DNS EXT: 4000.38 ms
DNS INT: 4000.82 ms (sub.domain.suffix)
Bascule:~# pveperf
CPU BOGOMIPS: 53200.06
REGEX/SECOND: 948020
HD SIZE: 94.49 GB (/dev/mapper/pve-root)
BUFFERED READS: 227.79 MB/sec
AVERAGE SEEK TIME: 8.80 ms
FSYNCS/SECOND: 2842.65
DNS EXT: 4000.33 ms
DNS INT: 4000.02 ms (sub.domain.suffix)
Bascule:~# pveperf
CPU BOGOMIPS: 53200.06
REGEX/SECOND: 952536
HD SIZE: 94.49 GB (/dev/mapper/pve-root)
BUFFERED READS: 219.62 MB/sec
AVERAGE SEEK TIME: 10.60 ms
FSYNCS/SECOND: 1590.63
DNS EXT: 4000.96 ms
DNS INT: 4000.67 ms (sub.domain.suffix)
Last edited:
L
linuxdatacenter
Guest
Hi,
It seems there's a module compiled in 2.6.35:
cat /boot/config-2.6.35-1-pve |grep VHOST
CONFIG_VHOST_NET=m
Don't know how to enable and use it. Do you have any reasonable tutorial for this?