Bug 119077 - Xen module in YaST should offer to install Xen packages if Xen has not already been installed
Summary: Xen module in YaST should offer to install Xen packages if Xen has not alread...
Status: RESOLVED DUPLICATE of bug 117215
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Xen (show other bugs)
Version: RC 4
Hardware: Other All
: P5 - None : Normal
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-27 18:48 UTC by Ted Haeger
Modified: 2005-09-28 10:03 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
This is the error window mentioned. (10.44 KB, image/png)
2005-09-27 18:49 UTC, Ted Haeger 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ted Haeger 2005-09-27 18:48:35 UTC 
When you open YaST, the first screen you see has "Virtual Machine Installation
(XEN)" on it. If you click it, the error message is very unfriendly"

"For installing a XEN virtual machine the system must be running XEN Linux
Kernel. XEN installation cannot be started."

The Xen module in YaST really should offer to install Xen packages if Xen has
not already been installed. Why not have a button option "Install Xen packages
now (requires reboot)" that shells out to the YaST "Software Management" module,
with the correct packages for Xen pre-selected?

P.S. Is the name Xen or XEN? The University of Cambridge home page for the
project has it "Xen."

P.S.S. This is incorrect grammar and mechanics: "For installing a XEN virtual
machine the system must be running XEN Linux Kernel. XEN installation cannot be
started." It should read: "For installing a XEN virtual machine, the system must
be running the XEN Linux Kernel. XEN installation cannot be started."
Comment 1 Ted Haeger 2005-09-27 18:49:32 UTC 
Created attachment 50968 [details]
This is the error window mentioned.
Comment 2 Martin Lasarsch 2005-09-28 10:03:06 UTC 

*** This bug has been marked as a duplicate of 117215 ***