From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 From: Alexander Kapshuk Date: Fri, 5 Jul 2019 09:22:48 +0300 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset="UTF-8" Subject: [9fans] Plan 9 won't boot on Xen 8.0 Topicbox-Message-UUID: 0144a6cc-eada-11e9-9d60-3106f5b1d025 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. From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 References: In-Reply-To: From: Alexander Sychev Date: Mon, 8 Jul 2019 10:51:34 +0300 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary="0000000000003546d7058d26b773" Subject: Re: [9fans] Plan 9 won't boot on Xen 8.0 Topicbox-Message-UUID: 0148c7f2-eada-11e9-9d60-3106f5b1d025 --0000000000003546d7058d26b773 Content-Type: text/plain; charset="UTF-8" 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 --0000000000003546d7058d26b773 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
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/mkfi= le xen2/mkfile
105c107,108
< =C2=A0 =C2=A0 =C2=A0 ./xenelf.$cputyp= e $target.elf $target __xen_guest ''$XENELF''
---
>= ; =C2=A0 =C2=A0 =C2=A0 ./xenelf.$cputype $target.elf $target.elf2 __xen_gue= st ''$XENELF''
> =C2=A0 =C2=A0 =C2=A0 ./xenelf.$cputy= pe $target.elf2 $target __xen_guest ''$XENELF''
diff -r = xen/xenelf.c xen2/xenelf.c
131c131,132
< =C2=A0 =C2=A0 =C2=A0 ns = =3D 0; //GETS(&e.shnum);
---
> =C2=A0 =C2=A0 =C2=A0 ns =3D GET= S(&e.shnum);

I run it on Xen 4.10.3

On Fri, Jul 5, 201= 9 at 9:25 AM Alexander Kapshuk <alexander.kapshuk@gmail.com> wrote:
I had Plan 9 running on Xen 7.5. After up= grading 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,
=C2=A0 A= lexander
--0000000000003546d7058d26b773-- From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 References: In-Reply-To: From: Alexander Kapshuk Date: Wed, 17 Jul 2019 21:28:51 +0300 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset="UTF-8" Subject: Re: [9fans] Plan 9 won't boot on Xen 8.0 Topicbox-Message-UUID: 019b0508-eada-11e9-9d60-3106f5b1d025 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 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 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 From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 References: In-Reply-To: From: Alexander Sychev Date: Thu, 18 Jul 2019 12:43:09 +0300 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary="000000000000b2bd86058df170dd" Subject: Re: [9fans] Plan 9 won't boot on Xen 8.0 Topicbox-Message-UUID: 01abf908-eada-11e9-9d60-3106f5b1d025 --000000000000b2bd86058df170dd Content-Type: text/plain; charset="UTF-8" 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 > 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 --000000000000b2bd86058df170dd Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
You are welcome, i hope it helps.
Can i ask, why do yo= u want to migrate from Xen to Qemu?
I am triyint to do the opposi= te, to use Xen only without any part of Qemu.
Some time ago i mad= e support of Xen keyboard and framebuffer, and full Plan9 was working in an= =C2=A0 X session.
But since Xen 4.10.x the framebuffer support st= oped to work, i don't know why, it seems only VNC is supported now.
But Xen framebuffer uses Qemu, so i was=C2=A0 anyway going to reimpl= ement 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 Alexa= nder Kapshuk <alexander.k= apshuk@gmail.com> wrote:
Thanks for your response, and apologies for the delay in re= plying.
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 f= rom a second section.
> A simple workaround is to make two '__xen_guest' sections (wit= h a small patch of xenelf.c):
>
> diff -r xen/mkfile xen2/mkfile
> 105c107,108
> <=C2=A0 =C2=A0 =C2=A0 =C2=A0./xenelf.$cputype $target.elf $target _= _xen_guest ''$XENELF''
> ---
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0./xenelf.$cputype $target.elf $target.e= lf2 __xen_guest ''$XENELF''
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0./xenelf.$cputype $target.elf2 $target = __xen_guest ''$XENELF''
> diff -r xen/xenelf.c xen2/xenelf.c
> 131c131,132
> <=C2=A0 =C2=A0 =C2=A0 =C2=A0ns =3D 0; //GETS(&e.shnum);
> ---
> >=C2=A0 =C2=A0 =C2=A0 =C2=A0ns =3D 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,
>=C2=A0 =C2=A0Alexander



--
Best regards,
=C2=A0 A= lexander
--000000000000b2bd86058df170dd-- From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: From: hiro <23hiro@gmail.com> Date: Thu, 18 Jul 2019 13:13:01 +0200 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset="UTF-8" Subject: Re: [9fans] Plan 9 won't boot on Xen 8.0 Topicbox-Message-UUID: 01b067d6-eada-11e9-9d60-3106f5b1d025 > 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. why not use drawterm instead? From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 References: In-Reply-To: From: Alexander Sychev Date: Thu, 18 Jul 2019 14:33:41 +0300 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary="000000000000fb68fc058df2fbec" Subject: Re: [9fans] Plan 9 won't boot on Xen 8.0 Topicbox-Message-UUID: 01b4b0b6-eada-11e9-9d60-3106f5b1d025 --000000000000fb68fc058df2fbec Content-Type: text/plain; charset="UTF-8" As usual for me, i have longterm plans for that usecase :-) drawterm supposes one Plan9 machine and one machine with any other OS + drawterm. I would like to have Plan9 in Xen with a support of peripherals as much as possible, and without X. Linux (or something similar) has to be minimal Dom0 On Thu, Jul 18, 2019 at 2:14 PM hiro <23hiro@gmail.com> wrote: > > 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. > > why not use drawterm instead? > > -- Best regards, Alexander --000000000000fb68fc058df2fbec Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
As usual for me, i have longterm plans for that usecase :-= )
drawterm supposes one Plan9 machine and one machine with any other OS= =C2=A0+ drawterm.
I would like to have Plan9 in Xen with a suppor= t of peripherals as much as possible, and without X.
Linux (or so= mething similar) has to be minimal Dom0


<= div class=3D"gmail_quote">
On Thu, Jul= 18, 2019 at 2:14 PM hiro <23hiro@gm= ail.com> wrote:
> Plan9 was working in an=C2=A0 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=C2=A0 anyway going to reimplem= ent the
> graphic output via DRM.

why not use drawterm instead?



--
Best regards,
=C2=A0 A= lexander
--000000000000fb68fc058df2fbec-- From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: From: hiro <23hiro@gmail.com> Date: Thu, 18 Jul 2019 16:12:54 +0200 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset="UTF-8" Subject: Re: [9fans] Plan 9 won't boot on Xen 8.0 Topicbox-Message-UUID: 01cd72cc-eada-11e9-9d60-3106f5b1d025 avoiding X sounds great. but i guess then it's probably a lot of work. unless you just go native! :)