Re[2]: Problem with new os template (pld)

Witam,

> I can't really help with --ipadd failure since it's *your* script 
> (pld-add_ip.sh) which should perform it. Try to debug it.

OK.

> As for the container entering problem, see 
> http://wiki.openvz.org/Container_enter_failed. Check that those device
> files exist and correct. Check that you can enter other (non-PLD) 
> containers fine.

I know this document very well... I read almost all wiki page.
Existing of this device files are enough to entering the container ?
Can anybody explain what is necessary to enter the container ?

non-PLD containers works OK, there is no problem in entering end
leaving the container.

--

-- 
Pozdrawiam,
 Łukasz Chrustek

1 VE on 1 Hardware Node

Hi,

is there a HowTo for configuring one single VE on a Hardware Node? I
tried with vzsplit -n 1 - but seems not working correctly?

-Stefan

Networking questions

Hi 

I have a few questions about the networking internals of open vz.
We are using debian etch, for the HN and the CTs and venet for the network.
The diagram for owr network is:

-----------------------------------------------------------
| --------------------------- --------------------------- |
| | VEID 20                 | | VEID 21                 | |
| | venet0 127.0.0.1        | | venet0 127.0.0.1        | |
| | venet0:0 192.168.8.20   | | venet0:0 192.168.8.21   | |
| | venet0:1 204.200.255.20 | | venet0:1 204.200.255.21 | |
| --------------------------- --------------------------- |
|                                                         |
| eth0:0 192.168.8.12                                     |
| eth0 204.200.255.12                                     |
-----------------------------------------------------------
      |
      |             -----------------    -------------
      |-------------|GATEWAY-SWITCH |----|INTERNET   |
      |             | 204.200.255.1 |    -------------
      |             -----------------
-----------------------------------------------------------
| --------------------------- --------------------------- |
| | VEID 22                 | | VEID 23                 | |
| | venet0 127.0.0.1        | | venet0 127.0.0.1        | |
| | venet0:0 192.168.8.22   | | venet0:0 192.168.8.23   | |
| | venet0:1 204.200.255.22 | |                         | |
| --------------------------- --------------------------- |
|                                                         |

Re: memory leak in 2.6.18 ovz kernels

On Tue, 2008-07-01 at 01:00 +0400, Kir Kolyshkin wrote:
> First, I hope you know the difference between memory shortage and memory 
> used for buffer/cache. In short: Linux tries to use all unused memory 
> for cache -- and if more memory is needed cache is shrunk. 

Sure.  But actually it never uses more than a couple hundred megs, even
if it's available (certainly not 6GB).  Also in this case buffer/cache
was driven down to under 100K and the server was using a couple hundred
megs of swap (which is unexpected given it has 8GB of RAM and only using
~2GB under normal circumstances).

Here's what top currently shows:

Mem:   8168892k total,  2161572k used,  6007320k free,   144216k buffers
Swap: 15631236k total,        0k used, 15631236k free,  1125972k cached

which is what I would expect.  I don't have exact numbers now, but
"used" was over 7.6GB at the time.

> Second, can you give us more details regarding "Athlon died after 
> exhausting memory"? If it was an oops -- we need its text.

No oops, just lots of processes killed by OOM, including sshd.  

> Third, are you using x86_64 kernel? What is your exact kernel version?

Yes, x86_64, kernel version 2.6.18-028.049 (Gentoo).

Currently, running 2.6.24 seems to have fixed it (but I may have to give
it longer to see).

Multiple bridge support

Hi all,

In Proxmox VE we want to support multiple bridges. I currently use a
patch
which adds an bridge parameter to the netif options: 

NETIF="ifname=XXX,bridge=XXX,mac=XXX,host_ifname=XXX,host_mac=XXX"

--netif_add ifname[,mac,host_ifname,host_mac,bridge]

I also modified --netif_add to accept empty parameters, for example:

--netif_add eth3,,,,vmbr3

I wonder if we can include that into the vzctl release - I will post 
the patch if soembody is interested.

- Dietmar

Re: Multiple bridge support

On Wednesday 02 July 2008 11:36:42 Dietmar Maurer wrote:
> Hi all,
>
> In Proxmox VE we want to support multiple bridges. I currently use a
> patch
> which adds an bridge parameter to the netif options:
>
> NETIF="ifname=XXX,bridge=XXX,mac=XXX,host_ifname=XXX,host_mac=XXX"
>
> --netif_add ifname[,mac,host_ifname,host_mac,bridge]
>
> I also modified --netif_add to accept empty parameters, for example:
>
> --netif_add eth3,,,,vmbr3
>
> I wonder if we can include that into the vzctl release - I will post
> the patch if soembody is interested.

