From: "Michal Prívozník" <mprivozn@redhat.com>
To: "Marc-André Lureau" <marcandre.lureau@gmail.com>,
QEMU <qemu-devel@nongnu.org>
Cc: oshoval@redhat.com, Michael Roth <mdroth@linux.vnet.ibm.com>
Subject: Re: RFC: extending QGA guest-network-get-interfaces
Date: Wed, 24 Nov 2021 16:15:59 +0100 [thread overview]
Message-ID: <052bedf2-e48e-2fe7-9376-eb943923b7cd@redhat.com> (raw)
In-Reply-To: <CAJ+F1C+HXNBbfROqQBU1Wrt5fiVa9xrSpgg9ymSO2wR+WPRqBA@mail.gmail.com>
On 11/24/21 15:00, Marc-André Lureau wrote:
> Hi
>
> Or Shoval filed two RFE for guest-network-get-interfaces:
> - "Guest agent should report the interface Permanent address"
> https://bugzilla.redhat.com/show_bug.cgi?id=2025303
> <https://bugzilla.redhat.com/show_bug.cgi?id=2025303>
As I've replied in the BZ, this is something that Libvirt can improve
on. What happens when guest changes a MAC address is that
NIC_RX_FILTER_CHANGED event is emitted and libvirt processes it (mostly
to update guest XML, but not limited only to that). But, Libvirt does
not forward this event further to users. Therefore, if a mgmt app on the
top of Libvirt wants to keep track of MAC addresses, it can't do that
simply.
> - "Guest agent should report interfaces from non root network
> namespaces" https://bugzilla.redhat.com/show_bug.cgi?id=2025296
> <https://bugzilla.redhat.com/show_bug.cgi?id=2025296>
This is a bit tricky to achieve. There's no easy way to list all nsids
(they don't form a hierarchy like other NSs). We could traverse all
mount points (be aware of mount namespaces), all PIDs (be aware of PID
namespaces) and hope we covered all net NSs (a net namespace can have no
nsid).
IOW, network NSs behave different to other namespaces.
Michal
prev parent reply other threads:[~2021-11-24 15:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-24 14:00 RFC: extending QGA guest-network-get-interfaces Marc-André Lureau
2021-11-24 15:15 ` Michal Prívozník [this message]
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=052bedf2-e48e-2fe7-9376-eb943923b7cd@redhat.com \
--to=mprivozn@redhat.com \
--cc=marcandre.lureau@gmail.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=oshoval@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).