source/locale/pot/virtual_machines.pot

# SOME DESCRIPTIVE TITLE.
# Copyright (C) 
# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2014-03-31 14:08-0400\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#: ../../virtual_machines.rst:18
# 2170d7c1a0e145718f15a48fdfd6376c
msgid "Working with Virtual Machines"
msgstr ""

#: ../../virtual_machines.rst:21
# 7b1c6837d7294d04b64fdefe3b860527
msgid "About Working with Virtual Machines"
msgstr ""

#: ../../virtual_machines.rst:23
# a8fcaad6e74c48de85dda47b508896ff
msgid "CloudStack provides administrators with complete control over the lifecycle of all guest VMs executing in the cloud. CloudStack provides several guest management operations for end users and administrators. VMs may be stopped, started, rebooted, and destroyed."
msgstr ""

#: ../../virtual_machines.rst:28
# 76072107bbd74ed58ef5e488bbc45361
msgid "Guest VMs have a name and group. VM names and groups are opaque to CloudStack and are available for end users to organize their VMs. Each VM can have three names for use in different contexts. Only two of these names can be controlled by the user:"
msgstr ""

#: ../../virtual_machines.rst:35
# fdf35c82059748b09618dc1b96c32958
msgid "Instance name – a unique, immutable ID that is generated by CloudStack and can not be modified by the user. This name conforms to the requirements in IETF RFC 1123."
msgstr ""

#: ../../virtual_machines.rst:41
# 35bab809b50548b78006bcf7edfd8375
msgid "Display name – the name displayed in the CloudStack web UI. Can be set by the user. Defaults to instance name."
msgstr ""

#: ../../virtual_machines.rst:46
# fc95d564a6b74400bdf7cbc43166b900
msgid "Name – host name that the DHCP server assigns to the VM. Can be set by the user. Defaults to instance name"
msgstr ""

#: ../../virtual_machines.rst:50
# 29b7bc970aec4088a82cb82eac51acf2
msgid "You can append the display name of a guest VM to its internal name. For more information, see `“Appending a Display Name to the Guest VM’s Internal Name” <#appending-a-display-name-to-the-guest-vms-internal-name>`_."
msgstr ""

#: ../../virtual_machines.rst:52
# 7776a17a323a4f91a6a4286428927bdf
msgid "Guest VMs can be configured to be Highly Available (HA). An HA-enabled VM is monitored by the system. If the system detects that the VM is down, it will attempt to restart the VM, possibly on a different host. For more information, see HA-Enabled Virtual Machines on"
msgstr ""

#: ../../virtual_machines.rst:57
# 89d81c5e76a047d0b049cbfcc9437d7d
msgid "Each new VM is allocated one public IP address. When the VM is started, CloudStack automatically creates a static NAT between this public IP address and the private IP address of the VM."
msgstr ""

#: ../../virtual_machines.rst:61
# 39ead95968f944999976e4c34017f685
msgid "If elastic IP is in use (with the NetScaler load balancer), the IP address initially allocated to the new VM is not marked as elastic. The user must replace the automatically configured IP with a specifically acquired elastic IP, and set up the static NAT mapping between this new IP and the guest VM’s private IP. The VM’s original IP address is then released and returned to the pool of available public IPs. Optionally, you can also decide not to allocate a public IP to a VM in an EIP-enabled Basic zone. For more information on Elastic IP, see `“About Elastic IP” <networking2.html#about-elastic-ip>`_."
msgstr ""

#: ../../virtual_machines.rst:71
# d4c486f223e24c42bd8704829023ab5d
msgid "CloudStack cannot distinguish a guest VM that was shut down by the user (such as with the “shutdown” command in Linux) from a VM that shut down unexpectedly. If an HA-enabled VM is shut down from inside the VM, CloudStack will restart it. To shut down an HA-enabled VM, you must go through the CloudStack UI or API."
msgstr ""

#: ../../virtual_machines.rst:78
# 9376b049fcf74e669edc936a118d19e3
msgid "Best Practices for Virtual Machines"
msgstr ""

#: ../../virtual_machines.rst:80
# 386619ec83cc48dfb2c427037f91d9f4
msgid "For VMs to work as expected and provide excellent service, follow these guidelines."
msgstr ""

#: ../../virtual_machines.rst:83
# 863fbc4da7ab48ceb27e621892255393
msgid "Monitor VMs for Max Capacity"
msgstr ""

#: ../../virtual_machines.rst:85
# b1c4a0929eb34ecb943335789bb31c92
msgid "The CloudStack administrator should monitor the total number of VM instances in each cluster, and disable allocation to the cluster if the total is approaching the maximum that the hypervisor can handle. Be sure to leave a safety margin to allow for the possibility of one or more hosts failing, which would increase the VM load on the other hosts as the VMs are automatically redeployed. Consult the documentation for your chosen hypervisor to find the maximum permitted number of VMs per host, then use CloudStack global configuration settings to set this as the default limit. Monitor the VM activity in each cluster at all times. Keep the total number of VMs below a safe level that allows for the occasional host failure. For example, if there are N hosts in the cluster, and you want to allow for one host in the cluster to be down at any given time, the total number of VM instances you can permit in the cluster is at most (N-1) \\* (per-host-limit). Once a cluster reaches this number of VMs, use the CloudStack UI to disable allocation of more VMs to the cluster."
msgstr ""

#: ../../virtual_machines.rst:103
# 07a8c32f156044b19d2ab4dc8c6911fa
msgid "Install Required Tools and Drivers"
msgstr ""

#: ../../virtual_machines.rst:105
# 3f8d86b785404f85abaf6c075cc419cd
msgid "Be sure the following are installed on each VM:"
msgstr ""

#: ../../virtual_machines.rst:109
# 5f5ab58b23b3484d806d822ff59a2de9
msgid "For XenServer, install PV drivers and Xen tools on each VM. This will enable live migration and clean guest shutdown. Xen tools are required in order for dynamic CPU and RAM scaling to work."
msgstr ""

#: ../../virtual_machines.rst:115
# 0535820eb5d040f4925c98cdfa7f1f00
msgid "For vSphere, install VMware Tools on each VM. This will enable console view to work properly. VMware Tools are required in order for dynamic CPU and RAM scaling to work."
msgstr ""

#: ../../virtual_machines.rst:119
# 52b93993efd74552bcbdffc5a0e4e982
msgid "To be sure that Xen tools or VMware Tools is installed, use one of the following techniques:"
msgstr ""

#: ../../virtual_machines.rst:124
# 74b0c1c26a5b460bb377b19ce856399d
msgid "Create each VM from a template that already has the tools installed; or,"
msgstr ""

#: ../../virtual_machines.rst:129
# 0e2a66d2e624435b827732e1a4e5f02c
msgid "When registering a new template, the administrator or user can indicate whether tools are installed on the template. This can be done through the UI or using the updateTemplate API; or,"
msgstr ""

#: ../../virtual_machines.rst:135
# be979443be424b4695d86d2417edaf13
msgid "If a user deploys a virtual machine with a template that does not have Xen tools or VMware Tools, and later installs the tools on the VM, then the user can inform CloudStack using the updateVirtualMachine API. After installing the tools and updating the virtual machine, stop and start the VM."
msgstr ""

#: ../../virtual_machines.rst:142
# d34d6ed121d543db962b242b95d76f47
msgid "VM Lifecycle"
msgstr ""

#: ../../virtual_machines.rst:144
# c150b40a15b348f5b5cdcc9af91ec2ec
msgid "Virtual machines can be in the following states:"
msgstr ""

#: ../../virtual_machines.rst:146
# 35450095449943769e4df916f2ba98d1
msgid "|basic-deployment.png|"
msgstr ""

#: ../../virtual_machines.rst:148
# 82d68697d2034dcaa1e4dd828818f3e5
msgid "Once a virtual machine is destroyed, it cannot be recovered. All the resources used by the virtual machine will be reclaimed by the system. This includes the virtual machine’s IP address."
msgstr ""

#: ../../virtual_machines.rst:152
# e5d85a86eec94820acffac7223216d7b
msgid "A stop will attempt to gracefully shut down the operating system, which typically involves terminating all the running applications. If the operation system cannot be stopped, it will be forcefully terminated. This has the same effect as pulling the power cord to a physical machine."
msgstr ""

