I am attempting to get a virtual machine running with Ubuntu Bionic beaver. The first couple times I started one went well. Very easy to install using the image and I would assign more cores to make it faster. I would also give a bit more ram to the VM. I would use these VM's to test certain things then delete them and reset. I assumed that VirtualBox would delete the usage of disk space, ram, and cores. Yet now when I try to create a virtual machine using the same instance of Bionic Beaver, it says that I haven't allocated enough core (though one should be enough?). Is virtual box not freeing up the hardware it uses? That is what it seems like to me from digging around. Thanks for your help. P.S. The VirtualBox version is 5.2.18. The Ubuntu bionic beaver is 18.04.1 LTS. I am running Windows 10 on the host computer
Related
Is it a good practice to install ROS (Robot Operating System ) on Windows 10 using a virtual machine ? Are there any limitations that I would face doing so ?.
I know its a basic and simple question. But as a beginner I think I must get help on here
As far as ROS itself is concerned, running it in a Linux VM should be fine. Depending on your usage you may run into trouble brought by software used alongside ROS.
Gazebo for example will likely run very slowly if at all on a VM (though it's true this again depends on hardware). I was unable to get it to run properly on an Ubuntu VM so I just started using Ubuntu as the host OS.
Try dual booting Windows and Ubuntu if you cannot drop Windows entirely.
I have an XP 32 bit installation on VirtualBox, but whenever I want to increase the cores of the cpu to more than one core, the OS won't boot! What's going on?
These two links might help:
How to change XP VM on virtualbox to have two CPUs without having to reinstall XP
VirtualBox - XP guest does not see multiple cores/multiple processors
You can try ways provided in these two links. If they does not work, you might need to reinstall.
I found the problem! At least in my case.
The problem was that I had "Virtual Machine Platform" feature enabled in Windows features.
I had looked and looked but many nothing said about this, some people said to just turn off Hyper-V which I did but same problem. So I decided to disabled everything that had to do with "virtual" then it worked!
Also I downgraded to WSL1
Don't turn off Hyper-V, otherwise it may give you some problems like slowing down your VM (atleast it did for me).
Disable Virtual Machine Platform
Enable Hyper-V as this allows you to run WSL and Virtual machine together
And if you really want WSL also enable "Windows Subsystem for Linux"
Downgrade to WSL1
I'm running Python 2.7 with Pandas, everything installed
with Anacondas Win 32bit distribution.
I got 4GB RAM, around 3GB are effectively used by WinXP on my machine.
Whenever I'm running scripts and the free accessable RAM drops below
1 GB there is a memory error thrown by the Python console.
No windows errors are observed.
Are there any known issues related to WIndows 32 Bit, WInXP and the use of Python?
I have Ubuntu 8.04 running on a Xen based VPS server that runs on a dual-core AMD Opteron 64-bit machine.
I have some locally developed C++ based daemons that I would want to deploy in that machine. My local machine is a 32 bit Ubuntu 9.04 running on an Intel core 2 duo laptop.
Can I execute binaries compiled from source code on my machine directly on the above mentioned server?
I am a newbie in this area. Would be great if someone could throw light on the standard practices in this kind of situation.
Thanks in advance
Xen is a hypervisor on top of which OSes are expected to run. It isn't an OS itself, in the normal sense of the word, and you can't build stuff to run on it. Unless the "stuff" is an OS, of course.
EDIT: Since Ubuntu is running inside the hypervisor, Xen itself is somewhat irrelevant. Pretty much anything you can do inside a normal Ubuntu install you can also do inside a Xen-hosted Ubuntu.
WRT deploying 9.04-built code onto an 8.04 system, it will often just work, though you can hit problems with library dependencies. One trick that may help mitigate this if you get into problems is to use debootstrap (apt-get it). It allows you to deploy a minimal Ubuntu or Debian version of your choice into a chroot environment. I've never used it, so caveat lector. A more heavyweight, but cleaner, option is to run a VM on your own system (e.g., Sun VirtualBox) and run 8.04 on it for doing release builds.
It is best to develop with the same OS that you deploy on to minimize differences due to configuration and libraries. It might work, but it could also break in the future when updated libraries are installed. I suggest you get on the same OS or simply recompile the source on the target server
I am trying to run VMWare Workstation 6.5.1 on Vista 64. It runs, but always as a *32 task. It is supposed to run as a native 64 bit task. I have uninstalled and reinstalled with no change. Any ideas?
Machine is a ASUS P5K, Intel Q6600 cpu, 8 GB RAM.
Thanks for any insight.
VMWare runs as a 32 bit task, but can still run 64 bit applications if you are running on hardware the supports the VT extensions. It can also access more than 4GB of memory because it plays a lot of tricks in the background.
Not sure what it is "supposed" to do, but mine runs the same as yours. Haven't had any problems with it either - in fact I am totally impressed with it having had it for just 2 weeks now. Amazing product.
I have a collegue with a very similar configuration, vista 64, vmware workstation 6.5. His VMS run as native 64 bit tasks in taskman. I have also seen other threads on the net that complain of the same issue. It appears that vmware workstation can indeed run as a native 64bit task and that there is a noticable performance difference yet no one seems to know how or why it sometimes runs as *32.