Zhaohui Wang | 1 Oct 03:34 2008
Picon

RE: problem compiling 2.6.26-openvz


Hi 

I also found a conflict in the 2.6.26-openvz kernel

When CONFIG_CGROUP_MEM_RES_CTLR is turned on, the kernel/exit.c can not compile.it reports

kernel/exit.c: In function âmm_update_next_ownerâ:
kernel/exit.c:633: error: implicit declaration of function âdo_each_threadâ
kernel/exit.c:633: error: expected â;â before â{â token
make[1]: *** [kernel/exit.o] Error 1
make: *** [kernel] Error 2

shoud I file a bug in the bugzilla?

Best Regards
Zhaohui Wang

> 
> seriv@... wrote:
> > Hi,
> > I have a problem compiling kernel 2.6.26-ovz.
> _______________________________________________
> Users mailing list
> Users@...
> https://openvz.org/mailman/listinfo/users
Zhaohui Wang | 1 Oct 20:06 2008
Picon

RE: problem compiling 2.6.26-openvz

Also,

kernel/built-in.o: In function `taskcount_read':
kernel/cgroup_debug.c:44: undefined reference to `cgroup_task_count'

Best Regards
Zhaohui Wang

> -----Original Message-----
> From: users-bounces@...
[mailto:users-bounces@...] On
> Behalf Of Zhaohui Wang
> Sent: Tuesday, September 30, 2008 9:35 PM
> To: users@...; seriv@...
> Subject: RE: [Users] problem compiling 2.6.26-openvz
> 
> 
> 
> Hi
> 
> I also found a conflict in the 2.6.26-openvz kernel
> 
> When CONFIG_CGROUP_MEM_RES_CTLR is turned on, the kernel/exit.c can not
> compile.it reports
> 
> kernel/exit.c: In function âmm_update_next_ownerâ:
> kernel/exit.c:633: error: implicit declaration of function
> âdo_each_threadâ
> kernel/exit.c:633: error: expected â;â before â{â token
> make[1]: *** [kernel/exit.o] Error 1
(Continue reading)

Samuel Tremblay-Cossette | 1 Oct 21:49 2008
Picon

unable to migrate / checkpoint

Hi,

I'm unable to checkpoint and migrate my VEs. I'm using
2.6.24-19-openvz that come with Ubuntu 8.04.

Here is the error message:

root <at> frontend:~# vzctl chkpnt 2
Setting up checkpoint...
	suspend...
	dump...
Can not dump VE: Invalid argument
Error: d_path is invisible /dev
Checkpointing failed

kernel: CPT ERR: f6d61000,2 :d_path is invisible /dev

And some info about my setup:

root <at> frontend:~# sysctl fs.vsyscall vm.vdso_enabled
fs.vsyscall = 0
vm.vdso_enabled = 0

root <at> frontend:~# vzctl enter 2
entered into VE 2
root <at> none-test:/# mount
simfs on / type simfs (rw,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec)
tmpfs on /var/run type tmpfs (rw,nosuid,nodev,noexec)
(Continue reading)

Scott Dowdle | 2 Oct 05:59 2008

Re: unable to migrate / checkpoint

Samuel,

----- "Samuel Tremblay-Cossette" <samueltc@...> wrote:
> I'm unable to checkpoint and migrate my VEs. I'm using
> 2.6.24-19-openvz that come with Ubuntu 8.04.

Check bugzilla and see if that is already reported... and if so, if a fix has been found yet.  I haven't looked. 
2.6.24-x isn't an OpenVZ Stable Branch so I would expect some bugs.

TYL,
--

-- 
Scott Dowdle
704 Church Street
Belgrade, MT 59714
(406)388-0827 [home]
(406)994-3931 [work]
jesse keys | 2 Oct 07:02 2008
Picon

Re: unable to migrate / checkpoint

Samuel Tremblay-Cossette wrote:
> Hi,
> 
> I'm unable to checkpoint and migrate my VEs. I'm using
> 2.6.24-19-openvz that come with Ubuntu 8.04.
> 
> Here is the error message:
> 
> root <at> frontend:~# vzctl chkpnt 2

VEIDs < 101 are not supported. Had the same problem a while ago, because
i didn't read the openvz guide correctly (:x).

Someone mentioned a tool that could fix the ids, but i haven't found it
yet. perhaps someone else in here can lighten us up?
Scott Dowdle | 2 Oct 07:54 2008

Re: unable to migrate / checkpoint

Jesse,

----- "jesse keys" <jesse@...> wrote:
> > root <at> frontend:~# vzctl chkpnt 2
> 
> VEIDs < 101 are not supported. Had the same problem a while ago,
> because i didn't read the openvz guide correctly (:x).

Wow, *THAT* is all it was?  I hope so because that is easy to fix.

> Someone mentioned a tool that could fix the ids, but i haven't found
> it yet. perhaps someone else in here can lighten us up?

1) Stop container
2) mv /vz/private/{currentID} /vz/private/{newID}
3) mv /etc/vz/conf/{currentID}.conf /etc/vz/conf/{newID}.conf
4) Start container

