Lingolol

Stefano MarinelliI've never hidden my admiration for <a href="https://mastodon.bsd.cafe/tags/illumos" class="mention hashtag" rel="nofollow noopener" target="_blank">#illumos</a>-based systems. I have a few setups based on <a href="https://mastodon.bsd.cafe/tags/OmniOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#OmniOS</a> and <a href="https://mastodon.bsd.cafe/tags/SmartOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#SmartOS</a>, and they're solid as a rock. I like them both: OmniOS is more "malleable", while SmartOS is more of a hypervisor like <a href="https://mastodon.bsd.cafe/tags/xcp" class="mention hashtag" rel="nofollow noopener" target="_blank">#xcp</a>-ng or <a href="https://mastodon.bsd.cafe/tags/xen" class="mention hashtag" rel="nofollow noopener" target="_blank">#xen</a> - meaning you install it on the host and delegate everything else to the zones.I also love <a href="https://mastodon.bsd.cafe/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeBSD</a> jails, but zones sometimes cover use cases that jails can't (and vice versa). For example, imposing RAM limits in jails works, but it effectively "denies more ram" to a process when it requests more memory. The end user doesn't see this directly. On illumos, the user sees everything. I have some `lx` zones with Debian and Virtualmin, and users have never noticed that they aren't really on <a href="https://mastodon.bsd.cafe/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a>. A free or top will show only the assigned RAM.And that's one of the biggest problems with open-source operating systems: they all have something good, and I always feel the urge to use them all! 🙂<a href="https://mastodon.bsd.cafe/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a> <a href="https://mastodon.bsd.cafe/tags/IT" class="mention hashtag" rel="nofollow noopener" target="_blank">#IT</a> <a href="https://mastodon.bsd.cafe/tags/SysAdmin" class="mention hashtag" rel="nofollow noopener" target="_blank">#SysAdmin</a>

Paco Hope #resistAnybody out there in <a href="https://infosec.exchange/tags/homelab" class="mention hashtag" rel="nofollow noopener" target="_blank">#homelab</a> land using <a href="https://infosec.exchange/tags/TrueNAS" class="mention hashtag" rel="nofollow noopener" target="_blank">#TrueNAS</a> Scale with VMs?I've built a nice, reliable NAS. And then I noticed that it could do VMs. Great! I thought. I have a couple different VMs running some important things like <a href="https://infosec.exchange/tags/HomeAssistant" class="mention hashtag" rel="nofollow noopener" target="_blank">#HomeAssistant</a>.What I have discovered is that their VM support is terrible. Unless I misunderstand, I literally cannot do any of these things:<ul><li>backup a VM</li><li>restore a VM</li><li>export a VM</li><li>import a VM</li><li>snapshot a VM</li></ul>If I treat each VM like a full <a href="https://infosec.exchange/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a> host, I can back it up using something else (e.g., <code>rsync</code>). But if this was <a href="https://infosec.exchange/tags/xcp" class="mention hashtag" rel="nofollow noopener" target="_blank">#xcp</a> with Xen Orchestra, I'd have this whole thing solved in seconds.I'm thinking about creating a big VM, running a nested hypervisor (XCP) and then running my VMs there. But that sounds like a huge faff. And even then, while I could snapshot the child VMs, that parent VM running the hypervisor would be hard to backup/restore.I have plenty of RAM and spare CPU cycles on my NAS. But I've only recently understood how bad this VM support is. If I lost my HomeAssistant VM I'd cry.Anybody have thoughts on this? <a href="https://infosec.exchange/tags/selfhosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#selfhosting</a> <a href="https://infosec.exchange/tags/selfhosted" class="mention hashtag" rel="nofollow noopener" target="_blank">#selfhosted</a>

Paco Hope #resistIf any <a href="https://infosec.exchange/tags/homelab" class="mention hashtag" rel="nofollow noopener" target="_blank">#homelab</a> folks have some spare disk space and bandwidth and want to help <a href="https://infosec.exchange/tags/resist" class="mention hashtag" rel="nofollow noopener" target="_blank">#resist</a>, you can <a href="https://infosec.exchange/tags/selfhost" class="mention hashtag" rel="nofollow noopener" target="_blank">#selfhost</a> an instance of <a href="https://wiki.archiveteam.org/index.php/ArchiveTeam_Warrior" rel="nofollow noopener" target="_blank">ArchiveTeam Warrior</a> as a VM.The VM appliances are downloadable off of GitHub and then you just launch the VM and let it work.If you use <a href="https://infosec.exchange/tags/xcp" class="mention hashtag" rel="nofollow noopener" target="_blank">#xcp</a> as your <a href="https://infosec.exchange/tags/xen" class="mention hashtag" rel="nofollow noopener" target="_blank">#xen</a> hypervisor, and <a href="https://infosec.exchange/tags/xenorchestra" class="mention hashtag" rel="nofollow noopener" target="_blank">#xenorchestra</a> to manage it, you might think you can just give it the GitHub URL and import. Sadly, no. I got an error. But the VM is only 165M, so if you download it to your laptop and then upload it via the XO web interface, it's trivial to launch.

