All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maarten <1861884@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1861884] Re: qemu socket multicast not working
Date: Tue, 04 Feb 2020 15:48:42 -0000	[thread overview]
Message-ID: <158083132308.27184.9025299138991480078.launchpad@soybean.canonical.com> (raw)
In-Reply-To: 158083099190.20144.2427615447806299744.malonedeb@wampee.canonical.com

** Description changed:

  Running two qemu vms on the same socket multicast address:
  
    qemu-system-x86_64 -m 2048 -smp 2 -serial mon:stdio
-     -display none -vga none
+     -display none -vga none
      -nodefaults -accel hax
      -netdev user,id=mynet0
      -device virtio-net-pci,netdev=mynet0
      -netdev socket,id=vlan,mcast=239.192.0.1:1235
      -device virtio-net-pci,netdev=vlan
      -device virtio-rng-pci
      -drive file=worker.qcow2,if=virtio
      -drive file=cloud-init.iso,format=raw,if=virtio
  
  The two machines have a static ip on the socket network interface,
  192.168.100.11 and 192.168.100.12, but are unable to reach each other.
  
+ Result when using ping command
+ 
+   PING 192.168.100.11 (192.168.100.11) 56(84) bytes of data.
+   From 192.168.100.12 icmp_seq=1 Destination Host Unreachable
+   From 192.168.100.12 icmp_seq=2 Destination Host Unreachable
+   From 192.168.100.12 icmp_seq=3 Destination Host Unreachable
+ 
  Is there additional configuration necessary on macos? Does this only
- work on Linux?
+ work on Linux? Is there additional configuration required inside of the
+ guest OS?
  
  guest OS: Debian 10 (Buster)
  host OS: macOS 10.15.2
  qemu: 4.2.0

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

Title:
  qemu socket multicast not working

Status in QEMU:
  New

Bug description:
  Running two qemu vms on the same socket multicast address:

    qemu-system-x86_64 -m 2048 -smp 2 -serial mon:stdio
      -display none -vga none
      -nodefaults -accel hax
      -netdev user,id=mynet0
      -device virtio-net-pci,netdev=mynet0
      -netdev socket,id=vlan,mcast=239.192.0.1:1235
      -device virtio-net-pci,netdev=vlan
      -device virtio-rng-pci
      -drive file=worker.qcow2,if=virtio
      -drive file=cloud-init.iso,format=raw,if=virtio

  The two machines have a static ip on the socket network interface,
  192.168.100.11 and 192.168.100.12, but are unable to reach each other.

  Result when using ping command

    PING 192.168.100.11 (192.168.100.11) 56(84) bytes of data.
    From 192.168.100.12 icmp_seq=1 Destination Host Unreachable
    From 192.168.100.12 icmp_seq=2 Destination Host Unreachable
    From 192.168.100.12 icmp_seq=3 Destination Host Unreachable

  Is there additional configuration necessary on macos? Does this only
  work on Linux? Is there additional configuration required inside of
  the guest OS?

  guest OS: Debian 10 (Buster)
  host OS: macOS 10.15.2
  qemu: 4.2.0

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


  reply	other threads:[~2020-02-04 15:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-04 15:43 [Bug 1861884] [NEW] qemu socket multicast not working Maarten
2020-02-04 15:48 ` Maarten [this message]
2021-05-05 15:21 ` [Bug 1861884] " Thomas Huth
2021-07-05  4:17 ` Launchpad Bug Tracker

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=158083132308.27184.9025299138991480078.launchpad@soybean.canonical.com \
    --to=1861884@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.