VMs won't start when I change network from NAT to Bridge adapter












1















I have Linux Mint 19.1 Tessa as host and my guest is Windows 10. When I go over VirtualBox to change the network from NAT to Bridge adapter Windows 10 VM does not start. Screenshots are attached here:




  • Network Details


Network Details




  • Changing network from nat to bridge adpater and selecting the network interface


NAT-to-Bridge




  • The error it shows


error



Things to know about my network



I am in college hostel where the hostel network is 10.2.0.x which is connected to a switch. Gateway is 10.2.0.1. IPs are static. There is also proxy server setup to access the internet which 172.16.0.11:3128. What is the reason for VM not starting up?



Also all the different network arrangements I can have. If I am able to start up VM then what IPs I should give. I am new to VirtualBox and having more difficulties as my host is Linux.










share|improve this question

























  • Every VM has its own log file. You need to investigate this log file to find clues about the error. // Also, don’t ask multiple questions at once.

    – Daniel B
    Jan 4 at 12:55


















1















I have Linux Mint 19.1 Tessa as host and my guest is Windows 10. When I go over VirtualBox to change the network from NAT to Bridge adapter Windows 10 VM does not start. Screenshots are attached here:




  • Network Details


Network Details




  • Changing network from nat to bridge adpater and selecting the network interface


NAT-to-Bridge




  • The error it shows


error



Things to know about my network



I am in college hostel where the hostel network is 10.2.0.x which is connected to a switch. Gateway is 10.2.0.1. IPs are static. There is also proxy server setup to access the internet which 172.16.0.11:3128. What is the reason for VM not starting up?



Also all the different network arrangements I can have. If I am able to start up VM then what IPs I should give. I am new to VirtualBox and having more difficulties as my host is Linux.










share|improve this question

























  • Every VM has its own log file. You need to investigate this log file to find clues about the error. // Also, don’t ask multiple questions at once.

    – Daniel B
    Jan 4 at 12:55
















1












1








1








I have Linux Mint 19.1 Tessa as host and my guest is Windows 10. When I go over VirtualBox to change the network from NAT to Bridge adapter Windows 10 VM does not start. Screenshots are attached here:




  • Network Details


Network Details




  • Changing network from nat to bridge adpater and selecting the network interface


NAT-to-Bridge




  • The error it shows


error



Things to know about my network



I am in college hostel where the hostel network is 10.2.0.x which is connected to a switch. Gateway is 10.2.0.1. IPs are static. There is also proxy server setup to access the internet which 172.16.0.11:3128. What is the reason for VM not starting up?



Also all the different network arrangements I can have. If I am able to start up VM then what IPs I should give. I am new to VirtualBox and having more difficulties as my host is Linux.










share|improve this question
















I have Linux Mint 19.1 Tessa as host and my guest is Windows 10. When I go over VirtualBox to change the network from NAT to Bridge adapter Windows 10 VM does not start. Screenshots are attached here:




  • Network Details


Network Details




  • Changing network from nat to bridge adpater and selecting the network interface


NAT-to-Bridge




  • The error it shows


error



Things to know about my network



I am in college hostel where the hostel network is 10.2.0.x which is connected to a switch. Gateway is 10.2.0.1. IPs are static. There is also proxy server setup to access the internet which 172.16.0.11:3128. What is the reason for VM not starting up?



Also all the different network arrangements I can have. If I am able to start up VM then what IPs I should give. I am new to VirtualBox and having more difficulties as my host is Linux.







linux networking windows-10 virtualbox virtual-machine






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jan 1 at 16:34









Biswapriyo

2,88531341




2,88531341










asked Dec 28 '18 at 12:03









Akashdeep NandiAkashdeep Nandi

62




62













  • Every VM has its own log file. You need to investigate this log file to find clues about the error. // Also, don’t ask multiple questions at once.

    – Daniel B
    Jan 4 at 12:55





















  • Every VM has its own log file. You need to investigate this log file to find clues about the error. // Also, don’t ask multiple questions at once.

    – Daniel B
    Jan 4 at 12:55



