#: ../../virtual_machines.rst:158
# 3262f9ef48524241b39ab24f50027665
msgid "A reboot is a stop followed by a start."
msgstr ""

#: ../../virtual_machines.rst:160
# 9fd4ac9dadd4498aba1893ab9ff67b37
msgid "CloudStack preserves the state of the virtual machine hard disk until the machine is destroyed."
msgstr ""

#: ../../virtual_machines.rst:163
# 225f316ae08b45c9af659bb8052ff60e
msgid "A running virtual machine may fail because of hardware or network issues. A failed virtual machine is in the down state."
msgstr ""

#: ../../virtual_machines.rst:166
# c87832d0da9849c99bb576cdc028a417
msgid "The system places the virtual machine into the down state if it does not receive the heartbeat from the hypervisor for three minutes."
msgstr ""

#: ../../virtual_machines.rst:169
# 38f2875d662c4c31b795e48e5666cdb5
msgid "The user can manually restart the virtual machine from the down state."
msgstr ""

#: ../../virtual_machines.rst:171
# f36a208dc3c04defb09639b1fc2c9ffa
msgid "The system will start the virtual machine from the down state automatically if the virtual machine is marked as HA-enabled."
msgstr ""

#: ../../virtual_machines.rst:175
# 435b7bc89e044825854f8238d54cd95c
msgid "Creating VMs"
msgstr ""

#: ../../virtual_machines.rst:177
# 90596cf453df41bea97abf4d26b55b9e
msgid "Virtual machines are usually created from a template. Users can also create blank virtual machines. A blank virtual machine is a virtual machine without an OS template. Users can attach an ISO file and install the OS from the CD/DVD-ROM."
msgstr ""

#: ../../virtual_machines.rst:183
# 89062b64f78c473bb4f095089a47a3e8
msgid "You can create a VM without starting it. You can determine whether the VM needs to be started as part of the VM deployment. A request parameter, startVM, in the deployVm API provides this feature. For more information, see the Developer's Guide."
msgstr ""

#: ../../virtual_machines.rst:185
# 0672247e369b4e2d946b125ca4084ed2
msgid "To create a VM from a template:"
msgstr ""

#: ../../virtual_machines.rst:189
#: ../../virtual_machines.rst:228
#: ../../virtual_machines.rst:379
#: ../../virtual_machines.rst:426
# dbdc45137b3844029f53e2cb9d9162c6
# 321604ea0f024536a10305764908c359
# 7f0370ba68fe4dae844b8c30bee8233e
# 60f232c6cc96485796b41b3a4e0e8595
msgid "Log in to the CloudStack UI as an administrator or user."
msgstr ""

#: ../../virtual_machines.rst:193
#: ../../virtual_machines.rst:232
#: ../../virtual_machines.rst:430
# 17cf7cb65591426fb58ec425f5fd55d8
# 770013bd81d74beab891f720896b414d
# c137363adbfd4c509c5f2496508d10e3
msgid "In the left navigation bar, click Instances."
msgstr ""

#: ../../virtual_machines.rst:197
#: ../../virtual_machines.rst:236
# 7d2ba36548a74ef1b9f34c832b763e04
# f3c1e3fb075f473dafabe13193f34933
msgid "Click Add Instance."
msgstr ""

#: ../../virtual_machines.rst:201
#: ../../virtual_machines.rst:240
# d0219b24a04045f995b827bd2898f2aa
# 539be5bfcf034e2aaa08ec396700de1c
msgid "Select a zone."
msgstr ""

#: ../../virtual_machines.rst:205
# 4a5fbf9ff1ee4269a55b0c3f549a22a5
msgid "Select a template, then follow the steps in the wizard. For more information about how the templates came to be in this list, see `*Working with Templates* <templates.html>`_."
msgstr ""

#: ../../virtual_machines.rst:211
# f131286995d64c42ac059085f726ae06
msgid "Be sure that the hardware you have allows starting the selected service offering."
msgstr ""

#: ../../virtual_machines.rst:216
#: ../../virtual_machines.rst:248
# edf69164fb0c47cb865ec5cbff2aa54e
# 4068a900b1d144749c414fd49b63db55
msgid "Click Submit and your VM will be created and started."
msgstr ""

#: ../../virtual_machines.rst:219
# f14fe68cb6e646b49647dfb709dffe56
msgid "For security reason, the internal name of the VM is visible only to the root admin."
msgstr ""

#: ../../virtual_machines.rst:221
# c7f29a0e0eca4b1fa04ae333390ec922
msgid "To create a VM from an ISO:"
msgstr ""

#: ../../virtual_machines.rst:224
# 9802d38bcbeb44faad59f0c6b4dd425f
msgid "(XenServer) Windows VMs running on XenServer require PV drivers, which may be provided in the template or added after the VM is created. The PV drivers are necessary for essential management functions such as mounting additional volumes and ISO images, live migration, and graceful shutdown."
msgstr ""

#: ../../virtual_machines.rst:244
# f11205e9a0634c1990bc69a94b684091
msgid "Select ISO Boot, and follow the steps in the wizard."
msgstr ""

#: ../../virtual_machines.rst:251
# 162cd4c1933b48c4a8e5a41c7ec37a5e
msgid "Accessing VMs"
msgstr ""

#: ../../virtual_machines.rst:253
# 1c1e1a7cc847480488dea9931bd3ffd6
msgid "Any user can access their own virtual machines. The administrator can access all VMs running in the cloud."
msgstr ""

#: ../../virtual_machines.rst:256
#: ../../virtual_machines.rst:657
# 582b288bbc8d448daa35ab6398edd5b6
# 63c33ffacebf44328922949b1d62e681
msgid "To access a VM through the CloudStack UI:"
msgstr ""

#: ../../virtual_machines.rst:260
#: ../../virtual_machines.rst:661
#: ../../virtual_machines.rst:741
#: ../../virtual_machines.rst:970
#: ../../virtual_machines.rst:1007
# 7966ee7c12414472976feb432099fd1e
# cc969f07182e4a4f825bb39d784326e2
# 717a93d287eb42e799e3246945610dee
# 7eedbf3ba193494f952fae4200c0bb8a
# c5992eae3ce542a287bec2ab940ce661
msgid "Log in to the CloudStack UI as a user or admin."
msgstr ""

#: ../../virtual_machines.rst:264
# 1bad53cc506643b4afa9f2f32d5c84df
msgid "Click Instances, then click the name of a running VM."
msgstr ""

#: ../../virtual_machines.rst:268
# ea61544613854ab98f0c7eaee19319b4
msgid "Click the View Console button |console-icon.png|."
msgstr ""

#: ../../virtual_machines.rst:270
# 7ee1f849247e4736b77106c631e33767
msgid "To access a VM directly over the network:"
msgstr ""

#: ../../virtual_machines.rst:274
# 210aa9db3b28438cae36441f14c29e2b
msgid "The VM must have some port open to incoming traffic. For example, in a basic zone, a new VM might be assigned to a security group which allows incoming traffic. This depends on what security group you picked when creating the VM. In other cases, you can open a port by setting up a port forwarding policy. See `“IP Forwarding and Firewalling” <networking2.html#ip-forwarding-and-firewalling>`_."
msgstr ""

#: ../../virtual_machines.rst:283
# b955202d572b4eab831bf58c7ddf0290
msgid "If a port is open but you can not access the VM using ssh, it’s possible that ssh is not already enabled on the VM. This will depend on whether ssh is enabled in the template you picked when creating the VM. Access the VM through the CloudStack UI and enable ssh on the machine using the commands for the VM’s operating system."
msgstr ""

#: ../../virtual_machines.rst:291
# eef15aa3610941a48b076ada83a93a76
msgid "If the network has an external firewall device, you will need to create a firewall rule to allow access. See `“IP Forwarding and Firewalling” <networking2.html#ip-forwarding-and-firewalling>`_."
msgstr ""

#: ../../virtual_machines.rst:296
# 07e9a7efad2c4aba92b7119770430d15
msgid "Stopping and Starting VMs"
msgstr ""

