From owner-freebsd-arm@FreeBSD.ORG  Sun Mar 22 21:48:17 2015
Return-Path: <owner-freebsd-arm@FreeBSD.ORG>
Delivered-To: freebsd-arm@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 0F480AEA
 for <freebsd-arm@freebsd.org>; Sun, 22 Mar 2015 21:48:17 +0000 (UTC)
Received: from mail.uniridge.com.au
 (ec2-54-206-17-100.ap-southeast-2.compute.amazonaws.com [54.206.17.100])
 by mx1.freebsd.org (Postfix) with ESMTP id C6492BFD
 for <freebsd-arm@freebsd.org>; Sun, 22 Mar 2015 21:48:16 +0000 (UTC)
Received: by mail.uniridge.com.au (Postfix, from userid 1000)
 id EEC584A71; Mon, 23 Mar 2015 08:40:34 +1100 (EST)
Date: Mon, 23 Mar 2015 08:40:34 +1100
From: George Abdelmalik <george@fork.id.au>
To: freebsd-arm@freebsd.org
Subject: ARM VERATILEPB 11.0-current under Qemu
Message-ID: <20150322214034.GA21171@barney.uniridge.com.au>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.22 (2013-10-16)
X-BeenThere: freebsd-arm@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: "Porting FreeBSD to ARM processors." <freebsd-arm.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arm/>
List-Post: <mailto:freebsd-arm@freebsd.org>
List-Help: <mailto:freebsd-arm-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Mar 2015 21:48:17 -0000

Hi list,

For the past few days I've been trying to run a 11.0-current build of FreeBSD
using a VERSATILEPB kernel under Qemu.

I've built the kernel and filesystem images using the crochet tools and all
references I've managed to find on the internet suggest that the following
Qemu command invocation should work:

% qemu-system-arm -machine versatilepb -m 128 -cpu arm1176 \
	-kernel FreeBSD-VERSATILEPB.flash \
	-hda FreeBSD-armv6-11.0-VERSATILEPB-r280209.img

And for me it partially does until the Qemu terminal output displays the
following and the messages outputted by the booting kernel within the VM's
window come to a stop.

pulseaudio: set_sink_input_volume() failed
pulseaudio: Reason: Invalid argument
pulseaudio: set_sink_input_mute() failed
pulseaudio: Reason: Invalid argument
main-loop: WARNING: I/O thread spun for 1000 iterations

I think the pulseaudio notices are harmless, the output of the warning however
coincides with when the booting of the kernal stops.

Firstly I'd just like to know if anyone has seen this behaviour before, or am
I alone here which perhaps points to a local issue on my side. I should also
point out that I'm running Qemu on Linux as sadly for the moment I've not 
access to a FreeBSD baremetal machine.

Any pointers as to how to further investigate, or reports of success or
otherwise with ARM under Qemu would be very welcomed.

Regards,
George.