Bug 209580

Summary: xen guest couldn't boot up on VMware server
Product: [Fedora] Fedora Reporter: NOKUBI Takatsugu <knok-e>
Component: kernel-xenAssignee: Xen Maintainance List <xen-maint>
Status: CLOSED CANTFIX QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: bstein
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-10-06 21:21:04 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
All of the guest's dmesg. none

Description NOKUBI Takatsugu 2006-10-06 06:28:08 UTC 
Description of problem:
When I created a FC6-devel guest with Virtual Machine Manager,
the guest kernel couldn't boot up.

Version-Release number of selected component (if applicable):
kernel-xen-2.6.18-1.2741.fc6

How reproducible:


Steps to Reproduce:
1.Install FC6-devel in VMware server
2.Run the Virtual Machine Manager
3.Create a para-virtual machine
4.The kernel is not boot up completely.
  
Actual results:
Stopped with the message:
"Write protecting the kernel read-only data: 370k"

Expected results:
Boot up completely.

Additional info:
Installed on VMware server 1.0.1 for Linux.
I also tried to install XenEnterprise 3.0.0 in VMware server for Windows,
it works good.
Comment 1 NOKUBI Takatsugu 2006-10-06 06:28:08 UTC 
Created attachment 137897 [details]
All of the guest's dmesg.
Comment 2 Rik van Riel 2006-10-06 21:21:04 UTC 
The Xen hypervisor uses the same virtual address range as the VMware hypervisor.

If VMware cannot deal with that, you could ask them to enhance their hypervisor
to support Xen or check a newer version of VMware.