KVM-61/62 build fails on SLES 10

KVM-61/62 build fails on SLES 10

[M.J. Rutter]

Whereas KVM-60 builds "out of the box" on SLES 10 SP1 (assuming gcc 3.4 is 
installed), KVM-61 and KVM-62 don't. They fail with:

make[1]: Entering directory `/scratch/KVM/kvm-61/kernel'
# include header priority 1) INUX 2) ERNELDIR 3) include-compat
make -C /lib/modules/2.6.16.54-0.2.5-smp/build M=`pwd` \
        LINUXINCLUDE="-I`pwd`/include -Iinclude -I`pwd`/include-compat \
        -include include/linux/autoconf.h" \
        "$@"
make[2]: Entering directory 
`/usr/src/linux-2.6.16.54-0.2.5-obj/x86_64/smp'
make -C ../../../linux-2.6.16.54-0.2.5 
O=../linux-2.6.16.54-0.2.5-obj/x86_64/smp
  LD      /scratch/KVM/kvm-61/kernel/built-in.o
  CC [M]  /scratch/KVM/kvm-61/kernel/svm.o
In file included from <command line>:1:
/scratch/KVM/kvm-61/kernel/external-module-compat.h:10:28: error: 
linux/compiler.h: No such file or directory
/scratch/KVM/kvm-61/kernel/external-module-compat.h:12:26: error: 
linux/string.h: No such file or directory

Trying to fiddle the include path to ensure that it finds 
/usr/src/linux/include then produces an error for linux/clocksource.h.

SLES 10 SP1 uses a kernel whose version is 2.6.16.54-0.2.5-smp, i.e. 
2.6.16 plus various back-ported bits. However, SLES 10 SP1 is the current 
version of SuSE Linux Enterprise Server, so in some sense this is current.

KVM was configured with

./configure --prefix=/usr/local/kvm/kvm-61 \
  --qemu-cc=/scratch/gcc-3.4/bin/gcc-3.4

Michael

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

Re: KVM-61/62 build fails on SLES 10

[M.J. Rutter]

On Fri, 29 Feb 2008, M.J. Rutter wrote:

> Whereas KVM-60 builds "out of the box" on SLES 10 SP1 (assuming gcc 3.4 is 
> installed), KVM-61 and KVM-62 don't.

Bother. Ignore that. As far as I can see, no KVM since about KVM-37 has 
actually run on a kernel that old, due to the lack of hrtimer_init and 
friends. KVM-60 may build, but it certainly doesn't run, so KVM-61/62's 
inability to build is of no consequence.

Michael

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

Re: KVM-61/62 build fails on SLES 10

[Alexey Eremenko]

