#virtiofs — Public Fediverse posts

oke, das ist geil
nachdem ich jetzt alles in das jeweilige subvolume der 16tb platte kopiert habe, habe ich jetzt beide 4tb blockdevices aus der windows VM entfernt und stattdessen die jeweiligen mountpoints per #virtiofs und #winfsp mit den selben laufwerkbuchstaben in windows eingebunden - as if nothing happend 😳
mit #linux kann man den pc einfach genau so nutzen wie man will und nicht wie irgend ne kack firma vorgibt ihn nutzen zu sollen 😎
#homelab

oke, das ist geil
nachdem ich jetzt alles in das jeweilige subvolume der 16tb platte kopiert habe, habe ich jetzt beide 4tb blockdevices aus der windows VM entfernt und stattdessen die jeweiligen mountpoints per #virtiofs und #winfsp mit den selben laufwerkbuchstaben in windows eingebunden - as if nothing happend 😳
mit #linux kann man den pc einfach genau so nutzen wie man will und nicht wie irgend ne kack firma vorgibt ihn nutzen zu sollen 😎
#homelab

oke, das ist geil
nachdem ich jetzt alles in das jeweilige subvolume der 16tb platte kopiert habe, habe ich jetzt beide 4tb blockdevices aus der windows VM entfernt und stattdessen die jeweiligen mountpoints per #virtiofs und #winfsp mit den selben laufwerkbuchstaben in windows eingebunden - as if nothing happend 😳
mit #linux kann man den pc einfach genau so nutzen wie man will und nicht wie irgend ne kack firma vorgibt ihn nutzen zu sollen 😎
#homelab

Файловый сервер SAMBA / pool ZFS

Всегда хотел развернуть шару SMB с хранилищем на ZFS, но есть нюансы… Совершенно не приемлю, чтобы пользователи каким либо образом взаимодействовали с сервером, где расположен pool\ZFS. В моем понимании, СХД может включать в себя только служебные компоненты без прямого пользовательского доступа к его сети. Идея казалось очень простой - поднимаем виртуальный сервер, подключаем его к домену, цепляем туда существующий ZFS пул....

https://habr.com/ru/articles/1013164/

#samba #zfs #kvm #VirtioFS #xattr #acl

Файловый сервер SAMBA / pool ZFS

Всегда хотел развернуть шару SMB с хранилищем на ZFS, но есть нюансы… Совершенно не приемлю, чтобы пользователи каким либо образом взаимодействовали с сервером, где расположен pool\ZFS. В моем понимании, СХД может включать в себя только служебные компоненты без прямого пользовательского доступа к его сети. Идея казалось очень простой - поднимаем виртуальный сервер, подключаем его к домену, цепляем туда существующий ZFS пул....

https://habr.com/ru/articles/1013164/

#samba #zfs #kvm #VirtioFS #xattr #acl

Файловый сервер SAMBA / pool ZFS

Всегда хотел развернуть шару SMB с хранилищем на ZFS, но есть нюансы… Совершенно не приемлю, чтобы пользователи каким либо образом взаимодействовали с сервером, где расположен pool\ZFS. В моем понимании, СХД может включать в себя только служебные компоненты без прямого пользовательского доступа к его сети. Идея казалось очень простой - поднимаем виртуальный сервер, подключаем его к домену, цепляем туда существующий ZFS пул....

https://habr.com/ru/articles/1013164/

#samba #zfs #kvm #VirtioFS #xattr #acl

Файловый сервер SAMBA / pool ZFS

Всегда хотел развернуть шару SMB с хранилищем на ZFS, но есть нюансы… Совершенно не приемлю, чтобы пользователи каким либо образом взаимодействовали с сервером, где расположен pool\ZFS. В моем понимании, СХД может включать в себя только служебные компоненты без прямого пользовательского доступа к его сети. Идея казалось очень простой - поднимаем виртуальный сервер, подключаем его к домену, цепляем туда существующий ZFS пул....

https://habr.com/ru/articles/1013164/

#samba #zfs #kvm #VirtioFS #xattr #acl

