From: "Marc-François LUCCA-DANIAU" <mfld.fr@gmail.com>
To: ELKS <Linux-8086@vger.kernel.org>
Subject: Re: Running elks in a vm.
Date: Mon, 27 Feb 2017 14:21:20 +0100 [thread overview]
Message-ID: <CACpuWUkV+ih_5h6ukMVSW-pwYcCAkOEXKgo=AcRu1eE7aitugg@mail.gmail.com> (raw)
In-Reply-To: <C941C42D137A43078895F07A477B9C1D@PotthastHP>
You cannot use that latest VM with ELKS networking. It emulates the
PCI version of the NE2K, not the ISA version (see
https://github.com/copy/v86/blob/master/Readme.md). ELKS does not
support PCI.
MFLD
2017-02-26 13:37 GMT+01:00 Georg Potthast <nospam@georgpotthast.de>:
> You can run ELKS e.g. in this Javascript VM within a web browser:
> http://copy.sh/v86/
>
> However, this will only work when you load a bootable hard disk image which
> you can generate with my recently committed script. This script is currently
> named buildHD.sh and in the elkscmd directory.
>
> How you can do ethernet networking when running in this VM I cannot tell.
>
> Georg
>
>
> -----Ursprüngliche Nachricht----- From: Tom
> Sent: Sunday, February 26, 2017 11:14 AM
> To: ELKS
> Subject: Running elks in a vm.
>
>
> I play a little in 8086tiny from time to time. Now there is networking
> I'm wondering if there is a vm it can run in?
>
> Tom
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-8086" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> --
> To unsubscribe from this list: send the line "unsubscribe linux-8086" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2017-02-27 13:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-26 10:14 Running elks in a vm Tom
2017-02-26 11:49 ` Marc-F. LUCCA-DANIAU
2017-02-26 12:37 ` Georg Potthast
2017-02-27 13:21 ` Marc-François LUCCA-DANIAU [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='CACpuWUkV+ih_5h6ukMVSW-pwYcCAkOEXKgo=AcRu1eE7aitugg@mail.gmail.com' \
--to=mfld.fr@gmail.com \
--cc=Linux-8086@vger.kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).