From: Alexander Sychev <santucco@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Plan 9 won't boot on Xen 8.0
Date: Thu, 18 Jul 2019 12:43:09 +0300 [thread overview]
Message-ID: <CAPavXpCGF78wPDhMAcFNKU=ikZs4iYhkdZDWRY6SmXCZehHS8A@mail.gmail.com> (raw)
In-Reply-To: <CAJ1xhMU+bKidMcOVNV3-=NnarudX5ApWvqAjciGFH5LsbGbwUw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2136 bytes --]
You are welcome, i hope it helps.
Can i ask, why do you want to migrate from Xen to Qemu?
I am triyint to do the opposite, to use Xen only without any part of Qemu.
Some time ago i made support of Xen keyboard and framebuffer, and full
Plan9 was working in an X session.
But since Xen 4.10.x the framebuffer support stoped to work, i don't know
why, it seems only VNC is supported now.
But Xen framebuffer uses Qemu, so i was anyway going to reimplement the
graphic output via DRM.
For the moment i can't say when i finish it.
On Wed, Jul 17, 2019 at 9:31 PM Alexander Kapshuk <
alexander.kapshuk@gmail.com> wrote:
> Thanks for your response, and apologies for the delay in replying.
> I was thinking if it would also be possible to migrate the current
> Plan 9 setup that is used with Xen to Qemu.
> Thanks.
>
> On Mon, Jul 8, 2019 at 10:53 AM Alexander Sychev <santucco@gmail.com>
> wrote:
> >
> > Hi,
> >
> > Xen now looks for a section with name '__xen_guest' starting from a
> second section.
> > A simple workaround is to make two '__xen_guest' sections (with a small
> patch of xenelf.c):
> >
> > diff -r xen/mkfile xen2/mkfile
> > 105c107,108
> > < ./xenelf.$cputype $target.elf $target __xen_guest ''$XENELF''
> > ---
> > > ./xenelf.$cputype $target.elf $target.elf2 __xen_guest
> ''$XENELF''
> > > ./xenelf.$cputype $target.elf2 $target __xen_guest ''$XENELF''
> > diff -r xen/xenelf.c xen2/xenelf.c
> > 131c131,132
> > < ns = 0; //GETS(&e.shnum);
> > ---
> > > ns = GETS(&e.shnum);
> >
> > I run it on Xen 4.10.3
> >
> > On Fri, Jul 5, 2019 at 9:25 AM Alexander Kapshuk <
> alexander.kapshuk@gmail.com> wrote:
> >>
> >> I had Plan 9 running on Xen 7.5. After upgrading to Xen 8.0 Plan 9
> >> won't boot any more.
> >> I get a 'No bootable device' message displayed.
> >>
> >> The system was previously setup by someone else.
> >> If I can, I would like to try and make it run on Xen 8.0.
> >>
> >> Any tips would be much appreciated.
> >>
> >
> >
> > --
> > Best regards,
> > Alexander
>
>
--
Best regards,
Alexander
[-- Attachment #2: Type: text/html, Size: 3069 bytes --]
next prev parent reply other threads:[~2019-07-18 9:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-05 6:22 Alexander Kapshuk
2019-07-08 7:51 ` Alexander Sychev
2019-07-17 18:28 ` Alexander Kapshuk
2019-07-18 9:43 ` Alexander Sychev [this message]
2019-07-18 11:13 ` hiro
2019-07-18 11:33 ` Alexander Sychev
2019-07-18 14:12 ` hiro
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='CAPavXpCGF78wPDhMAcFNKU=ikZs4iYhkdZDWRY6SmXCZehHS8A@mail.gmail.com' \
--to=santucco@gmail.com \
--cc=9fans@9fans.net \
/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).