Every VM has its own log file. You need to investigate this log file to find clues about the error. // Also, don’t ask multiple questions at once.

– Daniel B
Jan 4 at 12:55







Every VM has its own log file. You need to investigate this log file to find clues about the error. // Also, don’t ask multiple questions at once.

– Daniel B
Jan 4 at 12:55












1 Answer
1






active

oldest

votes


















1














It may happen when the configuration file get corrupted for some reason. So: find file VirtualBox.xml-prev (usually located at /home/$user/.VirtualBox/ );
then get differences with VirtualBox.xml



diff VirtualBox.xml-prev VirtualBox.xml


If there are differences on network configuration, restore the previous: delete VirtualBox.xml and change name VirtualBox.xml-prev to VirtualBox.xml






share|improve this answer


























  • I think it is rather unlikely the VirtualBox GUI would produce an invalid configuration file.

    – Daniel B
    Jan 4 at 12:54











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1388421%2fvms-wont-start-when-i-change-network-from-nat-to-bridge-adapter%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









1














It may happen when the configuration file get corrupted for some reason. So: find file VirtualBox.xml-prev (usually located at /home/$user/.VirtualBox/ );
then get differences with VirtualBox.xml



diff VirtualBox.xml-prev VirtualBox.xml


If there are differences on network configuration, restore the previous: delete VirtualBox.xml and change name VirtualBox.xml-prev to VirtualBox.xml






share|improve this answer


























  • I think it is rather unlikely the VirtualBox GUI would produce an invalid configuration file.

    – Daniel B
    Jan 4 at 12:54
















1














It may happen when the configuration file get corrupted for some reason. So: find file VirtualBox.xml-prev (usually located at /home/$user/.VirtualBox/ );
then get differences with VirtualBox.xml



diff VirtualBox.xml-prev VirtualBox.xml


If there are differences on network configuration, restore the previous: delete VirtualBox.xml and change name VirtualBox.xml-prev to VirtualBox.xml






share|improve this answer


























  • I think it is rather unlikely the VirtualBox GUI would produce an invalid configuration file.

    – Daniel B
    Jan 4 at 12:54














1












1








1







It may happen when the configuration file get corrupted for some reason. So: find file VirtualBox.xml-prev (usually located at /home/$user/.VirtualBox/ );
then get differences with VirtualBox.xml



diff VirtualBox.xml-prev VirtualBox.xml


If there are differences on network configuration, restore the previous: delete VirtualBox.xml and change name VirtualBox.xml-prev to VirtualBox.xml






share|improve this answer















It may happen when the configuration file get corrupted for some reason. So: find file VirtualBox.xml-prev (usually located at /home/$user/.VirtualBox/ );
then get differences with VirtualBox.xml



diff VirtualBox.xml-prev VirtualBox.xml


If there are differences on network configuration, restore the previous: delete VirtualBox.xml and change name VirtualBox.xml-prev to VirtualBox.xml







share|improve this answer














share|improve this answer



share|improve this answer








edited Jan 4 at 13:05

























answered Jan 4 at 12:52









TDKTDK

27711




27711













  • I think it is rather unlikely the VirtualBox GUI would produce an invalid configuration file.

    – Daniel B
    Jan 4 at 12:54



















  • I think it is rather unlikely the VirtualBox GUI would produce an invalid configuration file.

    – Daniel B
    Jan 4 at 12:54

















I think it is rather unlikely the VirtualBox GUI would produce an invalid configuration file.

– Daniel B
Jan 4 at 12:54





I think it is rather unlikely the VirtualBox GUI would produce an invalid configuration file.

– Daniel B
Jan 4 at 12:54


















draft saved

draft discarded




















































Thanks for contributing an answer to Super User!


  • 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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1388421%2fvms-wont-start-when-i-change-network-from-nat-to-bridge-adapter%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

Plaza Victoria

Puebla de Zaragoza

Musa