All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Huth <1922102@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1922102] Re: Broken tap networking on macOS host
Date: Fri, 14 May 2021 19:05:32 -0000	[thread overview]
Message-ID: <162101913244.8318.7852598844331489279.malone@gac.canonical.com> (raw)
In-Reply-To: 161720333927.2408.17717907169331715630.malonedeb@chaenomeles.canonical.com

The QEMU project is currently moving its bug tracking to another system.
For this we need to know which bugs are still valid and which could be
closed already. Thus we are setting the bug state to "Incomplete" now.

If the bug has already been fixed in the latest upstream version of QEMU,
then please close this ticket as "Fix released".

If it is not fixed yet and you think that this bug report here is still
valid, then you have two options:

1) If you already have an account on gitlab.com, please open a new ticket
for this problem in our new tracker here:

    https://gitlab.com/qemu-project/qemu/-/issues

and then close this ticket here on Launchpad (or let it expire auto-
matically after 60 days). Please mention the URL of this bug ticket on
Launchpad in the new ticket on GitLab.

2) If you don't have an account on gitlab.com and don't intend to get
one, but still would like to keep this ticket opened, then please switch
the state back to "New" or "Confirmed" within the next 60 days (other-
wise it will get closed as "Expired"). We will then eventually migrate
the ticket automatically to the new system (but you won't be the reporter
of the bug in the new system and thus you won't get notified on changes
anymore).

Thank you and sorry for the inconvenience.


** Changed in: qemu
       Status: New => Incomplete

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

Title:
  Broken tap networking on macOS host

Status in QEMU:
  Incomplete

Bug description:
  Building QEMU with GLib newer than 2.58.3 corrupts tap networking on macOS hosts.
  Tap device was provided by Tun/Tap kernel extension installed from brew:
    brew install tuntap

  Checked revisions:
    553032d (v5.2.0)
    6d40ce0 (v6.0.0-rc1)

  Host:
   MacBook Pro (Retina, 15-inch, Mid 2015)
   macOS Catalina 10.15.6 (19G2021)

  Guest:
    Linux Ubuntu 4.4.0-206-generic x86_64
    Also tested macOS Catalina 10.15.7 as a guest, the behaviour is the same.

  QEMU command line:

  qemu-system-x86_64 \
    -drive file=hdd.qcow2,if=virtio,format=qcow2 \
    -m 3G \
    -nic tap,script=tap-up.sh

  tap-up.sh:

   #!/bin/sh

   TAPDEV="$1"
   BRIDGEDEV="bridge0"

   ifconfig "$BRIDGEDEV" addm "$TAPDEV"

  Enabling/disabling Hypervisor.Framework acceleration (`-accel hvf`)
  has no effect.

  How to reproduce:
    1. Build & install GLib > 2.58.3 (tested 2.60.7)
    2. Build qemu-system-x86_64 with GLib > 2.58.3
    3. Boot any guest with tap networking enabled
    4. See that the external network is inaccessible

  Hotfix:
    1. Build & install GLib 2.58.3
    2. Build qemu-system-x86_64 with GLib 2.58.3
    3. Boot any guest with tap networking enabled
    4. See that the external network is accessible, everything is working as expected

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


  parent reply	other threads:[~2021-05-14 19:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-31 15:08 [Bug 1922102] [NEW] Broken tap networking on macOS host Vladislav Yaroshchuk
2021-04-17  7:40 ` [Bug 1922102] " Vladislav Yaroshchuk
2021-05-14 19:05 ` Thomas Huth [this message]
2021-05-18  4:26 ` Thomas Huth

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=162101913244.8318.7852598844331489279.malone@gac.canonical.com \
    --to=1922102@bugs.launchpad.net \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.