gyptazyVirtualization - How’s it going? My personal and the <a href="https://mastodon.bsd.cafe/@BoxyBSD" class="u-url mention" rel="nofollow noopener" target="_blank">@BoxyBSD</a> infrastructure will be shifted. By the end of the year a multi geo located setup (Germany, France, Canada) takes place - running on <a href="https://mastodon.gyptazy.com/tags/XCPng" class="mention hashtag" rel="nofollow noopener" target="_blank">#XCPng</a> and I’m really excited.<a href="https://mastodon.gyptazy.com/tags/XCP" class="mention hashtag" rel="nofollow noopener" target="_blank">#XCP</a> including <a href="https://mastodon.gyptazy.com/tags/Orchestra" class="mention hashtag" rel="nofollow noopener" target="_blank">#Orchestra</a> perfectly fits my requirements. Not being that nit-picky about latencies also allows me to include nodes located on the other site of the world. <a href="https://social.vates.tech/@olivier" class="u-url mention" rel="nofollow noopener" target="_blank">@olivier</a> is doing great with XCP! A blog post why I moved from <a href="https://mastodon.gyptazy.com/tags/bhyve" class="mention hashtag" rel="nofollow noopener" target="_blank">#bhyve</a> -> <a href="https://mastodon.gyptazy.com/tags/Proxmox" class="mention hashtag" rel="nofollow noopener" target="_blank">#Proxmox</a> -> XCPng follows!

gyptazyRunning <a href="https://mastodon.gyptazy.com/tags/Enterprise" class="mention hashtag" rel="nofollow noopener" target="_blank">#Enterprise</a> or <a href="https://mastodon.gyptazy.com/tags/Homelab" class="mention hashtag" rel="nofollow noopener" target="_blank">#Homelab</a> with <a href="https://mastodon.gyptazy.com/tags/Proxmox" class="mention hashtag" rel="nofollow noopener" target="_blank">#Proxmox</a>? Doesn’t matter!<a href="https://mastodon.gyptazy.com/tags/ProxLB" class="mention hashtag" rel="nofollow noopener" target="_blank">#ProxLB</a> is now available in version 1.0.4 with some more features and fixes! ProxLB fills the gap of missing DRS in Proxmox and also brings in some more features!<a href="https://github.com/gyptazy/ProxLB/releases/tag/v1.0.4" rel="nofollow noopener" translate="no" target="_blank">https://github.com/gyptazy/ProxLB/releases/tag/v1.0.4</a><a href="https://mastodon.gyptazy.com/tags/vmware" class="mention hashtag" rel="nofollow noopener" target="_blank">#vmware</a> <a href="https://mastodon.gyptazy.com/tags/xcp" class="mention hashtag" rel="nofollow noopener" target="_blank">#xcp</a> <a href="https://mastodon.gyptazy.com/tags/DRS" class="mention hashtag" rel="nofollow noopener" target="_blank">#DRS</a> <a href="https://mastodon.gyptazy.com/tags/esx" class="mention hashtag" rel="nofollow noopener" target="_blank">#esx</a> <a href="https://mastodon.gyptazy.com/tags/vsphere" class="mention hashtag" rel="nofollow noopener" target="_blank">#vsphere</a> <a href="https://mastodon.gyptazy.com/tags/virtualization" class="mention hashtag" rel="nofollow noopener" target="_blank">#virtualization</a> <a href="https://mastodon.gyptazy.com/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#opensource</a> <a href="https://mastodon.gyptazy.com/tags/vm" class="mention hashtag" rel="nofollow noopener" target="_blank">#vm</a> <a href="https://mastodon.gyptazy.com/tags/friday" class="mention hashtag" rel="nofollow noopener" target="_blank">#friday</a> <a href="https://mastodon.gyptazy.com/tags/virtualisation" class="mention hashtag" rel="nofollow noopener" target="_blank">#virtualisation</a> <a href="https://mastodon.gyptazy.com/tags/cluster" class="mention hashtag" rel="nofollow noopener" target="_blank">#cluster</a> <a href="https://mastodon.gyptazy.com/tags/vcloud" class="mention hashtag" rel="nofollow noopener" target="_blank">#vcloud</a> <a href="https://mastodon.gyptazy.com/tags/livemigration" class="mention hashtag" rel="nofollow noopener" target="_blank">#livemigration</a> <a href="https://mastodon.gyptazy.com/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a> <a href="https://mastodon.gyptazy.com/tags/debian" class="mention hashtag" rel="nofollow noopener" target="_blank">#debian</a> <a href="https://mastodon.gyptazy.com/tags/python" class="mention hashtag" rel="nofollow noopener" target="_blank">#python</a>

