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
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 have a PC with AMD FX CPU (Do not remember if it was FX51 or FX60)
it is 64Bit does it means that I can run 64Bit Guests? even if it does not have the Visualization extensions in the CPU?
This is really more of a question for Server Fault, but I don't have enough rep to vote for a move.
Assuming you can even install ESXi 4 on that CPU, it will be able to run a 64bit guest.
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
As some of you may have noticed, a few hours ago Microsoft released Windows 7 RTM to those of us with a Technet or MSDN subscription.
I unfortunately didn't have the opportunity time-wise to test the new OS. I'm asking of anyone who used it with Visual Studio 2008 during RC what was your experience? Did you feel the RC offered a stable environment for it? Did it behave well under Windows 7? In short, can I rely on Windows 7 as my soon-to-be development platform?
On another note, did anyone did any tests the new crt? What were the results?
EDIT: As an afterthought, I'm interested indeed in both 32bit and 64bit experiences, since the OS will go to just one of these machines.
x58 chipset and i7 processing unit, Windows 7 RC x64, I had a lot of issues with programs locking up and crashing (not responding, invoking windows "Ill find out whats wrong! .. not) when you try to close the form. It kills development time.
Especially visual studio 2008, countless crashes and lock ups or delays. It does run good most of the time, but it has its moments.
My experience is that its not 100% solid.
I thought that it was weird, because its built in the Vista SP1 core, and my hardware runs Vista very solid, no hitches -ever-.
And yes, it was a fresh install of Win7, not an upgrade. I'm installing Server R2 though, so I'll see how that works out! :D
edit
I couldn't put my finger on it. Under Vista SP1/SP2 it runs rock solid. The video drivers worked great however for my GTX295, motherboard BIOS is up to date.
I don't think that the problem was driver related per-se, but I can't say. The symptoms purely came across as a software related issue with the OS and how it handles the Windows.
The Event logs are not a help, because a generic form crashing doesn't produce any real detail for me to burn through and say "Ah ha!".
I must say though, it was mostly Visual Studio and forms run under the debugging host process. Anything else was pretty okay, so it could be more or less just a compatibility issue
edit
After a fresh install of Windows Server R2 RC, after the initial installation and a driver install for a wireless adapter, the system fails to boot up properly (or atleast "detects" an problem), so you have to manually tell it to boot Windows up normally, which works.
After doing some Windows updates, same thing, but this time the OS fails even when trying to boot up normally and just does a reboot (probably a blue screen, but surpressed by my BIOS)
My experience with R2 was blazingly fast, both in performance and a drop in satisfaction and warm fuzzies about it working good
It seems that either way you go, on the newest of new hardware, it has its issues. Bummer.
The best way to write Win7 compatible programs is to use Win7 as a development platform. I use Win7 x64 with Visual Studio 2008 almost half a year and it looks pretty stable and has some helpful features (e.g. snap). At this moment all my programs are ready for certification and compliant with all Win7 requirements. I use VirtualBox to test my programs in Windows XP/Vista environment and VirtualBox works without any problems on Win7 too.
My hardware is Intel Q6600 processor on ASUS P5KC motherboard. ATI video card was unstable until some build of drivers, now it works fine. NVidia video card has no problems all the way.
I've been using Visual Studio 2008 under the RC for a while now. No issues at all. For that matter, I don't remember having any under the Beta either.
Windows 7 is good to go for development, as far as I'm concerned.
We've been piloting Windows 7 internally for some time now and have had very few if any troubles with it. I've personally been using it with Visual Studio 2008 (Full and Express) and have been very pleased with the OS overall. I recommend it. (It is fair to note, however, that we use beefy hardware, generally dual or quad core, 4GB RAM and good video cards for our pilot).
I been using windows 7 (x86) for few month now, never had a single problem with that.
Visual Studio 2008, Adobe products, Netbeans and everything else running just fine.
Win7 RC1, VS 2008 SP1 here. The only issue so far is graphical glitches in drawing VisualSVN icons in the Solution Explorer if I scroll the projects tree using mouse wheel.
Also sometimes Tortoise SVN cache crushes. But it might not be related to Windows 7.