• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

question about 64bit guests on 32bit hosts

goodcooper

[H]F Junkie
Joined
Nov 4, 2005
Messages
9,771
i know it can be done with a machine (cpu + bios) capable of VT, but what about memory addressing...

can a 64bit guest address the >4GB that the 32bit host cannot?
 
No, the virtualization software running on the 32-bit host operating system can only use as much ram as the host OS can give it.
 
Not true :) Since you're passing the cpu through, you can use the full 64bit range.
 
?
So if I have a 12gb box with XP 32bit on it, windows seeing 3.25gb when booted up, I can make 2 other Vista64bit guest with 4gb each?
 
I suppose that you could, but that doesn't make a lot of sense to me since the host OS, afaik, is still telling vmware/virtualpc/etc what kind of hardware and such is installed. For instance, I can't connect my iphone to a guest OS unless I have itunes/bonjour installed on the host to pass it through to the guest.

the real question is, why would you run 12gb of memory on a 32bit os? :p
 
I suppose that you could, but that doesn't make a lot of sense to me since the host OS, afaik, is still telling vmware/virtualpc/etc what kind of hardware and such is installed. For instance, I can't connect my iphone to a guest OS unless I have itunes/bonjour installed on the host to pass it through to the guest.

the real question is, why would you run 12gb of memory on a 32bit os? :p

And VMware is ignoring the host OS and talking directly to the CPU :)

ESX 3.X is a 32bit operating system, for instance, too ;)
 
And VMware is ignoring the host OS and talking directly to the CPU :)

So would this be the case on a non-vt enabled chip as well? How does it determine how much memory to save for the host? My experience with virtualization is limited to basic/home stuff

ESX 3.X is a 32bit operating system, for instance, too ;)

I stand corrected lol
 
So would this be the case on a non-vt enabled chip as well? How does it determine how much memory to save for the host? My experience with virtualization is limited to basic/home stuff



I stand corrected lol

Non-VT won't be able to run a 64bit guest on a 32 bit system :)
 
Not true :) Since you're passing the cpu through, you can use the full 64bit range.

Yes, a 64-bit guest running inside of a VM on a 32-bit host can use 64-bit addresses for memory access. However, that address space has to map to physical RAM somewhere. In a hosted system such as VMWare workstation or Server, the host OS manages the mapping of the VM process to physical RAM. Thus, the VM process can only physically address a 32-bit address space.
 
Yes, a 64-bit guest running inside of a VM on a 32-bit host can use 64-bit addresses for memory access. However, that address space has to map to physical RAM somewhere. In a hosted system such as VMWare workstation or Server, the host OS manages the mapping of the VM process to physical RAM. Thus, the VM process can only physically address a 32-bit address space.

so if I understand you correctly, as long as the (32bit) host can use tricks to address all of the memory space, then you can run a 64bit VM with no memory limitations, but if you're using something like XP as the host, you'd still be bound to the 4gb limit?
 
sec...

edit: Yep- this is one of main advantages of VT- it lets the VM use the CPU's memory adressing range, regardless of the host OS. I just built, installed, and ran a Vista64 guest with 6gb of RAM on my XP32 machine. It saw, identified, and used all the memory without an issue. In VMware workstation.

like I said - VT lets you ignore this limitation - it passes the VM process through the host OS straight to the hardware, letting you ignore those limitations.
 
Last edited:
so if I understand you correctly, as long as the (32bit) host can use tricks to address all of the memory space, then you can run a 64bit VM with no memory limitations, but if you're using something like XP as the host, you'd still be bound to the 4gb limit?

If you have VT, there is no limit for your VMs. :)
 
oh ok, thanks for the clarification :) it's good info to know

edit: sorry op :D
 
Back
Top