public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Jason Weisberger" <jbdubbs@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Gentoo VMWare image works on Intel but not AMD. Are they not interchangeable?
Date: Wed, 7 Feb 2007 00:05:35 -0500	[thread overview]
Message-ID: <f05c493b0702062105y6c743822i7d6b1f9d475018c7@mail.gmail.com> (raw)
In-Reply-To: <BRAKA8jbI8bP80sU1x500004a20@mx1.lockdownnetworks.com>

[-- Attachment #1: Type: text/plain, Size: 2242 bytes --]

Daevid,

If your Gentoo installation was compiled with march=p4 or the like, your
image will not work on an AMD machine.  The way to have them interchangeable
is to use march=i686 mtune=p4, that way there are no cpu-specific
instructions compiled into your binaries.  mtune will just adjust the
scheduling to fit the pipeline of your most used arch.  The one piece of
hardware that cannot be virtualized on an x86 machine is unfortunately the
cpu, unless of course you're running a new cpu with Intel Virtualization or
AMD's Pacifica.  Even then, it can't deal with incompatible binaries.
You'll not just have to recompile your kernel, but your entire system with
the new cflags for it to work interchangeably.

Jason Weisberger

On 2/5/07, Daevid Vincent <daevid@daevid.com> wrote:
>
> I have a VMWare Workstation image of Gentoo Linux that I transfer between
> my
> desktop and my notebook (for LAMP/Ruby development) and it works fantastic
> on both. Both are running WindowsXP as the host VMWare. Both are Pentium4.
>
>
> Recently, I tried to share the image with a co-worker and it pukes out
> about
> the time it does some udev stuff at the top of starting up. The (rc.init?)
> scripts start breaking and spewing lots of errors and ultimately doesn't
> mount the filesystem properly. We are able to manually mount it later, but
> then lost of other things are broken. VMware doesn't have any errors we
> could find, not even in the logs. It seems to be an OS issue.
>
> Does the host CPU make a difference? I thought it was all emulated? I
> tried
> to recompile the kernel with the generic '386 CPU settings and removed all
> power mgmt etc, and the same issue happens.
>
> Can I not transfer between Intel and AMD CPUs? Is there some magic thing
> in
> the kernel I need to set so it can work on both?
>
> We attempted several times and tried using VMWare player and also VMWare
> workstation.
>
> It would really suck to have to have him re-compile everything just to get
>
> the same dev environment setup as mine.
>
> I also posted this on the VMWare forums in case anyone cares:
> http://www.vmware.com/community/thread.jspa?threadID=71079
>
> --
> gentoo-user@gentoo.org mailing list
>
>


-- 
Jason Weisberger
jbdubbs@gmail.com

[-- Attachment #2: Type: text/html, Size: 3080 bytes --]

      parent reply	other threads:[~2007-02-07  5:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AcdJgjNiEdO5BU1qTtK7xKDK55KmfQ==>
2007-02-06  0:03 ` [gentoo-user] Gentoo VMWare image works on Intel but not AMD. Are they not interchangeable? Daevid Vincent
     [not found]   ` <200702060927.01189.alan@linuxholdings.co.za>
     [not found]     ` <op.tnbj5pydv2ynd8@gak>
2007-02-06 12:58       ` Alan McKinnon
2007-02-07  5:05   ` Jason Weisberger [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f05c493b0702062105y6c743822i7d6b1f9d475018c7@mail.gmail.com \
    --to=jbdubbs@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox