Sponsored Content
Full Discussion: Container
Operating Systems Solaris Container Post 302605747 by gull04 on Thursday 8th of March 2012 11:45:39 AM
Old 03-08-2012
There is no difference between a zone and a container - they are the same thing!
 

10 More Discussions You Might Find Interesting

1. Solaris

LDOM vrs Container

Does anyone know the difference between a Logical Domain and a Container ? Both seem to be virtualisation technologies from Sun. Also I know a Domain can have containers within it but I don't see the point (4 Replies)
Discussion started by: jimthompson
4 Replies

2. Solaris

Solaris 8 Container Error

Log File: /var/tmp/server1.install.18730.log Source: /vmpool/tmp/server1.flar Installing: This may take several minutes... Postprocessing: This may take several minutes... Postprocess: ERROR: p2v module S40_setup_preload failed: 0 Postprocess: ERROR: Postprocessing failed. ... (0 Replies)
Discussion started by: cornsnap
0 Replies

3. Solaris

Cannot read MAC in a Zone Container

Hi, I have an app which reads MAC address. I read that Solaris 10 8/07 offers the solution to set MAC address for each container but I cannot find how to do that in any docs I found on Sun :( do you know how ? True that installed I only have Solaris 10 5/08. In a container zone it generates... (3 Replies)
Discussion started by: potro
3 Replies

4. Solaris

Solaris 6 container support

Is solaris 6 container support available ? Say, If I have a machine with Solaris 10 operating system.. Can i install Solaris 6 container on this machine, so that the machine will have Solaris 6 virtual environment... Does sun support Solaris 6 container ? Any ideas over this ? (1 Reply)
Discussion started by: shafi2all
1 Replies

5. Solaris

Swap issue on Container

Dear all, Kindly need your advice on swap issue on my container, SunOS 5.10. We have allocated swap 20GB and memory 8 GB. We have some application installed on the container. A few days ago we experienced a very slow system response...even for command like ls, df -k, etc.. I tried to... (8 Replies)
Discussion started by: sprout009
8 Replies

6. Solaris

Memory usage in a Solaris Container

Hi All, We have a server with Solaris 10 installed. The total memory of the server is 64GB. In order to check the memory info of the server I use "top" utility that gives me total and free memory in real-time. I have also installed a Sun container (non-global zone) on top of parent operating... (4 Replies)
Discussion started by: Slayer
4 Replies

7. Solaris

Solaris container date diference

Hi people, I dont have a real problem, its also a so strange issue. When i connect to my system from a ssh session or telnet normaly from putty and execute the command "date" its show me the correctly time in BRT format for root and all other users. But when i connect from the global... (3 Replies)
Discussion started by: anonymouzz
3 Replies

8. Solaris

solaris zones vs container..

kindly share what are difference b/w solaris zones and containers.... (8 Replies)
Discussion started by: Rajesh_Apple
8 Replies

9. UNIX for Advanced & Expert Users

mdadm container! How does it work

Hi everyone, I am not sure if I understand how mdadm --create /dev/md0 --level=container works? A device called /dev/md0 appears in /proc/mdstat but I am not sure how to use that device? I have 2 blank drives with 1 500GB partition on each. I would like to setup mirroring, but not in the... (0 Replies)
Discussion started by: hytron
0 Replies

10. Ubuntu

Ping a container LXC

Hello, Please, I try to do ping 10.0.3.8 (ip of LXC container) from VMB but it didn't work ! Have you an idea please ? Here is an explanation of what I want do: (red arrow) http://imgur.com/2IzJvXO imgur: the simple image sharer Thanks a lot. Best Regards. (0 Replies)
Discussion started by: chercheur111
0 Replies
vzmigrate(8)							    Containers							      vzmigrate(8)

NAME
vzmigrate - migrate a container between two OpenVZ servers SYNOPSIS
vzmigrate [-r|--remove-area yes|no] [--ssh=ssh_options] [--rsync=rsync_options] [--keep-dst] [--online] [-v] destination_address CTID DESCRIPTION
This utility is used to migrate a container from one (source) Hardware Node (HN) to another (destination) HN. The utility can migrate either stopped or running container. For a stopped container, simple CT private area transfer is performed (rsync(1) is used for file transfer). For running containers, migration may be offline (default) or online. This program uses ssh as a transport layer. You will need to put ssh public key to destination node and be able to connect to node without entering password. OPTIONS
-r, --remove-area yes | no Whether to remove a container area on source HN for the successfully migrated container. Default is yes. --ssh=options Additional options that will be passed to ssh while establishing connection to destination HN. --rsync=options Additional options that will be passed to rsync(8). You may add options like -z to enable data compression if you are migrating over a slow link. --keep-dst Do not clean synced destination container private area in case of some error. It makes sense to use this option on big container migration to avoid syncing container private area again in case some error (on container stop for example) occurs during first migration attempt. --online Perform online (zero-downtime) migration: during the migration the container hangs for a while and after the migration it continues working as though nothing has happened. -v Verbose mode. Causes vzmigrate to print debugging messages about its progress. Multiple -v options increase the verbosity. The maximum is 3. EXAMPLES
Migration of CT 101 to 192.168.1.130 with downtime: vzmigrate 192.168.1.130 101 Online migration of CT 102 to 192.168.1.130: vzmigrate --online 192.168.1.130 102 EXIT STATUS
0 EXIT_OK Command completed successfully. 1 EXIT_USAGE Bad command line options. 2 EXIT_VE_STOPPED Container is stopped. 4 EXIT_CONNECT Can't connect to destination (source) HN. 6 EXIT_COPY Container private area copying/moving failed. 7 EXIT_VE_START Can't start or restore destination CT. 8 EXIT_VE_STOP Can't stop or checkpoint source CT. 9 EXIT_EXISTS Container already exists on destination HN. 10 EXIT_NOTEXIST Container does not exists on source HN. 12 EXIT_IP_INUSE You attempt to migrate CT which IP address(es) are already in use on the destination node. 13 EXIT_QUOTA Operation with CT quota failed. SEE ALSO
rsync(1). COPYRIGHT
Copyright (C) 2001-2010, Parallels, Inc. Licensed under GNU GPL. OpenVZ 28 Jun 2011 vzmigrate(8)
All times are GMT -4. The time now is 03:16 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy