Lucid and OpenVZ and/or LXC ?

[bodhi.zazen]

I'm away from home and was doing it remotely but the server didn't come back up.

I learned this lesson as well, I do my testing on a VM. Testing is not 100 % on a VM , but at least when the VM fails it is not 300 miles away.

[JimGvo]

I learned this lesson as well, I do my testing on a VM. Testing is not 100 % on a VM , but at least when the VM fails it is not 300 miles away.

For many things I do the same, howerver when compiling and testing an Open
VZ kernel I can't do it. I suppose I could run virtualbox and then OpenVZ from within, but that's not my environment.

It's not a big problem since the server is primarily my backup server and since I'm not doing any development, current backups aren't very important.

Jim.

[JimGvo]

As requested I'm commenting on our conversation from the OpenVZ wiki. I apparently built my kernel a couple of days before you modified it. That's why I was using an old kernel. I have successfully built (maybe) a kernel based on 2.6.32-25. I say maybe because it didn't boot. I'm away from home and was doing it remotely but the server didn't come back up. I don't have access to the console from 300 miles from home, so will have to see why it didn't boot the next time I'm home.

The patching and compiling went along without a hitch.

Jim.

I found out why it wasn't working. The -25 generic kernel wasn't working either, so the openvz version didn't have a chance.

See http://ubuntuforums.org/showthread.p...1#post10093281 for details.

Jim.

[narcisgarcia]

JimGvo, try the tutorial replacing this URL:
http://download.openvz.org/kernel/br....1-combined.gz
For this other one:
http://download.openvz.org/kernel/br....1-combined.gz

You will get a package for OpenVZ kernel Linux 2.6.32.22 , and worked fine for me.

[JimGvo]

JimGvo, try the tutorial replacing this URL:
http://download.openvz.org/kernel/br....1-combined.gz
For this other one:
http://download.openvz.org/kernel/br....1-combined.gz

You will get a package for OpenVZ kernel Linux 2.6.32.22 , and worked fine for me.

I did get a 2.6.32.22 kernel, but it didn't work. It fails with the splash screen showing The disk drive for / is not ready yet or not present.
Continue to wait: or Press S to skip mounting or M for manual recovery.

If I press M I get:

some messages, of little importance and in the dmesg I see

ext4-fs sda5 mounted fs with ordered data
vfs mounted root (ext4 fs mode 3 ro on dev 8:5)

Not much else of interest. If I wait, it never continues, if I press S I get a list of some modules loaded and then:

init: plymouth main process killed by segv signal

it then waits for a long time. If I press C-A-D it will reboot so it isn't hung, just pausing. An enter doesn't do anything.

I'd really hate to have to run RHEL on this system. I'm quite pissed at Ubuntu for abandoning OpenVZ before a viable alternative is stable.

Jim.

[narcisgarcia]

- Have you read notes about ext4 and OpenVZ (ext3 or disable quotas)?
- Are you using GRUB1 or GRUB2?

[JimGvo]

- Have you read notes about ext4 and OpenVZ (ext3 or disable quotas)?
- Are you using GRUB1 or GRUB2?

No I don't know about ext4. I don't use quotas.

I believe the default is GRUB2. And I think that's what's be used.

Jim.

[realloc]

So, I got into my containers finally, made two of them.

How did you get past this error?

init: lxc pre-start process (2) terminated with status 32

I am getting the same thing (trying to set up a new LXC container).

[bodhi.zazen]

FYI: There is an openvz kernel available in the Debian repositories.

See : http://www.howtoforge.com/installing...-squeeze-amd64

I have not tried this kernel, but you could look at the sources and / or compile your own kernel if you so desire.

[JedMeister]

I have not tried the Debain Squeeze kernel either but I know someone who has (under Debian) and it seems to be working fine for them.