[-- Attachment #1.1: Type: text/plain, Size: 373 bytes --]


Well, There is a patch, that may help.

It must be applied against clean KVM-61 (maybe it works with 62).
Must be applied vs. KVM kernel-space Makefile.

# cd kvm-61/kernel/
# patch -p1 < kvm-susekernel.patch
# ./configure
# make
# make install

It helps here, on openSUSE Linux 10.3 host.

I hope that Avi will merge it in KVM-63.

-Alexey "Technologov"

[-- Attachment #1.2: Type: text/html, Size: 839 bytes --]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: kvm-susekernel.patch --]
[-- Type: text/x-patch; name="kvm-susekernel.patch", Size: 394 bytes --]

--- kernel/Makefile
+++ kernel/Makefile
@@ -27,7 +27,7 @@
 all::
 	# include header priority 1) $LINUX 2) $KERNELDIR 3) include-compat
 	$(MAKE) -C $(KERNELDIR) M=`pwd` \
-		LINUXINCLUDE="-I`pwd`/include -Iinclude -I`pwd`/include-compat \
+		LINUXINCLUDE="-I`pwd`/include -Iinclude -Iinclude2 -I/usr/src/linux/include -I`pwd`/include-compat \
 		-include include/linux/autoconf.h" \
 		"$$@"
 

[-- Attachment #3: Type: text/plain, Size: 228 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

[-- Attachment #4: Type: text/plain, Size: 158 bytes --]

_______________________________________________
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: KVM-61/62 build fails on SLES 10

[Alexander Graf]

[-- Attachment #1.1: Type: text/plain, Size: 994 bytes --]


On Mar 2, 2008, at 12:31 PM, Alexey Eremenko wrote:

>
> Well, There is a patch, that may help.
>
> It must be applied against clean KVM-61 (maybe it works with 62).
> Must be applied vs. KVM kernel-space Makefile.
>
> # cd kvm-61/kernel/
> # patch -p1 < kvm-susekernel.patch
> # ./configure
> # make
> # make install
>
> It helps here, on openSUSE Linux 10.3 host.
>

This patch is due to a different problem and I would have posted it if  
I would have wanted it to get upstream. If you have an idea how to  
_really_ fix it, please do so. This patch was only meant to be used  
internally.

The basic problem here is that the SUSE kernel splits the kernel in  
objects, headers and sources. So if you want to build anything, you  
have to include pieces that are scattered all around the different  
folders the different packages create. I can get into more detail on  
this if someone's really interested to fix this long-term without wild  
'guessing' of include folders.

Regards,

Alex

[-- Attachment #1.2: Type: text/html, Size: 1493 bytes --]

[-- Attachment #2: Type: text/plain, Size: 228 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

[-- Attachment #3: Type: text/plain, Size: 158 bytes --]

_______________________________________________
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: KVM-61/62 build fails on SLES 10

[M.J. Rutter]

On Sun, 2 Mar 2008, Alexey Eremenko wrote:

> Well, There is a patch, that may help.

Thanks. It did. I installed the current openSuSE 10.3 kernel on top
of SLES10 SP1, which worked after specifying --nodeps. KVM-62 then built 
and ran with your patch, and is rather faster than KVM-37 for 
networking...

I should probably give up on SuSE kernels and install a plain kernel.org 
one.

Michael

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

Re: KVM-61/62 build fails on SLES 10

[Alexey Eremenko]

[-- Attachment #1.1: Type: text/plain, Size: 606 bytes --]

>and ran with your patch, and is rather faster than KVM-37 for 
networking...

Hi Michael !

If you're looking for blazing fast networking, then KVM (61+) offers VirtIO - PV networking, capable of breaking the 1 Gbps barrier...
But to achieve such speeds you'll need to compile custom kernels (2.6.25) on both Linux Host & Guest.

Maybe openSUSE 11/SLES 11 will have the right kernels out-of-the-box.

Alternatively, you can try the newest Intel e1000 Gigabit Ethernet emulation (also part of newest KVMs).
This is much easier to setup. This will work for any guest.

-Technologov, 4.3.2008.

[-- Attachment #1.2: Type: text/html, Size: 1053 bytes --]

[-- Attachment #2: Type: text/plain, Size: 228 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

[-- Attachment #3: Type: text/plain, Size: 158 bytes --]

_______________________________________________
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: KVM-61/62 build fails on SLES 10

[Tomas Rusnak]

Alexey Eremenko napsal(a):
>  >and ran with your patch, and is rather faster than KVM-37 for
> networking...
> 
> Hi Michael !
> 
> If you're looking for blazing fast networking, then KVM (61+) offers 
> VirtIO - PV networking, capable of breaking the 1 Gbps barrier...
> But to achieve such speeds you'll need to compile custom kernels 
> (2.6.25) on both Linux Host & Guest.
> 
> Maybe openSUSE 11/SLES 11 will have the right kernels out-of-the-box.
> 
> Alternatively, you can try the newest Intel e1000 Gigabit Ethernet 
> emulation (also part of newest KVMs).
> This is much easier to setup. This will work for any guest.
> 
> -Technologov, 4.3.2008.
> 
> 
> ------------------------------------------------------------------------
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> kvm-devel mailing list
> kvm-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/kvm-devel

Hello

Sorry for my intervention into your communication, but are you sure, 
when you want to use virtio, you must have 2.6.25 kernel on both - guest 
and host system?
I test this case right now, and I have running 2.6.25-rc3 only on guest 
system with kvm-62.

-- 
Tomas Rusnak, Korex Networks

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

Re: KVM-61/62 build fails on SLES 10

[Dor Laor]

> Hello
> 
> Sorry for my intervention into your communication, but are you sure, 
> when you want to use virtio, you must have 2.6.25 kernel on both - guest 
> and host system?
> I test this case right now, and I have running 2.6.25-rc3 only on guest 
> system with kvm-62.
> 

It's enough running the new guest kernel. Virtio on the host is
implemented completely in qemu. Just use tap for better performance.
Actually there is a backport for the guest kernel that Anthony Liguori
wrote that needs minor changes, I'll post it tomorrow.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/