XEN Fully Virtual Machine (FVM) will not boot after a change to the vm's memory assignment
This document (7001252) is provided subject to the disclaimer at the end of this document.
Environment
SUSE Linux Enterprise Server 10 Service Pack 2
Situation
Changes:
Applied latest updates to XEN (versions 3.2.0_16718_16-0.3)
Made a virtual memory change to a virtual machine ( vm )
After applying the latest updates to XEN for SLES 10 SP2, a fully virtualized (FV) will not boot after making a memory assignment change.
Applied latest updates to XEN (versions 3.2.0_16718_16-0.3)
Made a virtual memory change to a virtual machine ( vm )
After applying the latest updates to XEN for SLES 10 SP2, a fully virtualized (FV) will not boot after making a memory assignment change.
Resolution
Fix was posted to the channel in November of 2008. Update to current xen rpm to resolve this issue.
Additional Information
This issue is only specific to a 64-bit SLES 10 SP2 environment. The problem was introduced with the XEN updates to SLES 10 SP2; Specifically, the xen hypervisor (xen-3.2.0_16718_16-0.3.x86_64.rpm). A kernel back-rev is not required. Back-reving only xen-3.2.0_16718_16-0.3.x86_64.rpm is not sufficient.
Disclaimer
This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:7001252
- Creation Date: 29-Aug-2008
- Modified Date:14-Mar-2021
-
- SUSE Linux Enterprise Server
For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com
