Upgrade to b2 killed MY Hardy VEs

argh

New Member
May 9, 2008
14
0
1
Had 3 hardy-VE's, all from ubuntu-8.04-amd64 template.
Worked perfectly until upgrade to beta2.
After upgrade I get:
"proxmox:~# vzctl enter 101
enter into CT 101 failed
Unable to open pty: No such file or directory"

ptyp*, ptmx and tty* exists in vz/root/101/dev/.static/dev/ and vz/private/101/dev. They do NOT exist in vz/root/101/dev.

- ii pve-manager 0.9-5 The Proxmox Virtul Environment

Have tried recreating ptmx, ptyp and tty via vzctl exec, but it adds the devices in /. It altso complains that /proc/devices is unreadable.

The logs are OK, no errors indicated, vzctl status 101 say: "CTID 101 exist mounted running"

Any ideas? I really need Hardy VEs for my mythbuntu-backend.

Regards,
Anders
 
I've just created a brand new VE using ubuntu-8.04-amd64-minimal.tar.gz from http://wiki.openvz.org/Download/template/precreated and it seems to create the proper /dev stuff. It also appears to not have udev installed.

I did have this problem with the user submitted ubuntu-6.06-i386-minimal template (including the /proc/devices error). I'm going to try that one again.
 
With the ubuntu-6.06-i386-minimal template I indeed did have this same problem. I solved it with this:

vzctl exec VID apt-get remvoe udev
 
Well, if I install a new hardy vm - it works. For some time.

Installed a brand new hardy VM yesterday, everything OK. Configured, installed mythbackend etc. Still working. Shut down and restarted the VM 6-7 times without any problems.
But this morning when I try shutown / restart the problem occurs.

I did a "vzctl exec VID apt-get remove udev", which seemed to work.
I did hovewer notice that it removed a whole bunch of other stuff. Not sure if anything is broken yet. :-)

I'm going to keep on testing; keep you posted.

Thx for the help so far. :-)