No inotifying the host in #virtiofs?

No inotifying the host in #virtiofs?

No inotifying the host in #virtiofs?

I'm looking for some advice. I have a #Proxmox install with a ZFS pool mounted at `/tank` and my #Nextcloud data at `/tank/nextcloud`

I currently have a non-Docker version of Nextcloud running in an LXC container but it has... issues.

I'm thinking of running the Docker AIO image but I every time I try to pass through the `/tank/nextcloud` directory to a VM via #VirtioFS, it ends up causing the host kernel to panic.

Is there another way to do this?

I'm looking for some advice. I have a #Proxmox install with a ZFS pool mounted at `/tank` and my #Nextcloud data at `/tank/nextcloud`

I currently have a non-Docker version of Nextcloud running in an LXC container but it has... issues.

I'm thinking of running the Docker AIO image but I every time I try to pass through the `/tank/nextcloud` directory to a VM via #VirtioFS, it ends up causing the host kernel to panic.

Is there another way to do this?

I'm looking for some advice. I have a #Proxmox install with a ZFS pool mounted at `/tank` and my #Nextcloud data at `/tank/nextcloud`

I currently have a non-Docker version of Nextcloud running in an LXC container but it has... issues.

I'm thinking of running the Docker AIO image but I every time I try to pass through the `/tank/nextcloud` directory to a VM via #VirtioFS, it ends up causing the host kernel to panic.

Is there another way to do this?

I'm looking for some advice. I have a #Proxmox install with a ZFS pool mounted at `/tank` and my #Nextcloud data at `/tank/nextcloud`

I currently have a non-Docker version of Nextcloud running in an LXC container but it has... issues.

I'm thinking of running the Docker AIO image but I every time I try to pass through the `/tank/nextcloud` directory to a VM via #VirtioFS, it ends up causing the host kernel to panic.

Is there another way to do this?

I'm looking for some advice. I have a #Proxmox install with a ZFS pool mounted at `/tank` and my #Nextcloud data at `/tank/nextcloud`

I currently have a non-Docker version of Nextcloud running in an LXC container but it has... issues.

I'm thinking of running the Docker AIO image but I every time I try to pass through the `/tank/nextcloud` directory to a VM via #VirtioFS, it ends up causing the host kernel to panic.

Is there another way to do this?

Unhappy with #DockerDesktop on #macOS? Give #Colima a try!

It's a free and open #container runtime for macOS. It now supports the macOS #virtualization framework, #virtiofs for fast volume mounts and forwarding #inotify events for hot/live reloading. It can even provide a #containerd, #kubernetes or #incus runtime.

https://github.com/abiosoft/colima

(I would've preferred #podman, as that's what I'm mostly using in production, but it still doesn't support forwarding inotify events on macOS)

Unhappy with #DockerDesktop on #macOS? Give #Colima a try!

It's a free and open #container runtime for macOS. It now supports the macOS #virtualization framework, #virtiofs for fast volume mounts and forwarding #inotify events for hot/live reloading. It can even provide a #containerd, #kubernetes or #incus runtime.

https://github.com/abiosoft/colima

(I would've preferred #podman, as that's what I'm mostly using in production, but it still doesn't support forwarding inotify events on macOS)

Unhappy with #DockerDesktop on #macOS? Give #Colima a try!

It's a free and open #container runtime for macOS. It now supports the macOS #virtualization framework, #virtiofs for fast volume mounts and forwarding #inotify events for hot/live reloading. It can even provide a #containerd, #kubernetes or #incus runtime.

https://github.com/abiosoft/colima

(I would've preferred #podman, as that's what I'm mostly using in production, but it still doesn't support forwarding inotify events on macOS)

Unhappy with #DockerDesktop on #macOS? Give #Colima a try!

It's a free and open #container runtime for macOS. It now supports the macOS #virtualization framework, #virtiofs for fast volume mounts and forwarding #inotify events for hot/live reloading. It can even provide a #containerd, #kubernetes or #incus runtime.

https://github.com/abiosoft/colima

