I'm building/booting a Xen DomU using an Autoyast template.
Under opensuse v11.0 (as Dom0 & DomU) all's well. Under v11.1, I see
a bunch of 'new', EDD-related messsages @ console -- & I'm not clear
if they're just new diagnostic, or a new problem:
...
>>> openSUSE installation program v3.3.22 (c) 1996-2008 SUSE Linux
Products GmbH <<<
Starting udev... udevd version 128 started
rtc_cmos rtc_cmos: rtc core: registered rtc_cmos as rtc0
netfront: Initialising virtual ethernet driver.
xen-vbd: registered block device major 202
blkfront: xvda: barriers enabled
xvda: unknown partition table
ok
GGLoading basic drivers...Uniform Multi-Platform E-IDE driver
SCSI subsystem initialized
st: Version 20080504, fixed bufsize 32768, s/g segs 256
BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
EDD information not available.
NET: Registered protocol family 17
BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
EDD information not available.
BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
EDD information not available.
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
EDD information not available.
BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
EDD information not available.
BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
EDD information not available.
BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
EDD information not available.
BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
EDD information not available.
BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
EDD information not available.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
EDD information not available.
BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
EDD information not available.
BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
EDD information not available.
BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
EDD information not available.
BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
EDD information not available.
BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
EDD information not available.
BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
EDD information not available.
BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
EDD information not available.
loop: module loaded
BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
EDD information not available.
BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
EDD information not available.
BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
EDD information not available.
BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
EDD information not available.
BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
EDD information not available.
BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
EDD information not available.
BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
EDD information not available.
BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
EDD information not available.
BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
EDD information not available.
BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
EDD information not available.
BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
EDD information not available.
BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
EDD information not available.
BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
EDD information not available.
BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
EDD information not available.
ok
BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
EDD information not available.
Starting hardware detection... ok
(If a driver is not working for you, try booting with
brokenmodules=driver_name.)
Xen Virtual Storage 0
...
My autoyast template starts with,
<?xml version="1.0"?>
<!DOCTYPE profile>
<profile xmlns="http://www.suse.com/1.0/yast2ns"
xmlns:config="http://www.suse.com/1.0/configns">