| 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 |
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
