Hi, I have a problem installing VMware Workstation 6.0. x86-64 on my 10.0 64-bit. Problem is, that VMware still doesn't want to run 64bit guest systems and also in YAST it still reports architecture as i386. Does anybody know how to install it correctly? Best regards Janko -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Are you building the guest from scratch from w/in VMWare, or trying to
use an already running drive for the VM guest?
I had a similar problem trying to run a Win/XP/64
already-built-and-running disk in VMWare Server (which is compatible
[and free] w/ VMWare WorKstation 5) running under a 32-bit OpenSuSE
10.2 host.
Building a Win/XP/64 small-root disk in VMWare Server, then attaching
the existing disk as a secondary drive worked (I can see all the files
fine... now I need to figure out how to get Windows to see the
programs and users on the old disk and use the old disk for the
program and user space... what would be trivial in Unix can't be done
in WinDoh's).
Also, the community support on the VMWare list servers is really good.
On 9/2/07, Janko Mivšek
Hi,
I have a problem installing VMware Workstation 6.0. x86-64 on my 10.0 64-bit. Problem is, that VMware still doesn't want to run 64bit guest systems and also in YAST it still reports architecture as i386. Does anybody know how to install it correctly?
Best regards Janko -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
I just checked my CPU with Processor Check for 64-Bit Compatibility and it seems that my CPU is too much "semi" 64-bit for VMware. More about that on http://kb.vmware.com/selfservice/dynamickc.do?externalId=1901&sliceId=1&command=show&forward=nonthreadedKC&kcId=1901 Thanks Chris anyway for a help. Janko Chris Worley wrote:
Are you building the guest from scratch from w/in VMWare, or trying to use an already running drive for the VM guest?
I had a similar problem trying to run a Win/XP/64 already-built-and-running disk in VMWare Server (which is compatible [and free] w/ VMWare WorKstation 5) running under a 32-bit OpenSuSE 10.2 host.
Building a Win/XP/64 small-root disk in VMWare Server, then attaching the existing disk as a secondary drive worked (I can see all the files fine... now I need to figure out how to get Windows to see the programs and users on the old disk and use the old disk for the program and user space... what would be trivial in Unix can't be done in WinDoh's).
Also, the community support on the VMWare list servers is really good.
On 9/2/07, Janko Mivšek
wrote: Hi,
I have a problem installing VMware Workstation 6.0. x86-64 on my 10.0 64-bit. Problem is, that VMware still doesn't want to run 64bit guest systems and also in YAST it still reports architecture as i386. Does anybody know how to install it correctly?
Best regards Janko -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-- Janko Mivšek Svetovalec za informatiko Eranova d.o.o. Ljubljana, Slovenija www.eranova.si tel: 01 514 22 55 faks: 01 514 22 56 gsm: 031 674 565 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 02 September 2007 22:16:05 Janko Mivšek wrote:
Hi,
I have a problem installing VMware Workstation 6.0. x86-64 on my 10.0 64-bit. Problem is, that VMware still doesn't want to run 64bit guest systems and also in YAST it still reports architecture as i386. Does anybody know how to install it correctly?
What CPU is in your machine? vmware can only run 64 bit guests on recent chips, with the "full virtualization" feature of the CPU enabled. On AMD, I believe it is revision D or later, and on Xeon you need to enable full virtualization in your BIOS. When you try to run a 64 bit guest in vmware, there is a popup which explains this, together with a link to the vmware knowledge base which explains the reasons for it. If it was too quick for you to read, you can click on the button in the lower right corner, and it will come up in a window which doesn't close automatically If the rpm was really called x86_64, and it still said i386 in YaST, then the people who created the spec file for the rpm most likely forgot to change the text in it. The architecture description is just plain text, so it is entirely possible that whoever built it just forgot to change it -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sun, 2 Sep 2007 22:33:07 +0200, Anders Johansson wrote:
On AMD, I believe it is revision D or later,
Easier to remember: it must be a socket AM2 cpu. Philipp -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (4)
-
Anders Johansson
-
Chris Worley
-
Janko Mivšek
-
Philipp Thomas