Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have a server running some VBox VMs in headless mode, but we also use it for testing purposes too and have a couple of VM that are started from the GUI for VBox from time to time. I recently created one for Windows 7, I ran the install then realized I forgot to change the network connection type from NAT to Bridged. So I opened up the properties of this VM and tried to change it but could not save it because VirtualBox told me that I had to lower the number of CPUs that the VM had as it could not be more than 2x the number of physical processors in the machine(0) which it reported to me as 0 processors in the physical machine. I then tried to edit another VM and received the same issue. So I figure no big deal I will edit it with VBoxManage at the command line, The command to change the adapter to bridged was accepted but viewing the VM info and starting up the VM bear out that it is still NATed. So I try the hard way I edit the text file with a text editor, I save it, I boot and still I have NATed networking. I go back and open the text file and my changes I made with the text editor are not there it says it is NAT again.
I am running VirtualBox 3.0.0 on an server with a XEON quad core with the host running Debian Lenny.
Anyone have any idea how to resolve this or what is going on? I have googled a good par tof the day with no answer forthcoming.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.