OpenVZ Forum


Home » General » Support » max number of VE
max number of VE [message #16205] Mon, 27 August 2007 21:01 Go to next message
yahbluez is currently offline  yahbluez
Messages: 18
Registered: August 2007
Location: Germany
Junior Member
Hello Gents,

i'm new here and like to ask where are the limits of VEs on a host. I try to start 100 on an 16GB dual quad core Dell2950. I build the .conf with vzsplit -n100 but i get at max 49 VEs running. I guess that kmemsize is my problem. How much kemsize is usefull for a verry small VE?

thx
yahbluez

Report message to a moderator

Re: max number of VE [message #16207 is a reply to message #16205] Tue, 28 August 2007 00:05 Go to previous messageGo to next message
kir is currently offline  kir
Messages: 1645
Registered: August 2005
Location: Moscow, Russia
Senior Member
vzsplit is probably not working well enough in your case. Can you tell us what vzmemcheck -v shows?

I recommend to stick to shipped configs. I guess you can run a few thousand VEs on such a machine, using the default ve-light.conf.

Kir Kolyshkin
http://static.openvz.org/userbars/openvz-developer.png

Report message to a moderator

Re: max number of VE [message #16213 is a reply to message #16207] Tue, 28 August 2007 12:31 Go to previous messageGo to next message
yahbluez is currently offline  yahbluez
Messages: 18
Registered: August 2007
Location: Germany
Junior Member
Same Problem.

I put together all informations:

Dell PE2950, 16GB RAM, 750GB HD, dual E5310
Debian ETCH AMD64 (aka x86_64)

The VE OS is a minimal debian etch.
I try to run 100 instances.

The conf file:

# Primary parameters
AVNUMPROC="40:50"
NUMPROC="80:80"
NUMTCPSOCK="60:80"
NUMOTHERSOCK="60:80"
VMGUARPAGES="1725:9223372036854775807"

# Secondary parameters
KMEMSIZE="524288:589824"
TCPSNDBUF="32768:65536"
TCPRCVBUF="32768:65536"
OTHERSOCKBUF="32768:65536"
DGRAMRCVBUF="32768:32768"
OOMGUARPAGES="1725:9223372036854775807"

# Auxiliary parameters
LOCKEDPAGES="4:4"
SHMPAGES="1152:1152"
PRIVVMPAGES="20480:40960"
NUMFILE="512:512"
NUMFLOCK="50:60"
NUMPTY="4:4"
NUMSIGINFO="256:256"
DCACHESIZE="196608:202752"
PHYSPAGES="0:9223372036854775807"
NUMIPTENT="16:16"

# Disk quota parameters (in form of softlimit:hardlimit)
DISKSPACE="204800:204800"
DISKINODES="80000:88000"
QUOTATIME="0"

# CPU fair sheduler parameter
CPUUNITS="4000"



ncl0:~/bin# vzmemcheck -v
Output values in %
veid LowMem LowMem RAM MemSwap MemSwap Alloc Alloc Alloc
util commit util util commit util commit limit
148 0.00 0.01 0.00 0.00 0.02 0.00 0.02 0.50
147 0.00 0.01 0.00 0.00 0.02 0.00 0.02 0.50

% and so on all the same

103 0.00 0.01 0.00 0.00 0.02 0.00 0.02 0.50
102 0.00 0.01 0.00 0.00 0.02 0.00 0.02 0.50
101 0.00 0.01 0.00 0.00 0.02 0.00 0.02 0.50
100 0.00 0.01 0.00 0.00 0.02 0.00 0.02 0.50
------------------------------------------------------------ -------------
Summary: 0.10 0.60 0.25 0.12 1.14 0.16 1.14 24.31


user_beans:
0: kmemsize 15036287 16002019 9223372036854775807 9223372036854775807 0
lockedpages 0 5205 9223372036854775807 9223372036854775807 0
privvmpages 4387 14309 9223372036854775807 9223372036854775807 0
shmpages 1292 1308 9223372036854775807 9223372036854775807 0
dummy 0 0 9223372036854775807 9223372036854775807 0
numproc 474 483 9223372036854775807 9223372036854775807 0
physpages 2076 3635 9223372036854775807 9223372036854775807 0
vmguarpages 0 0 9223372036854775807 9223372036854775807 0
oomguarpages 2076 3635 9223372036854775807 9223372036854775807 0
numtcpsock 3 4 9223372036854775807 9223372036854775807 0
numflock 1 5 9223372036854775807 9223372036854775807 0
numpty 2 2 9223372036854775807 9223372036854775807 0
numsiginfo 0 3 9223372036854775807 9223372036854775807 0
tcpsndbuf 89776 89776 9223372036854775807 9223372036854775807 0
tcprcvbuf 49152 0 9223372036854775807 9223372036854775807 0
othersockbuf 9248 17536 9223372036854775807 9223372036854775807 0
dgramrcvbuf 0 8456 9223372036854775807 9223372036854775807 0
numothersock 31 37 9223372036854775807 9223372036854775807 0
dcachesize 0 0 9223372036854775807 9223372036854775807 0
numfile 7730 7881 9223372036854775807 9223372036854775807 0
dummy 0 0 9223372036854775807 9223372036854775807 0
dummy 0 0 9223372036854775807 9223372036854775807 0
dummy 0 0 9223372036854775807 9223372036854775807 0
numiptent 10 10 9223372036854775807 9223372036854775807 0



look this:

ncl0:~/bin# cat /proc/user_beancounters |grep kmemsize
148: kmemsize 120682 585476 524288 589824 295
147: kmemsize 115675 585510 524288 589824 193
146: kmemsize 128874 581253 524288 589824 354
145: kmemsize 129785 584720 524288 589824 228
144: kmemsize 125069 583757 524288 589824 174
143: kmemsize 119771 585504 524288 589824 288
142: kmemsize 116586 583821 524288 589824 229
141: kmemsize 117497 579133 524288 589824 233
140: kmemsize 127052 584584 524288 589824 220
139: kmemsize 128874 580862 524288 589824 199
138: kmemsize 112490 584841 524288 589824 219
137: kmemsize 124778 582395 524288 589824 213
136: kmemsize 124778 583811 524288 589824 204
135: kmemsize 127884 583898 524288 589824 159
134: kmemsize 129165 584182 524288 589824 191
133: kmemsize 125689 583081 524288 589824 206
132: kmemsize 115675 585694 524288 589824 266
131: kmemsize 128874 579133 524288 589824 219
130: kmemsize 120682 583053 524288 589824 188
129: kmemsize 134172 583344 524288 589824 205
128: kmemsize 111579 585079 524288 589824 253
127: kmemsize 129785 585966 524288 589824 327
126: kmemsize 123247 584126 524288 589824 150
125: kmemsize 124778 585504 524288 589824 224
124: kmemsize 122956 582856 524288 589824 188
123: kmemsize 124778 585712 524288 589824 226
122: kmemsize 129785 579400 524288 589824 185
121: kmemsize 120682 584060 524288 589824 222
120: kmemsize 124778 583717 524288 589824 440
119: kmemsize 121757 585031 524288 589824 226
118: kmemsize 119771 579178 524288 589824 219
117: kmemsize 123867 581009 524288 589824 185
116: kmemsize 123867 584153 524288 589824 209
115: kmemsize 128874 584850 524288 589824 253
114: kmemsize 116586 578780 524288 589824 275
113: kmemsize 120973 578253 524288 ...

[ Show the rest of the message ]

Report message to a moderator

Re: max number of VE [message #16214 is a reply to message #16213] Tue, 28 August 2007 12:40 Go to previous messageGo to next message
kir is currently offline  kir
Messages: 1645
Registered: August 2005
Location: Moscow, Russia
Senior Member
I see. I got you wrong for the first time. The problem is not with number of VEs that you have -- the problem is kmemsize limits are way too small for those VEs. Just increase those; something like this should do the job:

for VE in `vzlist -a -H -oveid`; do
  vzctl set $VE --kmemsize 1740800:1847296 --save
done

Kir Kolyshkin
http://static.openvz.org/userbars/openvz-developer.png

Report message to a moderator

Re: max number of VE [message #16234 is a reply to message #16214] Wed, 29 August 2007 11:35 Go to previous messageGo to next message
yahbluez is currently offline  yahbluez
Messages: 18
Registered: August 2007
Location: Germany
Junior Member
Same effect as befor.

A question, is this typicall:

ncl0:/proc/sys# cat /proc/user_beancounters
Version: 2.5
uid resource held maxheld barrier limit failcnt
0: kmemsize 4949907 9474391 9223372036854775807 9223372036854775807 0
lockedpages 0 5203 9223372036854775807 9223372036854775807 0
privvmpages 3190 14306 9223372036854775807 9223372036854775807 0
shmpages 652 668 9223372036854775807 9223372036854775807 0
dummy 0 0 9223372036854775807 9223372036854775807 0
numproc 79 140 9223372036854775807 9223372036854775807 0
physpages 1667 3628 9223372036854775807 9223372036854775807 0
vmguarpages 0 0 9223372036854775807 9223372036854775807 0
oomguarpages 1667 3628 9223372036854775807 9223372036854775807 0
numtcpsock 2 2 9223372036854775807 9223372036854775807 0
numflock 1 6 9223372036854775807 9223372036854775807 0
numpty 1 1 9223372036854775807 9223372036854775807 0
numsiginfo 0 3 9223372036854775807 9223372036854775807 0
tcpsndbuf 43336 43336 9223372036854775807 9223372036854775807 0
tcprcvbuf 32768 0 9223372036854775807 9223372036854775807 0
othersockbuf 9248 17536 9223372036854775807 9223372036854775807 0
dgramrcvbuf 0 8456 9223372036854775807 9223372036854775807 0
numothersock 31 37 9223372036854775807 9223372036854775807 0
dcachesize 0 0 9223372036854775807 9223372036854775807 0
numfile 1354 2259 9223372036854775807 9223372036854775807 0
dummy 0 0 9223372036854775807 9223372036854775807 0
dummy 0 0 9223372036854775807 9223372036854775807 0
dummy 0 0 9223372036854775807 9223372036854775807 0
numiptent 10 10 9223372036854775807 9223372036854775807 0


I wonder about the barrier and limit values they look verry high?

thx

Report message to a moderator

Re: max number of VE [message #16239 is a reply to message #16234] Wed, 29 August 2007 14:16 Go to previous messageGo to next message
dev is currently offline  dev
Messages: 1693
Registered: September 2005
Location: Moscow
Senior Member
0 beancounter is a host system - it should be unlimited, so high values are ok.

http://static.openvz.org/userbars/openvz-developer.png

Report message to a moderator

Re: max number of VE [message #16240 is a reply to message #16205] Wed, 29 August 2007 14:17 Go to previous messageGo to next message
dev is currently offline  dev
Messages: 1693
Registered: September 2005
Location: Moscow
Senior Member
what do you mean by got only 49 VEs to run?
vzctl start failed on other 51 VEs? or machine started to be slow? or what?

http://static.openvz.org/userbars/openvz-developer.png

Report message to a moderator

Re: max number of VE [message #16241 is a reply to message #16213] Wed, 29 August 2007 14:18 Go to previous messageGo to next message
dev is currently offline  dev
Messages: 1693
Registered: September 2005
Location: Moscow
Senior Member
yep, these configs have terribly small limits. try to use config after vzsplit -n 20 or 10.
It will be a config with overcommitment, but it's ok for your test.

http://static.openvz.org/userbars/openvz-developer.png

Report message to a moderator

Re: max number of VE [message #16249 is a reply to message #16240] Wed, 29 August 2007 15:59 Go to previous messageGo to next message
yahbluez is currently offline  yahbluez
Messages: 18
Registered: August 2007
Location: Germany
Junior Member
I mean the openvz did not start more than 49 instances.

Please looke here:

I first run 10 Ves than add 30 add up to 49
and than when i try to strat VE nummber 50 it will not do that.
I got an error message at syslog. I have 100 identical Ves atthe stoarge so not working ist not based on the expliziet number of the instance. When i have 49 running i can't start more VEs.

I still don't see which limit i oversize, maybe someone here sees it:

no VE started
Version: 2.5
uid resource held maxheld barrier limit failcnt
0: kmemsize 5148172 9474391 9223372036854775807 9223372036854775807 0
lockedpages 0 5203 9223372036854775807 9223372036854775807 0
privvmpages 3190 14306 9223372036854775807 9223372036854775807 0
shmpages 652 668 9223372036854775807 9223372036854775807 0
dummy 0 0 9223372036854775807 9223372036854775807 0
numproc 79 140 9223372036854775807 9223372036854775807 0
physpages 1667 3628 9223372036854775807 9223372036854775807 0
vmguarpages 0 0 9223372036854775807 9223372036854775807 0
oomguarpages 1667 3628 9223372036854775807 9223372036854775807 0
numtcpsock 2 2 9223372036854775807 9223372036854775807 0
numflock 1 6 9223372036854775807 9223372036854775807 0
numpty 1 1 9223372036854775807 9223372036854775807 0
numsiginfo 0 3 9223372036854775807 9223372036854775807 0
tcpsndbuf 43336 43336 9223372036854775807 9223372036854775807 0
tcprcvbuf 32768 0 9223372036854775807 9223372036854775807 0
othersockbuf 9248 27856 9223372036854775807 9223372036854775807 0
dgramrcvbuf 0 8456 9223372036854775807 9223372036854775807 0
numothersock 31 37 9223372036854775807 9223372036854775807 0
dcachesize 0 0 9223372036854775807 9223372036854775807 0
numfile 1352 2259 9223372036854775807 9223372036854775807 0
dummy 0 0 9223372036854775807 9223372036854775807 0
dummy 0 0 9223372036854775807 9223372036854775807 0
dummy 0 0 9223372036854775807 9223372036854775807 0
numiptent 10 10 9223372036854775807 9223372036854775807 0


10 VEs running
0: kmemsize 6690269 9474391 9223372036854775807 9223372036854775807 0
lockedpages 0 5203 9223372036854775807 9223372036854775807 0
privvmpages 3191 14306 9223372036854775807 9223372036854775807 0
shmpages 652 668 9223372036854775807 9223372036854775807 0
dummy 0 0 9223372036854775807 9223372036854775807 0
numproc 159 167 9223372036854775807 9223372036854775807 0
physpages 1668 3628 9223372036854775807 9223372036854775807 0
vmguarpages 0 0 9223372036854775807 9223372036854775807 0
oomguarpages 1668 3628 9223372036854775807 9223372036854775807 0
numtcpsock 2 3 9223372036854775807 9223372036854775807 0
numflock 1 6 9223372036854775807 9223372036854775807 0
numpty 1 1 9223372036854775807 9223372036854775807 0
numsiginfo 0 3 9223372036854775807 9223372036854775807 0
tcpsndbuf 64936 64936 9223372036854775807 9223372036854775807 0
tcprcvbuf 32768 0 9223372036854775807 9223372036854775807 0
othersockbuf 9248 27856 9223372036854775807 9223372036854775807 0
dgramrcvbuf 0 8456 9223372036854775807 9223372036854775807 0
numothersock 31 37 9223372036854775807 9223372036854775807 0
dcachesize 0 0 9223372036854775807 9223372036854775807 0
numfile 2657 2756 9223372036854775807 9223372036854775807 0
dummy 0 0 9223372036854775807 9223372036854775807 0
dummy 0 0 9223372036854775807 9223372036854775807 0
dummy 0 0 9223372036854775807 9223372036854775807 0
numiptent 10 10 9223372036854775807 9223372036854775807 0

40 VEs running
0: kmemsize 11494115 12172126 9223372036854775807 9223372036854775807 0
lockedpages 0 5203 9223372036854775807 9223372036854775807 0
privvmpages 3192 16012 9223372036854775807 9223372036854775807 0
shmpages 652 668 9223372036854775807 9223372036854775807 0
dummy 0 0 9223372036854775807 9223372036854775807 0
numproc 407 415 9223372036854775807 9223372036854775807 0
physpages 1672 3628 9223372036854775807 9223372036854775807 0
vmguarpages 0 0 9223372036854775807 9223372036854775807 0
oomguarpages 1672 3628 9223372036854775807 9223372036854775807 0
numtcpsock 2 3 9223372036854775807 9223372036854775807 0
numflock 1 6 9223372036854775807 9223372036854775807 0
numpty 1 1 9223372036854775807 9223372036854775807 0
numsiginfo 0 3 9223372036854775807 9223372036854775807 0
tcpsndbuf 80264 80264 9223372036854775807 9223372036854775807 0
tcprcvbuf 32768 0 9223372036854775807 9223372036854775807 0
othersockbuf 9248 27856 9223372036854775807 9223372036854775807 0
dgramrcvbuf 0 8456 9223372036854775807 9223372036854775807 0
numothersock 31 37 9223372036854775807 9223372036854775807 0
dcachesize 0 0 9223372036854775807 9223372036854775807 0
numfile 6600 6745 9223372036854775807 9223372036854775807 0
dummy 0 0 9223372036854775807 9223372036854775807 0
dummy 0 0 9223372036854775807 9223372036854775807 0
dummy 0 0 9223372036854775807 9223372036854775807 0
numiptent 10 ...

[ Show the rest of the message ]

Report message to a moderator

Re: max number of VE [message #16254 is a reply to message #16249] Wed, 29 August 2007 21:24 Go to previous messageGo to next message
kir is currently offline  kir
Messages: 1645
Registered: August 2005
Location: Moscow, Russia
Senior Member
Is there something bad in dmesg? The exact quote would be appreciated.

Also it's not quite clear what OpenVZ kernel version do you use. Have you compiled that yourself? Then what was the version of linux-patch-openvz.

Also — can you reproduce the problem with the latest 2.6.18 kernel from http://debian.systs.org/?

Kir Kolyshkin
http://static.openvz.org/userbars/openvz-developer.png

Report message to a moderator

Re: max number of VE [message #16255 is a reply to message #16254] Wed, 29 August 2007 21:46 Go to previous messageGo to next message
yahbluez is currently offline  yahbluez
Messages: 18
Registered: August 2007
Location: Germany
Junior Member
Hi Kirr,

kernel:

Linux version 2.6.18-openvz-12-1etch1-amd64 () (ola@deb-build-amd64.openvz.org) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21))

Not self made.

full dmesg:

Bootdata ok (command line is root=/dev/mapper/vg-rootfs ro )
Linux version 2.6.18-openvz-12-1etch1-amd64 () (ola@deb-build-amd64.openvz.org) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP Fri May 4 23:37:24 MSD 2007
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
BIOS-e820: 0000000000100000 - 00000000cffa8000 (usable)
BIOS-e820: 00000000cffa8000 - 00000000cffb7c00 (ACPI data)
BIOS-e820: 00000000cffb7c00 - 00000000d0000000 (reserved)
BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
BIOS-e820: 00000000fe000000 - 0000000100000000 (reserved)
BIOS-e820: 0000000100000000 - 0000000430000000 (usable)
DMI 2.4 present.
ACPI: RSDP (v002 DELL ) @ 0x00000000000f2620
ACPI: XSDT (v001 DELL PE_SC3 0x00000001 DELL 0x00000001) @ 0x00000000000f26a0
ACPI: FADT (v003 DELL PE_SC3 0x00000001 DELL 0x00000001) @ 0x00000000000f27a8
ACPI: MADT (v001 DELL PE_SC3 0x00000001 DELL 0x00000001) @ 0x00000000000f289c
ACPI: SPCR (v001 DELL PE_SC3 0x00000001 DELL 0x00000001) @ 0x00000000000f297d
ACPI: HPET (v001 DELL PE_SC3 0x00000001 DELL 0x00000001) @ 0x00000000000f29cd
ACPI: MCFG (v001 DELL PE_SC3 0x00000001 DELL 0x00000001) @ 0x00000000000f2a05
ACPI: DSDT (v001 DELL PE_SC3 0x00000001 MSFT 0x0100000e) @ 0x0000000000000000
No NUMA configuration found
Faking a node at 0000000000000000-0000000430000000
Bootmem setup node 0 0000000000000000-0000000430000000
On node 0 totalpages: 4124603
DMA zone: 3027 pages, LIFO batch:0
DMA32 zone: 831464 pages, LIFO batch:31
Normal zone: 3290112 pages, LIFO batch:31
ACPI: PM-Timer IO Port: 0x808
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
Processor #0 6:15 APIC version 20
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x04] enabled)
Processor #4 6:15 APIC version 20
ACPI: LAPIC (acpi_id[0x03] lapic_id[0x01] enabled)
Processor #1 6:15 APIC version 20
ACPI: LAPIC (acpi_id[0x04] lapic_id[0x05] enabled)
Processor #5 6:15 APIC version 20
ACPI: LAPIC (acpi_id[0x05] lapic_id[0x02] enabled)
Processor #2 6:15 APIC version 20
ACPI: LAPIC (acpi_id[0x06] lapic_id[0x06] enabled)
Processor #6 6:15 APIC version 20
ACPI: LAPIC (acpi_id[0x07] lapic_id[0x03] enabled)
Processor #3 6:15 APIC version 20
ACPI: LAPIC (acpi_id[0x08] lapic_id[0x07] enabled)
Processor #7 6:15 APIC version 20
ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x05] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x06] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x07] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
ACPI: IOAPIC (id[0x09] address[0xfec81000] gsi_base[64])
IOAPIC[1]: apic_id 9, version 32, address 0xfec81000, GSI 64-87
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Setting APIC routing to flat
ACPI: HPET id: 0x8086a201 base: 0xfed00000
Using ACPI (MADT) for SMP configuration information
Allocating PCI resources starting at d1000000 (gap: d0000000:10000000)
Built 1 zonelists. Total pages: 4124603
Kernel command line: root=/dev/mapper/vg-rootfs ro
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 32768 bytes)
time.c: Using 14.318180 MHz WALL HPET GTOD HPET/TSC timer.
time.c: Detected 1596.045 MHz processor.
Console: colour VGA+ 80x25
Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Inode-cache hash table entries: 1048576 (order: 11, 8388608 bytes)
Checking aperture...
PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Placing software IO TLB between 0x2884000 - 0x6884000
Memory: 16401928k/17563648k available (1930k kernel code, 374552k reserved, 872k data, 204k init)
Calibrating delay using timer specific routine.. 3195.32 BogoMIPS (lpj=6390645)
Mount-cache hash table entries: 256
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 4096K
using mwait in idle threads.
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
CPU0: Thermal monitoring enabled (TM1)
Freeing SMP alternatives: 28k freed
ACPI: Core revision 20060707
Page beancounter hash is 2097152 entries.
Using local APIC timer interrupts.
result 16625469
Detected 16.625 MHz APIC timer.
Booting processor 1/8 APIC 0x4
Initializing CPU#1
Calibrating delay using timer specific routine.. 3192.18 BogoMIPS (lpj=6384368)
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 4096K
CPU: Physical Processor ID: 1
CPU: Processor Core ID: 0
CPU1: Thermal monitoring enabled (TM2)
Intel(R) Xeon(R) CPU E5310 @ 1.60GHz stepping 07
Booting processor 2/8 APIC 0x1
Initializing CPU#2
Calibrating delay using timer specific routine.. 3192.17 BogoMIPS (lpj=6384358)
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 4096K
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 1
CPU2: Thermal monitoring enabled (TM2)
Intel(R) Xeon(R) CPU E5310 @ 1.60GHz stepping 07
Booting processor 3/8 APIC 0x5
Initializing CPU#3
Calibrating delay using timer specific routine.. 3192.24 BogoMIPS (lpj=6384492)
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 4096K
CPU: Physical Processor ID: 1
CPU: Processor Core ID: 1
CPU3: Thermal monitoring enabled (TM2)
Intel(R) Xeon(R) CPU E5310 @ 1.60GHz stepping 07
Booting processor 4/8 APIC 0x2
Initializing CPU#4
Calibrating delay using timer specific routine.. 3192.17 BogoMIPS (lpj=6384348)
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 4096K
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 2
CPU4: Thermal monitoring enabled (TM2)
Intel(R) Xeon(R) CPU E5310 @ 1.60GHz stepping 07
Booting processor 5/8 APIC 0x6
Initializing CPU#5
Calibrating delay using timer specific routine.. 3192.18 BogoMIPS (lpj=6384371)
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 4096K
CPU: Physical Processor ID: 1
CPU: Processor Core ID: 2
CPU5: Thermal monitoring enabled (TM2)
Intel(R) Xeon(R) CPU E5310 @ 1.60GHz stepping 07
Booting processor 6/8 APIC 0x3
Initializing CPU#6
Calibrating delay using timer specific routine.. 3192.17 BogoMIPS (lpj=6384340)
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 4096K
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 3
CPU6: Thermal monitoring enabled (TM2)
Intel(R) Xeon(R) CPU E5310 @ 1.60GHz stepping 07
Booting processor 7/8 APIC 0x7
Initializing CPU#7
Calibrating delay using timer specific routine.. 3192.24 BogoMIPS (lpj=6384491)
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 4096K
CPU: Physical Processor ID: 1
CPU: Processor Core ID: 3
CPU7: Thermal monitoring enabled (TM2)
Intel(R) Xeon(R) CPU E5310 @ 1.60GHz stepping 07
Brought up 8 CPUs
testing NMI watchdog ... OK.
migration_cost=18,11860
checking if image is initramfs... it is
Freeing initrd memory: 5409k freed
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: Using MMCONFIG at e0000000
ACPI: Interpreter enabled
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Probing PCI hardware (bus 00)
PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1
Boot video device is 0000:10:0d.0
PCI: Transparent bridge - 0000:00:1e.0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX2._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX2.UPST._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX2.UPST.DWN1._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX2.UPST.DWN2._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX3._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX3.PE2P._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX4._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX6._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.SBEX._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.COMP._PRT]
ACPI: PCI Interrupt Link [LK00] (IRQs 3 4 5 6 7 10 *11 12)
ACPI: PCI Interrupt Link [LK01] (IRQs 3 4 5 6 7 10 11 12) *0, disabled.
ACPI: PCI Interrupt Link [LK02] (IRQs 3 4 *5 6 7 10 11 12)
ACPI: PCI Interrupt Link [LK03] (IRQs 3 4 5 6 7 *10 11 12)
ACPI: PCI Interrupt Link [LK04] (IRQs 3 4 5 6 7 *10 11 12)
ACPI: PCI Interrupt Link [LK05] (IRQs 3 4 5 6 7 10 *11 12)
ACPI: PCI Interrupt Link [LK06] (IRQs 3 4 5 6 7 10 11 12) *0, disabled.
ACPI: PCI Interrupt Link [LK07] (IRQs 3 4 5 6 7 10 11 12) *0, disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
pnp: ACPI device : hid PNP0A03
pnp: ACPI device : hid PNP0200
pnp: ACPI device : hid PNP0C04
pnp: ACPI device : hid PNP0C01
pnp: ACPI device : hid PNP0B00
pnp: ACPI device : hid PNP0700
pnp: ACPI device : hid PNP0501
pnp: ACPI device : hid PNP0501
pnp: ACPI device : hid PNP0C01
pnp: ACPI device : hid IPI0001
pnp: ACPI device : hid PNP0C02
pnp: ACPI device : hid PNP0103
pnp: PnP ACPI: found 12 devices
usbcore: registered new driver usbfs
usbcore: registered new driver hub
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
hpet0: at MMIO 0xfed00000 (virtual 0xffffffffff5fe000), IRQs 2, 8, 0
hpet0: 3 64-bit timers, 14318180 Hz
PCI-GART: No AMD northbridge found.
pnp: the driver 'system' has been registered
pnp: match found with the PnP device '00:03' and the driver 'system'
pnp: match found with the PnP device '00:08' and the driver 'system'
pnp: 00:08: ioport range 0x800-0x87f could not be reserved
pnp: 00:08: ioport range 0x880-0x8bf has been reserved
pnp: 00:08: ioport range 0x8c0-0x8df has been reserved
pnp: 00:08: ioport range 0x8e0-0x8e3 has been reserved
pnp: 00:08: ioport range 0xc00-0xc7f has been reserved
pnp: 00:08: ioport range 0xca0-0xca7 has been reserved
pnp: 00:08: ioport range 0xca9-0xcab has been reserved
pnp: 00:08: ioport range 0xcad-0xcaf has been reserved
pnp: match found with the PnP device '00:09' and the driver 'system'
pnp: 00:09: ioport range 0xca8-0xca8 has been reserved
pnp: 00:09: ioport range 0xcac-0xcac has been reserved
pnp: match found with the PnP device '00:0a' and the driver 'system'
PCI: Bridge: 0000:08:00.0
IO window: disabled.
MEM window: f4000000-f7ffffff
PREFETCH window: disabled.
PCI: Bridge: 0000:07:00.0
IO window: disabled.
MEM window: f4000000-f7ffffff
PREFETCH window: disabled.
PCI: Bridge: 0000:07:01.0
IO window: disabled.
MEM window: disabled.
PREFETCH window: disabled.
PCI: Bridge: 0000:06:00.0
IO window: disabled.
MEM window: f4000000-f7ffffff
PREFETCH window: disabled.
PCI: Bridge: 0000:06:00.3
IO window: disabled.
MEM window: disabled.
PREFETCH window: disabled.
PCI: Bridge: 0000:00:02.0
IO window: disabled.
MEM window: f2000000-f7ffffff
PREFETCH window: disabled.
PCI: Bridge: 0000:01:00.0
IO window: disabled.
MEM window: fc400000-fc5fffff
PREFETCH window: d8000000-d80fffff
PCI: Bridge: 0000:01:00.2
IO window: disabled.
MEM window: disabled.
PREFETCH window: disabled.
PCI: Bridge: 0000:00:03.0
IO window: disabled.
MEM window: fc300000-fc5fffff
PREFETCH window: d8000000-d80fffff
PCI: Bridge: 0000:00:04.0
IO window: disabled.
MEM window: disabled.
PREFETCH window: disabled.
PCI: Bridge: 0000:00:05.0
IO window: disabled.
MEM window: disabled.
PREFETCH window: disabled.
PCI: Bridge: 0000:00:06.0
IO window: disabled.
MEM window: disabled.
PREFETCH window: disabled.
PCI: Bridge: 0000:00:07.0
IO window: disabled.
MEM window: disabled.
PREFETCH window: disabled.
PCI: Bridge: 0000:04:00.0
IO window: disabled.
MEM window: f8000000-fbffffff
PREFETCH window: disabled.
PCI: Bridge: 0000:00:1c.0
IO window: disabled.
MEM window: f8000000-fbffffff
PREFETCH window: disabled.
PCI: Bridge: 0000:00:1e.0
IO window: e000-efff
MEM window: fc100000-fc2fffff
PREFETCH window: d0000000-d7ffffff
GSI 16 sharing vector 0xA9 and IRQ 16
ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 16 (level, low) -> IRQ 169
PCI: Setting latency timer of device 0000:00:02.0 to 64
ACPI: PCI Interrupt 0000:06:00.0[A] -> GSI 16 (level, low) -> IRQ 169
PCI: Setting latency timer of device 0000:06:00.0 to 64
ACPI: PCI Interrupt 0000:07:00.0[A] -> GSI 16 (level, low) -> IRQ 169
PCI: Setting latency timer of device 0000:07:00.0 to 64
PCI: Setting latency timer of device 0000:08:00.0 to 64
ACPI: PCI Interrupt 0000:07:01.0[A] -> GSI 16 (level, low) -> IRQ 169
PCI: Setting latency timer of device 0000:07:01.0 to 64
PCI: Setting latency timer of device 0000:06:00.3 to 64
ACPI: PCI Interrupt 0000:00:03.0[A] -> GSI 16 (level, low) -> IRQ 169
PCI: Setting latency timer of device 0000:00:03.0 to 64
PCI: Setting latency timer of device 0000:01:00.0 to 64
PCI: Setting latency timer of device 0000:01:00.2 to 64
ACPI: PCI Interrupt 0000:00:04.0[A] -> GSI 16 (level, low) -> IRQ 169
PCI: Setting latency timer of device 0000:00:04.0 to 64
PCI: Setting latency timer of device 0000:00:05.0 to 64
ACPI: PCI Interrupt 0000:00:06.0[A] -> GSI 16 (level, low) -> IRQ 169
PCI: Setting latency timer of device 0000:00:06.0 to 64
PCI: Setting latency timer of device 0000:00:07.0 to 64
ACPI: PCI Interrupt 0000:00:1c.0[A] -> GSI 16 (level, low) -> IRQ 169
PCI: Setting latency timer of device 0000:00:1c.0 to 64
PCI: Setting latency timer of device 0000:04:00.0 to 64
PCI: Setting latency timer of device 0000:00:1e.0 to 64
NET: Registered protocol family 2
IP route cache hash table entries: 524288 (order: 10, 4194304 bytes)
TCP established hash table entries: 262144 (order: 10, 4194304 bytes)
TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
TCP: Hash tables configured (established 262144 bind 65536)
TCP reno registered
audit: initializing netlink socket (disabled)
audit(1188385831.224:1): initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
PCI: Setting latency timer of device 0000:00:02.0 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:02.0:pcie00]
Allocate Port Service[0000:00:02.0:pcie01]
PCI: Setting latency timer of device 0000:00:03.0 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:03.0:pcie00]
Allocate Port Service[0000:00:03.0:pcie01]
PCI: Setting latency timer of device 0000:00:04.0 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:04.0:pcie00]
Allocate Port Service[0000:00:04.0:pcie01]
PCI: Setting latency timer of device 0000:00:05.0 to 64
pcie_portdrv_probe->Dev[25e5:8086] has invalid IRQ. Check vendor BIOS
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:05.0:pcie00]
Allocate Port Service[0000:00:05.0:pcie01]
PCI: Setting latency timer of device 0000:00:06.0 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:06.0:pcie00]
Allocate Port Service[0000:00:06.0:pcie01]
PCI: Setting latency timer of device 0000:00:07.0 to 64
pcie_portdrv_probe->Dev[25e7:8086] has invalid IRQ. Check vendor BIOS
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:07.0:pcie00]
Allocate Port Service[0000:00:07.0:pcie01]
PCI: Setting latency timer of device 0000:00:1c.0 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:1c.0:pcie00]
Allocate Port Service[0000:00:1c.0:pcie03]
PCI: Setting latency timer of device 0000:06:00.0 to 64
Allocate Port Service[0000:06:00.0:pcie10]
Allocate Port Service[0000:06:00.0:pcie11]
PCI: Setting latency timer of device 0000:07:00.0 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:07:00.0:pcie20]
Allocate Port Service[0000:07:00.0:pcie21]
PCI: Setting latency timer of device 0000:07:01.0 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:07:01.0:pcie20]
Allocate Port Service[0000:07:01.0:pcie21]
Real Time Clock Driver v1.12ac
hpet_resources: 0xfed00000 is busy
Linux agpgart interface v0.101 (c) Dave Jones
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
pnp: the driver 'serial' has been registered
pnp: match found with the PnP device '00:06' and the driver 'serial'
00:06: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
pnp: match found with the PnP device '00:07' and the driver 'serial'
00:07: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
RAMDISK driver initialized: 16 RAM disks of 65536K size 1024 blocksize
pnp: the driver 'i8042 kbd' has been registered
pnp: the driver 'i8042 aux' has been registered
pnp: the driver 'i8042 kbd' has been unregistered
pnp: the driver 'i8042 aux' has been unregistered
PNP: No PS/2 controller found. Probing ports directly.
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
mice: PS/2 mouse device common for all mice
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
NET: Registered protocol family 8
NET: Registered protocol family 20
Freeing unused kernel memory: 204k freed
SCSI subsystem initialized
megasas: 00.00.03.01 Sun May 14 22:49:52 PDT 2006
megasas: 0x1028:0x0015:0x1028:0x1f03: bus 2:slot 14:func 0
GSI 17 sharing vector 0x42 and IRQ 17
ACPI: PCI Interrupt 0000:02:0e.0[A] -> GSI 78 (level, low) -> IRQ 66
Broadcom NetXtreme II Gigabit Ethernet Driver bnx2 v1.4.44 (August 10, 2006)
ACPI: PCI Interrupt 0000:09:00.0[A] -> GSI 16 (level, low) -> IRQ 169
eth0: Broadcom NetXtreme II BCM5708 1000Base-T (B2) PCI-X 64-bit 133MHz found at mem f4000000, IRQ 169, node addr 001aa031b7eb
USB Universal Host Controller Interface driver v3.0
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
scsi0 : LSI Logic SAS based MegaRAID driver
Vendor: ATA Model: ST3250620NS Rev: 3BKH
Type: Direct-Access ANSI SCSI revision: 05
Vendor: ATA Model: ST3250620NS Rev: 3BKH
Type: Direct-Access ANSI SCSI revision: 05
Vendor: ATA Model: ST3250620NS Rev: 3BKH
Type: Direct-Access ANSI SCSI revision: 05
Vendor: ATA Model: ST3250620NS Rev: 3BKH
Type: Direct-Access ANSI SCSI revision: 05
Vendor: DP Model: BACKPLANE Rev: 1.05
Type: Enclosure ANSI SCSI revision: 05
Vendor: DELL Model: PERC 5/i Rev: 1.03
Type: Direct-Access ANSI SCSI revision: 05
ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 16 (level, low) -> IRQ 169
GSI 18 sharing vector 0x4A and IRQ 18
ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 21 (level, low) -> IRQ 74
PCI: Setting latency timer of device 0000:00:1d.0 to 64
uhci_hcd 0000:00:1d.0: UHCI Host Controller
uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1
uhci_hcd 0000:00:1d.0: irq 74, io base 0x0000dce0
eth1: Broadcom NetXtreme II BCM5708 1000Base-T (B2) PCI-X 64-bit 133MHz found at mem f8000000, IRQ 169, node addr 001aa031b7e9
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
SCSI device sda: 1461190656 512-byte hdwr sectors (748130 MB)
sda: Write Protect is off
sda: Mode Sense: 1f 00 10 08
SCSI device sda: drive cache: write through w/ FUA
SCSI device sda: 1461190656 512-byte hdwr sectors (748130 MB)
sda: Write Protect is off
sda: Mode Sense: 1f 00 10 08
SCSI device sda: drive cache: write through w/ FUA
sda: sda1 sda2 < sda5 >
sd 0:2:0:0: Attached scsi disk sda
GSI 19 sharing vector 0x52 and IRQ 19
ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 20 (level, low) -> IRQ 82
PCI: Setting latency timer of device 0000:00:1d.1 to 64
uhci_hcd 0000:00:1d.1: UHCI Host Controller
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:1d.1: irq 82, io base 0x0000dcc0
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 21 (level, low) -> IRQ 74
PCI: Setting latency timer of device 0000:00:1d.2 to 64
uhci_hcd 0000:00:1d.2: UHCI Host Controller
uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:1d.2: irq 74, io base 0x0000dca0
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:1d.7[A] -> GSI 21 (level, low) -> IRQ 74
PCI: Setting latency timer of device 0000:00:1d.7 to 64
ehci_hcd 0000:00:1d.7: EHCI Host Controller
ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 4
ehci_hcd 0000:00:1d.7: debug port 1
PCI: cache line size of 32 is not supported by device 0000:00:1d.7
ehci_hcd 0000:00:1d.7: irq 74, io mem 0xfc600400
ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 6 ports detected
ESB2: IDE controller at PCI slot 0000:00:1f.1
ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 16 (level, low) -> IRQ 169
ESB2: chipset revision 9
ESB2: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xfc00-0xfc07, BIOS settings: hda:DMA, hdb:pio
Probing IDE interface ide0...
hda: HL-DT-ST GCR-8240N, ATAPI CD/DVD-ROM drive
usb 4-5: new high speed USB device using ehci_hcd and address 3
usb 4-5: configuration #1 chosen from 1 choice
hub 4-5:1.0: USB hub found
hub 4-5:1.0: 4 ports detected
usb 2-2: new low speed USB device using uhci_hcd and address 2
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: ATAPI 24X CD-ROM drive, 128kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
usb 2-2: configuration #1 chosen from 1 choice
Probing IDE interface ide1...
usbcore: registered new driver hiddev
input: Logitech USB Receiver as /class/input/input0
input: USB HID v1.10 Keyboard [Logitech USB Receiver] on usb-0000:00:1d.1-2
input: Logitech USB Receiver as /class/input/input1
input: USB HID v1.10 Mouse [Logitech USB Receiver] on usb-0000:00:1d.1-2
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: dm-devel@redhat.com
Attempting manual resume
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
input: PC Speaker as /class/input/input2
intel_rng: FWH not detected
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
floppy0: no floppy controllers found
EXT3 FS on dm-2, internal journal
loop: loaded (max 8 devices)
kjournald starting. Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
Adding 16777208k swap on /dev/mapper/vg-swap. Priority:-1 extents:1 across:16777208k
bnx2: eth0: using MSI
ACPI: Power Button (FF) [PWRF]
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
ADDRCONF(NETDEV_UP): eth0: link is not ready
IPv6 over IPv4 tunneling driver
ip_tables: (C) 2000-2006 Netfilter Core Team
Netfilter messages via NETLINK v0.30.
ip_conntrack version 2.4 (8192 buckets, 65536 max) - 312 bytes per conntrack
bnx2: eth0 NIC Link is Up, 1000 Mbps full duplex, receive & transmit flow control ON
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
eth0: no IPv6 routers present
VE: 100: started
VE: 101: started
lo: Disabled Privacy Extensions
VE: 102: started
lo: Disabled Privacy Extensions
VE: 103: started
lo: Disabled Privacy Extensions
VE: 104: started
lo: Disabled Privacy Extensions
VE: 105: started
lo: Disabled Privacy Extensions
VE: 106: started
lo: Disabled Privacy Extensions
VE: 107: started
lo: Disabled Privacy Extensions
VE: 108: started
lo: Disabled Privacy Extensions
VE: 109: started
lo: Disabled Privacy Extensions
lo: Disabled Privacy Extensions
VE: 110: started
VE: 111: started
lo: Disabled Privacy Extensions
VE: 112: started
lo: Disabled Privacy Extensions
VE: 113: started
lo: Disabled Privacy Extensions
VE: 114: started
lo: Disabled Privacy Extensions
VE: 115: started
lo: Disabled Privacy Extensions
VE: 116: started
lo: Disabled Privacy Extensions
VE: 117: started
lo: Disabled Privacy Extensions
VE: 118: started
lo: Disabled Privacy Extensions
VE: 119: started
lo: Disabled Privacy Extensions
VE: 120: started
lo: Disabled Privacy Extensions
VE: 121: started
lo: Disabled Privacy Extensions
VE: 122: started
lo: Disabled Privacy Extensions
VE: 123: started
lo: Disabled Privacy Extensions
VE: 124: started
lo: Disabled Privacy Extensions
VE: 125: started
lo: Disabled Privacy Extensions
VE: 126: started
lo: Disabled Privacy Extensions
VE: 127: started
lo: Disabled Privacy Extensions
VE: 128: started
lo: Disabled Privacy Extensions
VE: 129: started
lo: Disabled Privacy Extensions
VE: 130: started
lo: Disabled Privacy Extensions
VE: 131: started
lo: Disabled Privacy Extensions
VE: 132: started
lo: Disabled Privacy Extensions
VE: 133: started
lo: Disabled Privacy Extensions
VE: 134: started
lo: Disabled Privacy Extensions
VE: 135: started
lo: Disabled Privacy Extensions
VE: 136: started
lo: Disabled Privacy Extensions
VE: 137: started
lo: Disabled Privacy Extensions
VE: 138: started
lo: Disabled Privacy Extensions
VE: 139: started
lo: Disabled Privacy Extensions
VE: 140: started
lo: Disabled Privacy Extensions
lo: Disabled Privacy Extensions
VE: 141: started
VE: 142: started
lo: Disabled Privacy Extensions
VE: 143: started
lo: Disabled Privacy Extensions
VE: 144: started
lo: Disabled Privacy Extensions
VE: 145: started
lo: Disabled Privacy Extensions
VE: 146: started
lo: Disabled Privacy Extensions
VE: 147: started
lo: Disabled Privacy Extensions
VE: 148: started
lo: Disabled Privacy Extensions
lo: Disabled Privacy Extensions
VE: 149: stopped
VE: 149: failed to start with err=-11
VE: 150: stopped
VE: 150: failed to start with err=-11
VE: 150: stopped
VE: 150: failed to start with err=-11
VE: 151: stopped
VE: 151: failed to start with err=-11
VE: 152: stopped
VE: 152: failed to start with err=-11
VE: 153: stopped
VE: 153: failed to start with err=-11
VE: 154: stopped
VE: 154: failed to start with err=-11
VE: 155: stopped
VE: 155: failed to start with err=-11
VE: 156: stopped
VE: 156: failed to start with err=-11
VE: 157: stopped
VE: 157: failed to start with err=-11
VE: 158: stopped
VE: 158: failed to start with err=-11
VE: 159: stopped
VE: 159: failed to start with err=-11
VE: 160: stopped
VE: 160: failed to start with err=-11
VE: 100: stopped
Ub 100 helds 3476 in kmemsize on put
VE: 101: stopped
Ub 101 helds 3476 in kmemsize on put
VE: 102: stopped
Ub 102 helds 3476 in kmemsize on put
VE: 103: stopped
Ub 103 helds 3476 in kmemsize on put
VE: 104: stopped
Ub 104 helds 3476 in kmemsize on put
VE: 105: stopped
Ub 105 helds 3476 in kmemsize on put
VE: 106: stopped
Ub 106 helds 3476 in kmemsize on put
VE: 107: stopped
Ub 107 helds 3476 in kmemsize on put
VE: 108: stopped
Ub 108 helds 3476 in kmemsize on put
VE: 109: stopped
Ub 109 helds 3476 in kmemsize on put
VE: 110: stopped
Ub 110 helds 3476 in kmemsize on put
VE: 111: stopped
Ub 111 helds 3476 in kmemsize on put
VE: 112: stopped
Ub 112 helds 3476 in kmemsize on put
VE: 113: stopped
Ub 113 helds 3476 in kmemsize on put
VE: 114: stopped
Ub 114 helds 3476 in kmemsize on put
VE: 115: stopped
Ub 115 helds 3476 in kmemsize on put
VE: 116: stopped
Ub 116 helds 3476 in kmemsize on put
VE: 117: stopped
Ub 117 helds 3476 in kmemsize on put
VE: 118: stopped
Ub 118 helds 3476 in kmemsize on put
VE: 119: stopped
Ub 119 helds 3476 in kmemsize on put
VE: 120: stopped
Ub 120 helds 3476 in kmemsize on put
VE: 121: stopped
Ub 121 helds 3476 in kmemsize on put
VE: 122: stopped
Ub 122 helds 3476 in kmemsize on put
VE: 123: stopped
Ub 123 helds 3476 in kmemsize on put
VE: 124: stopped
Ub 124 helds 3476 in kmemsize on put
VE: 125: stopped
Ub 125 helds 3476 in kmemsize on put
VE: 126: stopped
VE: 127: stopped
Ub 127 helds 3476 in kmemsize on put
Ub 126 helds 3476 in kmemsize on put
VE: 128: stopped
Ub 128 helds 3476 in kmemsize on put
VE: 129: stopped
Ub 129 helds 3476 in kmemsize on put
VE: 130: stopped
Ub 130 helds 3476 in kmemsize on put
VE: 131: stopped
Ub 131 helds 3476 in kmemsize on put
VE: 132: stopped
Ub 132 helds 3476 in kmemsize on put
VE: 133: stopped
VE: 134: stopped
Ub 134 helds 3476 in kmemsize on put
VE: 135: stopped
Ub 133 helds 3476 in kmemsize on put
Ub 135 helds 3476 in kmemsize on put
VE: 136: stopped
Ub 136 helds 3476 in kmemsize on put
VE: 137: stopped
Ub 137 helds 3476 in kmemsize on put
VE: 138: stopped
Ub 138 helds 3476 in kmemsize on put
VE: 139: stopped
Ub 139 helds 3476 in kmemsize on put
VE: 140: stopped
Ub 140 helds 3476 in kmemsize on put
VE: 141: stopped
Ub 141 helds 3476 in kmemsize on put
VE: 142: stopped
Ub 142 helds 3476 in kmemsize on put
VE: 143: stopped
Ub 143 helds 3476 in kmemsize on put
VE: 144: stopped
Ub 144 helds 3476 in kmemsize on put
VE: 145: stopped
Ub 145 helds 3476 in kmemsize on put
VE: 146: stopped
Ub 146 helds 3476 in kmemsize on put
VE: 147: stopped
Ub 147 helds 3476 in kmemsize on put
VE: 148: stopped
Ub 148 helds 3476 in kmemsize on put


