How do I stop virbr0 interface being created?
Whenever I start my laptop(HP) , 'Network Connections' shows it being connected (though it is actually not) . When I go to 'edit connections' option , it shows virbr0 . I have to delete it every time . How to get rid of this ? Is it a hardware problem ?
16.04 internet network-bridge
add a comment |
Whenever I start my laptop(HP) , 'Network Connections' shows it being connected (though it is actually not) . When I go to 'edit connections' option , it shows virbr0 . I have to delete it every time . How to get rid of this ? Is it a hardware problem ?
16.04 internet network-bridge
2
Are you running any VMs like VirtualBox or VMPlayer? If you are, virbr0 is created by those and should not be removed.
– Terrance
Nov 20 '17 at 17:20
No . I'm not using any of them . @Terrance
– Rangerix
Nov 21 '17 at 9:31
Sorry, I only listed 2 of them. There is a bigger list here of VMs. Any VM that is installed will create that for the virtual bridged network so the VM will get IP addresses.
– Terrance
Nov 21 '17 at 14:44
add a comment |
Whenever I start my laptop(HP) , 'Network Connections' shows it being connected (though it is actually not) . When I go to 'edit connections' option , it shows virbr0 . I have to delete it every time . How to get rid of this ? Is it a hardware problem ?
16.04 internet network-bridge
Whenever I start my laptop(HP) , 'Network Connections' shows it being connected (though it is actually not) . When I go to 'edit connections' option , it shows virbr0 . I have to delete it every time . How to get rid of this ? Is it a hardware problem ?
16.04 internet network-bridge
16.04 internet network-bridge
asked Nov 20 '17 at 17:16
RangerixRangerix
15138
15138
2
Are you running any VMs like VirtualBox or VMPlayer? If you are, virbr0 is created by those and should not be removed.
– Terrance
Nov 20 '17 at 17:20
No . I'm not using any of them . @Terrance
– Rangerix
Nov 21 '17 at 9:31
Sorry, I only listed 2 of them. There is a bigger list here of VMs. Any VM that is installed will create that for the virtual bridged network so the VM will get IP addresses.
– Terrance
Nov 21 '17 at 14:44
add a comment |
2
Are you running any VMs like VirtualBox or VMPlayer? If you are, virbr0 is created by those and should not be removed.
– Terrance
Nov 20 '17 at 17:20
No . I'm not using any of them . @Terrance
– Rangerix
Nov 21 '17 at 9:31
Sorry, I only listed 2 of them. There is a bigger list here of VMs. Any VM that is installed will create that for the virtual bridged network so the VM will get IP addresses.
– Terrance
Nov 21 '17 at 14:44
2
2
Are you running any VMs like VirtualBox or VMPlayer? If you are, virbr0 is created by those and should not be removed.
– Terrance
Nov 20 '17 at 17:20
Are you running any VMs like VirtualBox or VMPlayer? If you are, virbr0 is created by those and should not be removed.
– Terrance
Nov 20 '17 at 17:20
No . I'm not using any of them . @Terrance
– Rangerix
Nov 21 '17 at 9:31
No . I'm not using any of them . @Terrance
– Rangerix
Nov 21 '17 at 9:31
Sorry, I only listed 2 of them. There is a bigger list here of VMs. Any VM that is installed will create that for the virtual bridged network so the VM will get IP addresses.
– Terrance
Nov 21 '17 at 14:44
Sorry, I only listed 2 of them. There is a bigger list here of VMs. Any VM that is installed will create that for the virtual bridged network so the VM will get IP addresses.
– Terrance
Nov 21 '17 at 14:44
add a comment |
2 Answers
2
active
oldest
votes
On my machine virbr0 interface was created after installation of libvirt-bin
package which is dependency of virt-manager
.
Solution 1 (straight-forward):
It seems you can remove it from startup by removing corresponding file with
sudo rm /etc/libvirt/qemu/networks/autostart/default.xml
You can bring it back with
sudo ln -s /etc/libvirt/qemu/networks/default.xml /etc/libvirt/qemu/networks/autostart/default.xml
Solution 2 (with virsh
)
- disable:
sudo virsh net-autostart --disable default
- enable:
sudo virsh net-autostart default
But this has side-effect. If you want to use bridged network in virt-manager you should start bridge before launching VM with sudo virsh net-start default
.
Solution 3 (set virbr0 unmanaged in NetworkManager)
The following lines should be added to the end of /etc/NetworkManager/NetworkManager.conf:
[keyfile]
unmanaged-devices=interface-name:virbr0
The result: NetworkManager "does not know" about virbr0, but VMs can access bridged networking.
add a comment |
Give this a try this is mostly for Centos
sudo su -
virsh net-destroy default
virsh net-undefine default
systemctl stop libvirtd.service
systemctl disable libvirtd.service
apt remove qemu-kvm qemu-img virt-manager libvirt libvirt-python libvirt-client virt-install virt-viewer bridge-utils
1
Please read this about how to write a good answer, particularly the section "Provide context for links". Also: Did you successfully tried this on Ubuntu?
– Pablo Bianchi
Dec 29 '18 at 3:02
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f978487%2fhow-do-i-stop-virbr0-interface-being-created%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
On my machine virbr0 interface was created after installation of libvirt-bin
package which is dependency of virt-manager
.
Solution 1 (straight-forward):
It seems you can remove it from startup by removing corresponding file with
sudo rm /etc/libvirt/qemu/networks/autostart/default.xml
You can bring it back with
sudo ln -s /etc/libvirt/qemu/networks/default.xml /etc/libvirt/qemu/networks/autostart/default.xml
Solution 2 (with virsh
)
- disable:
sudo virsh net-autostart --disable default
- enable:
sudo virsh net-autostart default
But this has side-effect. If you want to use bridged network in virt-manager you should start bridge before launching VM with sudo virsh net-start default
.
Solution 3 (set virbr0 unmanaged in NetworkManager)
The following lines should be added to the end of /etc/NetworkManager/NetworkManager.conf:
[keyfile]
unmanaged-devices=interface-name:virbr0
The result: NetworkManager "does not know" about virbr0, but VMs can access bridged networking.
add a comment |
On my machine virbr0 interface was created after installation of libvirt-bin
package which is dependency of virt-manager
.
Solution 1 (straight-forward):
It seems you can remove it from startup by removing corresponding file with
sudo rm /etc/libvirt/qemu/networks/autostart/default.xml
You can bring it back with
sudo ln -s /etc/libvirt/qemu/networks/default.xml /etc/libvirt/qemu/networks/autostart/default.xml
Solution 2 (with virsh
)
- disable:
sudo virsh net-autostart --disable default
- enable:
sudo virsh net-autostart default
But this has side-effect. If you want to use bridged network in virt-manager you should start bridge before launching VM with sudo virsh net-start default
.
Solution 3 (set virbr0 unmanaged in NetworkManager)
The following lines should be added to the end of /etc/NetworkManager/NetworkManager.conf:
[keyfile]
unmanaged-devices=interface-name:virbr0
The result: NetworkManager "does not know" about virbr0, but VMs can access bridged networking.
add a comment |
On my machine virbr0 interface was created after installation of libvirt-bin
package which is dependency of virt-manager
.
Solution 1 (straight-forward):
It seems you can remove it from startup by removing corresponding file with
sudo rm /etc/libvirt/qemu/networks/autostart/default.xml
You can bring it back with
sudo ln -s /etc/libvirt/qemu/networks/default.xml /etc/libvirt/qemu/networks/autostart/default.xml
Solution 2 (with virsh
)
- disable:
sudo virsh net-autostart --disable default
- enable:
sudo virsh net-autostart default
But this has side-effect. If you want to use bridged network in virt-manager you should start bridge before launching VM with sudo virsh net-start default
.
Solution 3 (set virbr0 unmanaged in NetworkManager)
The following lines should be added to the end of /etc/NetworkManager/NetworkManager.conf:
[keyfile]
unmanaged-devices=interface-name:virbr0
The result: NetworkManager "does not know" about virbr0, but VMs can access bridged networking.
On my machine virbr0 interface was created after installation of libvirt-bin
package which is dependency of virt-manager
.
Solution 1 (straight-forward):
It seems you can remove it from startup by removing corresponding file with
sudo rm /etc/libvirt/qemu/networks/autostart/default.xml
You can bring it back with
sudo ln -s /etc/libvirt/qemu/networks/default.xml /etc/libvirt/qemu/networks/autostart/default.xml
Solution 2 (with virsh
)
- disable:
sudo virsh net-autostart --disable default
- enable:
sudo virsh net-autostart default
But this has side-effect. If you want to use bridged network in virt-manager you should start bridge before launching VM with sudo virsh net-start default
.
Solution 3 (set virbr0 unmanaged in NetworkManager)
The following lines should be added to the end of /etc/NetworkManager/NetworkManager.conf:
[keyfile]
unmanaged-devices=interface-name:virbr0
The result: NetworkManager "does not know" about virbr0, but VMs can access bridged networking.
edited Dec 29 '18 at 4:18
d a i s y
3,31782344
3,31782344
answered Nov 20 '17 at 17:58
N0rbertN0rbert
22.2k547104
22.2k547104
add a comment |
add a comment |
Give this a try this is mostly for Centos
sudo su -
virsh net-destroy default
virsh net-undefine default
systemctl stop libvirtd.service
systemctl disable libvirtd.service
apt remove qemu-kvm qemu-img virt-manager libvirt libvirt-python libvirt-client virt-install virt-viewer bridge-utils
1
Please read this about how to write a good answer, particularly the section "Provide context for links". Also: Did you successfully tried this on Ubuntu?
– Pablo Bianchi
Dec 29 '18 at 3:02
add a comment |
Give this a try this is mostly for Centos
sudo su -
virsh net-destroy default
virsh net-undefine default
systemctl stop libvirtd.service
systemctl disable libvirtd.service
apt remove qemu-kvm qemu-img virt-manager libvirt libvirt-python libvirt-client virt-install virt-viewer bridge-utils
1
Please read this about how to write a good answer, particularly the section "Provide context for links". Also: Did you successfully tried this on Ubuntu?
– Pablo Bianchi
Dec 29 '18 at 3:02
add a comment |
Give this a try this is mostly for Centos
sudo su -
virsh net-destroy default
virsh net-undefine default
systemctl stop libvirtd.service
systemctl disable libvirtd.service
apt remove qemu-kvm qemu-img virt-manager libvirt libvirt-python libvirt-client virt-install virt-viewer bridge-utils
Give this a try this is mostly for Centos
sudo su -
virsh net-destroy default
virsh net-undefine default
systemctl stop libvirtd.service
systemctl disable libvirtd.service
apt remove qemu-kvm qemu-img virt-manager libvirt libvirt-python libvirt-client virt-install virt-viewer bridge-utils
edited Dec 29 '18 at 3:06
Pablo Bianchi
2,4751532
2,4751532
answered Dec 28 '18 at 22:27
IT repoIT repo
1
1
1
Please read this about how to write a good answer, particularly the section "Provide context for links". Also: Did you successfully tried this on Ubuntu?
– Pablo Bianchi
Dec 29 '18 at 3:02
add a comment |
1
Please read this about how to write a good answer, particularly the section "Provide context for links". Also: Did you successfully tried this on Ubuntu?
– Pablo Bianchi
Dec 29 '18 at 3:02
1
1
Please read this about how to write a good answer, particularly the section "Provide context for links". Also: Did you successfully tried this on Ubuntu?
– Pablo Bianchi
Dec 29 '18 at 3:02
Please read this about how to write a good answer, particularly the section "Provide context for links". Also: Did you successfully tried this on Ubuntu?
– Pablo Bianchi
Dec 29 '18 at 3:02
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f978487%2fhow-do-i-stop-virbr0-interface-being-created%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
2
Are you running any VMs like VirtualBox or VMPlayer? If you are, virbr0 is created by those and should not be removed.
– Terrance
Nov 20 '17 at 17:20
No . I'm not using any of them . @Terrance
– Rangerix
Nov 21 '17 at 9:31
Sorry, I only listed 2 of them. There is a bigger list here of VMs. Any VM that is installed will create that for the virtual bridged network so the VM will get IP addresses.
– Terrance
Nov 21 '17 at 14:44