From owner-freebsd-virtualization@FreeBSD.ORG Tue May 6 15:21:22 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 13AA2FA2 for ; Tue, 6 May 2014 15:21:22 +0000 (UTC) Received: from nqhost.drenet.net (nqhost.drenet.net [184.95.47.164]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E957DDB8 for ; Tue, 6 May 2014 15:21:21 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by nqhost.drenet.net (Postfix) with ESMTP id C7D993ADD8 for ; Tue, 6 May 2014 11:21:19 -0400 (EDT) Received: from nqhost.drenet.net ([127.0.0.1]) by localhost (nqhost.drenet.net [127.0.0.1]) (maiad, port 10024) with ESMTP id 55571-03 for ; Tue, 6 May 2014 11:21:19 -0400 (EDT) Received: by nqhost.drenet.net (Postfix, from userid 80) id 6CB683AD11; Tue, 6 May 2014 11:21:19 -0400 (EDT) To: freebsd-virtualization@freebsd.org Subject: Re: Kernel Panic on FreeBSD guests with libvirt 1.2.2 and qemu 1.7.91 X-PHP-Originating-Script: 80:rcmail.php MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Date: Tue, 06 May 2014 11:21:19 -0400 From: Andre Goree In-Reply-To: <566708d82c9575d14789b91544ebe0fa@drenet.net> References: <201405021818.s42IIJnu095511@enceladus10.kn-bremen.de> <566708d82c9575d14789b91544ebe0fa@drenet.net> Message-ID: <046432f6833ebfe0f71dada0a3fa779c@drenet.net> X-Sender: andre@drenet.net User-Agent: Roundcube Webmail/0.9.5 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 May 2014 15:21:22 -0000 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.s42I0TiE094542@enceladus10.kn-bremen.de> you >>> write: >>>> In article >>>> >>>> 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-unsubscribe@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 > To: 737142-close@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 -=-=-=-=-=-