#: ../../virtual_machines.rst:298
# 3c483022f9974e77b1c3b4911b4b3ebb
msgid "Once a VM instance is created, you can stop, restart, or delete it as needed. In the CloudStack UI, click Instances, select the VM, and use the Stop, Start, Reboot, and Destroy buttons."
msgstr ""

#: ../../virtual_machines.rst:303
# 049108e92aae41a0bf087e70dee11846
msgid "Assigning VMs to Hosts"
msgstr ""

#: ../../virtual_machines.rst:305
# dd82ff2b06c14258a8d3b8de3cf2b75f
msgid "At any point in time, each virtual machine instance is running on a single host. How does CloudStack determine which host to place a VM on? There are several ways:"
msgstr ""

#: ../../virtual_machines.rst:311
# db958d47c4e14a3bb226699150d1e382
msgid "Automatic default host allocation. CloudStack can automatically pick the most appropriate host to run each virtual machine."
msgstr ""

#: ../../virtual_machines.rst:316
# c02752691e62472cbdcfeb12b718e2b5
msgid "Instance type preferences. CloudStack administrators can specify that certain hosts should have a preference for particular types of guest instances. For example, an administrator could state that a host should have a preference to run Windows guests. The default host allocator will attempt to place guests of that OS type on such hosts first. If no such host is available, the allocator will place the instance wherever there is sufficient physical capacity."
msgstr ""

#: ../../virtual_machines.rst:326
# 725d3214117b4a0e84922b5aa3395e44
msgid "Vertical and horizontal allocation. Vertical allocation consumes all the resources of a given host before allocating any guests on a second host. This reduces power consumption in the cloud. Horizontal allocation places a guest on each host in a round-robin fashion. This may yield better performance to the guests in some cases."
msgstr ""

#: ../../virtual_machines.rst:334
# 4aff1f16d00b45acab4019e0d726746f
msgid "End user preferences. Users can not control exactly which host will run a given VM instance, but they can specify a zone for the VM. CloudStack is then restricted to allocating the VM only to one of the hosts in that zone."
msgstr ""

#: ../../virtual_machines.rst:341
# 39bc261d5136423daceebdb26aa9c3b5
msgid "Host tags. The administrator can assign tags to hosts. These tags can be used to specify which host a VM should use. The CloudStack administrator decides whether to define host tags, then create a service offering using those tags and offer it to the user."
msgstr ""

#: ../../virtual_machines.rst:348
# 9bf9ddb0d6134624a599dea900cf220f
msgid "Affinity groups. By defining affinity groups and assigning VMs to them, the user or administrator can influence (but not dictate) which VMs should run on separate hosts. This feature is to let users specify that certain VMs won't be on the same host."
msgstr ""

#: ../../virtual_machines.rst:355
# 2bf39c550ec84d32bb321b563cf38e3f
msgid "CloudStack also provides a pluggable interface for adding new allocators. These custom allocators can provide any policy the administrator desires."
msgstr ""

#: ../../virtual_machines.rst:360
# 3f904a94520a464aaf183764319a1669
msgid "Affinity Groups"
msgstr ""

#: ../../virtual_machines.rst:362
# 1736a4811e0940b1a81a870d8894b714
msgid "By defining affinity groups and assigning VMs to them, the user or administrator can influence (but not dictate) which VMs should run on separate hosts. This feature is to let users specify that VMs with the same “host anti-affinity” type won’t be on the same host. This serves to increase fault tolerance. If a host fails, another VM offering the same service (for example, hosting the user's website) is still up and running on another host."
msgstr ""

#: ../../virtual_machines.rst:370
# 53fbff90dbfe4378912bdce947f6360c
msgid "The scope of an affinity group is per user account."
msgstr ""

#: ../../virtual_machines.rst:373
# f21a6c3edcb943709a5fd18034689340
msgid "Creating a New Affinity Group"
msgstr ""

#: ../../virtual_machines.rst:375
# 952aa2be921548eca8c72a16351e18aa
msgid "To add an affinity group:"
msgstr ""

#: ../../virtual_machines.rst:383
#: ../../virtual_machines.rst:452
#: ../../virtual_machines.rst:472
# b4788a23606446a28d9e54f23baa1d0a
# 9979d59417b340e4a9ccbe5403d7ac69
# 30711cca7fee42eea38e1ce82da4c842
msgid "In the left navigation bar, click Affinity Groups."
msgstr ""

#: ../../virtual_machines.rst:387
# cc4ced2fb2cb407692a1ee70f26a589d
msgid "Click Add affinity group. In the dialog box, fill in the following fields:"
msgstr ""

#: ../../virtual_machines.rst:392
# 7f6afe679e8146c98f7d6df960d9ea71
msgid "Name. Give the group a name."
msgstr ""

#: ../../virtual_machines.rst:396
# 3203d032a77d455483907eb99dad9f4e
msgid "Description. Any desired text to tell more about the purpose of the group."
msgstr ""

#: ../../virtual_machines.rst:401
# f0132b06c21a4ccf96e0e405288b2f01
msgid "Type. The only supported type shipped with CloudStack is Host Anti-Affinity. This indicates that the VMs in this group should avoid being placed on the same VM with each other. If you see other types in this list, it means that your installation of CloudStack has been extended with customized affinity group plugins."
msgstr ""

#: ../../virtual_machines.rst:409
# 68888c95236b4de6989162419f0b4d05
msgid "Assign a New VM to an Affinity Group"
msgstr ""

#: ../../virtual_machines.rst:411
# a7f949c20a7c4f7f92c6c36d19462f79
msgid "To assign a new VM to an affinity group:"
msgstr ""

#: ../../virtual_machines.rst:415
# b9be84f061894a848f0963c9c1a9b762
msgid "Create the VM as usual, as described in `“Creating VMs” <virtual_machines.html#creating-vms>`_. In the Add Instance wizard, there is a new Affinity tab where you can select the affinity group."
msgstr ""

#: ../../virtual_machines.rst:420
# 60d469cdf8b345b6bbccde8cea1c500d
msgid "Change Affinity Group for an Existing VM"
msgstr ""

#: ../../virtual_machines.rst:422
# 72f9a8cbe55f459c8e234d4829094f58
msgid "To assign an existing VM to an affinity group:"
msgstr ""

#: ../../virtual_machines.rst:434
# 2f2bed0782f840c0ae1f2403e67b0119
msgid "Click the name of the VM you want to work with."
msgstr ""

#: ../../virtual_machines.rst:438
# 1be9c0b8187d462099baa414f292414f
msgid "Stop the VM by clicking the Stop button."
msgstr ""

#: ../../virtual_machines.rst:442
# 9934a272aed044e1be6519701136b0f3
msgid "Click the Change Affinity button. |change-affinity-button.png|"
msgstr ""

#: ../../virtual_machines.rst:446
# 107b608573824f32b25733aa1be35a61
msgid "View Members of an Affinity Group"
msgstr ""

#: ../../virtual_machines.rst:448
# 39aa367909e247d9b7dda5e00fdc11d1
msgid "To see which VMs are currently assigned to a particular affinity group:"
msgstr ""

#: ../../virtual_machines.rst:456
#: ../../virtual_machines.rst:476
# c6ff79b2977f4780bba8d89d2939d6d7
# 528c4e24d64c40b782c2f097045479bd
msgid "Click the name of the group you are interested in."
msgstr ""

#: ../../virtual_machines.rst:460
# cd9344db1a7845e2ac6db8ae1b9cdce8
msgid "Click View Instances. The members of the group are listed."
msgstr ""

#: ../../virtual_machines.rst:462
# c8e598a21aa9411993a3e9d98098f792
msgid "From here, you can click the name of any VM in the list to access all its details and controls."
msgstr ""

#: ../../virtual_machines.rst:466
# bc6253fed6ef4ad9b34d66377fac822d
msgid "Delete an Affinity Group"
msgstr ""

#: ../../virtual_machines.rst:468
# 705ed7f11fa2492aa4f12cb7c3b83a33
msgid "To delete an affinity group:"
msgstr ""

#: ../../virtual_machines.rst:480
# 26faa61c5e374823a212c9ef948eaab7
msgid "Click Delete."
msgstr ""

