When I use it (its source code is available at https://github.com/Zero3K/ERAM) in a Windows 10 64-bit virtual machine (in driver signature enforcement disabled mode) with it configured to use 100 MB for a RAM Disk and is set as a fixed disk via its cpl, I get a FAT_FILE_SYSTEM blue screen that does not happen in a Windows 7 64-bit virtual machine. Maybe someone could look at its source code to see what is causing it and then offer a fix.
Related
Simple question: Is it dangerous to activate KSM on a running hypervisor (Debian 8 with 3.16 kernel)?
Or is it recommended to shut down all virtual machines (KVM/qemu) first, then activate KSM and then start the virtual machines again?
We expect a memory saving of approx. 50% (we have a similar system where KSM is already active and there we effectively save almost 50% due to the always very similar VM appliances).
I updated to Windows 10 Fall and it destroyed my entire virtual network. It removed my previous virtual switch and created a "Default Switch." It would not allow me to create a new External Virtual Switch.
So I wiped the machine, put a fresh install of windows on there, did all the updates, and I could finally create that External Virtual Switch. The only issue is that when that External Virtual Switch exists, it takes my host's download speed a reduces it to like 1 mb a second (on a 800 mb/s connection).
Anyone know how I can fix this issue?
After applying RHSA-2013:0911:R6-32 (Important: Red Hat Enterprise Linux 6 kernel update), tomcat refuses to start with a
Error occurred during initialization of VM
Could not reserve enough space for object heap
Could not create the Java virtual machine.
error in the catalina.out log.
In our particular environment, we are using RHEL 32 bits with 2 GB RAM machines. The new kernel is: 2.6.32-358.11.1.el6.i686
The config is pretty default, only a -XX:MaxPermSize=1024M is configured. (I know, it's high). If I decrease that value less than 800M, tomcat starts.
If I boot with the previous kernel (2.6.32-358.6.2.el6.i686) , tomcat starts.
It looks the new kernel changed some memory allocation behaviour...Are there more people with mem issues?
I had the same issue on Centos 32bit using this kernel, as well as the most recent one kernel-firmware-2.6.32-358.14.1.el6. http://bugs.centos.org/view.php?id=6529 suggests using sysctl vm.unmap_area_factor=1 to influence how memory is allocated. However, it didn't do the trick for me. I'll migrate to a 64 bit installation now.
Has anyone tried to get Windows 7/8 running on linux with the Microsoft Virtual PC download directly from Microsoft? It doesn't seem to be working using the default Boxes or Virtual Machine (QEMU) in CentOS / Red Hat?
SETTINGS:
Base Memory 1024 MB
Video Memory 128 MB
Network Adapter: Intel PRO/1000 MT Desktop (NAT)
Windows Virtual Box (from Microsoft)
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=11575
forward to http://dev.modern.ie/
Is there any chance Microsoft or modern.ie will just release an iso install rather then a native Virtual System File?
It sounds like you're trying to get Microsoft's IE Virtual PC images working in VirtualBox (not Virtual PC itself).
Luckily there is a tool available to automate the process of converting the images and getting them to work in VirtualBox. Take a look at ievms.
Check http://www.modern.ie/en-us/virtualization-tools#downloads
This images are legal as modern.ie launched by Microsoft.
Site provide a wide range of up-today Windows images for Windows/Mac/Linux.
Microsoft Virtual PC downloads from http://dev.modern.ie/ (MS) only support Virtual Box on linux and not the Virtual Machine Manager that comes with CentOS.
I use this windows API,
http://msdn.microsoft.com/en-us/library/aa366589(v=vs.85).aspx
GlobalMemoryStatusEx to get memory information
my computer total physcial memory is 4096MB ,why the program shows 3.XG
My computer's virtual memory is 3063MB ,but i use program which show 2047MB
my develop enviroment is visual studio 2008
how to modify this problem
thanks
Aren't other programs using your system as well? I suspect the memory you're "missing" is due to the OS itself and whatever other programs you're running. See if having a bunch of other applications open changes the virtual memory size that your program is able to see.
Assuming you are running a 32bit version of windows, then this is a limit of windows itself. See this Microsoft page for the details. By default you will only be able to access 2GB of RAM in a single process. There is a compiler switch in visual studio which will give you access to 3GB. This is the /LARGEADDRESSAWARE switch. Beyond that you just need to upgrade to a 64bit operating system.
By the way, the basic reason why you don't automatically get 4GB of address space is because part of it is reserved for the operating system. Those system calls and references to operating system resources have to live somewhere.