using in a virtual machine

[calepososepo]

hello everyone,
reading some various threads about bans, on how blizz big brother warden is working i stated something that may or may not be confirmed.

why not running the whole thing - d3 + DB in a virtual machine, since warden is looking in ram, i guess it can not actually read the virtually allocated RAM in a VM since its stored in a different manner. i'm not technical engineer so far but it sounds to me that this trick adds an other "layer" to the memory. COMP RAM > VM LAYER > VM RAM

i guess some people here already played with VMs so why not giving it a try ?! or at least digg the question.


/sry bad english i'm tired and not native XD

2.3 Memory Management Basics in ESX
Prior to talking about how ESX manages memory for virtual machines, it is useful to first understand how the application, guest
operating system, hypervisor, and virtual machine manage memory at their respective layers.
• An application starts and uses the interfaces provided by the operating system to explicitly allocate or deallocate the virtual
memory during the execution.
• In a non-virtual environment, the operating system assumes it owns all physical memory in the system. The hardware does not
provide interfaces for the operating system to explicitly “allocate” or “free” physical memory. The operating system establishes
the definitions of “allocated” or “free” physical memory. Different operating systems have different implementations to realize this
abstraction. One example is that the operating system maintains an “allocated” list and a “free” list, so whether or not a physical
page is free depends on which list the page currently resides in.
• Because a virtual machine runs an operating system and several applications, the virtual machine memory management properties
combine both application and operating system memory management properties. Like an application, when a virtual machine
first starts, it has no pre-allocated physical memory. Like an operating system, the virtual machine cannot explicitly allocate host
physical memory through any standard interfaces. The hypervisor also creates the definitions of “allocated” and “free” host memory
in its own data structures. The hypervisor intercepts the virtual machine’s memory accesses and allocates host physical memory for
the virtual machine on its first access to the memory. In order to avoid information leaking among virtual machines, the
hypervisor always writes zeroes to the host physical memory before assigning it to a virtual machine.
• Virtual machine memory deallocation acts just like an operating system, such that the guest operating system frees a piece of
physical memory by adding these memory page numbers to the guest free list, but the data of the “freed” memory may not be
modified at all. As a result, when a particular piece of guest physical memory is freed, the mapped host physical memory will
usually not change its state and only the guest free list will be changed.
The hypervisor knows when to allocate host physical memory for a virtual machine because the first memory access from the virtual
machine to a host physical memory will cause a page fault that can be easily captured by the hypervisor. However, it is difficult for the
hypervisor to know when to free host physical memory upon virtual machine memory deallocation because the guest operating system
free list is generally not publicly accessible. Hence, the hypervisor cannot easily find out the location of the free list and monitor its changes.
Although the hypervisor cannot reclaim host memory when the operating system frees guest physical memory, this does not mean
that the host memory, no matter how large it is, will be used up by a virtual machine when the virtual machine repeatedly allocates
and frees memory. This is because the hypervisor does not allocate host physical memory on every virtual machine’s memory allocation.
It only allocates host physical memory when the virtual machine touches the physical memory that it has never touched before. If a virtual
machine frequently allocates and frees memory, presumably the same guest physical memory is being allocated and freed again
and again. Therefore, the hypervisor just allocates host physical memory for the first memory allocation and then the guest reuses

its white paper from ESX wich is an advanced Virtualisation software but i guess -again- that it works the same on the basic product.
http://www.vmware.com/files/pdf/perf-vsphere-memory_management.pdf


------
old but still
[video=youtube;HPiLDkMO3co]https://www.youtube.com/watch?v=HPiLDkMO3co[/video]

 

[calepososepo]

bump, easy game,
after a software update, installing w7x64 in a vm you juste have to setup DB again to match your new folders. run diablo3 in windowed mode
DisplayModeWindowMode "1" to add to the D3pref.ini

and that's it.

 

[stud4fun]

I have been playing D3 in VM workstation over many years. It is not guaranteed playing in VM for Ban free.
I heard some people got banned even using VM machine. I was shocked too