#: ../../virtual_machines.rst:482
# e080c219cee941d2a3bd9afa644b52a0
msgid "Any VM that is a member of the affinity group will be disassociated from the group. The former group members will continue to run normally on the current hosts, but if the VM is restarted, it will no longer follow the host allocation rules from its former affinity group."
msgstr ""

#: ../../virtual_machines.rst:489
# 96f9f97fd07a401ca04a60cc43e9ddf7
msgid "Virtual Machine Snapshots"
msgstr ""

#: ../../virtual_machines.rst:491
#: ../../virtual_machines.rst:777
# c64deb2f10e54c858148630c5d08c79d
# 1cd91ec4adb3485cbef7eb7ad8a345e9
msgid "(Supported on VMware and XenServer)"
msgstr ""

#: ../../virtual_machines.rst:493
# 9f988407b4244ebd939a738c3e1171a4
msgid "In addition to the existing CloudStack ability to snapshot individual VM volumes, you can take a VM snapshot to preserve all the VM's data volumes as well as (optionally) its CPU/memory state. This is useful for quick restore of a VM. For example, you can snapshot a VM, then make changes such as software upgrades. If anything goes wrong, simply restore the VM to its previous state using the previously saved VM snapshot."
msgstr ""

#: ../../virtual_machines.rst:501
# 297acbf3278b49e3aebcdb2d625a42c9
msgid "The snapshot is created using the hypervisor's native snapshot facility. The VM snapshot includes not only the data volumes, but optionally also whether the VM is running or turned off (CPU state) and the memory contents. The snapshot is stored in CloudStack's primary storage."
msgstr ""

#: ../../virtual_machines.rst:506
# b2c35dd49ee449fe89b52c9e65cdca77
msgid "VM snapshots can have a parent/child relationship. Each successive snapshot of the same VM is the child of the snapshot that came before it. Each time you take an additional snapshot of the same VM, it saves only the differences between the current state of the VM and the state stored in the most recent previous snapshot. The previous snapshot becomes a parent, and the new snapshot is its child. It is possible to create a long chain of these parent/child snapshots, which amount to a \"redo\" record leading from the current state of the VM back to the original."
msgstr ""

#: ../../virtual_machines.rst:516
# b05ac4e6c37441b2bdf0604ab2728763
msgid "If you need more information about VM snapshots on VMware, check out the VMware documentation and the VMware Knowledge Base, especially `Understanding virtual machine snapshots <http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&externalId=1015180>`_."
msgstr ""

#: ../../virtual_machines.rst:522
# d5a9dd1a0e4f4d38ae6043e7107cef55
msgid "Limitations on VM Snapshots"
msgstr ""

#: ../../virtual_machines.rst:526
# 480356d265c44ccc955e6ec4d6b996a0
msgid "If a VM has some stored snapshots, you can't attach new volume to the VM or delete any existing volumes. If you change the volumes on the VM, it would become impossible to restore the VM snapshot which was created with the previous volume structure. If you want to attach a volume to such a VM, first delete its snapshots."
msgstr ""

#: ../../virtual_machines.rst:534
# e0539e9e649742e791fe86f92cf42c59
msgid "VM snapshots which include both data volumes and memory can't be kept if you change the VM's service offering. Any existing VM snapshots of this type will be discarded."
msgstr ""

#: ../../virtual_machines.rst:540
# af92c31e2cf54c6d93375e9b3b69359a
msgid "You can't make a VM snapshot at the same time as you are taking a volume snapshot."
msgstr ""

#: ../../virtual_machines.rst:545
# 51e49b30ae8e4501b16ef50f39f5c97b
msgid "You should use only CloudStack to create VM snapshots on hosts managed by CloudStack. Any snapshots that you make directly on the hypervisor will not be tracked in CloudStack."
msgstr ""

#: ../../virtual_machines.rst:550
# 33b02b024ce6425e827df49595c4f880
msgid "Configuring VM Snapshots"
msgstr ""

#: ../../virtual_machines.rst:552
# 438a0db0ad7f45dbbb046cbe9560f821
msgid "The cloud administrator can use global configuration variables to control the behavior of VM snapshots. To set these variables, go through the Global Settings area of the CloudStack UI."
msgstr ""

#: ../../virtual_machines.rst:556
# 8ab6bf4420be492e9639c233e77c6a0c
msgid "Configuration Setting Name"
msgstr ""

#: ../../virtual_machines.rst:558
# e5c65267d46a46588873cedef9381210
msgid "Description"
msgstr ""

#: ../../virtual_machines.rst:560
# a7756869a2d7450fa6c00d59471d65a9
msgid "vmsnapshots.max"
msgstr ""

#: ../../virtual_machines.rst:562
# 6b59688572f44a4084dee840e8cb92ab
msgid "The maximum number of VM snapshots that can be saved for any given virtual machine in the cloud. The total possible number of VM snapshots in the cloud is (number of VMs) \\* vmsnapshots.max. If the number of snapshots for any VM ever hits the maximum, the older ones are removed by the snapshot expunge job."
msgstr ""

#: ../../virtual_machines.rst:568
# 315e15f035d34660bf6c75e32f80bbf8
msgid "vmsnapshot.create.wait"
msgstr ""

#: ../../virtual_machines.rst:570
# 6c9f1eb1eee34263828e3616bc01b765
msgid "Number of seconds to wait for a snapshot job to succeed before declaring failure and issuing an error."
msgstr ""

#: ../../virtual_machines.rst:574
# 0a1f1d071bd5411aa41ed07db298dbd7
msgid "Using VM Snapshots"
msgstr ""

#: ../../virtual_machines.rst:576
# 1012a83b75ba4980ade5783df566d171
msgid "To create a VM snapshot using the CloudStack UI:"
msgstr ""

#: ../../virtual_machines.rst:580
# 33a990587dc74ae3a44b7680873a280a
msgid "Log in to the CloudStack UI as a user or administrator."
msgstr ""

#: ../../virtual_machines.rst:584
# 2c71edf0fbcf41d7b5cf19ccb31a2d8f
msgid "Click Instances."
msgstr ""

#: ../../virtual_machines.rst:588
# f0d034c90731414caf988c6b39daa3a4
msgid "Click the name of the VM you want to snapshot."
msgstr ""

#: ../../virtual_machines.rst:592
# cef255aa1bbf427eb67c09e57661c074
msgid "Click the Take VM Snapshot button. |VMSnapshotButton.png|"
msgstr ""

#: ../../virtual_machines.rst:594
# 91d86429adfe4fafa6557ac8fe9a4ebe
msgid "If a snapshot is already in progress, then clicking this button will have no effect."
msgstr ""

#: ../../virtual_machines.rst:598
# 0370dff77dde4e72adf2a67b45e8149c
msgid "Provide a name and description. These will be displayed in the VM Snapshots list."
msgstr ""

#: ../../virtual_machines.rst:603
# 855867a6500d429293ee8ebbcd75c9df
msgid "(For running VMs only) If you want to include the VM's memory in the snapshot, click the Memory checkbox. This saves the CPU and memory state of the virtual machine. If you don't check this box, then only the current state of the VM disk is saved. Checking this box makes the snapshot take longer."
msgstr ""

#: ../../virtual_machines.rst:611
# 555b611b1cd247a2996216ce643b91fd
msgid "Quiesce VM: check this box if you want to quiesce the file system on the VM before taking the snapshot. Not supported on XenServer when used with CloudStack-provided primary storage."
msgstr ""

#: ../../virtual_machines.rst:615
# 8e99f68110884748840edd18ab5dd2e6
msgid "When this option is used with CloudStack-provided primary storage, the quiesce operation is performed by the underlying hypervisor (VMware is supported). When used with another primary storage vendor's plugin, the quiesce operation is provided according to the vendor's implementation."
msgstr ""

#: ../../virtual_machines.rst:623
#: ../../virtual_machines.rst:770
#: ../../virtual_machines.rst:994
#: ../../virtual_machines.rst:1177
#: ../../virtual_machines.rst:1212
# 64c731c2d39b45c2a9bda67514d23efd
# a9ac563a0811423d904a5107ca94c503
# 591146dd0e264c80b6464b88ca9357c3
# dec56daa0b3542fbb8341e07033e9665
# 3636f9c70f554023be95dc5ac236d8df
msgid "Click OK."
msgstr ""

