OpenVZ Forum - RDF feed
type: channel
items: Feisty VE breaks Edgy HN
items: Re: Feisty VE breaks Edgy HN

Feisty VE breaks Edgy HN
type: item
description: I have created an OpenVZ setup for testing. This is the HN configuration: Dell PowerEdge 1800, dual Xeon OpenVZ kernel 2.6.18-028stab035.1 from debian.systs.org (openvz stable) vzctl version 3.0.16-5dso1 Ubuntu 6.10 "Edgy" server On this system, and using the assistance of http://wiki.openvz.org/Physical_to_VE, I was able to migrate a quite old Mandrake 9.1 physical server to a VE, which runs well with no problems. So, I believe the HN/OpenVZ configuration to be sound. However, runing a Feisty VE does create a problem. I have read through the related topic at http://forum.openvz.org/index.php?t=tree&th=2297&mid =11810&&rev=&reveal= and Upstart bug #87173 (https://bugs.launchpad.net/upstart/+bug/87173). The Feisty VE will start with the most notable changes: Apply the file descriptor patch to the VE's upstart: http://codebrowse.launchpad.net/~keybuk/upstart/main/revisio n/scott%40netsplit.com-20070313191319-gztu8c0r0sjla0hp?start _revid=scott%40netsplit.com-20070316171800-scmrd6w9r22uf4me Change the kill -USR1 1 in the VE's /etc/init.d/mountall.sh script to use TERM instead. However, the VE's init process and upstart's domain socket seem to be leaking between the VE and the HN. On the HN before starting the VE: sysadmin@pe18001:~$ ps -ef | grep init | grep -v grep root 1 0 0 08:45 ? 00:00:00 /sbin/init splash sysadmin@pe18001:~$ sudo netstat -anp | grep init | grep -v grep unix 2 [ ] DGRAM 4771 1/init @/com/ubuntu/upstart sysadmin@pe18001:~$ sudo initctl list tty1 (start) running, process 6552 active tty2 (start) running, process 6553 active tty3 (start) running, process 6554 active tty4 (start) running, process 6555 active tty5 (start) running, process 6556 active tty6 (start) running, process 6557 active rc-default (stop) waiting rc0 (stop) waiting rc0-halt (stop) waiting rc0-poweroff (stop) waiting rc1 (stop) waiting rc2 (stop) waiting rc3 (stop) waiting rc4 (stop) waiting rc5 (stop) waiting rc6 (stop) waiting rcS (stop) waiting rcS-sulogin (stop) waiting logd (st…
creator: smckown
date: 2007-06-27T15:51:14-00:00

Re: Feisty VE breaks Edgy HN
type: item
description: Thank you for your future contributions First of all, where can I download your Feisty VE? I will start it on my CentOS host-node and check, how many sockets this VE will create on my mashine. Thanks, Vasily.
creator: Vasily Tarasov
date: 2007-06-28T11:48:32-00:00

Re: Feisty VE breaks Edgy HN
type: item
description: Hi Vasily, I sent you the link to the VE via PM. If you didn't get it, please let me know. Thanks again!
creator: smckown
date: 2007-06-29T19:26:34-00:00

Re: Feisty VE breaks Edgy HN
type: item
description: Is there a fix available for this problem? Using 2.6.18-53.1.19.el5.028stab053.14PAE/fedora core 9/upstart.
creator: hoppaz
date: 2008-07-01T17:13:04-00:00

Re: Feisty VE breaks Edgy HN
type: item
description: I replaced upstart with sysvinit in my Feisty template, from which I create all my VEs. This strategy also works for Gutsy VE's, but I never looked closer to see if Gutsy VE's would work without changing out upstart for sysvinit. Here's one link. Several more via google. http://ubuntuforums.org/showthread.php?t=456414. Best, Steve
creator: smckown
date: 2008-07-01T17:27:17-00:00

Re: Feisty VE breaks Edgy HN
type: item
description: I patched 3 files in upstart sources and changed the path /com/ubuntu/upstart to /ve/com/ubuntu/upstart for ve. While upstart is running with the old path in ve0... This fixes the initctl-problem. I think this is a security issue between upstart and openvz. Question to developer: Is this a problem which has to get fixed in openvz?
creator: hoppaz
date: 2008-07-02T14:38:02-00:00

Re: Feisty VE breaks Edgy HN
type: item
description: I mailed to upstart developer Scott James Remnant and described the problem. He thinks that this problem should get solved in openvz.
creator: hoppaz
date: 2008-07-03T09:05:58-00:00