Bug#1014435: libvirt-daemon-system-systemd: virbr0 default fails to connect

2022-07-18 Thread Andrea Bolognani
On Tue, Jul 05, 2022 at 08:06:44PM -0500, Tim McConnell wrote:
> Package: libvirt-daemon-system-systemd
> Version: 8.4.0-1
> Severity: grave
> Justification: renders package unusable

This doesn't feel right. According to [1], "grave" means that the bug

  makes the package in question unusable or mostly so, or causes data
  loss, or introduces a security hole allowing access to the accounts
  of users who use the package

The fact that a single libvirt feature (the default network) has been
reported as not working by a single person (I just tested it on my
machine and it seems okay) doesn't match the description of the
severity IMO. I'll lower it to "important", which indicates

  a bug which has a major effect on the usability of a package,
  without rendering it completely unusable to everyone

and seems to describe the actual impact much more accurately.

> Virbr0 won't connect to external network.It did once, I was able to install
> Debian from a net install image. Now it tells me the Virtual Machine can't
> connect.

Please be more specific. Does the VM fail to start? If so, what is
the exact error message? Or does the VM boot up, but the guest OS is
unable to connect to the Internet? Can the guest OS ping the host, or
does that not work either? If you try performing another
installation, does that work?


[1] https://www.debian.org/Bugs/Developer#severities
-- 
Andrea Bolognani 
Resistance is futile, you will be garbage collected.


signature.asc
Description: PGP signature


Bug#1014435: libvirt-daemon-system-systemd: virbr0 default fails to connect

2022-07-05 Thread Tim McConnell
Package: libvirt-daemon-system-systemd
Version: 8.4.0-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: tmcconnell...@gmail.com

Dear Maintainer,

Virbr0 won't connect to external network.It did once, I was able to install
Debian from a net install image. Now it tells me the Virtual Machine can't
connect.
It shows as active in Virt-manager. IP ADDR shows the connection and NFTables
has a table for it. All the documentation I can find states the connection to
Virbr0 is supposed to work, what am I missing?


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.18.0-2-rt-amd64 (SMP w/1 CPU thread; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libvirt-daemon-system-systemd depends on:
ii  systemd-container  251.2-7
ii  systemd-sysv   251.2-7

libvirt-daemon-system-systemd recommends no packages.

libvirt-daemon-system-systemd suggests no packages.

-- no debconf information