(I would've preferred #podman, as that's what I'm mostly using in production, but it still doesn't support forwarding inotify events on macOS)

Unhappy with #DockerDesktop on #macOS? Give #Colima a try!

It's a free and open #container runtime for macOS. It now supports the macOS #virtualization framework, #virtiofs for fast volume mounts and forwarding #inotify events for hot/live reloading. It can even provide a #containerd, #kubernetes or #incus runtime.

https://github.com/abiosoft/colima

(I would've preferred #podman, as that's what I'm mostly using in production, but it still doesn't support forwarding inotify events on macOS)

Aaand I’m back on #9pfs. The #virtiofs mount turned out to be unstable very quickly. All I/O on the mount started hanging just after 2 days, requiring hard reset of a VM. I guess I’ll try that again in 12 months 🤷‍♂️

Aaand I’m back on #9pfs. The #virtiofs mount turned out to be unstable very quickly. All I/O on the mount started hanging just after 2 days, requiring hard reset of a VM. I guess I’ll try that again in 12 months 🤷‍♂️

Aaand I’m back on #9pfs. The #virtiofs mount turned out to be unstable very quickly. All I/O on the mount started hanging just after 2 days, requiring hard reset of a VM. I guess I’ll try that again in 12 months 🤷‍♂️

Aaand I’m back on #9pfs. The #virtiofs mount turned out to be unstable very quickly. All I/O on the mount started hanging just after 2 days, requiring hard reset of a VM. I guess I’ll try that again in 12 months 🤷‍♂️

Aaand I’m back on #9pfs. The #virtiofs mount turned out to be unstable very quickly. All I/O on the mount started hanging just after 2 days, requiring hard reset of a VM. I guess I’ll try that again in 12 months 🤷‍♂️

I've switched from #9pfs to #virtiofs mount for a VM I run under my #proxmox host at home and did a few #fio benchmarks.

9pfs (before):

seq read (1M, 1 thread) - 1950 MiB/s
rand read (4K, 4 threads) - 213 MiB/s
seq write (1M, 1 thread) - 468 MiB/s
rand write (4K, 4 threads) - 80 MiB/s

virtiofs (after):

seq read (1M, 1 thread) - 5258 MiB/s
rand read (4K, 4 threads) - 291 MiB/s
seq write (1M, 1 thread) - 1074 MiB/s
rand write (4K, 4 threads) - 84 MiB/s

2.7x sequential read, 2.3x sequential write, 1.3x random read, and 1.05x random write.

Pretty good improvements!

Especially that this is for my media (movies/tv) mount where mostly sequential I/O is typically performed.

Note the underlying hardware is Samsung QVO SATA SSD, which is rather slow SSD, and likely a bottleneck in those random read/write tests. I expect there would be much bigger differences on a fast NVMe drive.

I've switched from #9pfs to #virtiofs mount for a VM I run under my #proxmox host at home and did a few #fio benchmarks.

9pfs (before):

seq read (1M, 1 thread) - 1950 MiB/s
rand read (4K, 4 threads) - 213 MiB/s
seq write (1M, 1 thread) - 468 MiB/s
rand write (4K, 4 threads) - 80 MiB/s

virtiofs (after):

seq read (1M, 1 thread) - 5258 MiB/s
rand read (4K, 4 threads) - 291 MiB/s
seq write (1M, 1 thread) - 1074 MiB/s
rand write (4K, 4 threads) - 84 MiB/s

2.7x sequential read, 2.3x sequential write, 1.3x random read, and 1.05x random write.

Pretty good improvements!

Especially that this is for my media (movies/tv) mount where mostly sequential I/O is typically performed.

Note the underlying hardware is Samsung QVO SATA SSD, which is rather slow SSD, and likely a bottleneck in those random read/write tests. I expect there would be much bigger differences on a fast NVMe drive.

I've switched from #9pfs to #virtiofs mount for a VM I run under my #proxmox host at home and did a few #fio benchmarks.

9pfs (before):

