Hi, I have several random kernel errors in my logs like that : http://pastebin.com/XhfyEjYu I have tested some kernels (3.3.7, 3.4.4, and the latest 3.7.1). There is my "xm info" output : http://pastebin.com/ASyYU2f3 The errors occurs on multiple servers with different hardware, and seems to not happen when no domU are launched. Do you have some ideas to debug that ? Thanks, Neri _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
Hello, As I didn''t receive any response, maybe I have forgotten some important informations. If so, or if there is a better place to send my xen/kernel problem, please tell me. Thanks, Neri 2012/12/28 Nerilaunt Nerilaunt <nerilaunt@gmail.com>> Hi, > > I have several random kernel errors in my logs like that : > http://pastebin.com/XhfyEjYu > > I have tested some kernels (3.3.7, 3.4.4, and the latest 3.7.1). There is > my "xm info" output : http://pastebin.com/ASyYU2f3 > The errors occurs on multiple servers with different hardware, and seems > to not happen when no domU are launched. > > Do you have some ideas to debug that ? > > Thanks, > > Neri > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
On Fri, 2013-01-04 at 14:50 +0000, Nerilaunt Nerilaunt wrote:> Hello, > > As I didn''t receive any response, maybe I have forgotten some > important informations.Usually it is better to include at least a snippet of the logs in the email, many people will just skip over something which requires them to follow a link. Googling for "__sanitize_i387_state" from your logs suggests that you may be hitting an xsave related issue. Try adding "xsave=0" to either/both the hypervisor and kernel command line. Ian.
> > Usually it is better to include at least a snippet of the logs in the > email, many people will just skip over something which requires them to > follow a link. >Ok.> Googling for "__sanitize_i387_state" from your logs suggests that you > may be hitting an xsave related issue. Try adding "xsave=0" to > either/both the hypervisor and kernel command line. >Actually the real command line (seen in the Documentation/kernel-parameters.txt of my 3.7.1 kernel) is noxsave. I have added it and no more kernel errors. Thanks ! Neri _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users