FS#37005 - [seabios] seabios 1.7.3.1-1 breaks booting Windows on QEMU

Attached to Project: Arch Linux
Opened by Sebastián Peyrott (Pse) - Saturday, 21 September 2013, 02:13 GMT
Last edited by Tom Gundersen (tomegun) - Sunday, 22 September 2013, 10:31 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Eric Belanger (Snowman)
Tom Gundersen (tomegun)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 4
Private No

Details

Description:
Since seabios 1.7.3.1-1, qemu causes BSODs in all versions of Windows I could test (Windows 8 preview, and Windows XP SP3). Reverting to seabios 1.7.2-1 fixes the problem.

Additional info:
Using KVM on Intel, QEMU 1.5.2-1
Seabios 1.7.2-1 seems to work fine.
I found this, may be relevant: http://lists.gnu.org/archive/html/qemu-devel/2013-07/msg01438.html

Steps to reproduce:
1. Update to latest seabios release (1.7.3.1-1).
2. Try to run Windows VM in QEMU.
3. BSOD.
This task depends upon

Closed by  Tom Gundersen (tomegun)
Sunday, 22 September 2013, 10:31 GMT
Reason for closing:  Fixed
Comment by Tobias Powalowski (tpowa) - Saturday, 21 September 2013, 07:52 GMT
QEMU cdrom is also broken with latest seabios.
Comment by Simon Hollingshead (elpasi) - Saturday, 21 September 2013, 09:39 GMT
Linux guests seem to be doing something similar as well.

ata_piix and pata_acpi state "device not available (can't reserve [io 0xaddr-0xaddr])" and then whatever the root mountpoint is, whether a drive specified by UUID or even the Arch ISO, does not show up in the specified timeout, leaving it to fall back to the interactive prompt.
Comment by Dan Doel (dolio) - Saturday, 21 September 2013, 17:02 GMT
Came here to point to the above mailing list thread, too.

The problem, presumably, is that /usr/share/qemu/acpi-dsdt.aml is owned by the qemu package, which hasn't been updated. But seabios 1.7.3 requires a different/newer version of the file.
Comment by Roman Golovin (dantix) - Saturday, 21 September 2013, 17:25 GMT
Confirming this, solved by downgrading by now
Comment by Sebastián Peyrott (Pse) - Sunday, 22 September 2013, 03:52 GMT
With qemu-1.5.3-1 and seabios-1.7.3.1-2 (both now in stable) everything appears to be fine again. Good job, guys.

Loading...