https://bugzilla.novell.com/show_bug.cgi?id=463406 Summary: EDD info incorrrectly(?) sought in Xen DomU bootup Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Xen AssignedTo: cgriffin@novell.com ReportedBy: pgnet.trash@gmail.com QAContact: qa@suse.de CC: jbeulich@novell.com Found By: Customer 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. 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"> <module>edd</module> <bootloader> grub <module>xenblk</module> <module>xennet</module> <module>processor</module> ... Something's changed from v11.0 -> v11.1. According to, "[Xen-merge] [PATCH] disable EDD config option" (JBeulich) http://lists.xensource.com/archives/html/xen-merge/2005-12/msg00060.html "Since there is no way for the kernel to obtain this information, the consuming code should be disabled." where the referenced patch, --- 2005-12-16.orig/drivers/firmware/Kconfig 2005-12-02 09:27:45.000000000 +0100 +++ 2005-12-16/drivers/firmware/Kconfig 2005-12-22 14:31:33.000000000 +0100 @@ -8,7 +8,7 @@ menu "Firmware Drivers" config EDD tristate "BIOS Enhanced Disk Drive calls determine boot disk (EXPERIMENTAL)" depends on EXPERIMENTAL - depends on !IA64 + depends on !IA64 && !XEN help Say Y or M here if you want to enable BIOS Enhanced Disk Drive Services real mode BIOS calls to determine which disk Checking in Opensuse 11.1's, "/usr/src/linux-2.6.27.7-9/drivers/firmware/Kconfig" I see, ... config EDD tristate "BIOS Enhanced Disk Drive calls determine boot disk" depends on !IA64 ... I.e., that "&& !XEN" is missing. I'm not clear as to whether this is the cause of these EDD messages or not ... or if it's a problem, or just very 'noisy' reporting. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.