From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Carl Patenaude Poulin <carl.patenaudepoulin@mail.mcgill.ca>,
xen-devel@lists.xen.org
Subject: Re: Xen Unikernel: from zero to Hello World!
Date: Wed, 28 Oct 2015 12:02:36 +0000 [thread overview]
Message-ID: <5630B95C.3010104@citrix.com> (raw)
In-Reply-To: <CA+v+NpJSc8VeprxGb70R_zuoELVhGQrvpyO9AaovXOJz_hiLjA@mail.gmail.com>
On 27/10/15 19:42, 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.
-c is a parameter to `xl create`
Alternatively, you could do `xl create` followed by `xl console` later.
However, there are usability issues with both of these approaches in
combination with short-lived domains.
> * 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.
What is the error message you get? A PV guest always has a console, so
there is no refusal available to happen. I suspect you have actually
hit one of the usability issues I eluded to above.
> * On Xen debug builds, I don't need a console device driver, I can
> just do HYPERVISOR_console_io hypercalls.
Always do all development with a debug hypervisor. Even for guests, you
get more useful information out when something goes wrong.
Longterm you will want a better way of getting logging out of the guest,
but console_io hypercalls are a good start for very early bits.
~Andrew
prev parent reply other threads:[~2015-10-28 12:02 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
2015-10-28 12:02 ` Andrew Cooper [this message]
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=5630B95C.3010104@citrix.com \
--to=andrew.cooper3@citrix.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.