From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Carl Patenaude Poulin <carl.patenaudepoulin@mail.mcgill.ca>
Cc: xen-devel@lists.xen.org
Subject: Re: Xen Unikernel: from zero to Hello World!
Date: Tue, 27 Oct 2015 15:59:35 -0400 [thread overview]
Message-ID: <20151027195935.GD29620@l.oracle.com> (raw)
In-Reply-To: <CA+v+NpJSc8VeprxGb70R_zuoELVhGQrvpyO9AaovXOJz_hiLjA@mail.gmail.com>
On Tue, Oct 27, 2015 at 03:42:19PM -0400, Carl Patenaude Poulin wrote:
> Hi all,
>
> Thanks to Andrew Cooper's priceless help, I've managed to put
> together a Xen PV kernel that does nothing except loop forever. I'm
> going to try making it print "Hello, world!".
>
> I was hoping someone could fact-check my research. What I've dug up
> is:
> * I need to load my unikernel with `xl -c` to get console output.
> * My kernel currently refuses to load with the `-c` option. From
> what I've read online, this is because I need to implement a console
> device driver, similar to Mini-OS's xencons_ring.c.
/me nods.
> * On Xen debug builds, I don't need a console device driver, I can
> just do HYPERVISOR_console_io hypercalls.
Right.
>
> What strategy would you use to debug this early in the development
> process? Is there a debugger I should be using?
You can use gdbsx - and then gdb. See http://www.slideshare.net/xen_com_mgr/from-printk-to-qemu-xenlinux-kernel-debugging
slide 15.
>
> I'd appreciate any information and any links to information, even
> when it's only tangentially relevant.
>
> Thanks in advance,
>
> Carl Patenaude Poulin
> B Eng Software undergraduate at McGill University
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-10-27 19:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-27 19:42 Xen Unikernel: from zero to Hello World! Carl Patenaude Poulin
2015-10-27 19:59 ` Konrad Rzeszutek Wilk [this message]
2015-10-28 12:02 ` Andrew Cooper
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=20151027195935.GD29620@l.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=carl.patenaudepoulin@mail.mcgill.ca \
--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.