Hello~
I'm new to develop Xen and my first work is about its scheduler.
After I modified Xen 4.5 source code, my custom Xen has had a problem,
which it causes automatic reboot of Dom0 when I execute a micro benchmark
program.
To debug it, I have tried to use crashdump on Dom0 with the Xen but, I
fa
Oh!! I'm so sorry Jan Beulich.
It is my first time to use this mailing list.
Please understand my fault, this time only.
Anyway, as you mentioned, I added below line in '/etc/default/grub' file
and reboot:
> GRUB_CMDLINE_XEN="crashkernel=384M-:256M@64M"
Then,
1. I cannot see anything when I type "
), that method will be
more flexible way to debug on Xen.
Even if I have struggled to find the way to debug Xen using crashdump, I
failed. So, finally I ordered serial cable.
On Tue, Aug 29, 2017 at 7:05 PM, Roger Pau Monné
wrote:
> On Mon, Aug 28, 2017 at 05:01:48PM +0900, Minjun Hong wr
Hello~~
I'm struggling to resolve a kernel panic problem during developing
scheduler code.
But I have not made any progress since I can not get any meaningful
information from the serial log.
When the panic occurred, always there is no call trace and only panic
notification like following:
(XEN)
(
(XEN)
(XEN) Reboot in five seconds...
(XEN) Resetting with ACPI MEMORY or I/O RESET_REG.
I hope your help.
Sincerely,
On Wed, Sep 6, 2017 at 4:45 PM, Andrew Cooper
wrote:
> On 06/09/2017 03:39, Minjun Hong wrote:
> > Hello~~
> > I'm struggling to resolve a ker
Hello~
I think this might be duplicate issue but, I have not resolved for long
time.
So, please understand this post generously.
First, I should explain my history.
1) I worked on the scheduler(credit scheduler) and I had a kernel panic by
my modification.
2) I tried to get any information for deb
a code line that is never
related this problem.
I know that a beginner in the Xen developer community like me might be
annoying you, but I ask you one more help.
Thanks for your help again.
On Fri, Sep 8, 2017 at 4:40 PM, Dario Faggioli
wrote:
> On Fri, 2017-09-08 at 14:33 +0900, Minjun Hon
Hi.
I'm working on a scheduling code by which I received a patch regarding
credit scheduler from my professor.
I have had some troubles during that work and I need to make the Xen binary
with 'debug=y' option.
But there was a kernel panic caused by the debugging code triggered by
'debug=y' option d
