| 1 |
Brian Wince a écrit : |
| 2 |
> |
| 3 |
>> -----Original Message----- |
| 4 |
>> From: Xavier Parizet [mailto:xav@×××××××××.com] |
| 5 |
>> Sent: Wednesday, April 22, 2009 11:49 PM |
| 6 |
>> To: gentoo-user@l.g.o |
| 7 |
>> Subject: Re: [gentoo-user] trouble installing kvm on gentoo-2.6.24.-r4 |
| 8 |
>> |
| 9 |
>> On Wed, 22 Apr 2009 14:30:54 -0700, Brian Wince <bwince@×××××××.com> |
| 10 |
>> wrote: |
| 11 |
>>> All, |
| 12 |
>>> I am trying to install kvm (kernel virtual machine) on a box running |
| 13 |
>>> gentoo-2.6.24.-r4. |
| 14 |
>>> # uname -a |
| 15 |
>>> Linux rbos-hybrid-02 2.6.24-gentoo-r4-nosctp-nomsi #3 SMP Fri Aug 1 |
| 16 |
>>> 12:12:33 PDT 2008 i686 AMD Athlon(tm) Dual Core Processor 4450e |
| 17 |
>>> AuthenticAMD GNU/Linux |
| 18 |
>>> |
| 19 |
>>> When I first went to install it all of the KVM's were masked due to |
| 20 |
>> EAP |
| 21 |
>> so |
| 22 |
>>> I upgraded portage to 2.1.6.7. |
| 23 |
>>> |
| 24 |
>>> Now when I try and install kvm it complains with the following: |
| 25 |
>>> |
| 26 |
>>>>>> Failed to emerge app-emulation/kvm-84, Log file: |
| 27 |
>> [SNIP] |
| 28 |
>>> * If you need support, post the topmost build error, and the call |
| 29 |
>> stack |
| 30 |
>> if |
| 31 |
>>> relevant. |
| 32 |
>>> * A complete build log is located at |
| 33 |
>>> '/var/tmp/portage/app-emulation/kvm-84/temp/build.log'. |
| 34 |
>>> * The ebuild environment file is located at |
| 35 |
>>> '/var/tmp/portage/app-emulation/kvm-84/temp/environment'. |
| 36 |
>> Can you please post /var/tmp/portage/app-emulation/kvm-84/temp/build.log |
| 37 |
>> after running emerge kvm as portage suggests you ?? |
| 38 |
>> Because the above posted output doesn't help us to solve your problem... |
| 39 |
>> |
| 40 |
>>> I have the following in /etc/portage/package.use app-emulation/kvm kvm |
| 41 |
>> sdl |
| 42 |
>>> qemu |
| 43 |
>>> |
| 44 |
>>> and in package.keywords I have |
| 45 |
>>> app-emulation/kvm ~x86 |
| 46 |
>>> |
| 47 |
>>> Is this due to upgrading portage or something else and what is it that |
| 48 |
>>> needs to be done to make this work. |
| 49 |
>> I don't think the portage upgrade is the problem, but it remind me |
| 50 |
>> another |
| 51 |
>> thread about nvidia-drivers build, and i'm directing towards a kernel |
| 52 |
>> configuration problem... The log i ask you earlier will help us to see |
| 53 |
>> if |
| 54 |
>> it is the case ;) |
| 55 |
>> |
| 56 |
>>> Please let me know if you require further information and I will post |
| 57 |
>> it. |
| 58 |
>>> TIA, |
| 59 |
>>> |
| 60 |
>>> brian |
| 61 |
>> -- |
| 62 |
>> Xavier Parizet |
| 63 |
>> YaGB : http://gentooist.com |
| 64 |
>> GPG : DC81 6FEE 6EBE FCE4 |
| 65 |
>> 1C18 202F E575 4A5D 036D 1408 |
| 66 |
> |
| 67 |
> Xavier, |
| 68 |
> I have attached the build.log. |
| 69 |
> The kernel has KVM configured as modules for both Intel and AMD. |
| 70 |
> CONFIG_KVM=m |
| 71 |
> CONFIG_KVM_INTEL=m |
| 72 |
> CONFIG_KVM_AMD=m |
| 73 |
> |
| 74 |
> Also I doubt the portage version is the problem as I downgraded it to 2.1.4.5 and it still fails in the same way. |
| 75 |
> |
| 76 |
> Please let me know if you need other logs or configs. |
| 77 |
|
| 78 |
After reading the build log you provide, try to enable CONFIG_PCI_MSI |
| 79 |
under Bus options (PCI etc.) -> Message Signaled Interrupts (MSI and |
| 80 |
MSI-X) in make menuconfig for your kernel, and then make prepare et |
| 81 |
retry the KVM emerge. |
| 82 |
|
| 83 |
> |
| 84 |
> brian |
| 85 |
> |
| 86 |
> |
| 87 |
|
| 88 |
|
| 89 |
-- |
| 90 |
Xavier Parizet |
| 91 |
YaGB : http://gentooist.com |
| 92 |
GPG : DC81 6FEE 6EBE FCE4 |
| 93 |
1C18 202F E575 4A5D 036D 1408 |
Archives