kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Cristi Magherusan <Cristi.Magherusan@net.utcluj.ro>
To: "Fischer, Anna" <anna.fischer@hp.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: KVM for Linux 2.6.16?
Date: Thu, 09 Jul 2009 20:49:18 +0300	[thread overview]
Message-ID: <1247161758.28820.40.camel@localhost.localdomain> (raw)
In-Reply-To: <0199E0D51A61344794750DC57738F58E67D4F30729@GVW1118EXC.americas.hpqcorp.net>

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

On Thu, 2009-07-09 at 16:49 +0000, Fischer, Anna wrote:
> Hi, I am trying to compile the kvm-87 module for Linux 2.6.16. I thought that it has been back-ported to such an old kernel. However, I don't seem to be able to compile the module on my kernel. I get the following error:
> 
>   CC    tsc2005.o
>   CC    scsi-disk.o
>   CC    cdrom.o
>   CC    scsi-generic.o
>   CC    usb.o
>   CC    usb-hub.o
>   CC    usb-linux.o
> In file included from usb-linux.c:41:
> /usr/include/linux/usbdevice_fs.h:49: error: expected ':', ',', ';', '}' or '__attribute__' before '*' token
> /usr/include/linux/usbdevice_fs.h:56: error: expected ':', ',', ';', '}' or '__attribute__' before '*' token
> /usr/include/linux/usbdevice_fs.h:66: error: expected ':', ',', ';', '}' or '__attribute__' before '*' token
> /usr/include/linux/usbdevice_fs.h:100: error: expected ':', ',', ';', '}' or '__attribute__' before '*' token
> /usr/include/linux/usbdevice_fs.h:116: error: expected ':', ',', ';', '}' or '__attribute__' before '*' token
> usb-linux.c: In function 'async_complete':
> usb-linux.c:271: error: 'struct usbdevfs_urb' has no member named 'actual_length'
> usb-linux.c: In function 'usb_host_handle_data':
> usb-linux.c:464: error: 'struct usbdevfs_urb' has no member named 'buffer'
> usb-linux.c:465: error: 'struct usbdevfs_urb' has no member named 'buffer_length'
> usb-linux.c:471: error: 'struct usbdevfs_urb' has no member named 'number_of_packets'
> usb-linux.c:472: error: 'struct usbdevfs_urb' has no member named 'iso_frame_desc'
> usb-linux.c:478: error: 'struct usbdevfs_urb' has no member named 'usercontext'
> usb-linux.c: In function 'usb_host_handle_control':
> usb-linux.c:598: error: 'struct usbdevfs_urb' has no member named 'buffer'
> 
> 
> Is KVM not supposed to work on 2.6.16?
Hi Anna,

I'm afraid that I have some bad news for you. Usually KVM versions are
tailored to kernel versions contemporary with them. Version 87 is
supposed to need 2.6.26 kernels and newer, IIRC. So for your 2.6.16 you
should try some of the incipient KVM versions, and if you are lucky
enough, they might work.

Anyway, are you so tied to that specific kernel version?

Regards,
Cristi

-- 
Ing. Cristi Măgherușan, System/Network Engineer
Technical University of Cluj-Napoca, Romania
http://cc.utcluj.ro  +40264 401247

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  parent reply	other threads:[~2009-07-09 17:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-09 16:49 KVM for Linux 2.6.16? Fischer, Anna
2009-07-09 17:44 ` Alexander Graf
2009-07-09 17:49 ` Cristi Magherusan [this message]
2009-07-09 18:22   ` Fischer, Anna
2009-07-09 19:27     ` Alexander Graf
2009-07-12  6:02   ` Avi Kivity
2009-07-16 22:27 ` Anthony Liguori

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=1247161758.28820.40.camel@localhost.localdomain \
    --to=cristi.magherusan@net.utcluj.ro \
    --cc=anna.fischer@hp.com \
    --cc=kvm@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).