Hi there I have an opensuse10.3 domU running as a HVM guest on xen 3.2.1 No I would like to install the PV drivers to get better performance on disk IO. The Problem is that I do not manage to compile the drivers: linux-inna:~ # uname -a Linux linux-inna 2.6.22.17-0.1-default #1 SMP 2008/02/10 20:01:04 UTC i686 i686 i386 GNU/Linux linux-inna:/mnt/xen-3.2-testing.hg/unmodified_drivers/linux-2.6 # make -C /lib/modules/2.6.22.17-0.1-default/build M=$PWD modules make: Entering directory `/usr/src/linux-2.6.22.17-0.1-obj/i386/default'' make -C ../../../linux-2.6.22.17-0.1 O=../linux-2.6.22.17-0.1-obj/i386/default modules CC [M] /mnt/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.o In file included from /mnt/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.c:48: /mnt/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/asm/hypervisor.h: In function ‘HYPERVISOR_shutdown’: /mnt/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/asm/hypervisor.h:191: error: implicit declaration of function ‘VOID’ /mnt/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.c:101:58: error: macro "DECLARE_WORK" passed 3 arguments, but takes just 2 /mnt/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.c: At top level: /mnt/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.c:101: warning: type defaults to ‘int’ in declaration of ‘DECLARE_WORK’ /mnt/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.c: In function ‘balloon_alarm’: /mnt/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.c:186: error: ‘balloon_worker’ undeclared (first use in this function) /mnt/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.c:186: error: (Each undeclared identifier is reported only once /mnt/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.c:186: error: for each function it appears in.) /mnt/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.c: In function ‘balloon_set_new_target’: /mnt/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.c:425: error: ‘balloon_worker’ undeclared (first use in this function) /mnt/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.c: In function ‘alloc_empty_pages_and_pagevec’: /mnt/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.c:671: error: ‘balloon_worker’ undeclared (first use in this function) /mnt/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.c: In function ‘free_empty_pages_and_pagevec’: /mnt/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.c:704: error: ‘balloon_worker’ undeclared (first use in this function) /mnt/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.c: In function ‘balloon_release_driver_page’: /mnt/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.c:716: error: ‘balloon_worker’ undeclared (first use in this function) make[4]: *** [/mnt/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.o] Fehler 1 make[3]: *** [/mnt/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/balloon] Fehler 2 make[2]: *** [_module_/mnt/xen-3.2-testing.hg/unmodified_drivers/linux-2.6] Fehler 2 make[1]: *** [modules] Fehler 2 make: *** [modules] Fehler 2 make: Leaving directory `/usr/src/linux-2.6.22.17-0.1-obj/i386/default'' Is there anything I misunderstood? (I''m not THAT used to xen...) Regards Sebastian Ries -- ------------------------------------------------------------ DT Netsolution GmbH - Talaeckerstr. 30 - D-70437 Stuttgart Tel: +49-711-849910-36 Fax: +49-711-849910-936 WEB: http://www.dtnet.de/ email: Sebastian.Ries@dtnet.de _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Do you have a reason for not running OpenSuSE 10.3 in Paravirtualized mode instead of in an HVM? -Nick>>> On 2008/05/29 at 05:57, Sebastian Ries <Sebastian.Ries@dtnet.de>wrote: Hi there I have an opensuse10.3 domU running as a HVM guest on xen 3.2.1 No I would like to install the PV drivers to get better performance on disk IO. The Problem is that I do not manage to compile the drivers: linux-inna:~ # uname -a Linux linux-inna 2.6.22.17-0.1-default #1 SMP 2008/02/10 20:01:04 UTC i686 i686 i386 GNU/Linux linux-inna:/mnt/xen-3.2-testing.hg/unmodified_drivers/linux-2.6 # make -C /lib/modules/2.6.22.17-0.1-default/build M=$PWD modules make: Entering directory `/usr/src/linux-2.6.22.17-0.1-obj/i386/default' make -C ../../../linux-2.6.22.17-0.1 O=../linux-2.6.22.17-0.1-obj/i386/default modules CC [M] /mnt/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.o In file included from /mnt/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.c:48: /mnt/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/asm/hypervisor.h: In function *HYPERVISOR_shutdown*: /mnt/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/asm/hypervisor.h:191: error: implicit declaration of function *VOID* /mnt/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.c:101:58: error: macro "DECLARE_WORK" passed 3 arguments, but takes just 2 /mnt/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.c: At top level: /mnt/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.c:101: warning: type defaults to *int* in declaration of *DECLARE_WORK* /mnt/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.c: In function *balloon_alarm*: /mnt/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.c:186: error: *balloon_worker* undeclared (first use in this function) /mnt/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.c:186: error: (Each undeclared identifier is reported only once /mnt/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.c:186: error: for each function it appears in.) /mnt/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.c: In function *balloon_set_new_target*: /mnt/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.c:425: error: *balloon_worker* undeclared (first use in this function) /mnt/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.c: In function *alloc_empty_pages_and_pagevec*: /mnt/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.c:671: error: *balloon_worker* undeclared (first use in this function) /mnt/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.c: In function *free_empty_pages_and_pagevec*: /mnt/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.c:704: error: *balloon_worker* undeclared (first use in this function) /mnt/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.c: In function *balloon_release_driver_page*: /mnt/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.c:716: error: *balloon_worker* undeclared (first use in this function) make[4]: *** [/mnt/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.o] Fehler 1 make[3]: *** [/mnt/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/balloon] Fehler 2 make[2]: *** [_module_/mnt/xen-3.2-testing.hg/unmodified_drivers/linux-2.6] Fehler 2 make[1]: *** [modules] Fehler 2 make: *** [modules] Fehler 2 make: Leaving directory `/usr/src/linux-2.6.22.17-0.1-obj/i386/default' Is there anything I misunderstood? (I'm not THAT used to xen...) Regards Sebastian Ries -- ------------------------------------------------------------ DT Netsolution GmbH - Talaeckerstr. 30 - D-70437 Stuttgart Tel: +49-711-849910-36 Fax: +49-711-849910-936 WEB: http://www.dtnet.de/ email: Sebastian.Ries@dtnet.de This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Am Donnerstag, den 29.05.2008, 06:06 -0600 schrieb Nick Couchman:> Do you have a reason for not running OpenSuSE 10.3 in Paravirtualized > mode instead of in an HVM?Unfortunately yes. We are developing a management system to automatically create and destroy domUs as they are needed. Therefore we need to have a common handling off ALL domUs including e.g. being able to connect to the console via VNC an such things. Therefore the minimal common manner is to have ALL domUs fully virtualized (as paravirtualization) is not possible with all domUs :-( Regards Sebastian Ries -- ------------------------------------------------------------ DT Netsolution GmbH - Talaeckerstr. 30 - D-70437 Stuttgart Tel: +49-711-849910-36 Fax: +49-711-849910-936 WEB: http://www.dtnet.de/ email: Sebastian.Ries@dtnet.de _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi, I got it working on a Pardus 2007.3 Linux DomU with 2.6.18 kernel (disto specific). Did you read the README file over there? You need to run a command before "make" and you need to give some parameters to the make command also. Also make sure you have the source code of your kernel installed... Emre On Thu, May 29, 2008 at 2:15 PM, Sebastian Ries <Sebastian.Ries@dtnet.de> wrote:> Hi > > Am Donnerstag, den 29.05.2008, 06:06 -0600 schrieb Nick Couchman: > > Do you have a reason for not running OpenSuSE 10.3 in Paravirtualized > > mode instead of in an HVM? > > Unfortunately yes. > > We are developing a management system to automatically create and > destroy domUs as they are needed. > Therefore we need to have a common handling off ALL domUs including e.g. > being able to connect to the console via VNC an such things. > > Therefore the minimal common manner is to have ALL domUs fully > virtualized (as paravirtualization) is not possible with all domUs :-( > > Regards > Sebastian Ries > > -- > ------------------------------------------------------------ > DT Netsolution GmbH - Talaeckerstr. 30 - D-70437 Stuttgart > Tel: +49-711-849910-36 Fax: +49-711-849910-936 > WEB: http://www.dtnet.de/ email: Sebastian.Ries@dtnet.de > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >-- Emre _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thursday May 29 2008 07:57:22 am Sebastian Ries wrote:> linux-inna:/mnt/xen-3.2-testing.hg/unmodified_drivers/linux-2.6 # make > -C /lib/modules/2.6.22.17-0.1-default/build M=$PWD modules > make: Entering directory `/usr/src/linux-2.6.22.17-0.1-obj/i386/default''Umm - is there a reason you are compiling against the default kernel, instead of the xen or xenpae kernel? On Thursday May 29 2008 08:15:14 am Sebastian Ries wrote:> We are developing a management system to automatically create and > destroy domUs as they are needed. > Therefore we need to have a common handling off ALL domUs including e.g. > being able to connect to the console via VNC an such things. > > Therefore the minimal common manner is to have ALL domUs fully > virtualized (as paravirtualization) is not possible with all domUs :-(You can certainly connect to PV & HVM domains alike with vnc. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Fri, May 30, 2008 at 12:40 AM, jim burns <jim_burn@bellsouth.net> wrote:> On Thursday May 29 2008 07:57:22 am Sebastian Ries wrote: > > linux-inna:/mnt/xen-3.2-testing.hg/unmodified_drivers/linux-2.6 # make > > -C /lib/modules/2.6.22.17-0.1-default/build M=$PWD modules > > make: Entering directory `/usr/src/linux-2.6.22.17-0.1-obj/i386/default'' > > Umm - is there a reason you are compiling against the default kernel, > instead > of the xen or xenpae kernel? >Hi Jim, Well, the entire reason for having these "unmodified_drivers" aka PV Drivers for Linux is to be able to use your own Distro (possibly recent) kernel, with near PV performance thanks to the PV drivers.> > On Thursday May 29 2008 08:15:14 am Sebastian Ries wrote: > > We are developing a management system to automatically create and > > destroy domUs as they are needed. > > Therefore we need to have a common handling off ALL domUs including e.g. > > being able to connect to the console via VNC an such things. > > > > Therefore the minimal common manner is to have ALL domUs fully > > virtualized (as paravirtualization) is not possible with all domUs :-( > > You can certainly connect to PV & HVM domains alike with vnc. > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >-- Emre _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Fri, May 30, 2008 at 01:59:07AM +0200, Emre ERENOGLU wrote:> On Fri, May 30, 2008 at 12:40 AM, jim burns <jim_burn@bellsouth.net> wrote: > > > On Thursday May 29 2008 07:57:22 am Sebastian Ries wrote: > > > linux-inna:/mnt/xen-3.2-testing.hg/unmodified_drivers/linux-2.6 # make > > > -C /lib/modules/2.6.22.17-0.1-default/build M=$PWD modules > > > make: Entering directory `/usr/src/linux-2.6.22.17-0.1-obj/i386/default'' > > > > Umm - is there a reason you are compiling against the default kernel, > > instead of the xen or xenpae kernel? > > Well, the entire reason for having these "unmodified_drivers" aka PV Drivers > for Linux is to be able to use your own Distro (possibly recent) kernel, > with near PV performance thanks to the PV drivers.Hi, you are right - the normal distri-kernel is easier to maintain, so it would be very nice to use it with the PV-drivers.> > > > You can certainly connect to PV & HVM domains alike with vnc.How to configure? I thought a PV domain has no BIOS and therefore i can connect only with the "xm console" command ? regards Danny _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thursday May 29 2008 11:55:24 pm Daniel Schwager wrote:> > > You can certainly connect to PV & HVM domains alike with vnc. > > How to configure? I thought a PV domain has no BIOS and therefore i can > connect only with the "xm console" command ?Old style, still works in my hvm configs on Fedora 8: sdl=0 vnc=1 vnclisten="0.0.0.0" #vnclisten="192.168.1.0/24" # set VNC display number, default = domid vncdisplay=3 # try to find an unused port for the VNC server, default = 1 vncunused=0 vncconsole=1 monitor=1 vncpasswd="" New style (xen 3.1.2 and up) which I use in pv domains: #vfb=[ ''type=vnc, keymap=en-us, vnclisten=0.0.0.0, vncunused=1'' ] vfb=[ ''type=vnc, keymap=en-us, vnclisten=0.0.0.0, vncunused=0, vncdisplay=4'' ] vncconsole=1 Note, on Fedora, I can never get the vnc window to come up automatically on issuing ''xm create'', despite the vncconsole statement (which doesn''t work inside the vfb= clause). This shouldn''t be a problem for your admin colsole function, which would do the equivalent of a manual vnc connect. Also note, on recent xens, the vncdisplay=n statement selects port # 5900+n to connect with, despite the comments in the xmexample* files, that say it should be the domid. Emre - thanx for the correction on the usage of the unmodified drivers. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Back to the PV Drivers issue, I guess I''m facing similar problem on a 2.6.24 HVM kernel for building unmodified_drivers. - Are those unmodified_drivers only for 2.6.18 kernel? - If not, what are the prerequisites? Besides, when running the ./mkbuildtree command, the command references "../../linux-2.6.18-xen.hg/drivers/xen/" , which makes me surprised and I don''t have a clue why... For example, James'' PV Drivers for Windows doesn''t require to have any 2.6.18 kernel anywhere... I was thinking that these PV unmodified_drivers for HVM Linux DomUs would be "kernel independent" as long as the kernel is from 2.6 tree. Emre On Fri, May 30, 2008 at 11:20 AM, jim burns <jim_burn@bellsouth.net> wrote:> On Thursday May 29 2008 11:55:24 pm Daniel Schwager wrote: > > > > You can certainly connect to PV & HVM domains alike with vnc. > > > > How to configure? I thought a PV domain has no BIOS and therefore i can > > connect only with the "xm console" command ? > > Old style, still works in my hvm configs on Fedora 8: > > sdl=0 > vnc=1 > vnclisten="0.0.0.0" > #vnclisten="192.168.1.0/24" > # set VNC display number, default = domid > vncdisplay=3 > # try to find an unused port for the VNC server, default = 1 > vncunused=0 > vncconsole=1 > monitor=1 > vncpasswd="" > > New style (xen 3.1.2 and up) which I use in pv domains: > > #vfb=[ ''type=vnc, keymap=en-us, vnclisten=0.0.0.0, vncunused=1'' ] > vfb=[ ''type=vnc, keymap=en-us, vnclisten=0.0.0.0, vncunused=0, > vncdisplay=4'' ] > vncconsole=1 > > Note, on Fedora, I can never get the vnc window to come up automatically on > issuing ''xm create'', despite the vncconsole statement (which doesn''t work > inside the vfb= clause). This shouldn''t be a problem for your admin colsole > function, which would do the equivalent of a manual vnc connect. Also note, > on recent xens, the vncdisplay=n statement selects port # 5900+n to connect > with, despite the comments in the xmexample* files, that say it should be > the > domid. > > Emre - thanx for the correction on the usage of the unmodified drivers. > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >-- Emre _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
and here's the attempt to build on my system, note that some messages are in
Turkish, but they are things like "entering directory, error 1 etc which
I'm
sure you can guess:
emre@voyager2008 linux-2.6 $ ./mkbuildtree
Defaulting to this machine's architecture, i686, for linking.
This may be overridden on the command line (i386,x86_64,ia64).
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/../../linux-2.6.18-xen.hg/include/xen/interface:
interface: is a link instead of a directory
emre@voyager2008 linux-2.6 $ make -C /usr/src/linux M=$PWD modules
make: `/usr/src/linux-2.6.24.7-95' dizine giriliyor
CC [M]
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.o
In file included from
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/asm/hypervisor.h:41,
from
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.c:48:
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/xen/interface/platform.h:46:
warning: data definition has no type or storage class
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/xen/interface/platform.h:46:
warning: type defaults to 'int' in declaration of
'DEFINE_XEN_GUEST_HANDLE'
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/xen/interface/platform.h:58:
error: expected specifier-qualifier-list before 'xen_pfn_t'
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/xen/interface/platform.h:66:
warning: data definition has no type or storage class
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/xen/interface/platform.h:66:
warning: type defaults to 'int' in declaration of
'DEFINE_XEN_GUEST_HANDLE'
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/xen/interface/platform.h:66:
error: conflicting types for 'DEFINE_XEN_GUEST_HANDLE'
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/xen/interface/platform.h:46:
error: previous declaration of 'DEFINE_XEN_GUEST_HANDLE' was here
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/xen/interface/platform.h:82:
warning: data definition has no type or storage class
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/xen/interface/platform.h:82:
warning: type defaults to 'int' in declaration of
'DEFINE_XEN_GUEST_HANDLE'
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/xen/interface/platform.h:82:
error: conflicting types for 'DEFINE_XEN_GUEST_HANDLE'
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/xen/interface/platform.h:46:
error: previous declaration of 'DEFINE_XEN_GUEST_HANDLE' was here
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/xen/interface/platform.h:90:
error: expected specifier-qualifier-list before 'xen_pfn_t'
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/xen/interface/platform.h:95:
warning: data definition has no type or storage class
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/xen/interface/platform.h:95:
warning: type defaults to 'int' in declaration of
'DEFINE_XEN_GUEST_HANDLE'
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/xen/interface/platform.h:95:
error: conflicting types for 'DEFINE_XEN_GUEST_HANDLE'
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/xen/interface/platform.h:46:
error: previous declaration of 'DEFINE_XEN_GUEST_HANDLE' was here
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/xen/interface/platform.h:100:
error: expected specifier-qualifier-list before 'XEN_GUEST_HANDLE'
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/xen/interface/platform.h:104:
warning: data definition has no type or storage class
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/xen/interface/platform.h:104:
warning: type defaults to 'int' in declaration of
'DEFINE_XEN_GUEST_HANDLE'
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/xen/interface/platform.h:104:
error: conflicting types for 'DEFINE_XEN_GUEST_HANDLE'
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/xen/interface/platform.h:46:
error: previous declaration of 'DEFINE_XEN_GUEST_HANDLE' was here
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/xen/interface/platform.h:115:
warning: data definition has no type or storage class
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/xen/interface/platform.h:115:
warning: type defaults to 'int' in declaration of
'DEFINE_XEN_GUEST_HANDLE'
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/xen/interface/platform.h:115:
error: conflicting types for 'DEFINE_XEN_GUEST_HANDLE'
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/xen/interface/platform.h:46:
error: previous declaration of 'DEFINE_XEN_GUEST_HANDLE' was here
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/xen/interface/platform.h:138:
error: expected specifier-qualifier-list before 'XEN_GUEST_HANDLE'
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/xen/interface/platform.h:149:
error: expected specifier-qualifier-list before 'XEN_GUEST_HANDLE'
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/xen/interface/platform.h:154:
warning: data definition has no type or storage class
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/xen/interface/platform.h:154:
warning: type defaults to 'int' in declaration of
'DEFINE_XEN_GUEST_HANDLE'
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/xen/interface/platform.h:154:
error: conflicting types for 'DEFINE_XEN_GUEST_HANDLE'
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/xen/interface/platform.h:46:
error: previous declaration of 'DEFINE_XEN_GUEST_HANDLE' was here
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/xen/interface/platform.h:165:
warning: data definition has no type or storage class
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/xen/interface/platform.h:165:
warning: type defaults to 'int' in declaration of
'DEFINE_XEN_GUEST_HANDLE'
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/xen/interface/platform.h:165:
error: conflicting types for 'DEFINE_XEN_GUEST_HANDLE'
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/xen/interface/platform.h:46:
error: previous declaration of 'DEFINE_XEN_GUEST_HANDLE' was here
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/xen/interface/platform.h:175:
warning: data definition has no type or storage class
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/xen/interface/platform.h:175:
warning: type defaults to 'int' in declaration of
'DEFINE_XEN_GUEST_HANDLE'
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/xen/interface/platform.h:175:
error: conflicting types for 'DEFINE_XEN_GUEST_HANDLE'
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/xen/interface/platform.h:46:
error: previous declaration of 'DEFINE_XEN_GUEST_HANDLE' was here
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/xen/interface/platform.h:189:
error: expected specifier-qualifier-list before 'XEN_GUEST_HANDLE'
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/xen/interface/platform.h:200:
warning: data definition has no type or storage class
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/xen/interface/platform.h:200:
warning: type defaults to 'int' in declaration of
'DEFINE_XEN_GUEST_HANDLE'
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/xen/interface/platform.h:200:
error: conflicting types for 'DEFINE_XEN_GUEST_HANDLE'
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/xen/interface/platform.h:46:
error: previous declaration of 'DEFINE_XEN_GUEST_HANDLE' was here
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/xen/interface/platform.h:220:
warning: data definition has no type or storage class
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/xen/interface/platform.h:220:
warning: type defaults to 'int' in declaration of
'DEFINE_XEN_GUEST_HANDLE'
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/xen/interface/platform.h:220:
error: conflicting types for 'DEFINE_XEN_GUEST_HANDLE'
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/xen/interface/platform.h:46:
error: previous declaration of 'DEFINE_XEN_GUEST_HANDLE' was here
In file included from
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/asm/hypervisor.h:45,
from
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.c:48:
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/xen/interface/nmi.h:60:
warning: data definition has no type or storage class
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/xen/interface/nmi.h:60:
warning: type defaults to 'int' in declaration of
'DEFINE_XEN_GUEST_HANDLE'
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/xen/interface/nmi.h:60:
error: conflicting types for 'DEFINE_XEN_GUEST_HANDLE'
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/xen/interface/platform.h:46:
error: previous declaration of 'DEFINE_XEN_GUEST_HANDLE' was here
In file included from
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.c:48:
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/asm/hypervisor.h:58:
error: expected '=', ',', ';', 'asm' or
'__attribute__' before '*' token
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/asm/hypervisor.h:72:
error: expected '=', ',', ';', 'asm' or
'__attribute__' before '*' token
In file included from
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/xen/hypercall.h:4,
from
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/asm/hypervisor.h:138,
from
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.c:48:
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/asm/hypercall.h:133:
warning: type defaults to 'int' in declaration of 'trap_info_t'
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/asm/hypercall.h:133:
error: expected ';', ',' or ')' before '*' token
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/asm/hypercall.h:140:
error: expected ')' before '*' token
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/asm/hypercall.h:246:
error: expected ')' before '*' token
In file included from
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/asm/hypervisor.h:138,
from
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.c:48:
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/xen/hypercall.h:8:
error: expected ')' before '*' token
In file included from
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.c:48:
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/asm/hypervisor.h:
In function 'HYPERVISOR_poll':
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/include/asm/hypervisor.h:209:
error: implicit declaration of function 'set_xen_guest_handle'
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.c:101:58:
error: macro "DECLARE_WORK" passed 3 arguments, but takes just 2
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.c: At
top level:
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.c:101:
warning: type defaults to 'int' in declaration of 'DECLARE_WORK'
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.c: In
function 'balloon_alarm':
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.c:186:
error: 'balloon_worker' undeclared (first use in this function)
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.c:186:
error: (Each undeclared identifier is reported only once
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.c:186:
error: for each function it appears in.)
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.c: In
function 'balloon_set_new_target':
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.c:425:
error: 'balloon_worker' undeclared (first use in this function)
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.c: In
function 'alloc_empty_pages_and_pagevec':
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.c:671:
error: 'balloon_worker' undeclared (first use in this function)
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.c: In
function 'free_empty_pages_and_pagevec':
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.c:704:
error: 'balloon_worker' undeclared (first use in this function)
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.c: In
function 'balloon_release_driver_page':
/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.c:716:
error: 'balloon_worker' undeclared (first use in this function)
*** 43 errors, 26 warnings
make[2]: ***
[/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/balloon/balloon.o]
Hata 1
make[1]: *** [/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6/balloon]
Hata 2
make: *** [_module_/tmp/xen-3.2-testing.hg/unmodified_drivers/linux-2.6]
Hata 2
make: `/usr/src/linux-2.6.24.7-95' dizininden çıkılıyor
emre@voyager2008 linux-2.6 $
--
Emre
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users