Home » Mailing lists » Users » veth and checkpoint and restore
| veth and checkpoint and restore [message #11106] |
Tue, 13 March 2007 15:58  |
Nils Domrose
Messages: 6
Registered: March 2007
|
Junior Member |
|
|
Hi,
I have a Problem that I cannot restore a VE (and also not migrate)
ovz2:/etc/vz/conf# vzctl --verbose restore 151 --dumpfile /var/tmp/
dump.151
Restoring VE ...
Starting VE ...
VE is mounted
undump...
Setting CPU units: 112005
Configure veth devices: veth151.0
Adding interface veth151.0 and route 10.215.127.151 for VE151 to VE0
Error: undump failed: Invalid argument
Restoring failed:
add ifaddr err -22 for 5 eth0
rst_restore_net: -22
VE start failed
Stopping VE ...
VE was stopped
VE is unmounted
vzctl start/stop works nicely in combination with the vznet.conf script.
If i run strace the last scripts (vznet.conf) and if for testing - I
create a 151.start script return exit 0. Never the less the restore
fails and I have no more clue why.
It looks like some script or program is still trying to restore the
networking for vnet interfaces - I have no IP_ADDRESS set in my
151.conf. Since I only use veth devices.
Nils
|
|
|
|
|
|
| Re: veth and checkpoint and restore [message #11132 is a reply to message #11107] |
Wed, 14 March 2007 10:07  |
Nils Domrose
Messages: 6
Registered: March 2007
|
Junior Member |
|
|
Hi Andrey,
vzctl version:
ovz1:~# vzctl --version
vzctl version 3.0.14-1dso31.2
for the kernel this is more problematic:
i noticed that i cannot provide you with the version since i
installed this kernel
http://download.openvz.org/kernel/debian/etch/linux-headers- 2.6.18-
openvz-amd64_02_amd64.deb
cat /proc/version
Linux version 2.6.18-openvz-amd64 (02) (ola@deb-build-
amd64.openvz.org) (gcc version 4.1.2 20061115 (prerelease) (Debian
4.1.1-21)) #1 SMP Fri Jan 26 18:14:59 UTC 2007
problem is that the debian packet and file name does not indicate the
version of the ovz patch - so your question was already helpfull
since no know that I do not know which version I use ;-)
Do you think it makes sense to upgrade to the latest version 028.18 -
I would try out:
http://download.openvz.org/kernel/debian/etch/linux-headers- 2.6.18-
openvz-amd64_028.18-2.6.18-11-1_amd64.deb
Nils
On Mar 13, 2007, at 5:21 PM, Andrey Mirkin wrote:
> Hello,
>
> Can you, please, provide us what kernel and vzctl do you use.
>
> Regards,
> Andrey
>
> On Tuesday 13 March 2007 18:58 Nils Domrose wrote:
>> Hi,
>>
>> I have a Problem that I cannot restore a VE (and also not migrate)
>>
>> ovz2:/etc/vz/conf# vzctl --verbose restore 151 --dumpfile /var/tmp/
>> dump.151
>> Restoring VE ...
>> Starting VE ...
>> VE is mounted
>> undump...
>> Setting CPU units: 112005
>> Configure veth devices: veth151.0
>> Adding interface veth151.0 and route 10.215.127.151 for VE151 to VE0
>> Error: undump failed: Invalid argument
>> Restoring failed:
>> add ifaddr err -22 for 5 eth0
>> rst_restore_net: -22
>> VE start failed
>> Stopping VE ...
>> VE was stopped
>> VE is unmounted
>>
>>
>> vzctl start/stop works nicely in combination with the vznet.conf
>> script.
>>
>>
>> If i run strace the last scripts (vznet.conf) and if for testing - I
>> create a 151.start script return exit 0. Never the less the restore
>> fails and I have no more clue why.
>> It looks like some script or program is still trying to restore the
>> networking for vnet interfaces - I have no IP_ADDRESS set in my
>> 151.conf. Since I only use veth devices.
>>
>>
>>
>> Nils
|
|
|
|
| Re: veth and checkpoint and restore [message #11148 is a reply to message #11132] |
Wed, 14 March 2007 11:44 |
Nils Domrose
Messages: 6
Registered: March 2007
|
Junior Member |
|
|
I installed the 028-18 debian package mentioned below,
same effect.
ovz2:~# vzctl chkpnt 151 --dumpfile /var/tmp/dump.151
Setting up checkpoint...
suspend...
dump...
kill...
VE is unmounted
Checkpointing completed succesfully
ovz2:~#
ovz2:~# vzctl restore 151 --dumpfile /var/tmp/dump.151
Restoring VE ...
Starting VE ...
VE is mounted
undump...
Setting CPU units: 112005
Configure veth devices: veth151.0
Adding interface veth151.0 and route 10.215.127.151 for VE151 to VE0
Error: undump failed: Invalid argument
Restoring failed:
add ifaddr err -22 for 5 eth0
rst_restore_net: -22
VE start failed
Stopping VE ...
VE was stopped
VE is unmounted
ovz2:~# uname -a
Linux ovz2 2.6.18-openvz-amd64 #1 SMP Mon Mar 12 21:59:13 UTC 2007
x86_64 GNU/Linux
On Mar 14, 2007, at 11:07 AM, Nils Domrose wrote:
> Hi Andrey,
>
> vzctl version:
> ovz1:~# vzctl --version
> vzctl version 3.0.14-1dso31.2
>
> for the kernel this is more problematic:
>
> i noticed that i cannot provide you with the version since i
> installed this kernel
> http://download.openvz.org/kernel/debian/etch/linux-headers- 2.6.18-
> openvz-amd64_02_amd64.deb
>
> cat /proc/version
> Linux version 2.6.18-openvz-amd64 (02) (ola@deb-build-
> amd64.openvz.org) (gcc version 4.1.2 20061115 (prerelease) (Debian
> 4.1.1-21)) #1 SMP Fri Jan 26 18:14:59 UTC 2007
>
> problem is that the debian packet and file name does not indicate
> the version of the ovz patch - so your question was already
> helpfull since no know that I do not know which version I use ;-)
>
> Do you think it makes sense to upgrade to the latest version 028.18
> - I would try out:
>
> http://download.openvz.org/kernel/debian/etch/linux-headers- 2.6.18-
> openvz-amd64_028.18-2.6.18-11-1_amd64.deb
>
> Nils
>
>
>
>
>
>
> On Mar 13, 2007, at 5:21 PM, Andrey Mirkin wrote:
>
>> Hello,
>>
>> Can you, please, provide us what kernel and vzctl do you use.
>>
>> Regards,
>> Andrey
>>
>> On Tuesday 13 March 2007 18:58 Nils Domrose wrote:
>>> Hi,
>>>
>>> I have a Problem that I cannot restore a VE (and also not migrate)
>>>
>>> ovz2:/etc/vz/conf# vzctl --verbose restore 151 --dumpfile /var/tmp/
>>> dump.151
>>> Restoring VE ...
>>> Starting VE ...
>>> VE is mounted
>>> undump...
>>> Setting CPU units: 112005
>>> Configure veth devices: veth151.0
>>> Adding interface veth151.0 and route 10.215.127.151 for VE151 to VE0
>>> Error: undump failed: Invalid argument
>>> Restoring failed:
>>> add ifaddr err -22 for 5 eth0
>>> rst_restore_net: -22
>>> VE start failed
>>> Stopping VE ...
>>> VE was stopped
>>> VE is unmounted
>>>
>>>
>>> vzctl start/stop works nicely in combination with the vznet.conf
>>> script.
>>>
>>>
>>> If i run strace the last scripts (vznet.conf) and if for testing - I
>>> create a 151.start script return exit 0. Never the less the restore
>>> fails and I have no more clue why.
>>> It looks like some script or program is still trying to restore the
>>> networking for vnet interfaces - I have no IP_ADDRESS set in my
>>> 151.conf. Since I only use veth devices.
>>>
>>>
>>>
>>> Nils
|
|
|
|
| Re: veth and checkpoint and restore [message #11152 is a reply to message #11148] |
Wed, 14 March 2007 12:31 |
Andrey Mirkin
Messages: 193
Registered: May 2006
|
Senior Member |
|
|
Hello!
Can you give an access to node?
If not, then try following:
1. Increase log level of CPT modules with commands:
echo 3 > /proc/sys/debug/cpt
echo 3 > /proc/sys/debug/rst
2. Checkpoint and restore VE in question
After that send me kernel logs and image file. Image file can be huge, so
please do not send it to list.
Regards,
Andrey
On Wednesday 14 March 2007 14:44 Nils Domrose wrote:
> I installed the 028-18 debian package mentioned below,
>
> same effect.
>
> ovz2:~# vzctl chkpnt 151 --dumpfile /var/tmp/dump.151
> Setting up checkpoint...
> suspend...
> dump...
> kill...
> VE is unmounted
> Checkpointing completed succesfully
> ovz2:~#
>
> ovz2:~# vzctl restore 151 --dumpfile /var/tmp/dump.151
> Restoring VE ...
> Starting VE ...
> VE is mounted
> undump...
> Setting CPU units: 112005
> Configure veth devices: veth151.0
> Adding interface veth151.0 and route 10.215.127.151 for VE151 to VE0
> Error: undump failed: Invalid argument
> Restoring failed:
> add ifaddr err -22 for 5 eth0
> rst_restore_net: -22
> VE start failed
> Stopping VE ...
> VE was stopped
> VE is unmounted
> ovz2:~# uname -a
> Linux ovz2 2.6.18-openvz-amd64 #1 SMP Mon Mar 12 21:59:13 UTC 2007
> x86_64 GNU/Linux
>
> On Mar 14, 2007, at 11:07 AM, Nils Domrose wrote:
> > Hi Andrey,
> >
> > vzctl version:
> > ovz1:~# vzctl --version
> > vzctl version 3.0.14-1dso31.2
> >
> > for the kernel this is more problematic:
> >
> > i noticed that i cannot provide you with the version since i
> > installed this kernel
> > http://download.openvz.org/kernel/debian/etch/linux-headers- 2.6.18-
> > openvz-amd64_02_amd64.deb
> >
> > cat /proc/version
> > Linux version 2.6.18-openvz-amd64 (02) (ola@deb-build-
> > amd64.openvz.org) (gcc version 4.1.2 20061115 (prerelease) (Debian
> > 4.1.1-21)) #1 SMP Fri Jan 26 18:14:59 UTC 2007
> >
> > problem is that the debian packet and file name does not indicate
> > the version of the ovz patch - so your question was already
> > helpfull since no know that I do not know which version I use ;-)
> >
> > Do you think it makes sense to upgrade to the latest version 028.18
> > - I would try out:
> >
> > http://download.openvz.org/kernel/debian/etch/linux-headers- 2.6.18-
> > openvz-amd64_028.18-2.6.18-11-1_amd64.deb
> >
> > Nils
> >
> > On Mar 13, 2007, at 5:21 PM, Andrey Mirkin wrote:
> >> Hello,
> >>
> >> Can you, please, provide us what kernel and vzctl do you use.
> >>
> >> Regards,
> >> Andrey
> >>
> >> On Tuesday 13 March 2007 18:58 Nils Domrose wrote:
> >>> Hi,
> >>>
> >>> I have a Problem that I cannot restore a VE (and also not migrate)
> >>>
> >>> ovz2:/etc/vz/conf# vzctl --verbose restore 151 --dumpfile /var/tmp/
> >>> dump.151
> >>> Restoring VE ...
> >>> Starting VE ...
> >>> VE is mounted
> >>> undump...
> >>> Setting CPU units: 112005
> >>> Configure veth devices: veth151.0
> >>> Adding interface veth151.0 and route 10.215.127.151 for VE151 to VE0
> >>> Error: undump failed: Invalid argument
> >>> Restoring failed:
> >>> add ifaddr err -22 for 5 eth0
> >>> rst_restore_net: -22
> >>> VE start failed
> >>> Stopping VE ...
> >>> VE was stopped
> >>> VE is unmounted
> >>>
> >>>
> >>> vzctl start/stop works nicely in combination with the vznet.conf
> >>> script.
> >>>
> >>>
> >>> If i run strace the last scripts (vznet.conf) and if for testing - I
> >>> create a 151.start script return exit 0. Never the less the restore
> >>> fails and I have no more clue why.
> >>> It looks like some script or program is still trying to restore the
> >>> networking for vnet interfaces - I have no IP_ADDRESS set in my
> >>> 151.conf. Since I only use veth devices.
> >>>
> >>>
> >>>
> >>> Nils
|
|
|
|
| Re: veth and checkpoint and restore [message #11157 is a reply to message #11152] |
Wed, 14 March 2007 13:16 |
Nils Domrose
Messages: 6
Registered: March 2007
|
Junior Member |
|
|
Hi,
here is the kernel log file:
Mar 14 14:06:48 ovz2 kernel: CPT DBG: cpt itimer 16736,17760(syslogd)
25303356000
Mar 14 14:06:48 ovz2 kernel: CPT DBG: cpt itimer 16769,17793(exim4)
1795377143000
Mar 14 14:06:48 ovz2 kernel: CPT DBG: ffff81007c262000,153:
16780,17804(cron) 13469949000
Mar 14 14:06:48 ovz2 kernel: VE: 153: stopped
Mar 14 14:06:51 ovz2 kernel: VE: 153: started
Mar 14 14:06:51 ovz2 kernel: CPT DBG: ffff81007da74000,153: JFixup
-30 3643948000
Mar 14 14:06:51 ovz2 kernel: lo: Disabled Privacy Extensions
Mar 14 14:06:51 ovz2 kernel: CPT ERR: ffff81007da74000,153 :add
ifaddr err -22 for 5 eth0
Mar 14 14:06:51 ovz2 kernel: CPT ERR:
ffff81007da74000,153 :rst_restore_net: -22
Mar 14 14:06:51 ovz2 kernel: CPT DBG: ffff81007da74000,153: leaked
through 16804/1 ffff81007d158e40
Mar 14 14:06:52 ovz2 kernel: VE: 153: stopped
the image is on its way.
never the less i notice the following:
----------------snip-----------------------
I shutdown the interface in the VE and all went OK:
----------------snip-----------------------
root@vz-test:/# ifdown eth0
root@vz-test:/# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:18:51:00:01:53
inet addr:10.215.127.153 Bcast:10.215.127.255 Mask:
255.255.254.0
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:4 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:244 (244.0 b) TX bytes:384 (384.0 b)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
venet0 Link encap:UNSPEC HWaddr
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
BROADCAST POINTOPOINT NOARP MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
root@vz-test:/# ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
root@vz-test:/# ifconfig
root@vz-test:/# logout
exited from VE 153
ovz2:/etc/vz/conf# vzctl chkpnt 153 --dumpfile /var/tmp/dump.153
Setting up checkpoint...
suspend...
dump...
kill...
VE is unmounted
Checkpointing completed succesfully
ovz2:/etc/vz/conf# vzctl restore 153 --dumpfile /var/tmp/dump.153
Restoring VE ...
Starting VE ...
VE is mounted
undump...
Setting CPU units: 112005
Configure veth devices: veth153.0
Adding interface veth153.0 and route 10.215.127.153 for VE153 to VE0
resume...
VE start in progress...
Restoring completed succesfully
----------------snip-----------------------
Now i configure the interface again:
----------------snip-----------------------
ovz2:/etc/vz/conf# vzctl enter 153
entered into VE 153
root@vz-test:/# ifup eth0
root@vz-test:/# logout
exited from VE 153
ovz2:/etc/vz/conf# vzctl chkpnt 153 --dumpfile /var/tmp/dump.153
Setting up checkpoint...
suspend...
dump...
kill...
VE is unmounted
Checkpointing completed succesfully
ovz2:/etc/vz/conf# vzctl restore 153 --dumpfile /var/tmp/dump.153
Restoring VE ...
Starting VE ...
VE is mounted
undump...
Setting CPU units: 112005
Configure veth devices: veth153.0
Adding interface veth153.0 and route 10.215.127.153 for VE153 to VE0
Error: undump failed: Invalid argument
Restoring failed:
add ifaddr err -22 for 5 eth0
rst_restore_net: -22
VE start failed
Stopping VE ...
VE was stopped
VE is unmounted
ovz2:/etc/vz/conf#
----------------snip-----------------------
Here is the log file:
Mar 14 14:08:54 ovz2 kernel: CPT DBG: cpt itimer 17026,18050(syslogd)
4280821000
Mar 14 14:08:54 ovz2 kernel: CPT DBG: cpt itimer 17059,18083(exim4)
1744368281000
Mar 14 14:08:54 ovz2 kernel: CPT DBG: ffff81007c20e800,153:
17069,18093(cron) 7427290000
Mar 14 14:08:54 ovz2 kernel: VE: 153: stopped
Mar 14 14:08:57 ovz2 kernel: VE: 153: started
Mar 14 14:08:57 ovz2 kernel: CPT DBG: ffff81007c7fb000,153: JFixup
-37 3613296000
Mar 14 14:08:57 ovz2 kernel: lo: Disabled Privacy Extensions
Mar 14 14:08:57 ovz2 kernel: CPT DBG: ffff81007c7fb000,153: 17125,1
(init)open RDONLY fifo ino 4648 ffff8100f6899980 1180
Mar 14 14:08:57 ovz2 kernel: CPT DBG: ffff81007c7fb000,153: file is
attached to a socket
Mar 14 14:08:57 ovz2 kernel: CPT DBG: ffff81007c7fb000,153:
17145,18050(syslogd)open RDONLY fifo ino 4872 ffff8100f6813dc0 11a0
Mar 14 14:08:57 ovz2 kernel: CPT DBG: ffff81007c7fb000,153: file is
attached to a socket
Mar 14 14:08:57 ovz2 kernel: CPT DBG: ffff81007c7fb000,153: rst_file:
file obtained by dentry_open
Mar 14 14:08:57 ovz2 kernel: CPT DBG: ffff81007c7fb000,153: file is
attached to a socket
Mar 14 14:08:57 ovz2 kernel: CPT DBG: ffff81007c7fb000,153: rst_file:
file obtained by dentry_open
Mar 14 14:08:57 ovz2 last message repeated 2 times
Mar 14 14:08:57 ovz2 kernel: CPT DBG: ffff81007c7fb000,153: bsd lock
restored
Mar 14 14:08:57 ovz2 kernel: CPT DBG: ffff81007c7fb000,153: settids
Mar 14 14:08:57 ovz2 kernel: CPT DBG: ffff81007c7fb000,153: settids
Mar 14 14:08:57 ovz2 kernel: CPT DBG: rst itimer 17145,18050(syslogd)
+667525000 4280821000
Mar 14 14:08:57 ovz2 kernel: CPT DBG: ffff81007c7fb000,153: itimer
17145,18050(syslogd) +667525000
Mar 14 14:08:57 ovz2 kernel: CPT DBG: ffff81007c7fb000,153: settids
Mar 14 14:08:57 ovz2 kernel: CPT DBG: rst itimer 17146,18083(exim4)
+1740754985000 1744368281000
Mar 14 14:08:57 ovz2 kernel: CPT DBG: ffff81007c7fb000,153: itimer
17146,18083(exim4) +1740754985000
Mar 14 14:08:57 ovz2 kernel: CPT DBG: ffff81007c7fb000,153: settids
Mar 14 14:08:57 ovz2 kernel: CPT DBG: ffff81007c7fb000,153: settids
Mar 14 14:08:57 ovz2 kernel: CPT DBG: ffff81007c7fb000,153: task
1/17125(init) is started
Mar 14 14:08:57 ovz2 kernel: CPT DBG: ffff81007c7fb000,153: task
18050/17145(syslogd) is started
Mar 14 14:08:57 ovz2 kernel: CPT DBG: rct: 17125,1(init)
Mar 14 14:08:57 ovz2 kernel: CPT DBG: rrs: 17125,1(init)
Mar 14 14:08:57 ovz2 kernel: CPT DBG: ffff81007c7fb000,153: task
18083/17146(exim4) is started
Mar 14 14:08:57 ovz2 kernel: CPT DBG: rct: 17145,18050(syslogd)
Mar 14 14:08:57 ovz2 kernel: CPT DBG: rrs: 17145,18050(syslogd)
Mar 14 14:08:57 ovz2 kernel: CPT DBG: ffff81007c7fb000,153: task
18090/17147(sshd) is started
Mar 14 14:08:57 ovz2 kernel: CPT DBG: rct: 17146,18083(exim4)
Mar 14 14:08:57 ovz2 kernel: CPT DBG: rrs: 17146,18083(exim4)
Mar 14 14:08:57 ovz2 kernel: CPT DBG: ffff81007c7fb000,153: task
18093/17148(cron) is started
Mar 14 14:08:57 ovz2 kernel: CPT DBG: rct: 17147,18090(sshd)
Mar 14 14:08:57 ovz2 kernel: CPT DBG: rrs: 17147,18090(sshd)
Mar 14 14:08:57 ovz2 kernel: CPT DBG: rct: 17148,18093(cron)
Mar 14 14:08:57 ovz2 kernel: CPT DBG: rrs: 17148,18093(cron)
Mar 14 14:09:08 ovz2 kernel: veth153.0: no IPv6 routers present
Mar 14 14:09:15 ovz2 kernel: CPT DBG: cpt itimer 17145,18050(syslogd)
12864503000
Mar 14 14:09:15 ovz2 kernel: CPT DBG: cpt itimer 17146,18083(exim4)
1722949124000
Mar 14 14:09:15 ovz2 kernel: CPT DBG: ffff81007c20e800,153:
17148,18093(cron) 45896571000
Mar 14 14:09:16 ovz2 kernel: VE: 153: stopped
Mar 14 14:09:18 ovz2 kernel: VE: 153: started
Mar 14 14:09:18 ovz2 kernel: CPT DBG: ffff8100f2685000,153: JFixup
-68 2861114000
Mar 14 14:09:18 ovz2 kernel: lo: Disabled Privacy Extensions
Mar 14 14:09:18 ovz2 kernel: CPT ERR: ffff8100f2685000,153 :add
ifaddr err -22 for 5 eth0
Mar 14 14:09:18 ovz2 kernel: CPT ERR:
ffff8100f2685000,153 :rst_restore_net: -22
Mar 14 14:09:18 ovz2 kernel: CPT DBG: ffff8100f2685000,153: leaked
through 17186/1 ffff8100f7badbc0
Mar 14 14:09:18 ovz2 kernel: VE: 153: stopped
so it looks like this happens only if veth(eth0) device inside the ve
is configured(and up)
Nils
On Mar 14, 2007, at 1:31 PM, Andrey Mirkin wrote:
> Hello!
>
> Can you give an access to node?
> If not, then try following:
> 1. Increase log level of CPT modules with commands:
> echo 3 > /proc/sys/debug/cpt
> echo 3 > /proc/sys/debug/rst
> 2. Checkpoint and restore VE in question
>
> After that send me kernel logs and image file. Image file can be
> huge, so
> please do not send it to list.
>
> Regards,
> Andrey
>
> On Wednesday 14 March 2007 14:44 Nils Domrose wrote:
>> I installed the 028-18 debian package mentioned below,
>>
>> same effect.
>>
>> ovz2:~# vzctl chkpnt 151 --dumpfile /var/tmp/dump.151
>> Setting up checkpoint...
>> suspend...
>> dump...
>> kill...
>> VE is unmounted
>> Checkpointing completed succesfully
>> ovz2:~#
>>
>> ovz2:~# vzctl restore 151 --dumpfile /var/tmp/dump.151
>> Restoring VE ...
>> Starting VE ...
>> VE is mounted
>> undump...
>> Setting CPU units: 112005
>> Configure veth devices: veth151.0
>> Adding interface veth151.0 and route 10.215.127.151 for VE151 to VE0
>> Error: undump failed: Invalid argument
>> Restoring failed:
>> add ifaddr err -22 for 5 eth0
>> rst_restore_net: -22
>> VE start failed
>> Stopping VE ...
>> VE was stopped
>> VE is unmounted
>> ovz2:~# uname -a
>> Linux ovz2 2.6.18-
...
|
|
|
|
Goto Forum:
Current Time: Sun Sep 01 19:19:51 GMT 2024
Total time taken to generate the page: 0.06066 seconds
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