Dietmar,

it will be useful indeed, please, provide patch to devel <at>  mailing list. 

>
> - Dietmar
>
>
> _______________________________________________
> Users mailing list
> Users@...
> https://openvz.org/mailman/listinfo/users

Re: Multiple bridge support

Dmitry Mishin wrote:
> On Wednesday 02 July 2008 11:36:42 Dietmar Maurer wrote:
>   
>> Hi all,
>>
>> In Proxmox VE we want to support multiple bridges. I currently use a
>> patch
>> which adds an bridge parameter to the netif options:
>>
>> NETIF="ifname=XXX,bridge=XXX,mac=XXX,host_ifname=XXX,host_mac=XXX"
>>
>> --netif_add ifname[,mac,host_ifname,host_mac,bridge]
>>
>> I also modified --netif_add to accept empty parameters, for example:
>>
>> --netif_add eth3,,,,vmbr3
>>
>> I wonder if we can include that into the vzctl release - I will post
>> the patch if soembody is interested.
>>     
>
> Dietmar,
>
> it will be useful indeed, please, provide patch to devel <at>  mailing list. 
>
>   
Please do so. I've written my own solution for this, but yours looks 
much better.

AW: Multiple bridge support

And here is the vznetaddbr we use (attached).

> >> I wonder if we can include that into the vzctl release - I 
> will post 
> >> the patch if soembody is interested.
> >>     
> >
> > Dietmar,
> >
> > it will be useful indeed, please, provide patch to devel <at>  
> mailing list. 
> >
> >   
> Please do so. I've written my own solution for this, but 
> yours looks much better.

_______________________________________________
Users mailing list
Users@...
https://openvz.org/mailman/listinfo/users

2.6.24 general protection fault

Just got general protection fault when doing (2.6.24 from git (pve)):

# /etc/init.d/vz stop
# /etc/init.d/vz start

But i cant reproduce the error anymore.

- Dietmar

-----------------------
Jul  3 12:40:52 oahu kernel: general protection fault: 0000 [1] PREEMPT
SMP
Jul  3 12:40:52 oahu kernel: CPU: 3
Jul  3 12:40:52 oahu kernel: Modules linked in: vznetdev simfs vzrst
vzcpt tun vzmon xt_tcpudp xt_length ipt_ttl xt_tcpmss xt_TCPMSS
iptable_mangle iptable_filter xt_multiport xt_limit ipt_tos ipt_REJECT
ip_tables x_tables kvm_intel kvm vzdquota vzdev ipv6 fan ac battery nfs
lockd nfs_acl sunrpc bridge dm_snapshot dm_mirror firewire_sbp2
firewire_core crc_itu_t loop snd_hda_intel snd_pcm_oss snd_mixer_oss
snd_pcm snd_timer snd serio_raw joydev th
ermal soundcore psmouse intel_agp snd_page_alloc button processor e1000e
r8169 evdev pcspkr sg dm_mod usbhid hid usb_storage sd_mod sr_mod
ide_disk ide_generic ide_cd cdrom shpchp pci_hotplug uhci_hcd ehci_hcd
iTCO_wdt i2c_i801 i2c_core ata_piix generic ide_core pata_marvell
ata_generic libata scsi_mod isofs zlib_inflate msdos fat
Jul  3 12:40:52 oahu kernel: Pid: 4089, comm: modprobe Not tainted
2.6.24 #1 ovz005
Jul  3 12:40:52 oahu kernel: RIP: 0010:[<ffffffff8025ff95>]
[<ffffffff8025ff95>] m_show+0x76/0x144
Jul  3 12:40:52 oahu kernel: RSP: 0018:ffff8100cd973e48  EFLAGS:

Re: AW: Multiple bridge support

Dietmar,

I have committed both the patch and the script to git, see [1] and [2]. 
I have modified the script a bit, hope I haven't break anything.

It would be just great if you can provide a patch to vzctl man page 
describing the new parameter, and the according wiki 
modifications/additions.

[1] 
http://git.openvz.org/?p=vzctl;a=commit;h=a16e0ecf72d4f2c7bd08aadbaa8272cbdc9e25a5
[2] 
http://git.openvz.org/?p=vzctl;a=commit;h=41fb6973bc205c00e25ba73431110ac8e821d6c9

Dietmar Maurer wrote:
> And here is the vznetaddbr we use (attached).
>
>   
>>>> I wonder if we can include that into the vzctl release - I 
>>>>         
>> will post 
>>     
>>>> the patch if soembody is interested.
>>>>     
>>>>         
>>> Dietmar,
>>>
>>> it will be useful indeed, please, provide patch to devel <at>  
>>>       
>> mailing list.