Bug 117711 - Yast (XEN) creates wrong config entries
Summary: Yast (XEN) creates wrong config entries
Status: RESOLVED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Installation (show other bugs)
Version: RC 4
Hardware: x86-64 All
: P5 - None : Normal
Target Milestone: ---
Assignee: Ladislav Slezák
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-19 05:23 UTC by Wilken Gottwalt
Modified: 2005-09-27 10:54 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Wilken Gottwalt 2005-09-19 05:23:06 UTC
If you create a sparse image file and try to run the new domain for installing
into this image. The domain fails to run, it hangs after a while:

Xen virtual console successfully installed as tty1
Event-channel device installed.
Neither TPM-BE Domain nor INIT domain!
xen_blk: Initialising virtual block device driver
Registering block device major 3
 hda:

The reason for this is a wrong driver in the line:

disk = [ 'file:/var/lib/xen/images/dom2/hda,hda,w' ]

To get this work a block device emulation must be activated. Every time you use
images as filesystems, you must inlcude an "ioemu" into this line. It should
look like this:

disk = [ 'file:/var/lib/xen/images/dom2/hda,ioemu:hda,w' ]
Comment 1 Ladislav Slezák 2005-09-27 10:54:09 UTC
Fixed in yast2-vm-2.13.0