| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
[Xen-devel] Re: Failure to load the most recent 2.6.32.21 pvops under Xe
Adding dom0_mem=1024M to xen.gz line fixes the problem in my case
for any recent 2.6.32.21 pvops kernel ( MY's 168 aswell)
Boris.
--- On Fri, 9/24/10, Jeremy Fitzhardinge <jeremy@xxxxxxxx> wrote:
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: Re: Failure to load the most recent 2.6.32.21 pvops under Xen 4.0.1
To: "Boris Derzhavets" <bderzhavets@xxxxxxxxx>
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, "Pasi Kärkkäinen" <pasik@xxxxxx>
Date: Friday, September 24, 2010, 3:03 PM
On 09/24/2010 04:39 AM, Boris Derzhavets wrote:
> Last commit (b297cdac0373625d3cd0e6f2b393570dcf2edba6)
> Console drops into stack trace:-
>
> - - - - - - - - - - - - -
- - - - - - - - - - - - - - - - - - - - - -
> - - - - - - - - -
> Kernel Bug at drivers/xen/balloon.c:270 !
> invalid opcode 0000 [#] SMP
> last sysfs file : /sys/devices/virtual/misc/xen!gntdev/uevent
> . . . . . . .
>
> RIP [<fffff ....>] balloon_process+0x1c4/0x580
>
Please don't truncate oops/BUG messages like this. It removes a lot of
useful information.
Dom0 or domU? 32 or 64 bit? Are you using maxmem? Can you send a
complete boot log for the domain (or system if dom0)?
I suspect this bug has been fixed later on, but hasn't made it into
stable-2.6.32.x yet.
Thanks,
J
|
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home