seq read (1M, 1 thread) - 1950 MiB/s
rand read (4K, 4 threads) - 213 MiB/s
seq write (1M, 1 thread) - 468 MiB/s
rand write (4K, 4 threads) - 80 MiB/s

virtiofs (after):

seq read (1M, 1 thread) - 5258 MiB/s
rand read (4K, 4 threads) - 291 MiB/s
seq write (1M, 1 thread) - 1074 MiB/s
rand write (4K, 4 threads) - 84 MiB/s

2.7x sequential read, 2.3x sequential write, 1.3x random read, and 1.05x random write.

Pretty good improvements!

Especially that this is for my media (movies/tv) mount where mostly sequential I/O is typically performed.

Note the underlying hardware is Samsung QVO SATA SSD, which is rather slow SSD, and likely a bottleneck in those random read/write tests. I expect there would be much bigger differences on a fast NVMe drive.

I've switched from #9pfs to #virtiofs mount for a VM I run under my #proxmox host at home and did a few #fio benchmarks.

9pfs (before):

seq read (1M, 1 thread) - 1950 MiB/s
rand read (4K, 4 threads) - 213 MiB/s
seq write (1M, 1 thread) - 468 MiB/s
rand write (4K, 4 threads) - 80 MiB/s

virtiofs (after):

seq read (1M, 1 thread) - 5258 MiB/s
rand read (4K, 4 threads) - 291 MiB/s
seq write (1M, 1 thread) - 1074 MiB/s
rand write (4K, 4 threads) - 84 MiB/s

2.7x sequential read, 2.3x sequential write, 1.3x random read, and 1.05x random write.

Pretty good improvements!

Especially that this is for my media (movies/tv) mount where mostly sequential I/O is typically performed.

Note the underlying hardware is Samsung QVO SATA SSD, which is rather slow SSD, and likely a bottleneck in those random read/write tests. I expect there would be much bigger differences on a fast NVMe drive.

I've switched from #9pfs to #virtiofs mount for a VM I run under my #proxmox host at home and did a few #fio benchmarks.

9pfs (before):

seq read (1M, 1 thread) - 1950 MiB/s
rand read (4K, 4 threads) - 213 MiB/s
seq write (1M, 1 thread) - 468 MiB/s
rand write (4K, 4 threads) - 80 MiB/s

virtiofs (after):

seq read (1M, 1 thread) - 5258 MiB/s
rand read (4K, 4 threads) - 291 MiB/s
seq write (1M, 1 thread) - 1074 MiB/s
rand write (4K, 4 threads) - 84 MiB/s

2.7x sequential read, 2.3x sequential write, 1.3x random read, and 1.05x random write.

Pretty good improvements!

Especially that this is for my media (movies/tv) mount where mostly sequential I/O is typically performed.

Note the underlying hardware is Samsung QVO SATA SSD, which is rather slow SSD, and likely a bottleneck in those random read/write tests. I expect there would be much bigger differences on a fast NVMe drive.

Linux und eine WindowsVM teilen sich ein Laufwerk

VirtioFS ist eine Technologie, die es ermöglicht, Dateisysteme zwischen dem Host-Betriebssystem und Gast-Betriebssystemen in einer virtuellen Umgebung effizient zu teilen. Es bietet eine hohe Leistung und niedrige Latenzzeiten, da es speziell für den Einsatz in Virtualisierungsumgebungen optimiert ist.

#kvm #qemu #virtiofs

https://dirkwouters.de/linux-und-eine-windowsvm-teilen-sich-ein-laufwerk/

Linux und eine WindowsVM teilen sich ein Laufwerk

VirtioFS ist eine Technologie, die es ermöglicht, Dateisysteme zwischen dem Host-Betriebssystem und Gast-Betriebssystemen in einer virtuellen Umgebung effizient zu teilen. Es bietet eine hohe Leistung und niedrige Latenzzeiten, da es speziell für den Einsatz in Virtualisierungsumgebungen optimiert ist.

#kvm #qemu #virtiofs

https://dirkwouters.de/linux-und-eine-windowsvm-teilen-sich-ein-laufwerk/

Linux und eine WindowsVM teilen sich ein Laufwerk

