From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:45631)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <bounces@canonical.com>) id 1XtiNM-0006RR-1r
	for qemu-devel@nongnu.org; Wed, 26 Nov 2014 14:35:50 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <bounces@canonical.com>) id 1XtiNF-0006OW-SV
	for qemu-devel@nongnu.org; Wed, 26 Nov 2014 14:35:43 -0500
Received: from indium.canonical.com ([91.189.90.7]:51308)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <bounces@canonical.com>) id 1XtiNF-0006OS-L3
	for qemu-devel@nongnu.org; Wed, 26 Nov 2014 14:35:37 -0500
Received: from loganberry.canonical.com ([91.189.90.37])
	by indium.canonical.com with esmtp (Exim 4.76 #1 (Debian))
	id 1XtiND-0005x2-VO
	for <qemu-devel@nongnu.org>; Wed, 26 Nov 2014 19:35:35 +0000
Received: from loganberry.canonical.com (localhost [127.0.0.1])
	by loganberry.canonical.com (Postfix) with ESMTP id B108F2E80C3
	for <qemu-devel@nongnu.org>; Wed, 26 Nov 2014 19:35:34 +0000 (UTC)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 26 Nov 2014 19:27:38 -0000
From: Eduardo Habkost <ehabkost@redhat.com>
Sender: bounces@canonical.com
References: <20141121223040.7362.48987.malonedeb@gac.canonical.com>
Message-Id: <20141126192738.29127.57826.malone@wampee.canonical.com>
Errors-To: bounces@canonical.com
Subject: [Qemu-devel] [Bug 1395217] Re: Networking in qemu 2.0.0 and beyond
 is not compatible with Open Solaris (Illumos) 5.11
Reply-To: Bug 1395217 <1395217@bugs.launchpad.net>
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

So, if it breaks even with -cpu SandyBridge and -cpu host, it is likely
to be a KVM or QEMU bug. Thanks for the testing!

-- =

You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1395217

Title:
  Networking in qemu 2.0.0 and beyond is not compatible with Open
  Solaris (Illumos) 5.11

Status in QEMU:
  New

Bug description:
  The networking code in qemu in versions 2.0.0 and beyond is non-
  functional with Solaris/Illumos 5.11 images.

  Building 1.7.1, 2.0.0, 2.0.2, 2.1.2,and 2.2.0rc1with the following
  standard Slackware config:

  # From Slackware build tree . . . =

  ./configure \
    --prefix=3D/usr \
    --libdir=3D/usr/lib64 \
    --sysconfdir=3D/etc \
    --localstatedir=3D/var \
    --enable-gtk \
    --enable-system \
    --enable-kvm \
    --disable-debug-info \
    --enable-virtfs \
    --enable-sdl \
    --audio-drv-list=3Dalsa,oss,sdl,esd \
    --enable-libusb \
    --disable-vnc \
    --target-list=3Dx86_64-linux-user,i386-linux-user,x86_64-softmmu,i386-s=
oftmmu \
    --enable-spice \
    --enable-usb-redir =


  =

  And attempting to run the same VM image with the following command (or vi=
a virt-manager):

  macaddress=3D"DE:AD:BE:EF:3F:A4"

  qemu-system-x86_64 nex4x -cdrom /dev/cdrom -name "Nex41" -cpu Westmere
  -machine accel=3Dkvm -smp 2 -m 4000 -net nic,macaddr=3D$macaddress  -net =
bridge,br=3Db
  r0 -net dump,file=3D/usr1/tmp/<FILENAME> -drive file=3Dnex4x_d1 -drive fi=
le=3Dnex4x_d2
   -enable-kvm

  Gives success on 1.7.1, and a deaf VM on all subsequent versions.

  Notable in validating my config, is that a Windows 7 image runs
  cleanly with networking on *all* builds, so my configuration appears
  to be good - qemu just hates Solaris at this point.

  Watching with wireshark (as well as pulling network traces from qemu
  as noted above) it appears that the notable difference in the two
  configs is that for some reason, Solaris gets stuck arping for it's
  own interface on startup, and never really comes on line on the
  network.  If other hosts attempt to ping the Solaris instance, they
  can successfully arp the bad VM, but not the other way around.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1395217/+subscriptions