02-23-2010
To run 64 bit guests, VirtualBox needs a 64 bit CPU with hardware virtualization support (VT-x). The T4300 processor does not offer this feature.
8 More Discussions You Might Find Interesting
1. Solaris
Dear All,
This is Viswanadhan, new to Sun Solaris domain.
In Sun Solaris ( SPARC ) has 32 bit and 64 bit OS. While insallation of OS there no specific option for 32 / 64 bit OS .On which basis OS installs for 32 / 64 bit OS ?
Regards,
Viswanadhan. (1 Reply)
Discussion started by: viswanadhan
1 Replies
2. Solaris
I had previous implemented the following in my menu.lst to be able to get to 32-bit operations.
#
title Solaris 10 32-bit
root (hd0,0,a)
kernel /platform/i86pc/multiboot kernel/unix
module /platform/i86pc/boot_archive
</code>
Now, it is not working as I get the following error :
... (0 Replies)
Discussion started by: praveenr
0 Replies
3. Solaris
Hi,
I am trying to convert 32-bit code to 64-bit.
I have defined function
int main()
{
int* l;
size_t len1;
fun(len1);
return 0;
}
void fun(int* ptr)
{
cout<<"\nsizeof(ptr)"<<sizeof(ptr);
}
However while compiling getting error as :
Error: Formal argument ptr... (2 Replies)
Discussion started by: amit_27
2 Replies
4. Solaris
I have an Ultra 24 with Solaris 10 U6 with the latest patches. I'm running VirtualBox 2.1.0 with Windows 2003 as the guest. What I'm trying to do is have the Windows VM start at Solaris startup. I had a simple script that was working that was in /etc/init.d and linked to /etc/rc3.d. For some reason... (2 Replies)
Discussion started by: Lespaul20
2 Replies
5. Solaris
:confused:
how to find out wether my os is 32 bit or 64 bit. I am using Solaris 5.6.
also i want to know the difference between 32 bit and 64bit os.
any help will be much appreciated as i am in urgent need of this information (6 Replies)
Discussion started by: asalman.qazi
6 Replies
6. UNIX for Dummies Questions & Answers
Hi Gurus
can I emulate solaris/sparc on virtualbox? Or other emulator to run solaris for sparc in my win7 PC?
regards,
Israel. (9 Replies)
Discussion started by: iga3725
9 Replies
7. UNIX for Dummies Questions & Answers
I have a VirtualBox w2008r2 Domain Controller running on a Solaris 10 server. I have the time on the Virtual machine set to Default time sync (bios clock) and the Solaris server set to sync to
0 8,20 * * * /usr/sbin/ntpdate tick.usno.navy.mil tock.usno.navy.mil >> /tmp/ntp.log
My problem is... (2 Replies)
Discussion started by: SIFT3R
2 Replies
8. Solaris
Hi there,
I am new to this operating system, so would like to ask for directions on how to go about doing Solaris 10 dual boot with freeBSD on a virtual machine (virtualbox).
Do you have to partition the disk to allow for another OS to occupy? Like in windows? I tried doing this but failed... (6 Replies)
Discussion started by: czy
6 Replies
LEARN ABOUT DEBIAN
openssl_ia32cap
OPENSSL_ia32cap(3SSL) OpenSSL OPENSSL_ia32cap(3SSL)
NAME
OPENSSL_ia32cap - finding the IA-32 processor capabilities
SYNOPSIS
unsigned long *OPENSSL_ia32cap_loc(void);
#define OPENSSL_ia32cap (*(OPENSSL_ia32cap_loc()))
DESCRIPTION
Value returned by OPENSSL_ia32cap_loc() is address of a variable containing IA-32 processor capabilities bit vector as it appears in EDX
register after executing CPUID instruction with EAX=1 input value (see Intel Application Note #241618). Naturally it's meaningful on
IA-32[E] platforms only. The variable is normally set up automatically upon toolkit initialization, but can be manipulated afterwards to
modify crypto library behaviour. For the moment of this writing six bits are significant, namely:
1. bit #28 denoting Hyperthreading, which is used to distiguish
cores with shared cache; 2. bit #26 denoting SSE2 support; 3. bit #25 denoting SSE support; 4. bit #23 denoting MMX support; 5. bit #20,
reserved by Intel, is used to choose between RC4 code
pathes; 6. bit #4 denoting presence of Time-Stamp Counter.
For example, clearing bit #26 at run-time disables high-performance SSE2 code present in the crypto library. You might have to do this if
target OpenSSL application is executed on SSE2 capable CPU, but under control of OS which does not support SSE2 extentions. Even though you
can manipulate the value programmatically, you most likely will find it more appropriate to set up an environment variable with the same
name prior starting target application, e.g. on Intel P4 processor 'env OPENSSL_ia32cap=0x12900010 apps/openssl', to achieve same effect
without modifying the application source code. Alternatively you can reconfigure the toolkit with no-sse2 option and recompile.
1.0.1e 2013-02-11 OPENSSL_ia32cap(3SSL)