# Release Notes

# WebLogic Virtual Edition Release Notes

This document includes information about the following topics:

- What’s New in WebLogic Server 10.0 MP1 Virtual Edition v1.2
- Known and Resolved Issues

## What’s New in WebLogic Server 10.0 MP1 Virtual Edition v1.2

WebLogic Server 10.0 MP1 Virtual Edition v1.2 (WLS-VE) includes LiquidVM 1.2, which provides significant performance improvements over earlier releases of LiquidVM. This release also includes the following changes:

- New WLS-VE Packaging
- Physical-to-Virtual Domain Conversion Utility

### New WLS-VE Packaging

This version of WLS-VE has some packaging differences compared to previous releases of WLS-VE 9.2:

- Works with existing WebLogic Server 10.0 MP1 domains.
- Unlike previous releases of WLS-VE 9.2, WLS-VE 10 does not include WebLogic Server or the WebLogic Domain Configuration Wizard to create new virtual domains. Instead, WLS-VE introduces a new tool to help convert physical WLS 10.0 MP1-based domains into virtual domains. See the Physical-to-Virtual Domain Conversion Utility.
- WLS-VE 10 v1.2 is available only as a distribution archive and does not include a BEA product installer mechanism. See Creating Virtual WebLogic Domains in the WLS-VE Configuration and User Guide.

### Physical-to-Virtual Domain Conversion Utility

The Physical-to-Virtual (P2V) Domain Conversion utility enables you to convert physical WLS 10.0 MP1-based domains hosted on traditional OSes into virtual domains that can be hosted on LiquidVMs in hypervisor environments, as follows:

- Stages virtual machines on the ESX server for selected servers in a domain, and makes sure that the domain, patches, and connection information is available for the new virtual machines.
- Generates start scripts in the domain directory on the launcher machine (the host on which the tool is run). These scripts are used to complete the configuration and start the newly generated virtual machines.

For more information, see Creating Virtual WebLogic Domains in the WLS-VE Configuration and User Guide.

## Known and Resolved Issues

This following table describes problems that have been identified in this release of WLS-VE. Where applicable, a Change Request Number is specified for the problem. These Change Request Numbers enable BEA and users to monitor the status of issues while solutions are being developed. Entries include a description of the problem, and a workaround or solution where appropriate.

Change Request Number | Description and Workaround or Solution | Found In | Fixed In
--- | --- | --- | ---
CR316773 | Using Ctrl-C to shut down a WLS-VE server instance in the Virtual Infrastructure Client console window can cause an error: `Error connecting: VMX Connection handshake failed for mks of /vmfs/volumes/<volume-id-string>/<WLS-VE instance name>/<WLS-VE instance name>.vmx` `Do you want to try again?` This error is harmless and can be ignored. | 9.2 v1.0 |
CR322659 | When you shut down an Administration or Managed Server using the WLS Administration Console, the following message is displayed: `The administration server is shutting down, and the console is no longer available. You will have to manually start the Administration Server using the node manager or a command line to continue administering this domain.` You cannot use Node Manager with WLS-VE. Instead, you should restart the servers by pressing Power On in the Virtual Infrastructure Client or by executing the start scripts. For more information about starting servers, see Starting and Stopping WLS-VE in the WLS-VE Configuration and User Guide. | 9.2 v1.0 |
CR357340 | LiquidVM launcher does not recognize spaces in pathnames. Workaround: Do not use pathnames that contain spaces in the server start scripts, such as `C:\Documents and Settings`. | 9.2 v1.1 |
CR368020 | WLS 10.0 MP1 VE v1.2 defaults to the Java muxer (`JavaSocketMuxer`) instead of the native muxer (`EpollSocketMuxer`). However, the start scripts generated by the P2V utility pass the appropriate command line-argument to cause WLS-VE to use the native muxer. Workaround: If you are using custom start scripts for WLS-VE, you can enable the EPoll native muxer by passing the following command-line argument: `-l posixOSName=linux` | 10.0 v1.2 |