Thanks Simon and Adam, what you suggest sounds reasonable.
Do you mind raising this as a bug against the debian package? (If you
do, I'll go ahead and do it).
** Changed in: libvirt (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of U
I am also annoyed by that behaviour after every update of the package.
Adam's analysis in comment #7 is right and I think its suggestion should
be implemented.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://b
This is happening because the package is shipping the symlink as a
conffile. Generally speaking, this isn't a great idea, and dpkg's
handling of symlink-as-conffile cases is shockingly non-obvious.
Like most packages with symlink trees in /etc, what this should be doing
is not shipping the symlin
Every time you create a virtual machine, using virt-manager, it will be
started again. Maybe that's the case here?
--
default network autostart symlink recreated
https://bugs.launchpad.net/bugs/372001
You received this bug notification because you are a member of Ubuntu
Server Team, which is subs
** Changed in: libvirt (Ubuntu)
Assignee: Jamie Strandboge (jdstrand) => (unassigned)
--
default network autostart symlink recreated
https://bugs.launchpad.net/bugs/372001
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubu
** Changed in: libvirt (Ubuntu)
Status: Incomplete => Confirmed
--
default network autostart symlink recreated
https://bugs.launchpad.net/bugs/372001
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
--
Ubuntu-ser
I don't want them undefined or removed, only not set to auto start.
--
default network autostart symlink recreated
https://bugs.launchpad.net/bugs/372001
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
--
Ubuntu-server
Jamin, is the network recreated if you undefine the default network with:
$ virsh net-destroy default
$ virsh net-undefine default
** Changed in: libvirt (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: libvirt (Ubuntu)
Assignee: (unassigned) => Jamie Strandboge (jdstrand)
--
** Changed in: libvirt (Ubuntu)
Status: Incomplete => Confirmed
--
default network autostart symlink recreated
https://bugs.launchpad.net/bugs/372001
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
--
Ubuntu-ser
Steps to reproduce:
Create additional network definitions. I have the following (all set to start
on boot):
- public_1, 192.168.51.0/24, 192.168.51.128, 192.168.51.254, w/NAT
- private_1, 192.168.61.0/24, 192.168.61.128, 192.168.61.254, isolated
- private_2, 192.168.62.0/24, 192.168.62.128, 192.1
** Changed in: libvirt (Ubuntu)
Importance: Undecided => Low
--
default network autostart symlink recreated
https://bugs.launchpad.net/bugs/372001
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
--
Ubuntu-server-bug
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Please answer these questions:
1. Is this reproducible?
2. If so, what specific steps should we take to recreate this bug? Be as
detailed as possible.
This will help us to find and resolve the problem.
** Changed
12 matches
Mail list logo