#: ../../virtual_machines.rst:625
# 8b2f4e3ab42c4ecca13a79bdeda7aef4
msgid "To delete a snapshot or restore a VM to the state saved in a particular snapshot:"
msgstr ""

#: ../../virtual_machines.rst:630
# 100fcc6b769847daadd44b81deb01660
msgid "Navigate to the VM as described in the earlier steps."
msgstr ""

#: ../../virtual_machines.rst:634
# b42bf19ec7fe4d348bb9896919e99d7e
msgid "Click View VM Snapshots."
msgstr ""

#: ../../virtual_machines.rst:638
# 116e22cf4bbc46f583ec19afc7a83234
msgid "In the list of snapshots, click the name of the snapshot you want to work with."
msgstr ""

#: ../../virtual_machines.rst:643
# 9680e9db4d1d45e0a4f1355162d48d87
msgid "Depending on what you want to do:"
msgstr ""

#: ../../virtual_machines.rst:645
# cc915de819194759a4730b1596fd0f45
msgid "To delete the snapshot, click the Delete button. |delete-button.png|"
msgstr ""

#: ../../virtual_machines.rst:647
# 5720d90a77164d1c9b47a6e4d6493f58
msgid "To revert to the snapshot, click the Revert button. |revert-vm.png|"
msgstr ""

#: ../../virtual_machines.rst:649
# 1eb4b6de42fc4a958c571bddd6fdf4af
msgid "VM snapshots are deleted automatically when a VM is destroyed. You don't have to manually delete the snapshots in this case."
msgstr ""

#: ../../virtual_machines.rst:652
# bf0cbd9990334eb78c0a68b58fd55949
msgid "Changing the VM Name, OS, or Group"
msgstr ""

#: ../../virtual_machines.rst:654
# bb3f878a35cd400eb4dbc5590833c6a4
msgid "After a VM is created, you can modify the display name, operating system, and the group it belongs to."
msgstr ""

#: ../../virtual_machines.rst:665
#: ../../virtual_machines.rst:745
#: ../../virtual_machines.rst:974
#: ../../virtual_machines.rst:1011
#: ../../virtual_machines.rst:1196
# 3c79485483a24041b1a63ff8c4962455
# 26a8095e2378453aae012204e61d5012
# 892ab93158c6470293b350d2c1a1683b
# 7292d4056be84a7da4271b3efcf751eb
# 74da77f007b54413b23a8cf4c355ea97
msgid "In the left navigation, click Instances."
msgstr ""

#: ../../virtual_machines.rst:669
# b3c44fd119fd4d3ca4a21c70c141006b
msgid "Select the VM that you want to modify."
msgstr ""

#: ../../virtual_machines.rst:673
#: ../../virtual_machines.rst:756
# cd5efcab714940198a37940b533fb83e
# b98ba035b8fe4339955221cfa626e541
msgid "Click the Stop button to stop the VM. |StopButton.png|"
msgstr ""

#: ../../virtual_machines.rst:677
# 2c56bc69a7b441e9a866eb6c9a2cc8ad
msgid "Click Edit. |EditButton.png|"
msgstr ""

#: ../../virtual_machines.rst:681
# c532542833a74aff9cb5d19bfb2fa261
msgid "Make the desired changes to the following:"
msgstr ""

#: ../../virtual_machines.rst:685
# bc23e5df14ed483584bea8c0150a484c
msgid "**Display name**: Enter a new display name if you want to change the name of the VM."
msgstr ""

#: ../../virtual_machines.rst:690
# 7afcc727427d45fe96e478ea446336a0
msgid "**OS Type**: Select the desired operating system."
msgstr ""

#: ../../virtual_machines.rst:694
# abbc86a92d4444ed9f7b9b2357baa1be
msgid "**Group**: Enter the group name for the VM."
msgstr ""

#: ../../virtual_machines.rst:698
#: ../../virtual_machines.rst:846
# dd76abfa5c964108a6c9230c9fbcd606
# 415be7be9d294588a419692258b1ba1a
msgid "Click Apply."
msgstr ""

#: ../../virtual_machines.rst:701
# bfc324b750b049169c4a90709c8f6fe5
msgid "Appending a Display Name to the Guest VM’s Internal Name"
msgstr ""

#: ../../virtual_machines.rst:703
# 3fdb1ec3e9ca4ab2bed35e0b9d0fc31d
msgid "Every guest VM has an internal name. The host uses the internal name to identify the guest VMs. CloudStack gives you an option to provide a guest VM with a display name. You can set this display name as the internal name so that the vCenter can use it to identify the guest VM. A new global parameter, vm.instancename.flag, has now been added to achieve this functionality."
msgstr ""

#: ../../virtual_machines.rst:710
# 70ebc8d7fb524bba80935443c9bb5a38
msgid "The default format of the internal name is i-<user\\_id>-<vm\\_id>-<instance.name>, where instance.name is a global parameter. However, If vm.instancename.flag is set to true, and if a display name is provided during the creation of a guest VM, the display name is appended to the internal name of the guest VM on the host. This makes the internal name format as i-<user\\_id>-<vm\\_id>-<displayName>. The default value of vm.instancename.flag is set to false. This feature is intended to make the correlation between instance names and internal names easier in large data center deployments."
msgstr ""

#: ../../virtual_machines.rst:720
# e7dcf9ff2ede40e7ad88cc9d45558874
msgid "The following table explains how a VM name is displayed in different scenarios."
msgstr ""

#: ../../virtual_machines.rst:724
# a9e2bf46d7c346d8af293ad73c2e684a
msgid "User-Provided Display Name"
msgstr ""

#: ../../virtual_machines.rst:724
# fee0cd8b1fe4487d8c082ef34a9fc968
msgid "vm.instancename.flag"
msgstr ""

#: ../../virtual_machines.rst:724
# 0802a64909d3466191c2bad24ec8bbe9
msgid "Hostname on the VM"
msgstr ""

#: ../../virtual_machines.rst:724
# 431d32ea296544f9b8e951dcc7988ec1
msgid "Name on vCenter"
msgstr ""

#: ../../virtual_machines.rst:724
# adc50a465cb94885ae79c571546e7570
msgid "Internal Name"
msgstr ""

#: ../../virtual_machines.rst:726
#: ../../virtual_machines.rst:728
# 3dc225bc98dd447ba275ccc6b1fc3c4a
# b100851adac24eb6b9b6159a2f934f7e
msgid "Yes"
msgstr ""

#: ../../virtual_machines.rst:726
#: ../../virtual_machines.rst:727
# f51d73dfb1b149be9803bf629bd5adaa
# be1874026cab4afd8a1717bf4a88618b
msgid "True"
msgstr ""

#: ../../virtual_machines.rst:726
#: ../../virtual_machines.rst:728
# 003ebc1da3174970bb1750546ae5ce4a
# ce3520ca7d684836aff5c98244992ba2
msgid "Display name"
msgstr ""

#: ../../virtual_machines.rst:726
#: ../../virtual_machines.rst:726
# 5838c808f46141f0bb3d0ec56b725f2b
# 0148868b3e774a4db0afb05287ebc1ff
msgid "i-<user\\_id>-<vm\\_id>-displayName"
msgstr ""

#: ../../virtual_machines.rst:727
#: ../../virtual_machines.rst:729
# b2ae497e2b0642e3a4f8603ccedfe021
# 8132948b1e674e5eb57f3d1ec76613ce
msgid "No"
msgstr ""

#: ../../virtual_machines.rst:727
#: ../../virtual_machines.rst:729
# 976d1732c80e416895823f19d9ea3d33
# 03b0a027103941e785544c80d73c35a0
msgid "UUID"
msgstr ""

#: ../../virtual_machines.rst:727
#: ../../virtual_machines.rst:727
#: ../../virtual_machines.rst:728
#: ../../virtual_machines.rst:728
#: ../../virtual_machines.rst:729
#: ../../virtual_machines.rst:729
# b7cbaa66caa14d6cb52d162873d6e34a
# 21ccfc6d8c7d48da985a9dbe38ad47f9
# cf8e6e77c0b7410ebf9f734284ae8051
# 491471d146974889873f5b29feab9516
# 442b5ea91886462f8e77ec3c3fa26f73
# f65b3aaa71f34436b30c67aa875be464
msgid "i-<user\\_id>-<vm\\_id>-<instance.name>"
msgstr ""

