OpenVZ Forum: Support » Moved VE to new system and now network doesn't work

Home » General » Support » Moved VE to new system and now network doesn't work

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Moved VE to new system and now network doesn't work [message #25833]

Wed, 09 January 2008 15:06

JimL
Messages: 116
Registered: February 2007

Senior Member

I had a motherboard apparently go bad and would no longer see my sata drive, so I took it out and used a USB harness to access the data on a different system. This system is successfully running a VE on 192.168.2.251 so I know OpenVZ is working OK.

What I did was copy all of the files from the USB mounted drive from .../vz/private/1002 into /vz/private/1002
I also copied the 1002.conf file into the /etc/vz/conf directory.

Here's the result:

[root@server1 conf]# vzctl start 1002
Starting VE ...
VE is mounted
Adding IP address(es): 192.168.2.50
Setting CPU units: 1000
Configure meminfo: 200000
Set hostname: walnut
File resolv.conf was modified
VE start in progress...
[root@server1 conf]# ping 192.168.2.50
PING 192.168.2.50 (192.168.2.50) 56(84) bytes of data.

--- 192.168.2.50 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 1999ms

[root@server1 conf]# vzctl enter 1002
entered into VE 1002
root@walnut:/# ifconfig -a
lo Link encap:Local Loopback
LOOPBACK 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)

Any ideas? I assume I neglected to move something necessary but what?

Thanks,
Jim.

{added later]
I actually was able to get it to work when I entered the VE and did an
/etc/init.d/networking restart
Any idea why init didn't do that at boot time?

Thanks,
Jim.

[Updated on: Wed, 09 January 2008 15:19]

Report message to a moderator

Re: Moved VE to new system and now network doesn't work [message #25834 is a reply to message #25833]

Wed, 09 January 2008 15:19

ugob
Messages: 271
Registered: March 2007

Senior Member

I don't really have any idea, except running 'service network restart' inside the VE.

I usually use vzdump to do such migration, you may want to try it out.

Please read the manual before asking questions:
http://download.openvz.org/doc/OpenVZ-Users-Guide.pdf

Please have a look at the wiki before asking questions:
http://wiki.openvz.org/Main_Page

Report message to a moderator

Re: Moved VE to new system and now network doesn't work [message #25837 is a reply to message #25834]

Wed, 09 January 2008 15:43

JimL
Messages: 116
Registered: February 2007

Senior Member

ugob wrote on Wed, 09 January 2008 10:19

I don't really have any idea, except running 'service network restart' inside the VE.

I usually use vzdump to do such migration, you may want to try it out.

Well, since the original system is toast wrt reading the drive with the /vz/* data, that's not a option.

For some reason the links from the /etc/init.d are missing in /etc/rc?.d. I redid those and all seems to be OK again.

Strange.

Thanks,
Jim.

Report message to a moderator

Previous Topic:	BUG REPORTED Network issues inside of VE
Next Topic:	Memory Management again

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Fri Aug 16 23:09:20 GMT 2024

Total time taken to generate the page: 0.03824 seconds