Virtualization enabled in bios?

It is the more flexible one since it allows to mount ro volumes which virtiofs doesn’t allow yet

Also virtiofs can be really resource intensive concerning RAM

you have a server

o

on Host

mkdir /share
chmod 777 /share

then add a “filesystem” and on source put “/share”, and on target “/sharepoint”

on guest
mkdir /share
mount -t 9p -o trans=virtio /sharepoint /share

also on guest you can add it to fstab, but i dont remember how

/sharepoint /share 9p trans=virtio 0 0
i guess

the order of factors does not change the product

seriously, being parameters i think it does not affect, i just copied what was in the bash_history of my virtual machine

The same way duh

Also the rights may be fucked up there, better going with matching uid or mapped mode

What the fuck are you saying

https://twitter.com/nixcraft/status/1559781405785493504?t=

When I start a virtual machine, the progress stay at here for ever. Why?

Give me a hand, please

And I can’t close the dialog.

Can’t kill the process.

Wait, the plan9 protocol? Haven’t seen that used a lot outside of plan 9 itself

strange, it’s widely used

why chinese,and VirtualBox need dkms modules

artix linux kiwami

dkms installed

My CPU is 12th Gen Intel i7

Virtualization enabled in bios?

wut. I’d say every mainstream SO kernel support 9p. don’t know about *bsd but I believe they support it too

It is a standard for host/guest communication

The main problem is still that it needs 18 balls

Enabled

what

Finally

At last

I have confirmation

My CPU has a hardware bug

Its borked