Description of problem: Windows guests (at least Windows Server 2008 with updates) fail to boot properly at all, will reboot-fail infinitely if left alone. Version-Release number of selected component (if applicable): seabios-bin-0.5.1-3.fc13.noarch How reproducible: 100% with current version Steps to Reproduce: 1. Install update 2. Boot Windows guest Actual results: Blue screen (reboots to fast to capture error number) Expected results: Successful boot Additional info: temporary fix : yum downgrade seabios-bin
Created attachment 434502 [details] SeaBios Windows blue screen STOP: 0x0000007B (0x80699BB0, 0XC0000034, 0x00000000, 0x00000000)
Is this using virtio-win drivers? If so which ones?
Yes, this is with virtio-win: netkvm.sys 6.0.209.605 viostor.sys 5.00 built by: WinDDk
What version of seabios-bin is going to be in F14 ?
I would like to know what's up with this bug almost 5 months later. I can't really upgrade to Fedora 14 without knowing if virtualization, and my guest will work -- this is my only Windows machine of any kind and I need it from time to time.
seabios in f14 is version 0.6.0-1 That same version was pushed to f13 as an update on 2010-08-24. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Thank you. I had no idea that there was a new version. I wish there was some better communication in Bugzilla. I thought there was a bot that notified of updates to the package the bug was filed against.
only if the packager tags the update as fixing the bug in question. the update system can't magically determine whether an update fixes a particular bug, the packager has to provide that information. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers