rface as an egress.
This is useful if the host machine has several interfaces with several
virtual networks across disparate interfaces.
Signed-off-by: Mike Ryan
---
net.c |4
net/socket.c| 51 ++-
qemu-options.hx |
e has several interfaces with several
virtual networks across disparate interfaces.
Signed-off-by: Mike Ryan
---
net.c |4
net/socket.c| 46 ++
qemu-options.hx | 11 +--
3 files changed, 47 insertions(+), 14 deletions(-)
On Tue, Nov 23, 2010 at 03:05:49PM +0200, Michael S. Tsirkin wrote:
> On Mon, Nov 22, 2010 at 10:48:45AM -0800, Mike Ryan wrote:
> > Michael, this patch implements the feature with a bind address instead
> > of a bind interface. It should address the cross-platform issues that
Michael, this patch implements the feature with a bind address instead
of a bind interface. It should address the cross-platform issues that
were raised.
Others: any comments?
On Wed, Nov 17, 2010 at 05:16:26PM -0800, Mike Ryan wrote:
> Add an option to specify the host IP to send multic
Add an option to specify the host IP to send multicast packets from when
using a multicast socket for networking. The option takes an IP address
and sets the IP_MULTICAST_IF socket option, which causes the packets to
use that IP's interface as an egress.
This is useful if the host machine has seve
On Tue, Nov 16, 2010 at 07:54:58PM +0200, Michael S. Tsirkin wrote:
>
>
>
> Let's let the user pass in the IP address? That would solve the
> portability issue. Further, we could be doing IPv6, right?
> So you'd need IPV6_MULTICAST_IF?
> Also - you might also want to control
> IP_MULTICAST_LOOP/IP
On Mon, Nov 15, 2010 at 03:07:51PM -0600, Anthony Liguori wrote:
> Thanks. Second question is how portable is SIOCGIFADDR? I suspect
> that's very Linux-centric..
It ostensibly exists in FreeBSD, but I can't get master to compile under
7.3-RELEASE or 8.1-STABLE.
Given that it is unavailable
2010 12:54 PM, Mike Ryan wrote:
> >Anyone care to comment?
>
> I must admit, I don't understand the use-case well enough to really
> give an appropriate amount of review as to whether this is the best
> solution to the problem.
>
> Michael, do you have any thoughts?
&
Anyone care to comment?
On Wed, Nov 10, 2010 at 05:47:35PM -0800, Mike Ryan wrote:
> Add an option to specify the host interface to send multicast packets on
> when using a multicast socket for networking. The option takes the name
> of a host interface (e.g., eth0) and sets the IP_MUL
Add the space in 'thesecurity'.
** Patch added: "0002-include-a-missing-space-in-and-error-message.patch"
https://bugs.launchpad.net/qemu/+bug/674740/+attachment/1731776/+files/0002-include-a-missing-space-in-and-error-message.patch
--
qemu segfaults when security_model=none using virtio-9p-
** Patch added: "patch to fix the bug"
https://bugs.launchpad.net/bugs/674740/+attachment/1731775/+files/0001-return-an-error-code-if-the-virtio-9p-pci-driver-can.patch
--
qemu segfaults when security_model=none using virtio-9p-pci driver
https://bugs.launchpad.net/bugs/674740
You received t
Public bug reported:
qemu version: 0.13
commit-id: 6ed912999d6ef636a5be5ccb266d7d3c0f0310b4
example invocation:
$ qemu -virtfs local,path=/tmp,security_model=none,mount_tag=mmm r.img
one of the following must be specified as thesecurity option:
security_model=passthrough
securi
Add an option to specify the host interface to send multicast packets on
when using a multicast socket for networking. The option takes the name
of a host interface (e.g., eth0) and sets the IP_MULTICAST_IF socket
option, which causes the packets to use that interface as an egress.
This is useful
13 matches
Mail list logo
