From: Dario Faggioli <dario.faggioli@citrix.com>
To: Harmandeep Kaur <write.harmandeep@gmail.com>,
Jan Beulich <JBeulich@suse.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
xen-devel@lists.xen.org, Shuai Ruan <shuai.ruan@linux.intel.com>
Subject: Re: Error booting Xen
Date: Tue, 26 Jan 2016 18:28:59 +0000 [thread overview]
Message-ID: <1453832939.13383.91.camel@citrix.com> (raw)
In-Reply-To: <CAPtdW15JcNEHhS+Ykt63WV_Zrx_yGHK=v89coHD0Rip5QChtiQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 3131 bytes --]
On Tue, 2016-01-26 at 23:32 +0530, Harmandeep Kaur wrote:
> Last time, I did absolutely nothing. System was idle
> and it crashed just after the login. Now, I booted the
> system again and this time, there is no reset. But,
> performance of the system is very slow. Browser
> (Mozilla Firefox) freezes a lot. Also, before applying
> patches, when I used to disabe xsave it resulted in
> same kind of performance issues.
>
Mmm... are you sure the performance is actually affected by "xsave=0",
and/or by Jan's patch? It's hard to check, as without at least one of
them the box does not boot, but I don't think the things (e.g., Firefox
freezing or not starting) are necessarily related.
In particular, you have in your Xen boot parameters list, this item:
"dom0_mem=1024M,max:1024M"
This means that, in dom0, you will "only" have 1GB of RAM available.
And if you just login after boot and start Firefox, dom0 is where
Firefox is going to be running... and 1G, that Firefox will have to
share with the rest of Linux running as dom0, may be too few RAM for
it. And in fact, in your last log, we see this (from dom0, not from
Xen!):
[ 851.644443] Out of memory: Kill process 1945 (firefox) score 325 or sacrifice child
[ 851.644461] Killed process 1945 (firefox) total-vm:1228008kB, anon-rss:305536kB, file-rss:0kB
If you want to run a graphical environment on that test box, and browse
with Firefox, then you should increase the amount of RAM you allow dom0
to use. When I suggested you to use 1024, I was assuming (given how
your work environment is setup) you were not going to do any such
thing.
> And the following
> is still present in the log.
>
> (XEN) traps.c:3290: GPF (0000): ffff82d0801c1cea -> ffff82d080252e5c
> (XEN) d1v1 fault#1: mxcsr=00001f80
> (XEN) d1v1 xs=0000000000000003 xc=8000000000000000
> (XEN) d1v1 r0=0000000000000000 r1=0000000000000000
> (XEN) d1v1 r2=0000000000000000 r3=0000000000000000
> (XEN) d1v1 r4=0000000000000000 r5=0000000000000000
> (XEN) traps.c:3290: GPF (0000): ffff82d0801c1cea -> ffff82d080252e5c
> (XEN) d1v1 fault#2: mxcsr=00001f80
> (XEN) d1v1 xs=0000000000000000 xc=0000000000000000
> (XEN) d1v1 r0=0000000000000000 r1=0000000000000000
> (XEN) d1v1 r2=0000000000000000 r3=0000000000000000
> (XEN) d1v1 r4=0000000000000000 r5=0000000000000000
>
Mmm... and this is with all Jan's patches applied?
So, just to make sure we understand each others, you're saying that,
again with all patches applied, and with you not doing anything
significantly different between a) and b) below, the system either:
a) crashes right after login, like this: http://paste2.org/KEAetMHb
b) does not crash (you're even able to try starting Firefox), but Xen
produces the following output: http://paste2.org/C8WpyKOg
Is this correct?
Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-01-26 18:28 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 18:03 Error booting Xen Harmandeep Kaur
2016-01-18 18:09 ` Andrew Cooper
2016-01-18 18:29 ` Dario Faggioli
2016-01-19 13:36 ` Jan Beulich
2016-01-19 14:51 ` Dario Faggioli
2016-01-19 15:07 ` Andrew Cooper
2016-01-19 16:27 ` Harmandeep Kaur
2016-01-19 16:47 ` Jan Beulich
2016-01-19 17:02 ` Andrew Cooper
2016-01-19 17:08 ` Dario Faggioli
2016-01-19 17:09 ` Andrew Cooper
2016-01-19 19:55 ` Harmandeep Kaur
2016-01-20 10:06 ` Jan Beulich
2016-01-21 15:14 ` Dario Faggioli
2016-01-21 15:24 ` Harmandeep Kaur
2016-01-25 13:42 ` Jan Beulich
2016-01-26 11:58 ` Dario Faggioli
2016-01-26 12:51 ` Harmandeep Kaur
2016-01-26 13:13 ` Harmandeep Kaur
2016-01-26 13:23 ` Jan Beulich
2016-01-26 17:01 ` Harmandeep Kaur
2016-01-26 17:23 ` Jan Beulich
2016-01-26 18:02 ` Harmandeep Kaur
2016-01-26 18:28 ` Dario Faggioli [this message]
2016-01-26 18:36 ` Harmandeep Kaur
2016-01-27 8:24 ` Jan Beulich
2016-01-27 13:12 ` Jan Beulich
2016-01-27 13:28 ` Harmandeep Kaur
2016-01-27 14:28 ` Jan Beulich
2016-01-28 19:17 ` Harmandeep Kaur
2016-01-29 10:13 ` Jan Beulich
2016-02-03 8:23 ` Dario Faggioli
2016-02-03 11:35 ` Harmandeep Kaur
2016-02-03 12:49 ` Jan Beulich
2016-02-03 12:55 ` Dario Faggioli
2016-02-03 13:10 ` Andrew Cooper
2016-02-03 13:17 ` Dario Faggioli
2016-02-03 16:57 ` Konrad Rzeszutek Wilk
2016-02-03 13:40 ` Harmandeep Kaur
2016-02-03 14:18 ` Jan Beulich
2016-01-26 13:22 ` Jan Beulich
2016-02-02 4:43 ` Shuai Ruan
[not found] ` <20160202044349.GA3036@shuai.ruan@linux.intel.com>
2016-02-02 10:39 ` Andrew Cooper
2016-02-03 0:56 ` Shuai Ruan
2016-02-03 7:56 ` Shuai Ruan
2016-01-19 14:07 ` Harmandeep Kaur
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1453832939.13383.91.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=shuai.ruan@linux.intel.com \
--cc=write.harmandeep@gmail.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.