WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

AW: [Xen-users] AW: Re: [Xen-devel] 2.6.34.7 with SUSE patches: Invalid

To: Boris Derzhavets <bderzhavets@xxxxxxxxx>, Andrew Lyon <andrew.lyon@xxxxxxxxx>
Subject: AW: [Xen-users] AW: Re: [Xen-devel] 2.6.34.7 with SUSE patches: Invalid Kernel
From: Carsten Schiers <carsten@xxxxxxxxxx>
Date: Tue, 19 Oct 2010 14:15:53 +0200
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 19 Oct 2010 05:17:17 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <183519.55339.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thanks, Boris.

It's even worse: 64 Bit HW, 64 Bit Dom0, 32 Bit PV DomUs with PCI devs.

BR,
Carsten.


Von: Boris Derzhavets <bderzhavets@xxxxxxxxx>
Gesendet: Die, 19.10.2010 14:09
An: Andrew Lyon <andrew.lyon@xxxxxxxxx> ; Carsten Schiers <carsten@xxxxxxxxxx>
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Betreff: Re: [Xen-users] AW: Re: [Xen-devel] 2.6.34.7 with SUSE patches: Invalid Kernel

Not sure it's right thing to do.
Just copy config32 to ./linux-2.6.34.7 and run "make menuconfig"
Check parameters you concerned about and save .config
( turn off and on no matter what).   It should generate config64.

Boris.
P.S. Never ran Xen Dom0&DomUs on 32-bit hardware.

--- On Tue, 10/19/10, Carsten Schiers <carsten@xxxxxxxxxx> wrote:

From: Carsten Schiers <carsten@xxxxxxxxxx>
Subject: [Xen-users] AW: Re: [Xen-devel] 2.6.34.7 with SUSE patches: Invalid Kernel
To: "Boris Derzhavets" <bderzhavets@xxxxxxxxx>, "Andrew Lyon" <andrew.lyon@xxxxxxxxx>
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Date: Tuesday, October 19, 2010, 7:19 AM

Jup, 64 Bit Kernel build is done now and works, but 32 Bit kernel config is different, as
I use 64 Bit in Dom0 and DomU, 32 Bit only in DomU incl. DomU with DVB etc. XEN
options are the same, it's only the selection of drivers...

Andrew, any idea?

Boris, do you know a safe way to create a 64 Bit config out of a 32 Bit one? Sorry, I am
not so used to kernel building...

BR,
Carsten.


Von: Boris Derzhavets <bderzhavets@xxxxxxxxx>
Gesendet: Die, 19.10.2010 12:09
An: Carsten Schiers <carsten@xxxxxxxxxx>
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Betreff: ***SPAM*** Re: [Xen-devel] 2.6.34.7 with SUSE patches: Invalid Kernel

I have 2.6.34.7 xenified aka Suse running under Xen 4.0.1 on top of Ubuntu 10.10 Desktop. But , it is 64-bit system.

Boris.

--- On Tue, 10/19/10, Carsten Schiers <carsten@xxxxxxxxxx> wrote:

From: Carsten Schiers <carsten@xxxxxxxxxx>
Subject: [Xen-devel] 2.6.34.7 with SUSE patches: Invalid Kernel
To: "xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Date: Tuesday, October 19, 2010, 5:59 AM

Hi,

any idea what i configured wrong with my 2.6.34.7 32 Bit kernel? I get:
VmError: (2, 'Invalid kernel', 'elf_xen_note_check: ERROR: Will only
load images built for the generic loader or Linux images')PAE is enabled...

BR,
Carsten.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


-----Inline Attachment Follows-----

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>