1 |
On Thu, Aug 01, 2013 at 08:41:56AM +0200, Michael Hampicke wrote |
2 |
|
3 |
> You can use march=native on your gentoo hosts, that's no problem, as |
4 |
> long as you don't use it on your guests. That's the hole idea of VMs: |
5 |
> being able to move the virtual machine to another machine, that might be |
6 |
> completely different in terms of hardware. The goal is, to be machine |
7 |
> independent. |
8 |
|
9 |
I want to clarify one item, so please pardon me if it looks like I'm |
10 |
asking the same question over again. Assume that I launch QEMU with |
11 |
"-cpu core2duo" and set "-march=native" in the guest's make.conf. My |
12 |
understanding is that the gcc compiler on the guest will see a core2duo, |
13 |
not the physical i5 cpu on my desktop. |
14 |
|
15 |
We may be looking at different ways of doing the same thing. You're |
16 |
suggesting "-march=core2" in the guest's make.conf. I'm suggesting |
17 |
"-march=native" in the guest's make.conf, which would pick up the cpu |
18 |
type that QEMU sets (cor2duo). I'm trying to make things simpler, by |
19 |
only having to specify the cpu type once, on the QEMU commandline, and |
20 |
leaving gcc to adapt to the QEMU-specified cpu. |
21 |
|
22 |
-- |
23 |
Walter Dnes <waltdnes@××××××××.org> |
24 |
I don't run "desktop environments"; I run useful applications |