Issues wtih creating openvz machines

I

itconstruct

Active Member
Aug 3, 2009
77
0
26
I keep getting this error message upon creating new virtual machines under openvz:
moz-screenshot.png
moz-screenshot-1.png
moz-screenshot-2.png
unable to get tty name: Bad file descriptor.

I thought that this might have just been one machine that I created but I have created a new machine to the same error, deleted all templates under my proxmox install and created a new template using dab and I still get this error.

How can I fix this and continue to use openvz for my linux machines.

I have also tried to update the proxmox install to no luck.

Please help.
 
dietmar said:
Just tested with the template from our server - works without problems.
Click to expand...

Well it ain't working for me and this was the same template I had used many times before without issue.

I tried re-creating the template from scratch but I still received the same error.

Any clues as to why this is happening?
 
Nope nothing was changed on the system before this error occurred on the physical proxmox machine or os.

I had been working on both kvm and openvz virtual machines and then encountered this error.

Then I went through the steps above.

Will I have to backup all vm's and do a fresh install of proxmox to be able to fix this error?

How do I restore kvm and openvz backup images if I need to do this?
 
itconstruct said:
I tried setting up redmine under a openvz container which involved following the steps outlined here - http://www.redmine.org/wiki/1/RedmineInstall and here - http://ubuntuforums.org/showthread.php?t=674598

After doing these steps in an openvz container is when issues with creating new openvz containers started I believe as I was able to create a container to start setting up this machine fine.
Click to expand...

Confused - please can you confirm that:

a.) you did not modify any files one the host (only inside a VM)?

b.) The problem occur whitin the standard ubuntu template created with dab (no additional packages installed)?
 
dietmar said:
Confused - please can you confirm that:

a.) you did not modify any files one the host (only inside a VM)?

b.) The problem occur whitin the standard ubuntu template created with dab (no additional packages installed)?
Click to expand...

a) Yes I have not modified the host before this error occurred. The only changes made were to a openvz container.

b) Yes that is correct. I have not changed the standard dab template for ubuntu that I created via this means.
 
I cant reproduce that here - maybe you can do a fresh install somewhere and try to reproduce the problem - step by step util the error occur?
 
dietmar said:
I cant reproduce that here - maybe you can do a fresh install somewhere and try to reproduce the problem - step by step util the error occur?
Click to expand...

hmm. I think I will just need to do a reinstall and move all my vm's across to a new box.

It seems I have screwed up somewhere but I can't figure out where.

I will do some testing when I get a chance which will require me to turn off one of my main home server to do thee testing and migration to re-install that box.

Will let you know how it goes when I have the time to do this.
 
You must log in or register to reply here.
Top Bottom