From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:49682) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VLY0Z-0003tW-Cf for Qemu-devel@nongnu.org; Mon, 16 Sep 2013 08:34:33 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VLY0T-0005Qe-DS for Qemu-devel@nongnu.org; Mon, 16 Sep 2013 08:34:27 -0400 Received: from mx1.redhat.com ([209.132.183.28]:42315) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VLY0T-0005QL-5K for Qemu-devel@nongnu.org; Mon, 16 Sep 2013 08:34:21 -0400 Date: Mon, 16 Sep 2013 15:36:28 +0300 From: "Michael S. Tsirkin" Message-ID: <20130916123627.GB2992@redhat.com> References: <20130910172934.GB3913@redhat.com> <20130910174946.GB4065@redhat.com> <8b90976a8d824414a10e656ebbc67202@mspexmb1.Beer.Town> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8b90976a8d824414a10e656ebbc67202@mspexmb1.Beer.Town> Subject: Re: [Qemu-devel] Q35 FreeBSD install status List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Bret Ketchum Cc: "Qemu-devel@nongnu.org" , "kraxel@redhat.com" On Mon, Sep 16, 2013 at 12:28:41PM +0000, Bret Ketchum wrote: > > As a workaround until I can uncover the qemu/FreeBSD AHCI/SATA issue, I simply create a legacy IDE to hang the CD and HD from: > > -device piix4-ide \ > -drive if=none,file=/home/ehv/images/FreeBSD-9.1-RELEASE-amd64-dvd1.iso,id=drive-ide0-0-0 \ > -device ide-cd,bus=ide.0,drive=drive-ide0-0-0,id=ide0-0-0 \ > -drive if=none,file=/home/ehv/images/r060501.img,format=raw,id=drive-ide0-0-1 \ > -device ide-hd,bus=ide.0,drive=drive-ide0-0-1,id=ide0-0-1 \ > > But now the e1000 emulated network device under q35 does not seem to pass interrupts. Using: > > -netdev tap,id=hostnet0,script=/home/ehv/images/qemu-ifup,downscript=/home/ehv/images/qemu-ifdown \ > -device e1000,netdev=hostnet0 \ > > Or a user network: > > -netdev user,id=hostnet0,net=192.168.76.0/24,dhcpstart=192.168.76.9 \ > > But machine pc-i440fx-1.6 works just fine. Anyone have any > thoughts on where to start looking or a possible workaround? Maybe irq gets asserted, but guest does not have a handler? Take a look at system log, that might give some hints. -- MST