From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 3 01:44:11 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F06E81065672 for ; Wed, 3 Dec 2008 01:44:10 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: from mail-gx0-f19.google.com (mail-gx0-f19.google.com [209.85.217.19]) by mx1.freebsd.org (Postfix) with ESMTP id CDF488FC0C for ; Wed, 3 Dec 2008 01:44:09 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: by gxk12 with SMTP id 12so2180174gxk.19 for ; Tue, 02 Dec 2008 17:44:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type; bh=MfSNjRVdihqtHhD0e/UpC0PZuwBxzYsdCOEKQdJqTso=; b=MJ8jkBEg9DYVmypK46VyCVIe++gXb0e8YpbRUv6S59hu65fc0HAIHtvtWAEt2wfM7X b7iS5h/iMAsSuHD4rOcZQt2OoOJVJSj6xaEQfA+8iIxdK0slGg6s4xHs8WQB21cVr1wc /ijmu2mchw4IBNFKiJ2R/rm3W307r1th4G/tg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=nNJqvBO0XT+5N94V6aVziyarcl0v7ZaYCX/hLIv/pkMyH8GOrrYwqe7bgdVSHrYxyZ lJt7BuK3Ob/UBHF6qq2VbGpAoRuKpVGUgyLYlgOC7vwXx/KK9em9sHwPgQhsmx/YZNSo 3bc6oJrc8PrI9qHwlzpFuibhUAgZzXO/7Ixuc= Received: by 10.150.191.15 with SMTP id o15mr14888982ybf.197.1228267098419; Tue, 02 Dec 2008 17:18:18 -0800 (PST) Received: by 10.151.128.6 with HTTP; Tue, 2 Dec 2008 17:18:18 -0800 (PST) Message-ID: <5f67a8c40812021718i4cc225fem5b02a448702ec606@mail.gmail.com> Date: Tue, 2 Dec 2008 20:18:18 -0500 From: "Zaphod Beeblebrox" To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: AMD64 qemu completely broken? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Dec 2008 01:44:11 -0000 I decided to take the comments about testing ZFS to heart --- so I decided to try copying my 7.0 "v6" ZFS configuration into a qemu instance and upgrading it. To do this, I carefully copied my UFS boot partition and my ZFS partion to a physical USB disk that I could put on a system to do the test. After compiling qemu and loading the kqemu and aio kernel module, I started the emulator, first in VNC mode. It loaded the kernel (currently 7.1-RC) and tried to boot, but kept failing either shortly after kbdmux detected a keyboard or it would get through to mounting root and not find any drives. For reference, besides the display option (ie: -vnc or whatever), my command line was: qemu-system-x86_64 -hda /dev/da0 -snapshot -m 512 I couldn't scroll back in VNC mode using the pause/break key, so I tried to get qemu running directly in X. Now... I see a few posts stating that running qemu remotely causes an X protocol error. I can confirm that. Something about Qemu's use of X will no work over an SSH remote connection (with -X), nor will it work with dxpc. It dies for me every time at X event sequence number 22. Xterms work. Gimp even works. qemu does not. So I got a vnc server running to run it locally. And now it crashes reliably in one spot. boot0 and boot1 don't recognize the keyboard ... but the press space after crash does. Besides that quirk, the 7.1-RC kernel crashes with the following transcript reliably: MADT: Forcing active-low polarity and level trigger for SCI kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) Fatal trap 9: general protection fault while in kernel mode cpuid = 0; apic id=00 instruction pointer = 0x8:0xffff ... and so on. I'd like to test this... has anyone any successes with the AMD64 qemu?