And finally as FYI, before this appears to be a "they are fixing it but
we are not" case it was fixed in Debian by removing netcf.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1764314
Title:
libvir
** Changed in: netcf (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1764314
Title:
libvirt doesn't show all interfaces
To manage notifications about this
As we demoted netcf and it doesn't work we can drop the further netcf tasks in
Ubuntu in Won't Fix.
It is not that important to Ubuntu to have it working as discussed before it
would a) pull in ifupdown and suggest it is well supported (which it is no
more).
The Debian bug is open and would fix
There already was an upload ongoing, but I need to group bug 1758037 on the
same run and need to set new branches. ... Integrated that now.
Regression- and Case-Tested once more from a ppa and being good.
Uploaded to Cosmic - and it already completed.
Also pushed to ubuntu libvirt-maintainers git.
** Changed in: netcf (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1764314
Title:
libvirt doesn't show all interfaces
To manage notifications about this bug g
This bug was fixed in the package libvirt - 4.0.0-1ubuntu10
---
libvirt (4.0.0-1ubuntu10) cosmic; urgency=medium
* Fix nwfilters that set CTRL_IP_LEARNING set to dhcp failing with "An error
occurred, but the cause is unknown" due to a buffer being too small
for pcap with TPA
Filed a bug in Debian for the netcf Dependency going forward, linked at
the bug tasks.
** Bug watch added: Debian Bug tracker #898194
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898194
** Also affects: libvirt (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898194
Im
We had a discussion on this:
I have to beg your pardon for all of the Ubuntu community, but we never
intended to support write-managing through libvirt in Bionic. Libvirt iface-*
never supported networkd or NetworkManager. To manage networks with different
backends there is netplan.io.
Adding a
Hi rbasak,
almost right - just missing a slight twist.
Yes to all you said until "leaving the situation as-is for stable releases is
appropriate since use case 1 above is far less serious than a potential
regression in use case 3."
I think we all ack on >=18.10 to select the udev backend and be
> This implementation is based on ENI as network_interfaces_path is essentially
> static const char *const network_interfaces_path =
> "/files/etc/network/interfaces"
Does it look at /etc/network/interfaces.d/ at all?
>From the perspective of stable releases, my understanding is that:
1) The on
Thanks Cyphermox for co-testign this with me.
Here an example of his better interface overview now:
virsh # iface-list
Name State MAC Address
---
enp3s0 active c8:60:00:6d:8c:07
lxdbr0 active
For me the main problem is the fact that the dialog in virt-manager is
misleading.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1764314
Title:
libvirt doesn't show all interfaces
To manage notific
Thanks for your reply Nicolas, so even for you if udev backend would
work it would be preferred (full view of the network).
We are evaluating if udev works well for the read-only part and I
discussed with upstream how to enable/disable as well as on the approach
in general.
--
You received this
I tried to select an interface in virt-manager and the desired interface
didn't show in the pop-up menu. But it's true that the name can be
entered in the free-form dialog. But I think that for virt-manager it
makes sense to offer a complete view of the network _or_ a statement
informing of the sho
Networks are configured through net-* commands (and respective APIs) and they
all work.
This is what is commonly used by libvirt users and solutions depending on
libvirt.
The scope of iface-* commands is to manage the Host network interfaces.
This is not really what we'd want libvirt to do.
You
Note: easiest test without compiling is likely
$ apt install netcf
$ netcftool list
...
Related to all of that is bug 1688345.
I contacted cyphermox who filed and worked on that to get his opinion.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Hi,
after sleeping once about this to sort my thoughts I have this morning
revisited most of the code.
## Usage and state of ncf ##
In its only user currently being libvirt I checked that usage via:
$ git log src/interface/
There were only structural changes (how to allocate, make interface ac
This didn't fully work even pre netplan, in fact it is separate.
On my partially E/N/I partially NetworkManager system only the former are
accessible to netcf.
So this functionality from libvirts POV was reduced for quite a while.
While netcf itself can be considered really broken atm.
That is w
It is sometimes surprising what extra features libvirt all has - I
haven't touched this for all the time working with it - Feature of 2009
it seems :-)
First of all yes, I also can't see anything on 18.04 boxes (not that on
16.04 I'd have got a lot, only "lo" actually).
There is nothing of the co
For what is worth, I get nothing listed on my 18.04 laptop, where I use
libvirt extensively:
$ virsh iface-list --all
Name State MAC Address
---
$
** Changed in: libvirt (Ubuntu)
Status: New => Confirmed
--
You recei
20 matches
Mail list logo