VirtioFS ist eine Technologie, die es ermöglicht, Dateisysteme zwischen dem Host-Betriebssystem und Gast-Betriebssystemen in einer virtuellen Umgebung effizient zu teilen. Es bietet eine hohe Leistung und niedrige Latenzzeiten, da es speziell für den Einsatz in Virtualisierungsumgebungen optimiert ist.

#kvm #qemu #virtiofs

https://dirkwouters.de/linux-und-eine-windowsvm-teilen-sich-ein-laufwerk/

Linux und eine WindowsVM teilen sich ein Laufwerk

VirtioFS ist eine Technologie, die es ermöglicht, Dateisysteme zwischen dem Host-Betriebssystem und Gast-Betriebssystemen in einer virtuellen Umgebung effizient zu teilen. Es bietet eine hohe Leistung und niedrige Latenzzeiten, da es speziell für den Einsatz in Virtualisierungsumgebungen optimiert ist.

#kvm #qemu #virtiofs

https://dirkwouters.de/linux-und-eine-windowsvm-teilen-sich-ein-laufwerk/

Linux und eine WindowsVM teilen sich ein Laufwerk

VirtioFS ist eine Technologie, die es ermöglicht, Dateisysteme zwischen dem Host-Betriebssystem und Gast-Betriebssystemen in einer virtuellen Umgebung effizient zu teilen. Es bietet eine hohe Leistung und niedrige Latenzzeiten, da es speziell für den Einsatz in Virtualisierungsumgebungen optimiert ist.

#kvm #qemu #virtiofs

https://dirkwouters.de/linux-und-eine-windowsvm-teilen-sich-ein-laufwerk/

If you use #limavm to build #linux stuff on a #mac, be careful - the #virtiofs driver is speedy but the case insensitivity of the underlying filesystem is also passed through. The kernel build does not like this.

If you use #limavm to build #linux stuff on a #mac, be careful - the #virtiofs driver is speedy but the case insensitivity of the underlying filesystem is also passed through. The kernel build does not like this.

If you use #limavm to build #linux stuff on a #mac, be careful - the #virtiofs driver is speedy but the case insensitivity of the underlying filesystem is also passed through. The kernel build does not like this.

If you use #limavm to build #linux stuff on a #mac, be careful - the #virtiofs driver is speedy but the case insensitivity of the underlying filesystem is also passed through. The kernel build does not like this.

If you use #limavm to build #linux stuff on a #mac, be careful - the #virtiofs driver is speedy but the case insensitivity of the underlying filesystem is also passed through. The kernel build does not like this.

Having a weird issue with #virtiofs. I'd like to use Uptime Kuma to monitor services. It uses sqlite as its database, but it seems to complain about the filesystem. People using NFS also seem to have problems

Having a weird issue with #virtiofs. I'd like to use Uptime Kuma to monitor services. It uses sqlite as its database, but it seems to complain about the filesystem. People using NFS also seem to have problems

Ever wanted a VM, but without all that "clicking through an installer through emulated VGA" nonsense?
Why can't you just boot from a folder with a file system?
Well, with #virtiofs you can!

Ever wanted a VM, but without all that "clicking through an installer through emulated VGA" nonsense?
Why can't you just boot from a folder with a file system?
Well, with #virtiofs you can!

Ever wanted a VM, but without all that "clicking through an installer through emulated VGA" nonsense?
Why can't you just boot from a folder with a file system?
Well, with #virtiofs you can!

Ever wanted a VM, but without all that "clicking through an installer through emulated VGA" nonsense?
Why can't you just boot from a folder with a file system?
Well, with #virtiofs you can!

Ever wanted a VM, but without all that "clicking through an installer through emulated VGA" nonsense?
Why can't you just boot from a folder with a file system?
Well, with #virtiofs you can!

Does anyone else keep thinking about the potential of #microVM|s and #virtiofs?

Does anyone else keep thinking about the potential of #microVM|s and #virtiofs?

Does anyone else keep thinking about the potential of #microVM|s and #virtiofs?