Koen de Jonge - SynQNext time when someone asks me which #Linux do I use my answer will be

p̻̻̥r̥̻̥o̻j̤͛ec͔t̞dp :verifiedpurple:I used to run QubesOS somewhere around 3.0 RC1 back in 2015. I was impressed with how well it worked out of the box for a major OS project such as this. The only thing that didn't work on my machine at that time was automatic suspend/resume within the netvm.I loved what <a href="https://mastodon.social/@rootkovska" class="u-url mention" rel="nofollow noopener" target="_blank">@rootkovska</a> was proposing with security by isolation, a much needed step in the right direction for secure systems.Fast forward to today and the supported hardware has expanded significantly and many problems have been solved in the 4.1 release. The community has also expended and I saw <a href="https://infosec.exchange/@micahflee" class="u-url mention" rel="nofollow noopener" target="_blank">@micahflee</a>'s HOPE talk in 2018: "Qubes OS: The Operating System That Can Protect You Even If You Get Hacked" <a href="https://www.youtube.com/watch?v=f4U8YbXKwog" rel="nofollow noopener" target="_blank">https://www.youtube.com/watch?v=f4U8YbXKwog</a>If you're looking to join a community to learn more about Qubes OS I have a few resources. Hope to see you around!1. Qubes Forum: <a href="https://forum.qubes-os.org/" rel="nofollow noopener" target="_blank">https://forum.qubes-os.org/</a> 2. Reddit: <a href="https://www.reddit.com/r/Qubes/" rel="nofollow noopener" target="_blank">https://www.reddit.com/r/Qubes/</a> 3. Discord: <a href="https://www.reddit.com/r/Qubes/comments/zt5roz/qubesos_content_poll_vote_and_let_me_know_what/" rel="nofollow noopener" target="_blank">https://www.reddit.com/r/Qubes/comments/zt5roz/qubesos_content_poll_vote_and_let_me_know_what/</a><a href="https://infosec.exchange/tags/qubes" class="mention hashtag" rel="nofollow noopener" target="_blank">#qubes</a> <a href="https://infosec.exchange/tags/qubesos" class="mention hashtag" rel="nofollow noopener" target="_blank">#qubesos</a> <a href="https://infosec.exchange/tags/infosec" class="mention hashtag" rel="nofollow noopener" target="_blank">#infosec</a> <a href="https://infosec.exchange/tags/privacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#privacy</a> <a href="https://infosec.exchange/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#opensource</a> <a href="https://infosec.exchange/tags/infosecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#infosecurity</a> <a href="https://infosec.exchange/tags/computersecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#computersecurity</a> <a href="https://infosec.exchange/tags/isolation" class="mention hashtag" rel="nofollow noopener" target="_blank">#isolation</a> <a href="https://infosec.exchange/tags/community" class="mention hashtag" rel="nofollow noopener" target="_blank">#community</a> <a href="https://infosec.exchange/tags/hacking" class="mention hashtag" rel="nofollow noopener" target="_blank">#hacking</a> <a href="https://infosec.exchange/tags/whonix" class="mention hashtag" rel="nofollow noopener" target="_blank">#whonix</a> <a href="https://infosec.exchange/tags/xen" class="mention hashtag" rel="nofollow noopener" target="_blank">#xen</a> <a href="https://infosec.exchange/tags/xcpng" class="mention hashtag" rel="nofollow noopener" target="_blank">#xcpng</a> <a href="https://infosec.exchange/tags/xcp" class="mention hashtag" rel="nofollow noopener" target="_blank">#xcp</a> <a href="https://infosec.exchange/tags/virtualization" class="mention hashtag" rel="nofollow noopener" target="_blank">#virtualization</a> <a href="https://infosec.exchange/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#security</a>

Recent searches

Search options

Administered by:

Server stats:

#XCP