RE: KVM for Linux 2.6.16?

["Fischer, Anna" <anna.fischer@hp.com>]

> Subject: Re: KVM for Linux 2.6.16?
> 
> 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.

So if I run an ancient Linux kernel, then I can only run with an ancient KVM version? I thought the code was kept backwards compatible to some extend?