9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: hiro <23hiro@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] VMX Cores
Date: Mon, 18 Mar 2024 12:40:42 +0100	[thread overview]
Message-ID: <CAFSF3XMb9QDncSSmtVeMqy3S+N-c7W3o81UdicbfFNj3Q+LvTg@mail.gmail.com> (raw)
In-Reply-To: <13FCA7C1E47C7879DAEF559AB19DEE5F@felloff.net>

> i dont see vmx causing kernel crashes for me.
> however, i think the author meant to express is lack
> of confidence in the air-tightiness of vmx giving
> the zillions of architectual registers you have to
> setup to contain a guest. it is easy to forget
> to set some bit and everything works until someone
> manages to exploit that.

and not like any competitor has any great solution to that either. the
hardware just never was built for such strong isolation to
meaningfully prevent that kind of exploit. and if it did, there would
still always be other side-channels. just less obvious ones (from
today's pov).
in terms of stability, my slowlaris hypervisor (their own vmx plus
qemu) has finally reached some limit, which destroyed the guest
kernel's interpretation of time, which created some centuries of
timeshifting, waits don't fire any more, and suddenly i have 1000s
days of uptime bec. it's like a hundred years later now. forced me to
destroy this virtual computer and thus reboot the guest. :D stuff
breaks. everywhere. vmx is small, so actually it might break less in
some edge-cases. but yes, virtualization is one more layer, and the
interfaces, drivers, aren't as minimal as they could be, so
virtualization still sucks. even with all these hw optimizations now.
still a neat hack, i guess if you want to implement multi-core vmx, a
lot of firefox on vmx on plan9 users will be happy. otherwise, what do
we need that needs multiple cores in a vm?

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Tc08115552282a0a2-M62c7b76e5e8a766d7ecc601d
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

      reply	other threads:[~2024-03-18 11:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-17 18:46 jubal.biggs
2024-03-17 20:45 ` cinap_lenrek
2024-03-18 11:40   ` hiro [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=CAFSF3XMb9QDncSSmtVeMqy3S+N-c7W3o81UdicbfFNj3Q+LvTg@mail.gmail.com \
    --to=23hiro@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).