Focus sentinelFocus sentinel
Something went wrong
Focus sentinelFocus sentinel
Everything you love about POWER with the benefits of Hybrid Cloud.
Pay-as-you-use billing make it easy to adjust workloads with flexible compute capacity.
Why Power Virtual Server?
Deploy workloads in the best environment for each application and manage them through a consistent experience, making hybrid cloud operations more efficient.
IBM data centers
Provision in one of or many data centers worldwide without the need to up-skill in specialized technologies.
Client location
Keep data localized in your premises with remote geo micro data centers, driven by local regulations, connected through IBM Cloud.
Consume managed infrastructure with a pricing plan that best fits your needs and reduces operational costs.
Metered usage
(available for IBM data centers or Client locations)
Pay for allocated resources at a metered hourly rate, with no upfront costs. Scale up and scale down resources on-demand -- compute, memory, storage, and operating system licenses. View rates
Subscription
(available for Client locations only)
Pay a flat rate for 100% of the infrastructure delivered to your data center, without metered costs. Only supported for SAP workloads and does not include AIX or IBM i workloads.
Committed use savings plans
Leverage up to 45% savings with 3-year committed use, or 30% savings with 1-year committed use. Applicable with metered usage or subscription models.
Getting started
1. Create a workspace
A workspace is a free working environment that acts as a folder for all Power Virtual Server resources at a specific geographic region, including compute, networking and storage resources.
1. Create a workspace2. Create a virtual server instance
Deploy your first virtual server instance with the storage and networking needed.
2. Create a virtual server instanceFollow the steps below to rapidly deploy Power virtual server instances (LPARs) to host your mission critical workloads.
1. Create a workspace
A workspace is a free working environment that acts as a folder for all Power Virtual Server resources at a specific geographic region, including compute, networking and storage resources.
2. Create a subnet
In a new workspace, the first priority is to create a private subnet from which an IP address will be assigned to the LPAR.
Within the PowerVS workspace, a user can specify their own private subnets. It is a Bring your own IP (BYOIP) environment for private IPs, with the caveat that you must be careful not to conflict with any environment you intend to integrate the Power LPAR with, including either on-premises or IBM Cloud Classic integration. GRE Tunneling can be used if a subnet’s range conflicts with existing classical infrastructure.
Explore diagrams to understand the Power Systems™ Virtual Server network architecture.
3. Create an SSH key
Set up one or more SSH keys for root login. SSH keys allow you to securely log in to a VM.
4. Import a boot image (optional)
The OS can be an IBM-supplied OS (AIX, IBM i, or Linux) or a customer-supplied image (AIX or IBM i), or even a custom Linux image.
In order to import custom VM images, the VM must already be zipped (in OVA format) and uploaded to IBM Cloud Object Storage.
5. Create a virtual server instance
Start deploying your workloads by provisioning a virtual server instance with the cores, memory, and storage required by your environment.
6. Access your virtual server instance
Once the virtual server instance is in a “Ready” state after step 5, log in using the console to the VM (access in UI or through CLI) or over the network using SSH.
7. Connect a PowerVS service instance (optional)
For PowerVS workspaces that leverage the upgraded networking technology, go to IBM Transit Gateway to configure virtual connections and connect to any of the following endpoints without virtual routers:
- Other PowerVS workspaces
- Remote Power sites
- Classic infrastructures
- VPC infrastructures
To know if a PowerVS workspace can leverage the upgraded technology on IBM Transit Gateway, go to the workspace and check the navigation for a Cloud connections page. If there is none, the workspace leverages IBM Transit Gateway. Otherwise, virtual connections must be configured with Cloud connections on the workspace.
Data center capabilities
View and compare capabilities available across data centers.
Data center
Location
Satellite location determined upon ordering
Machine types
- Determined upon ordering infrastructure
GRS replication site pair(s)
Go to docs
Go to docs
Asynchronously replicates to
- Determined upon ordering infrastructure
Networking
Connect to IBM Cloud
Use Transit Gateway to connect to services within IBM Cloud, like VPC, VMware, Classic, etc.
Connect to on-premises environments
Use VPC VPN connections to connect to workloads running in your data center.
View the documentation
Frequently asked questions
- Power Virtual Server is an IaaS offering that allows you to deploy your current IBM i, AIX and Linux workloads in a hybrid cloud environment, without refactoring. Some examples include SAP, SAP HANA, and Oracle, though other home-grown applications are supported too.
- - Power E1080 - Power E1050 - Power S1022 - Power E980 - Power S922 Read more
- Go to IBM Transit Gateway to configure virtual connections and connect to any of the following endpoints across local and global regions and without virtual routers: - Other PowerVS workspaces - Remote Power sites - Classic infrastructures - VPC infrastructures If using Cloud connections on PowerVS, create a new connection and enable IBM Transit Gateway. Read more
- Configure the on-prem environment as a virtual connection in IBM Transit Gateway. Or create a VPN connection if the workspace uses Cloud connections or DL. Read more
- You can bring your own customized AIX or IBM i operating system (OS) image to deploy within Power Virtual Server. Simply store your image on Cloud Object Storage (COS), point the Power Virtual Server console to the image, and deploy the Virtual Server instance. Read more
- Uncapped shared processors are shared among other clients, while capped shared processors do not expand resources beyond those that are requested, and are used mostly for licensing. Dedicated resources are allocated for a specific client, usually for for specific third-party considerations. Performance on PowerVS is the same as on-prem. Read more
- The license for the AIX and IBM i operating systems is included in the overall cost for the workspace. You cannot use an existing license that you already purchased.