public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: Chris Friesen <chris.friesen@genband.com>
Cc: David Ahern <dsahern@gmail.com>, Avi Kivity <avi@redhat.com>,
	mtosatti@redhat.com, kvm@vger.kernel.org
Subject: Re: help?  need to enable VT-d for 2.6.27
Date: Tue, 30 Aug 2011 21:59:57 +0200	[thread overview]
Message-ID: <4E5D413D.1070700@web.de> (raw)
In-Reply-To: <4E5D3C67.1020908@genband.com>

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

On 2011-08-30 21:39, Chris Friesen wrote:
> On 08/30/2011 12:31 PM, David Ahern wrote:
> 
>> In my case I am setting the MAC address for the VFs in the host at boot;
>> they are getting reset on passthrough so the VM driver creates a random
>> one. A backport of commit a6b5ea3 fixes one aspect. Looking at the code
>> for the igb driver I think commit 8fa7e0f fixes the other reset problem.
>>
>> On the plus side I can tell you that the VF driver for the VM
>>    http://sourceforge.net/projects/e1000/files/igbvf%20stable/
>>
>> compiles cleaning against WRL3 and appears to work fine (limited testing
>> with benchmarks).
>>
>> kernel module wise I ran some basic KVM tests with kvm-kmod-2.6.32.27; I
>> have not tried VF passthrough. This is on my radar as well, so I would
>> be interested in what you learn.
> 
> I downloaded the latest kvm-kmod release.  It looks interesting, but it
> has some issues:
> 
> 1) I use separate source and build output directories.  kvm-kmod assumes
> that there is a "source" link in my build output directory pointing back
> to the source directory.  This doesn't exist, so the build breaks.

That's at least how recent vanilla kernels work. I think to remember
that my old OpenSUSE 11.1 (2.6.27) used to work fine with kvm-kmod as
well, and that was an out-of-tree setup too (but maybe a post-processed
one).

Anyway, if you have some patch to fix this, it will always be welcome.

> 
> 2) If I create such a link, it builds a few files, and then gives the
> following:
> 
> /home/cfriesen/Download/kvm-kmod-3.0b/x86/x86.c: In function
> ‘vcpu_enter_guest’:
> /home/cfriesen/Download/kvm-kmod-3.0b/x86/x86.c:5539:26: error:
> ‘prof_on’ undeclared (first use in this function)
> /home/cfriesen/Download/kvm-kmod-3.0b/x86/x86.c:5539:26: note: each
> undeclared identifier is reported only once for each function it appears in
> 
> 
> This appears to be due to the fact that KVM_PROFILING is defined
> unconditionally in my kernel, but "prof_on" is only defined if
> CONFIG_PROFILING is enabled.  Commenting out that chunk of code in x86.c
> lets everything build.

If CONFIG_PROFILING is off, prof_on is defined to 0. But we may miss
some include on older kernels. Does adding linux/profile.h to x86.c
solve the issue as well?

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

  parent reply	other threads:[~2011-08-30 20:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-30 16:29 help? need to enable VT-d for 2.6.27 Chris Friesen
2011-08-30 17:55 ` David Ahern
2011-08-30 18:11   ` Chris Friesen
2011-08-30 18:31     ` David Ahern
2011-08-30 19:39       ` Chris Friesen
2011-08-30 19:54         ` David Ahern
2011-08-30 19:59         ` Jan Kiszka [this message]
2011-08-30 23:03           ` Chris Friesen
2011-08-31  7:30             ` Jan Kiszka
2011-08-31  0:03           ` [BUG] error compiling qemu-kvm-0.15.0 without vnc Chris Friesen
2011-08-31  7:40             ` Jan Kiszka
2011-08-31  8:14               ` Kevin Wolf
2011-08-31 20:11                 ` [Qemu-devel] " Justin M. Forbes

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=4E5D413D.1070700@web.de \
    --to=jan.kiszka@web.de \
    --cc=avi@redhat.com \
    --cc=chris.friesen@genband.com \
    --cc=dsahern@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    /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