On 05/02/2014 3:51 pm, Andre Goree wrote:
On 05/02/2014 3:42 pm, Andre Goree wrote:
On 05/02/2014 2:18 pm, Juergen Lock wrote:
In article <201405021800.s42i0tie094...@enceladus10.kn-bremen.de> you write:
In article <f946e633356b1161c0d43217f59893b9-62z4zxnhd7cstnjn9+b...@public.gmane.org> you write:
I think you have hit this issue for which the workaround is a patch
to seabios:

        https://bugs.debian.org/cgi-bin/bugreport.cgi?bug

Hm for some reason that link got truncated, try this one:

        https://bugs.debian.org/737142


        Juergen
_______________________________________________
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to
"freebsd-virtualization-unsubscr...@freebsd.org"

Lol, yeah, I was gonna say...but thanks!  Not sure if I'm into
implementing a patch vs. finding a way around this, and I'm wondering
why it reared it's head after an update to libvirt & qemu vs. earlier
in my testing -- makes me think it may be an unrelated, albeit similar
bug.  Thanks again Juergen.

Btw, from the link you posted:

"From: Michael Tokarev <m...@tls.msk.ru>
To: 737142-cl...@bugs.debian.org
Subject: Bug#737142: fixed in seabios 1.7.4-4
Source: seabios
Source-Version: 1.7.4-4

We believe that the bug you reported is fixed in the latest version of
seabios, which is due to be installed in the Debian FTP archive."

and on my host server having the issue:
"# dpkg -l |grep seabio
ii  seabios                          1.7.4-4~cloud0
         Legacy BIOS implementation"

I'll try to determine which version of seabios I had running initially
before the issue, however from what I can tell, an upgrade to the
version that _should_ have fixed this appears be what caused my issue
in the first place, heh.

Oddly enough, after downgrading seabios to version 1.7.3, I'm able to boot FreeBSD on the Ubuntu hosts without issue. I downgraded like so:

apt-get install seabios=1.7.3-1ubuntu0.1~cloud0

No other packages (namely, libvirt/qemu/etc.) were downgraded as a result and I do not see any dependency issues, so it looks like this will be the workaround for now. I suppose I should make my situation know in that bug report, eh?

Thanks again Juergen for pointing me in the right direction!

--
Andre Goree
-=-=-=-=-=-
Email     - andre at drenet.net
Website   - http://www.drenet.net
PGP key   - http://www.drenet.net/pubkey.txt
-=-=-=-=-=-
_______________________________________________
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

Reply via email to