#: ../../virtual_machines.rst:728
#: ../../virtual_machines.rst:729
# 80ad2684aaef4dd4a4c4e661b4780896
# 772274ff3eac4e59afaed9d440dce9b4
msgid "False"
msgstr ""

#: ../../virtual_machines.rst:734
# c9ae081445274a4f8ed0bab875e10d91
msgid "Changing the Service Offering for a VM"
msgstr ""

#: ../../virtual_machines.rst:736
# 24262c17e18946c69d73feb0f92d470a
msgid "To upgrade or downgrade the level of compute resources available to a virtual machine, you can change the VM's compute offering."
msgstr ""

#: ../../virtual_machines.rst:749
# 5635030af83f40ecb65cccb32dc8e5d5
msgid "Choose the VM that you want to work with."
msgstr ""

#: ../../virtual_machines.rst:753
# 5f129aad75ed42008e8dfe5a33c70b3c
msgid "(Skip this step if you have enabled dynamic VM scaling; see :ref:`cpu-and-memory-scaling`.)"
msgstr ""

#: ../../virtual_machines.rst:760
# 7558361b218c43b6a41cab8d88ad8917
msgid "Click the Change Service button. |ChangeServiceButton.png|"
msgstr ""

#: ../../virtual_machines.rst:762
# e2a7b28c0ed643628721bae2c57866ad
msgid "The Change service dialog box is displayed."
msgstr ""

#: ../../virtual_machines.rst:766
# c534200b0f234e4c9bab8bde5e8870e9
msgid "Select the offering you want to apply to the selected VM."
msgstr ""

#: ../../virtual_machines.rst:775
# 27cc346285d64fc28e5ae5385a64ccf2
msgid "CPU and Memory Scaling for Running VMs"
msgstr ""

#: ../../virtual_machines.rst:779
# 003ea8b547a9485b93e271dd28f999c7
msgid "It is not always possible to accurately predict the CPU and RAM requirements when you first deploy a VM. You might need to increase these resources at any time during the life of a VM. You can dynamically modify CPU and RAM levels to scale up these resources for a running VM without incurring any downtime."
msgstr ""

#: ../../virtual_machines.rst:785
# 01c0085974924811b187eae6b78a7e3c
msgid "Dynamic CPU and RAM scaling can be used in the following cases:"
msgstr ""

#: ../../virtual_machines.rst:789
# 31c363b5061f41f0a3d90253661544bd
msgid "User VMs on hosts running VMware and XenServer."
msgstr ""

#: ../../virtual_machines.rst:793
# a5aa7ca4c88e404c856aa6e294e9d37e
msgid "System VMs on VMware."
msgstr ""

#: ../../virtual_machines.rst:797
# a7d2cfb519ec4add81f26ea49d645daa
msgid "VMware Tools or XenServer Tools must be installed on the virtual machine."
msgstr ""

#: ../../virtual_machines.rst:802
# 2bba4d9cff7f4ba7a99dbcaf432658b8
msgid "The new requested CPU and RAM values must be within the constraints allowed by the hypervisor and the VM operating system."
msgstr ""

#: ../../virtual_machines.rst:807
# dea06443628241338663ac0823265090
msgid "New VMs that are created after the installation of CloudStack 4.2 can use the dynamic scaling feature. If you are upgrading from a previous version of CloudStack, your existing VMs created with previous versions will not have the dynamic scaling capability unless you update them using the following procedure."
msgstr ""

#: ../../virtual_machines.rst:814
# f85afebe892a4ace9207f033d6491f66
msgid "Updating Existing VMs"
msgstr ""

#: ../../virtual_machines.rst:816
# 5b1650cd938443f58757171129549956
msgid "If you are upgrading from a previous version of CloudStack, and you want your existing VMs created with previous versions to have the dynamic scaling capability, update the VMs using the following steps:"
msgstr ""

#: ../../virtual_machines.rst:822
# e17b5670258343b49b747ee6e079d4ec
msgid "Make sure the zone-level setting enable.dynamic.scale.vm is set to true. In the left navigation bar of the CloudStack UI, click Infrastructure, then click Zones, click the zone you want, and click the Settings tab."
msgstr ""

#: ../../virtual_machines.rst:829
# bee04f5bc16843af85ad08de5482bb0b
msgid "Install Xen tools (for XenServer hosts) or VMware Tools (for VMware hosts) on each VM if they are not already installed."
msgstr ""

#: ../../virtual_machines.rst:834
# b1f2bf5ed45a4fcfa061660f0df1f283
msgid "Stop the VM."
msgstr ""

#: ../../virtual_machines.rst:838
# 4d3222f75f4441acb3f7516e2d388648
msgid "Click the Edit button."
msgstr ""

#: ../../virtual_machines.rst:842
# 61e90315c538406a9c315c62f747cc2e
msgid "Click the Dynamically Scalable checkbox."
msgstr ""

#: ../../virtual_machines.rst:850
# 9aa7f5d09507405ea98a7e3a187f958b
msgid "Restart the VM."
msgstr ""

#: ../../virtual_machines.rst:853
# 73d1c7490e504d2281a6892402c02e81
msgid "Configuring Dynamic CPU and RAM Scaling"
msgstr ""

#: ../../virtual_machines.rst:855
# 05f20343444d4826bbcf7850a03ff73e
msgid "To configure this feature, use the following new global configuration variables:"
msgstr ""

#: ../../virtual_machines.rst:860
# 1aaa2fb09309444697b5b4bf9ef5ef75
msgid "enable.dynamic.scale.vm: Set to True to enable the feature. By default, the feature is turned off."
msgstr ""

#: ../../virtual_machines.rst:865
# 52efb56d95374359815b6efedb138880
msgid "scale.retry: How many times to attempt the scaling operation. Default = 2."
msgstr ""

#: ../../virtual_machines.rst:869
# 2ae2186e2b6e404dbd39ee8095a87bf4
msgid "How to Dynamically Scale CPU and RAM"
msgstr ""

#: ../../virtual_machines.rst:871
# 0e93a4355ab7478e98e7505e737337d1
msgid "To modify the CPU and/or RAM capacity of a virtual machine, you need to change the compute offering of the VM to a new compute offering that has the desired CPU and RAM values. You can use the same steps described above in `“Changing the Service Offering for a VM” <#changing-the-service-offering-for-a-vm>`_, but skip the step where you stop the virtual machine. Of course, you might have to create a new compute offering first."
msgstr ""

#: ../../virtual_machines.rst:879
# b101fbdc248247569dec5af8568168b6
msgid "When you submit a dynamic scaling request, the resources will be scaled up on the current host if possible. If the host does not have enough resources, the VM will be live migrated to another host in the same cluster. If there is no host in the cluster that can fulfill the requested level of CPU and RAM, the scaling operation will fail. The VM will continue to run as it was before."
msgstr ""

#: ../../virtual_machines.rst:887
# 1d09d0d96932426eaedf888c5d4bb7b3
msgid "Limitations"
msgstr ""

#: ../../virtual_machines.rst:891
# 8df5bd609d334564a90f30f51a4a07f1
msgid "You can not do dynamic scaling for system VMs on XenServer."
msgstr ""

#: ../../virtual_machines.rst:895
# 2f2a3e6456674e06ace3c43636415177
msgid "CloudStack will not check to be sure that the new CPU and RAM levels are compatible with the OS running on the VM."
msgstr ""

#: ../../virtual_machines.rst:900
# 492ccb959cfc432e88b64e8dd249b28c
msgid "When scaling memory or CPU for a Linux VM on VMware, you might need to run scripts in addition to the other steps mentioned above. For more information, see `Hot adding memory in Linux (1012764) <http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1012764>`_ in the VMware Knowledge Base."
msgstr ""

#: ../../virtual_machines.rst:908
# 715ff91daf224aeab90718b612d41d50
msgid "(VMware) If resources are not available on the current host, scaling up will fail on VMware because of a known issue where CloudStack and vCenter calculate the available capacity differently. For more information, see `https://issues.apache.org/jira/browse/CLOUDSTACK-1809 <https://issues.apache.org/jira/browse/CLOUDSTACK-1809>`_."
msgstr ""

#: ../../virtual_machines.rst:916
# f0f4ca2f349f499fadb1cc2a3d13b761
msgid "On VMs running Linux 64-bit and Windows 7 32-bit operating systems, if the VM is initially assigned a RAM of less than 3 GB, it can be dynamically scaled up to 3 GB, but not more. This is due to a known issue with these operating systems, which will freeze if an attempt is made to dynamically scale from less than 3 GB to more than 3 GB."
msgstr ""

#: ../../virtual_machines.rst:923
# e5f94051809f4fdc9b73c3c2a82fda21
msgid "Resetting the Virtual Machine Root Volume on Reboot"
msgstr ""

#: ../../virtual_machines.rst:925
# 48d80af594204278be829b174c5a4523
msgid "For secure environments, and to ensure that VM state is not persisted across reboots, you can reset the root disk. For more information, see `“Reset VM to New Root Disk on Reboot” <storage.html#reset-vm-to-new-root-disk-on-reboot>`_."
msgstr ""

#: ../../virtual_machines.rst:931
# aa4ca1c9e6f1450b872d7b19cb306a9d
msgid "Moving VMs Between Hosts (Manual Live Migration)"
msgstr ""

#: ../../virtual_machines.rst:933
# 991bc31743834bd285fd42664f467f3b
msgid "The CloudStack administrator can move a running VM from one host to another without interrupting service to users or going into maintenance mode. This is called manual live migration, and can be done under the following conditions:"
msgstr ""

#: ../../virtual_machines.rst:940
# 3155449d7c29414bb311284884f57a23
msgid "The root administrator is logged in. Domain admins and users can not perform manual live migration of VMs."
msgstr ""

#: ../../virtual_machines.rst:945
# ea6b697cd1214233b579d728a08a9398
msgid "The VM is running. Stopped VMs can not be live migrated."
msgstr ""

#: ../../virtual_machines.rst:949
# ef589ba17133433db3d1e4374fedb177
msgid "The destination host must have enough available capacity. If not, the VM will remain in the \"migrating\" state until memory becomes available."
msgstr ""

#: ../../virtual_machines.rst:955
# 70e5acb9366945f3a292924549f075c5
msgid "(KVM) The VM must not be using local disk storage. (On XenServer and VMware, VM live migration with local disk is enabled by CloudStack support for XenMotion and vMotion.)"
msgstr ""

#: ../../virtual_machines.rst:961
# ad1e58fdb03a4bda8f7cbe3509dc1b29
msgid "(KVM) The destination host must be in the same cluster as the original host. (On XenServer and VMware, VM live migration from one cluster to another is enabled by CloudStack support for XenMotion and vMotion.)"
msgstr ""

#: ../../virtual_machines.rst:966
# 3bbeb916fadc4d5485cc2311778dea39
msgid "To manually live migrate a virtual machine"
msgstr ""

#: ../../virtual_machines.rst:978
# cac7bb80e52140ffb9b2064aaf90a545
msgid "Choose the VM that you want to migrate."
msgstr ""

#: ../../virtual_machines.rst:982
# ad6a7c7fc2774af19be664773c62991f
msgid "Click the Migrate Instance button. |Migrateinstance.png|"
msgstr ""

#: ../../virtual_machines.rst:986
# f6a8c2c04d5a419ea87d0eb7c6aab2f9
msgid "From the list of suitable hosts, choose the one to which you want to move the VM."
msgstr ""

#: ../../virtual_machines.rst:990
# aa10e98e071f4ce6a979503514da6fc6
msgid "If the VM's storage has to be migrated along with the VM, this will be noted in the host list. CloudStack will take care of the storage migration for you."
msgstr ""

#: ../../virtual_machines.rst:997
# 2ee1776c823e444bb96036b1353934ff
msgid "Deleting VMs"
msgstr ""

#: ../../virtual_machines.rst:999
# 4506fdbbd39a4d90822765565d24819e
msgid "Users can delete their own virtual machines. A running virtual machine will be abruptly stopped before it is deleted. Administrators can delete any virtual machines."
msgstr ""

#: ../../virtual_machines.rst:1003
# 913edf18c98446f7add9e9b002dc571e
msgid "To delete a virtual machine:"
msgstr ""

#: ../../virtual_machines.rst:1015
# 4471e96b3042480887044b650cf5dfa7
msgid "Choose the VM that you want to delete."
msgstr ""

#: ../../virtual_machines.rst:1019
# 14c5b440483c444190fd3fc8d953c2a5
msgid "Click the Destroy Instance button. |Destroyinstance.png|"
msgstr ""

#: ../../virtual_machines.rst:1022
# 7739d729c35f4724a4c0492fbc8c1b97
msgid "Working with ISOs"
msgstr ""

#: ../../virtual_machines.rst:1024
# 037ea9c2997f4695a6eb7227eda501ca
msgid "CloudStack supports ISOs and their attachment to guest VMs. An ISO is a read-only file that has an ISO/CD-ROM style file system. Users can upload their own ISOs and mount them on their guest VMs."
msgstr ""

#: ../../virtual_machines.rst:1028
# bb915cb78ccb40fbb74f5c72bfc775f9
msgid "ISOs are uploaded based on a URL. HTTP is the supported protocol. Once the ISO is available via HTTP specify an upload URL such as http://my.web.server/filename.iso."
msgstr ""

#: ../../virtual_machines.rst:1032
# 49d1e81d8d2f431ead35a0681b93930e
msgid "ISOs may be public or private, like templates.ISOs are not hypervisor-specific. That is, a guest on vSphere can mount the exact same image that a guest on KVM can mount."
msgstr ""

#: ../../virtual_machines.rst:1036
# ec9f85158e634c70bb3289ba4354c53e
msgid "ISO images may be stored in the system and made available with a privacy level similar to templates. ISO images are classified as either bootable or not bootable. A bootable ISO image is one that contains an OS image. CloudStack allows a user to boot a guest VM off of an ISO image. Users can also attach ISO images to guest VMs. For example, this enables installing PV drivers into Windows. ISO images are not hypervisor-specific."
msgstr ""

#: ../../virtual_machines.rst:1045
# 66d6d4e68aaa46fc8a38ea3d9e9eff72
msgid "Adding an ISO"
msgstr ""

#: ../../virtual_machines.rst:1047
# 4d9f89344dbd49cf809056b015c893e9
msgid "To make additional operating system or other software available for use with guest VMs, you can add an ISO. The ISO is typically thought of as an operating system image, but you can also add ISOs for other types of software, such as desktop applications that you want to be installed as part of a template."
msgstr ""

#: ../../virtual_machines.rst:1055
# 9498811c36fa4b7081260060ea17df89
msgid "Log in to the CloudStack UI as an administrator or end user."
msgstr ""

#: ../../virtual_machines.rst:1059
# 9c94cd61bf874dde87586c83b2468101
msgid "In the left navigation bar, click Templates."
msgstr ""

#: ../../virtual_machines.rst:1063
# a5071eb73fa449c18ce96de2c342e45d
msgid "In Select View, choose ISOs."
msgstr ""

#: ../../virtual_machines.rst:1067
# e19433ec2d144a92bbf9c55ad2bc3484
msgid "Click Add ISO."
msgstr ""

#: ../../virtual_machines.rst:1071
# b760a614085c4b59bb13262b7892cde4
msgid "In the Add ISO screen, provide the following:"
msgstr ""

#: ../../virtual_machines.rst:1075
# 9fdde4dd08374f0793251a5518e975be
msgid "**Name**: Short name for the ISO image. For example, CentOS 6.2 64-bit."
msgstr ""

#: ../../virtual_machines.rst:1080
# 057c511f14834d53b851241e6e307b66
msgid "**Description**: Display test for the ISO image. For example, CentOS 6.2 64-bit."
msgstr ""

#: ../../virtual_machines.rst:1085
# 45877549dabb466b9cf1d79d86e902f3
msgid "**URL**: The URL that hosts the ISO image. The Management Server must be able to access this location via HTTP. If needed you can place the ISO image directly on the Management Server"
msgstr ""

