OpenVZ Forum: Support » *BUG REPORTED* Migration problem with 2.6.18-028stab035

Home » General » Support » *BUG REPORTED* Migration problem with 2.6.18-028stab035

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

Re: Migration problem with 2.6.18-028stab035 [message #14858 is a reply to message #14854]

Thu, 12 July 2007 04:30

Vasily Tarasov
Messages: 1345
Registered: January 2006

Senior Member

Hello,

I filled the bug report http://bugzilla.openvz.org/show_bug.cgi?id=642 about the problem with tun device. It is really necessary to implement the migration of tun device! Smile

As concerns moving 500Mb RAM... Do you really have so thick VE? Wink

Well, ususally the dump file is not so large. You can check it by performing:

vzctl chkpnt VEID --dumpfile <file>
ls -lh <file>

Usually the most time-consuming part of migrating is syncing of private area. You can compress this data by adding "-z" option to rsync in vzmigrate script, as we already discussed...

Summary: Do you really think that the dump file is so big? (500+ Mb)

HTH,
Vasily

Report message to a moderator

[Message index]

		BUG REPORTED Migration problem with 2.6.18-028stab035 By: draga on Wed, 11 July 2007 12:22
		Re: Migration problem with 2.6.18-028stab035 By: Vasily Tarasov on Wed, 11 July 2007 12:34
		Re: Migration problem with 2.6.18-028stab035 By: draga on Wed, 11 July 2007 14:34
		Re: Migration problem with 2.6.18-028stab035 By: draga on Wed, 11 July 2007 22:11
		Re: Migration problem with 2.6.18-028stab035 By: Vasily Tarasov on Thu, 12 July 2007 04:30
		Re: Migration problem with 2.6.18-028stab035 By: draga on Thu, 12 July 2007 06:37
		Re: Migration problem with 2.6.18-028stab035 By: draga on Sun, 15 July 2007 21:24

Previous Topic:	SOLVED VEs with different subnets
Next Topic:	SOLVED Out of socket memory

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sun Aug 03 10:13:09 GMT 2025

Total time taken to generate the page: 1.17091 seconds