I think there is a quota file on the filesystem that can be moved too... but if you don't, it'll just make a new
one... so I don't think it is that big of a deal.

TYL,
--

-- 
Scott Dowdle
704 Church Street
Belgrade, MT 59714
(406)388-0827 [home]
(406)994-3931 [work]
Gregor Mosheh | 2 Oct 08:09 2008

Re: unable to migrate / checkpoint

Scott Dowdle wrote:
> I think there is a quota file on the filesystem that can be moved
 > too... but if you don't, it'll just make a new one...

FYI:
The quota files are in /var/vzquota However, each quota file has the 
pathname inside it, so if you rename the quota file it is no longer 
valid. And if you get clever and modify the binary file, it breaks the 
checksum and invalidates it anyway.

Either way, you will have to sit through vzquota init and start, which 
can be VERY tedious if you deal with 100-200 GB VPSs like I do.

But you may want to delete the old quota file, in case you reuse the ID# 
later.

--

-- 
Gregor Mosheh / Greg Allensworth    BS, A+, Network+, Security+, Server+
System Administrator, Lead Programmer
HostGIS development & hosting services, http://www.HostGIS.com/

"Remember that no one cares if you can back up,
  only if you can restore." - AMANDA
jesse | 2 Oct 17:10 2008
Picon

Re: unable to migrate / checkpoint

Scott Dowdle wrote:

> 1) Stop container
> 2) mv /vz/private/{currentID} /vz/private/{newID}
> 3) mv /etc/vz/conf/{currentID}.conf /etc/vz/conf/{newID}.conf
> 4) Start container

I really should have tried that but was afraid to miss something.

Thanks Scott :)
Samuel Tremblay-Cossette | 2 Oct 18:08 2008
Picon

Re: unable to migrate / checkpoint

On Thu, Oct 2, 2008 at 1:02 AM, jesse keys <jesse@...> wrote:
> Samuel Tremblay-Cossette wrote:
>> Hi,
>>
>> I'm unable to checkpoint and migrate my VEs. I'm using
>> 2.6.24-19-openvz that come with Ubuntu 8.04.
>>
>> Here is the error message:
>>
>> root <at> frontend:~# vzctl chkpnt 2
>
> VEIDs < 101 are not supported. Had the same problem a while ago, because
> i didn't read the openvz guide correctly (:x).
>
> Someone mentioned a tool that could fix the ids, but i haven't found it
> yet. perhaps someone else in here can lighten us up?
> _______________________________________________
> Users mailing list
> Users@...
> https://openvz.org/mailman/listinfo/users
>

Still have the same error :(

root <at> frontend:~# vzctl chkpnt 1000
Setting up checkpoint...
	suspend...
	dump...
Can not dump VE: Invalid argument
Error: d_path is invisible /dev
(Continue reading)

Stanichenko Marat | 2 Oct 19:19 2008

Re: unable to migrate / checkpoint

Samuel Tremblay-Cossette wrote on 01.10.2008 23:49:
> Hi,
>
> I'm unable to checkpoint and migrate my VEs. I'm using
> 2.6.24-19-openvz that come with Ubuntu 8.04.
>
> Here is the error message:
>
> root <at> frontend:~# vzctl chkpnt 2
> Setting up checkpoint...
> 	suspend...
> 	dump...
> Can not dump VE: Invalid argument
> Error: d_path is invisible /dev
> Checkpointing failed
>
>   
Hello,

I'm not sure how that did happen on your node but that message should 
have been appeared when overmount was detected.
I can give a simple example. Let's assume that you have a process that 
opend a file /var/log/messages, after that you decide to use "another" 
/var  directory and for instance do the bind mount from the HN (mount 
--bind /var/ /vz/root/$VEID/var). So, when you try to checkpoint your VE 
you get this message.

May be you've started udev after your VE have been started and any 
process uses "old" /dev directory?
Do you have a way to reproduce it for sure? Is there a particular 
(Continue reading)


Gmane