#: ../../virtual_machines.rst:1091
# 68c8d3975adf4027a8cbceacace184c5
msgid "**Zone**: Choose the zone where you want the ISO to be available, or All Zones to make it available throughout CloudStack."
msgstr ""

#: ../../virtual_machines.rst:1096
# 0159cee8f9ad46aab66d2a0b15a0026f
msgid "**Bootable**: Whether or not a guest could boot off this ISO image. For example, a CentOS ISO is bootable, a Microsoft Office ISO is not bootable."
msgstr ""

#: ../../virtual_machines.rst:1102
# 20cb0c8a4e1d4ffd8279d8587ac831d2
msgid "**OS Type**: This helps CloudStack and the hypervisor perform certain operations and make assumptions that improve the performance of the guest. Select one of the following."
msgstr ""

#: ../../virtual_machines.rst:1108
# 5ccda673858b485d9d029499d3c6e0db
msgid "If the operating system of your desired ISO image is listed, choose it."
msgstr ""

#: ../../virtual_machines.rst:1113
# 2ab6ca22329e4c3e877533c892467967
msgid "If the OS Type of the ISO is not listed or if the ISO is not bootable, choose Other."
msgstr ""

#: ../../virtual_machines.rst:1118
# 9be1c439f3ce4ab9a41d7137880e76cd
msgid "(XenServer only) If you want to boot from this ISO in PV mode, choose Other PV (32-bit) or Other PV (64-bit)"
msgstr ""

#: ../../virtual_machines.rst:1123
# b50992f8bb54434387b26839fd05e1a2
msgid "(KVM only) If you choose an OS that is PV-enabled, the VMs created from this ISO will have a SCSI (virtio) root disk. If the OS is not PV-enabled, the VMs will have an IDE root disk. The PV-enabled types are:"
msgstr ""

#: ../../virtual_machines.rst:1128
# aad0ef1396ee4a6f9bc531d842d53100
msgid "Fedora 13"
msgstr ""

#: ../../virtual_machines.rst:1130
# 59079d1f59324bbe8b1abcea8603f2cc
msgid "Fedora 12"
msgstr ""

#: ../../virtual_machines.rst:1132
# b8b262bd1513438d840f6124407681e2
msgid "Fedora 11"
msgstr ""

#: ../../virtual_machines.rst:1134
# b4b9f21ef32a4ef6a55ca72d8ecb6e21
msgid "Fedora 10"
msgstr ""

#: ../../virtual_machines.rst:1136
# 63098f620c9846d0bb57b96bce1570f7
msgid "Fedora 9"
msgstr ""

#: ../../virtual_machines.rst:1138
# 23123eb72cc94f54a8c080e0d7e3f9b1
msgid "Other PV"
msgstr ""

#: ../../virtual_machines.rst:1140
# e2502905c8ad4a5082eaf77c12a663a2
msgid "Debian GNU/Linux"
msgstr ""

#: ../../virtual_machines.rst:1142
# 3e223c0e18b546c6aa44380d75dbcd75
msgid "CentOS 5.3"
msgstr ""

#: ../../virtual_machines.rst:1144
# 22c90e96d87b47b9b52f5d36afbb4bca
msgid "CentOS 5.4"
msgstr ""

#: ../../virtual_machines.rst:1146
# 08857787cb804700851faf1944428e9a
msgid "CentOS 5.5"
msgstr ""

#: ../../virtual_machines.rst:1148
# 3d0c5c0b25ac43dfb9c6f424494416c5
msgid "Red Hat Enterprise Linux 5.3"
msgstr ""

#: ../../virtual_machines.rst:1150
# 192d89c4588a46089607de0c7d8eb8d1
msgid "Red Hat Enterprise Linux 5.4"
msgstr ""

#: ../../virtual_machines.rst:1152
# 577c9a33d98b4fc4a4a121cd9f026fd1
msgid "Red Hat Enterprise Linux 5.5"
msgstr ""

#: ../../virtual_machines.rst:1154
# 99aa5f6d829c492ca635ff7a54373fd8
msgid "Red Hat Enterprise Linux 6"
msgstr ""

#: ../../virtual_machines.rst:1157
# b33e5a4f06cf443b9506e80db9f2e83d
msgid "It is not recommended to choose an older version of the OS than the version in the image. For example, choosing CentOS 5.4 to support a CentOS 6.2 image will usually not work. In these cases, choose Other."
msgstr ""

#: ../../virtual_machines.rst:1161
# e4e2e905b80442298bc0b64ce88ecab1
msgid "**Extractable**: Choose Yes if the ISO should be available for extraction."
msgstr ""

#: ../../virtual_machines.rst:1166
# a2f23bd50ec54f93ba29dffc1fb73308
msgid "**Public**: Choose Yes if this ISO should be available to other users."
msgstr ""

#: ../../virtual_machines.rst:1171
# a045b92e96314a2b9ca966ae7d9e69e7
msgid "**Featured**: Choose Yes if you would like this ISO to be more prominent for users to select. The ISO will appear in the Featured ISOs list. Only an administrator can make an ISO Featured."
msgstr ""

#: ../../virtual_machines.rst:1179
# f6a3a2db613242338786ae4594017ed0
msgid "The Management Server will download the ISO. Depending on the size of the ISO, this may take a long time. The ISO status column will display Ready once it has been successfully downloaded into secondary storage. Clicking Refresh updates the download percentage."
msgstr ""

#: ../../virtual_machines.rst:1186
# 0fed1d5c6f1043ffb6867a5b24e6f76d
msgid "**Important**: Wait for the ISO to finish downloading. If you move on to the next task and try to use the ISO right away, it will appear to fail. The entire ISO must be available before CloudStack can work with it."
msgstr ""

#: ../../virtual_machines.rst:1192
# 75e7c4822f2949598aa3a5e8cfa3c75a
msgid "Attaching an ISO to a VM"
msgstr ""

#: ../../virtual_machines.rst:1200
# c49011305c6040abac9c4c10904564b0
msgid "Choose the virtual machine you want to work with."
msgstr ""

#: ../../virtual_machines.rst:1204
# a3b01615c42b489a9c2ca0f920b92cb1
msgid "Click the Attach ISO button. |iso.png|"
msgstr ""

#: ../../virtual_machines.rst:1208
# 02bc55c3634a43e9947613722f71ada2
msgid "In the Attach ISO dialog box, select the desired ISO."
msgstr ""

#: ../../virtual_machines.rst:1215
# 071721241f504f06bfb0b36125fc3870
msgid "Changing a VM's Base Image"
msgstr ""

#: ../../virtual_machines.rst:1217
# 0d3190522cde471aa0ebe72afd3e6cf8
msgid "Every VM is created from a base image, which is a template or ISO which has been created and stored in CloudStack. Both cloud administrators and end users can create and modify templates, ISOs, and VMs."
msgstr ""

#: ../../virtual_machines.rst:1221
# de60998312a04130be852dba54b0e5d8
msgid "In CloudStack, you can change an existing VM's base image from one template to another, or from one ISO to another. (You can not change from an ISO to a template, or from a template to an ISO)."
msgstr ""

#: ../../virtual_machines.rst:1225
# da938830337643e9992dbf05c3792f8c
msgid "For example, suppose there is a template based on a particular operating system, and the OS vendor releases a software patch. The administrator or user naturally wants to apply the patch and then make sure existing VMs start using it. Whether a software update is involved or not, it's also possible to simply switch a VM from its current template to any other desired template."
msgstr ""

#: ../../virtual_machines.rst:1232
# 8218e4d0e098440f88209b1124c5ee3c
msgid "To change a VM's base image, call the restoreVirtualMachine API command and pass in the virtual machine ID and a new template ID. The template ID parameter may refer to either a template or an ISO, depending on which type of base image the VM was already using (it must match the previous type of image). When this call occurs, the VM's root disk is first destroyed, then a new root disk is created from the source designated in the template ID parameter. The new root disk is attached to the VM, and now the VM is based on the new template."
msgstr ""

#: ../../virtual_machines.rst:1241
# 9f9d3ce3a34c4a55ba84e57c2537163e
msgid "You can also omit the template ID parameter from the restoreVirtualMachine call. In this case, the VM's root disk is destroyed and recreated, but from the same template or ISO that was already in use by the VM."
msgstr ""