All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Ruh <jan.ruh@tttech.com>
To: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Kernel requires x86-64 CPU, after modifying arch_shared_info struct
Date: Mon, 29 Jun 2020 07:43:43 +0000	[thread overview]
Message-ID: <6f88fc3e2795436fa1f30dd026dd8eda@tttech.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1499 bytes --]

Hi Xen Dev Community,


I ran into an issue when implementing a prototype for a new paravirtualized clock for x86-64 hosts. I extended the arch_shared_info struct by 6 fields totaling at 36 bytes. I updated the xen-foreign/references.size to represent the new size of the arch_shared_info struct. The fields are correctly updated in Xen and I am also able to read the correct information stored from dom0. However, if I try to start a hvm VM with pvh extensions it does not boot telling me that "This kernel requires an x86-64 CPU, but only detected an i686 CPU.". I have rebuild my Linux domU kernel just as the dom0 kernel and everything should be compatible. To me this looks like Xen or libxc does some compatibility checks before booting up my HVM domU and decides to downgrade the detectable CPU due to some issue that I am not aware of. Do I miss something? Is my approach to extend the arch_shared_info wrong in the first place? I am really thankful for some advice or pointers what is happening here.


Best


Jan

CONFIDENTIALITY: The contents of this e-mail are confidential and intended only for the above addressee(s). If you are not the intended recipient, or the person responsible for delivering it to the intended recipient, copying or delivering it to anyone else or using it in any unauthorized manner is prohibited and may be unlawful. If you receive this e-mail by mistake, please notify the sender and the systems administrator at straymail@tttech.com immediately.

[-- Attachment #2: Type: text/html, Size: 1949 bytes --]

             reply	other threads:[~2020-06-29  7:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-29  7:43 Jan Ruh [this message]
2020-06-29  9:18 ` Kernel requires x86-64 CPU, after modifying arch_shared_info struct Roger Pau Monné
2020-06-29  9:56   ` AW: " Jan Ruh
2020-06-29 10:17     ` Roger Pau Monné
2020-06-30  7:30       ` AW: " Jan Ruh

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=6f88fc3e2795436fa1f30dd026dd8eda@tttech.com \
    --to=jan.ruh@tttech.com \
    --cc=xen-devel@lists.xenproject.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.