[Bug 1724441] Re: No external network access for VMs

2021-03-29 Thread Paride Legovini
Speaking specifically of the libvirt task: in comment #12 Christian dug into this issue and concluded that this is not a libvirt bug, proposing to set it to Invalid and focus on LP: #1754871, which is now Fix Released. I see no elements here pointing to a libvirt bug, but as I can't fully rule it

[Bug 1724441] Re: No external network access for VMs

2021-03-26 Thread Thomas Schweikle
Same problem again: guests can resolve internet addresses, but are unable to access them: # host google.com google.com has address 172.217.20.238 google.com has IPv6 address 2a00:1450:4016:801::200e google.com mail is handled by 30 alt2.aspmx.l.google.com. google.com mail is handled by 10 aspmx.l.

[Bug 1724441] Re: No external network access for VMs

2019-12-14 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-boxes (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724441 Title:

[Bug 1724441] Re: No external network access for VMs

2018-04-23 Thread ChristianEhrhardt
Hi Michael, thank you for the discussion, no need to apologize - I can see your troubles and want to help. But lets dissect the different aspects of it. TL;DR: - path in qemu.conf should not matter - need to set-uid manually is wanted for security reasons - apparmor fixes exist, please chime in

[Bug 1724441] Re: No external network access for VMs

2018-04-22 Thread Ubuntu Foundations Team Bug Bot
The attachment "Changes needed to /etc/qemu.conf" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned

[Bug 1724441] Re: No external network access for VMs

2018-04-22 Thread Michael Gratton
** Patch added: "Changes needed to /etc/libvirt/usr.sbin.libvirtd" https://bugs.launchpad.net/ubuntu/+source/gnome-boxes/+bug/1724441/+attachment/5125661/+files/usr.sbin.libvirtd-fixed.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to U

[Bug 1724441] Re: No external network access for VMs

2018-04-22 Thread Michael Gratton
The changes to the apparmour profile aren't minimal, they could probably be tightened up, but I'm not very familiar with it. I also needed to "sudo chmod u+s /usr/lib/qemu/qemu-bridge-helper" again, as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1724441] Re: No external network access for VMs

2018-04-22 Thread Michael Gratton
** Patch added: "Changes needed to /etc/qemu.conf" https://bugs.launchpad.net/ubuntu/+source/gnome-boxes/+bug/1724441/+attachment/5125660/+files/qemu.conf-fixed.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.laun

[Bug 1724441] Re: No external network access for VMs

2018-04-22 Thread Michael Gratton
Apologies to re-open this for libvirt again, but I just had to go through the same song and dance again after upgrading to 18.04 and fixing the problem this required making some changes to the apparmour profile for libvirt. Will attach a diff of the changes in a moment. -- You received this bug n

[Bug 1724441] Re: No external network access for VMs

2018-04-22 Thread Michael Gratton
** Changed in: libvirt (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724441 Title: No external network access for VMs To manage notifications about thi

[Bug 1724441] Re: No external network access for VMs

2018-02-13 Thread ChristianEhrhardt
Hi, the dependency to libvirt atm is only -> libvirt-daemon (Depend) -> libvirt-daemon-system (suggest) And if that would be all that would be needed I'd expect that it could be changed in gnome-boxes. But I wonder about "whichever libvirt package is responsible for creating that network needs t

[Bug 1724441] Re: No external network access for VMs

2018-02-11 Thread Michael Gratton
I managed to get this working in the end. Turns out that despite using the libvirt/qemu user session for the VMs, gnome-boxes actually uses the *system* libvirt network named "default" for networking so it works "out of the box". In reality, I had to delete that network and re-create it using virt-

[Bug 1724441] Re: No external network access for VMs

2017-11-20 Thread Michael Gratton
Hey, thanks for the pointers, I've been looking into this a bit and performed the following: - Set `bridge_helper` correctly in `/etc/libvirt/qemu.conf` - it was commented out and pointing to the wrong binary - Made qemu-bridge-helper set-uid - Created an appropriate /etc/qemu/bridge.conf - Resta

[Bug 1724441] Re: No external network access for VMs

2017-10-24 Thread ChristianEhrhardt
Hi, thanks Michael for the report. Looking into this from the libvirt POV. This is - on the virtualization side - a known limitation of qemu:///session Here an example to show the basics. I first started with a test to confirm/debug the issue test xml describing a most basic nat network: # cat

[Bug 1724441] Re: No external network access for VMs

2017-10-23 Thread Michael Gratton
Added libvirt since I can't add a NAT network to the qemu:///session using virt-manager, either. ** Also affects: libvirt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bug