http://bugzilla.novell.com/show_bug.cgi?id=542707
User frank.arnold@amd.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=542707#c12
Frank Arnold changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |frank.arnold@amd.com
--- Comment #12 from Frank Arnold 2009-10-19 10:25:01 MDT ---
Something is seriously wrong here. Just a quick rundown:
Guest OS Bitness Result
Fedora 11 32 Guest booted up properly
Windows 2003 SP2 32 Crashed during boot, no blue screen visible
MS Server 2008 32 Blue Screen 'HAL_INITIALIZATION_FAILED'
MS Vista 64 Blue Screen 'HAL_INITIALIZATION_FAILED'
openSUSE 11.1 32 Buffer I/O error, dev sda, sector 0
openSUSE 11.2 M8 32 Guest booted up properly
RHEL 5.4 SMP 32 Guest got stuck during boot
RHEL 5.4 SMP 64 Guest booted up properly
SLES 10 SP3 SMP 32 Guest got stuck during boot
SLES 10 SP3 SMP 64 Guest got stuck during boot
SLES 11 32 Guest booted up properly
Everything was done on an AMD Toonie 1, equipped with 2x Shanghai and 16 GB of
RAM. You can verify it on approximately the same hardware, because you got some
of those from us. All guest images are pre-installed and used for upstream
testing of Xen and KVM.
The Xen packages are exactly the ones from openSUSE-DVD-Build0334-x86_64.iso
(RC1). We don't see such issues with the upstream xen-3.4-testing tree.
Guest configuration template:
device_model = "/usr/lib64/xen/bin/qemu-dm"
kernel = "/usr/lib/xen/boot/hvmloader"
builder = "hvm"
vif = [ "mac=52:54:00:0F:20:01,bridge=xenbr0" ]
vnc = 1
vnclisten = "0.0.0.0"
vncpasswd = ""
serial = "file:/tmp/guest1.fifo"
monitor = 1
usb = 1
usbdevice = "tablet"
name = "001-boottest"
disk = [ "tap:qcow:/xen/images/suse_sles10_sp3_64b_smp_qcow.img,hda,w",
"file:/xen/images/001-boottest.img,hdb,w" ]
boot = "c"
acpi = 1
apic = 1
pae = 1
timer_mode = 2
hpet = 0
shadow_memory = 37
memory = 3840
vcpus = 3
hap = 1
on_crash = "preserve"
on_reboot = "preserve"
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.