From: blallo@riseup.net
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
daniel.kiper@oracle.com, George Dunlap <george.dunlap@citrix.com>,
Jan Beulich <JBeulich@suse.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [Xen-users] xl info displays less ram than the total available
Date: Thu, 6 Oct 2016 15:03:08 +0200 [thread overview]
Message-ID: <20161006130308.f25weki2s55e34u3@riseup.net> (raw)
In-Reply-To: <20161006125857.7kavmrfe27yudsud@supernova>
blallo@riseup.net:
>blallo@riseup.net:
>>Konrad Rzeszutek Wilk:
>>>On Thu, Oct 06, 2016 at 12:59:13PM +0200, Blallo wrote:
>>>>I'm using grub2. After the lunch break I can post the full grub menu entry and the exact version of grub2.
>>>
>>>Cc-ing Daniel (who is now an GRUB2 maintainer).
>>>
>>>Is this by chance an EFI box?And you are booting using EFI GRUB2?
>>Hi everybody,
>>first of all, thanks for all the effort you're putting in this issue of
>>mine. Secondly, I apologize for the top quoting of my last email: I was
>>on my mobile.
>>
>>Konrad, yes, I boot using efi grub2. The version is
>>
>>% grub-install -V
>>grub-install (GRUB) 2.02~beta3
>>
>>as obtained from the Arch repos.
>>
>>I attach the custom /etc/grub.d/ script I use to generate the grub menu
>>entry for Xen booting. It is largely taken by the original one I use to
>>boot into the ordinary Arch kernel.
>>
>>
>Sorry, forgot to attach the file :)
>
>Here it is.
>
Worth to mention that, despite the "echo" in the menu entry seem to
suggest that I'm chainbooting a grsec-patched kernel and initrd, they
are not. They are indeed the ordinary Arch 4.7 kernel and initrd.
I tried to boot the grsec versios, but Xen failed.
Anyway, this is the subject of a new thread :)
Sorry for the number of emails :)
Greetings
--
Leonardo
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2016-10-06 13:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20161005101600.odbvl632lmjigvsi@riseup.net>
[not found] ` <CAFLBxZYWiGWTf2zhVOF3yfWQvtNpndF9avcOVgEGPDg7PZ1wog@mail.gmail.com>
[not found] ` <20161005125229.ixcvhldn4ra62prn@riseup.net>
2016-10-05 13:02 ` [Xen-users] xl info displays less ram than the total available George Dunlap
2016-10-05 13:06 ` Andrew Cooper
2016-10-05 13:32 ` blallo
2016-10-05 14:01 ` Jan Beulich
2016-10-06 10:55 ` George Dunlap
2016-10-06 10:59 ` Blallo
2016-10-06 12:06 ` Konrad Rzeszutek Wilk
2016-10-06 12:39 ` blallo
2016-10-06 13:00 ` Jan Beulich
2016-10-06 12:56 ` blallo
[not found] ` <20161006125650.ww7lq7gpn7ovvqrr@supernova>
2016-10-06 12:58 ` blallo
2016-10-06 13:16 ` Daniel Kiper
[not found] ` <53339FBD-ABBC-4047-A787-74F97867015A@riseup.net>
2016-10-26 8:30 ` blallo
2016-10-26 13:26 ` Konrad Rzeszutek Wilk
2016-10-27 8:24 ` Daniel Kiper
[not found] ` <20161006125857.7kavmrfe27yudsud@supernova>
2016-10-06 13:03 ` blallo [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=20161006130308.f25weki2s55e34u3@riseup.net \
--to=blallo@riseup.net \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=daniel.kiper@oracle.com \
--cc=george.dunlap@citrix.com \
--cc=konrad.wilk@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).