Hi, I'm Artichiro Seda from NTT. Today, I want to talk about the updates in DIMA page
on 2.0. In this series, we are expanding the project focus to cover protecting AI, as well
as Israeli running continuous on laptops.
So, by the DIMA, RIMA stands for Linux Virtual Machine. It's optimized for running
containers and AI agents, but early candidates for other workloads as well.
And DIMA features automatic host-of-fire system sharing.
That means the host-of-fire system can be easily shared to the case operating system.
And it also supports automatic port routing.
That means you can access to the TCP IP ports of the guest OS, just as a local host on the host operating system.
So, you can just access the guest IP, just as a local host on the web browser running on the host operating system.
And DIMA comes with a built-in integration for several functional times, including continuity, which is a default.
And it also supports Joker, Potsumer, Kubernetes, and Aptiner.
And DIMA supports several host operating systems.
But in the case of Mac OS, you can just use PURU to install DIMA, PURU installed DIMA.
And you can use DIMA CTR set to stretch our virtual machine.
And you can just prefix as a DIMA command in the disk commands, such as not CTR.
Not CTR means continuity CTR uses the whole controlling or continuity.
Basically, it's similar to Joker.
So, this is Mac OS, and you can just pre-painted DIMA to Union.
And it's not Linux.
And inside DIMA share, the host directly is a business goal.
This is mounted on the Mac OS host operating system.
And you can run continuous using another CTR command.
This round is another CTR container, who running NX.
And you can just access to the test port as a Joker host.
So this is conducting through the disk as a Joker host.
So basically, it just looks like a process running on the host operating system directly.
But actually, it's wrapped inside the virtual machine.
So, here is the project similar to DIMA.
One example is WC2.
So, with WC2, the Windows host 5 system is visible to the Linux disk.
And the Linux disk supports are just accessible as a Joker host on the Windows host.
So, it's a very similar to DIMA, but the WC2, of course, only supports Windows host.
And it reminds also similar to big runs in some sense.
But big runs is not property.
And big runs also missing some features such as automatic port running.
So you can just configure big runs to who are the ports.
But it doesn't automatically scan ports used in the guest operating system.
So it's quite different from DIMA in that sense.
And also DIMA is a very similar to DIMA.
But it's only made for Joker.
And it's now abandoned a few years ago.
And DIMA is also similar to the desktop, but without GUI.
But the DIMA desktop is just made for the cover.
Of course, and it's property.
And let me talk about origin of the project in the current status.
So I launched the project five years ago for the sake of promoting
Continuity, including NRC to market or users.
So this project was originally designed as Continuity in my scene.
But through the course of the community, the scope has expanded.
That's just for a quantity.
So it's the Linux machine.
Naturally, it's the machine.
So we support several container engines, including Joker,
Pokémon, Kubernetes, and Optiner.
And we also support known container workloads.
For example, it's also used for sandboxing AI coding engines.
So you know, if you run AI coding agents like Clouds,
it's a oxygen three rooms.
Everything under your home directory, or maybe it's
installs some random properties from the internet.
So it's really scary to run AI coding agents, or you are up directly.
So you can use the DIMA to send up such AI coding agents.
And DIMA is also used for a way.
You want to run a known Ubuntu OS such as Hydra on GitHub Actions.
There was a GitHub Actions on this supports Ubuntu as a Linux guest.
But you can just run DIMA inside GitHub Actions.
So you can run any distribution such as Hydra, or
Princess AI, or Work Linux, or Aromalyics, or Optine,
and other distributions, and there's GitHub Actions.
And DIMA is originally made of marketing tools,
but we now support several host operating systems,
including Linux Windows, new to BSD, and Dragon Privacy.
We don't support previously because our queueing
doesn't really work well on previously host.
But I think we can see a real support previously as well.
And we have lots of support, the free software projects
based on DIMA.
The most of the famous one is KORIMA.
This is an alternative to the AI for DIMA,
with a Docker at the default engine.
KORIMA is very famous.
Maybe it's more famous than DIMA itself.
It has a very huge number of GitHub stores.
So with KORIMA, you can just run Joker, or MacOS, very easily.
And it doesn't need a proprietary Joker desktop license.
And also there's a runger desktop license.
It's a combination of DIMA and KORIMA, and KORIMA.
So this is a screenshot of runger desktop.
And this is a JOR dashboard, or you can check the new
other status of DIMA runger desktop running KORIMA.
And this is also free software.
And the next run is a print.
It's AWS product.
And it's made for local development with AWS services,
such as AWS server, application model,
AWS, some of the recent way announced this support.
And which is also free software as well.
And there are projects like DIMA, GUI, which provides GUI based on
huge framework, like this.
And also, platform desktop supports
managing DIMA instances.
And we have more server-party projects.
So let's talk about how it works.
So this is a picture of DIMA.
So DIMA is a DIMA city CIRI, KORIMA interface.
This is used by Shuman, or GUI, or MCP programming.
And this CIRI can be used for managing DIMA host-egent processes.
And host-egent processes use this BIM driver
to support a server-party machine implementations.
And this driver runs this BIM, and also connects to
the network driver.
And instead of BIM, we have DIMA-egent processes,
which handles five-system sharing and port-wadding,
and thinking real-time cook, and other jobs.
And DIMA is designed to be
incredible to support different implementations of
hyperbysers, such as QEMU, or Apple's
virtualization framework.
And then was busy on MacOS.
We also support WSR2 on Windows hosts.
And in button 2.0, we added support for KLONKIT,
which supports GPU acceleration on MacOS.
And in DIMA-egent 2, we also support GRPC
programming to support your own favorite hyperbysers
implementation.
And we also have the concept of inter-on-arm binary
effectors.
So the default is two-emium user mode.
So you can just run inter-bying ways on
the term instances of QEMU.
And on MacOS hosts, you can also use ROS-8.2,
which is more fast, faster than QEMU.
And for five-system sharing, we support
Part-VIOFS and Part-VIO90.
And we also support reverse SSHFS,
where the guest operating system doesn't support
Part-VIOFS and Part-VIO90.
And for networking, the default is user mode
network based on GByser.
So this company works in the user space,
so it doesn't need any route privilege on the host.
But when you want to access the virtual machine by IP,
not just by the Roka host address,
you can use a sorted BEMU driver.
This needs route privilege.
So you have to launch it with SIDO.
And for busy driver, you can automatically use
a busy network driver to access the BEMU by IP.
This one only works with busy but this doesn't need SIDO command.
And for port routing,
we watch EVP events.
It's a need to link SOC diagnosis events.
And we use EVP to watch this port routing events.
But this implementation doesn't work
for key brand service ports,
because key brand service ports are quite different from regular ports,
because it uses IP tables.
So we also have a custom logic for
what's the key brand service ports.
And the default,
this row of the guestways is Ubuntu,
but you can also choose other distribution
as automatically used by our Linux,
sent of stream, db and open services,
Oracle Linux, and from Linux.
And the default contenting is contenting,
but you can also use updating a dog or a partner.
In route risk mode by default,
or in route for mode,
when you need privileged operations.
And you can also use several
additional instructions,
such as Kubernetes.
And you can just choose your templates
using this DMACC to your start command.
And let me talk about recent updates.
So we recently got promoted to CNC incorporating projects.
CNC is responsible for creating a project,
which is hosting several projects,
such as Kubernetes.
And CNC has three strategies.
Sandbox, integrating and graduated.
We joined CNC as a Sandbox in 2022,
and we got promoted to integrating
last year.
And we anticipate that we can promote it
to graduate to be able in the next couple of years.
And the number of retailers is growing.
So we now have more than 20,000 upstairs,
and we have more than 170 contributors.
So thanks to all the contributors and all the users.
And in November, we released a remote version to 0.
And this week, we added a product infrastructure
to auto implementing new features
without modifying remote.
So we have the concept of BM driver
projects to support additional hyperbysers.
And we also support CLI projects to add more subcommands
to the DMACC to CLI.
And we also have projects for URL schema
for fixing templates from custom remote addresses.
And we support GP access additional using
care on to the BM driver.
And we also added MCP server,
model contest protocol server for protecting AI agents.
So in just weeks, we are extending things
to cover AI as well as consumers.
So the original goal in 2021 was to facilitate
running continuity on Mac OS.
But the project turned out to be very useful
for securing AI agents too.
So as to prevent them from accessing the host of files
and the commands.
So you know, AI agents may make
hallucination to remove files under the home directory.
So this example is from Reddit,
but this example quote attempted
to clean up some packages and unused files.
And quote launched RMR commands
to test, test, test, test, press, press.
And the program is that it even removes
the home directory to the source.
So it removes everything in the home directory.
So it's very scary to run AI on your laptop
directly.
So it's useful for securing such AI agents.
And I also have to note that AI may also make
hallucination to install fake packages with
plausible names by running people in store or
MPM install or go install or party buyers.
And AI agents now have a web search too.
And AI agents are sometimes deceived by fake websites
once they're internet, appears the web search too
to install some malicious purchases.
So AI agents often come with built in a sandboxing
who is an example.
They use a dandroque or joker container or Linux,
but it's not as strong as virtual machines.
And some AI agents use a sandbox exec,
which is similar to dandroque or macOS,
but this sandbox exec command has been
deported almost a decade ago.
And Apple recommends using up sandbox,
but it's not direct refreshment to a sandbox exec
command.
So AI agent products are still
derived on sandbox exec commands.
So we can use Dima as a reversal sandbox
for any AI agent.
And it's also, it can coexist with
the built in sandboxing provided by AI agents.
And we're running AI with Dima,
there are two scenarios.
AI inside Dima and AI outside Dima.
So AI inside Dima is running codex,
compiled or crawled or jiminite,
or maybe open code inside Dima.
And you can also do an inference inside Dima
using GPU acceleration.
And AI outside Dima means AI agent running on the host
can connect to Dima and Dima provides
MCP servers for protecting five system course
and command execution course.
And you can also use the escorts and remote SSH
and compile notes with Dima.
And we have example of running AI inside Dima.
For example, you can use this Dima CTR
start command to only mouse working
directly in mid-right mode.
And we can install open code.
So I don't have time to show the demo.
But inside websites, we have example for continuous.
And we also have examples for AI agents.
So you can choose a crawled code or codex or jiminite or
jiminite and compile.
And you can just run its inside Dima.
And we also have GPU acceleration.
So that must CPP running inside Dima
uses a partner to talk to a partner or GPU.
And the partner or GPU,
you talk to both Dima and Brieke,
which translates partner library code
to meta library course, which is used by Apple.
I think I can show a quick demo.
So this is using a partner GPU,
a partner or GPU binas, a point for max.
And I can talk to AI running inside Dima.
Yeah, so the performance is not so much.
And for running AI outside Dima,
Dima exposes several MCP tools,
such as district where you apply run share command.
These are a similar to jiminite CRIs commands,
but it's stored with some of us using BM.
And we plan to raise budget to a point to run in March.
And in this race, we have single modes,
unlike months.
I think the diverse are with Dima,
but only after user information.
So this prevents AI from the situation
where a story I removed everything,
including Dr. Dima.
So this should be highly useful running AI inside Dima.
And I don't have time to cover our future ideas,
but we've come contributions in this field.
And we have a huge community,
and we have website, GitHub, and Slack, and Twitter,
and thank you.
Any questions?
Sorry?
Any questions?
So Dima, on different posters, talking to each other,
or they have to run on the same post?
So you can use a bridge device
to directly connect virtual machine
to the host network.
So you can just connect multiple instances
running on several posts.
How does Dima remove this mouse and try to?
What have we received too?
In the object itself, you're lost.
The C-try is mounted,
between two of the VMDU terms.
How does Dima remove the mouse and feed?
Actually, I don't use WC2 by myself,
so I'm not sure about WC2 implementation.
Please, don't worry.
These are a lot of big questions.
That's it.