wbr
yahbluez

Report message to a moderator

Re: max number of VE [message #16261 is a reply to message #16249] Thu, 30 August 2007 08:10 Go to previous messageGo to next message
dev is currently offline  dev
Messages: 1693
Registered: September 2005
Location: Moscow
Senior Member
yahbluez wrote on Wed, 29 August 2007 19:59

I mean the openvz did not start more than 49 instances.

Please looke here:

I first run 10 Ves than add 30 add up to 49
and than when i try to strat VE nummber 50 it will not do that.
I got an error message at syslog.


what message in syslog? please always report exact info from logs/output from commands when something fails. Otherwise it is impossible to help w/o knowing what fails.

http://static.openvz.org/userbars/openvz-developer.png

Report message to a moderator

Re: max number of VE [message #16263 is a reply to message #16261] Thu, 30 August 2007 09:17 Go to previous messageGo to next message
yahbluez is currently offline  yahbluez
Messages: 18
Registered: August 2007
Location: Germany
Junior Member
Sorry it was at the end of my post,
i show you the output of vzmemcheck and vzcpucheck just befor i try to start the next VE.

You see the error message and the paste from syslog.

It says error -11.


I try to move to centos 5.0 instead of etch, maybe that will make things easier?


wbr
yahbluez


ncl0:~/bin# vzmemcheck
Output values in %
LowMem LowMem RAM MemSwap MemSwap Alloc Alloc Alloc
util commit util util commit util commit limit
0.39 3.34 0.82 0.41 1.68 0.59 1.68 24.85

ncl0:~/bin# vzcpucheck
Current CPU utilization: 197000
Power of the node: 657217

Try to start VE 49:

Starting VPS ...
VPS is mounted
env_create error: Resource temporarily unavailable
VPS start failed

/var/log/syslog tells me:

Aug 29 17:52:02 ncl0 kernel: VE: 149: stopped
Aug 29 17:52:02 ncl0 kernel: VE: 149: failed to start with err=-11

ncl0:~/bin# uname -a
Linux ncl0 2.6.18-openvz-12-1etch1-amd64 #1 SMP Fri May 4 23:37:24 MSD 2007 x86_64 GNU/Linux

Report message to a moderator

Re: max number of VE [message #16264 is a reply to message #16263] Thu, 30 August 2007 09:21 Go to previous messageGo to next message
dev is currently offline  dev
Messages: 1693
Registered: September 2005
Location: Moscow
Senior Member
hmm... -11 == EAGAIN... strange...
Can you please first try the most recent kernel 012 is too old and I remember there were many fixes...

if you can recompile the kernel I could prepare you debug patch which could help to resolve it...

http://static.openvz.org/userbars/openvz-developer.png

Report message to a moderator

Re: max number of VE [message #16268 is a reply to message #16264] Thu, 30 August 2007 09:58 Go to previous messageGo to next message
yahbluez is currently offline  yahbluez
Messages: 18
Registered: August 2007
Location: Germany
Junior Member
I can compile on this server. To do so i need the patch and the information for wich kernel version the patch is.

Do you think that it is always a better idea to use a redhat based system for the host themself?

I preffer to run debian inside the Ves but outside centos or even SLES will be finde for me too.

thx
yahbluez

Report message to a moderator

Re: max number of VE [message #16275 is a reply to message #16268] Thu, 30 August 2007 11:26 Go to previous messageGo to next message
kir is currently offline  kir
Messages: 1645
Registered: August 2005
Location: Moscow, Russia
Senior Member
Well, I guess you do not need to compile anything (yet).

Just add debian.systs.org repository to your apt sources list and update the kernel from that repo. Reboot into that new kernel (should be 2.6.18-028stab039 as of now) and try to reproduce the problem.

Kir Kolyshkin
http://static.openvz.org/userbars/openvz-developer.png

Report message to a moderator

icon14.gif  SOLVED Re: max number of VE [message #16288 is a reply to message #16275] Thu, 30 August 2007 12:53 Go to previous messageGo to next message
yahbluez is currently offline  yahbluez
Messages: 18
Registered: August 2007
Location: Germany
Junior Member
Thx kir,

the newest kernel in this rep is:
2.6.18-028stab035.1-ovz-smp #1 SMP Wed Jun 13 21:52:27 CEST 2007 x86_64 GNU/Linux


With that kernel the bug did not apear.
Im able to run 100 VEs.

So no need for me to switch to centos on the host.

where may i found the sources of this kernel tree?

thanks again for your quick assistance.

with best regards
yahbluez

Report message to a moderator

Re: SOLVED Re: max number of VE [message #16290 is a reply to message #16288] Thu, 30 August 2007 13:39 Go to previous messageGo to next message
kir is currently offline  kir
Messages: 1645
Registered: August 2005
Location: Moscow, Russia
Senior Member
Quote:

where may i found the sources of this kernel tree?


Why do you need it? Want to rebuild? Why?

Sources are at
http://download.openvz.org/kernel/branches/2.6.18/028stab035 .1/

or you may use the latest released kernel:
http://download.openvz.org/kernel/branches/2.6.18/current/

Kir Kolyshkin
http://static.openvz.org/userbars/openvz-developer.png

Report message to a moderator

Re: SOLVED Re: max number of VE [message #16291 is a reply to message #16290] Thu, 30 August 2007 14:05 Go to previous message
yahbluez is currently offline  yahbluez
Messages: 18
Registered: August 2007
Location: Germany
Junior Member
to include squashfs.
But its possibly to do that on an other machine.

thx again for your help.

yahbluez

Report message to a moderator

Previous Topic: Maximum number of users : 200
Next Topic: Web Based VZ Administration
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Sat May 18 12:12:27 GMT 2024

Total time taken to generate the page: 0.00489 seconds
Powered by FUDforum Powered by Virtuozzo Containers