From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alexander Graf Subject: Re: KVM for Linux 2.6.16? Date: Thu, 9 Jul 2009 21:27:50 +0200 Message-ID: References: <0199E0D51A61344794750DC57738F58E67D4F30729@GVW1118EXC.americas.hpqcorp.net> <1247161758.28820.40.camel@localhost.localdomain> <0199E0D51A61344794750DC57738F58E67D4F3074F@GVW1118EXC.americas.hpqcorp.net> Mime-Version: 1.0 (Apple Message framework v935.3) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Cc: Cristi Magherusan , "kvm@vger.kernel.org" To: "Fischer, Anna" Return-path: Received: from cantor2.suse.de ([195.135.220.15]:52155 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752775AbZGIT2B (ORCPT ); Thu, 9 Jul 2009 15:28:01 -0400 In-Reply-To: <0199E0D51A61344794750DC57738F58E67D4F3074F@GVW1118EXC.americas.hpqcorp.net> Sender: kvm-owner@vger.kernel.org List-ID: On 09.07.2009, at 20:22, Fischer, Anna wrote: >> 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? It is, but nobody really tested it on such old systems I think. The issue you're running into is in userland though and related to usb passthrough. So you should be able to get away with disabling HOST_USB in your config-host.mak file. May I ask again why you need to have things running on 2.6.16? Alex