MastodonTech.de

dsFolks, this is getting serious. My first open source (MIT license) project and I have no idea what I'm doing 😨It's called nvirt. The concept in a nutshell: it's similar to writing/using a dockerfile, but for libvirt VMs.Docs if you're curious to read more: <a href="https://nvirt-cli.gitlab.io/" rel="nofollow noopener" translate="no" target="_blank">https://nvirt-cli.gitlab.io/</a>I've just tagged v0.1.0 for testing, feedback and a bit more "tidy up" dev, especially before I commit to backwards compatibility for the "virtfile" format, but for anyone who's interested I'd appreciate feedback, ideas and/or rebukes (if I have wasted my time or committed any cardinal sins given I'm new to Go and actually publishing stuff...)Huge shout-out for the <a href="https://infosec.exchange/tags/libguestfs" class="mention hashtag" rel="nofollow noopener" target="_blank">#libguestfs</a> and <a href="https://infosec.exchange/tags/virtManager" class="mention hashtag" rel="nofollow noopener" target="_blank">#virtManager</a> projects - pretty sure I wouldn't have attempted something like this if those tools didn't exist.<a href="https://infosec.exchange/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a> <a href="https://infosec.exchange/tags/libvirt" class="mention hashtag" rel="nofollow noopener" target="_blank">#libvirt</a> <a href="https://infosec.exchange/tags/nvirt" class="mention hashtag" rel="nofollow noopener" target="_blank">#nvirt</a> <a href="https://infosec.exchange/tags/golang" class="mention hashtag" rel="nofollow noopener" target="_blank">#golang</a> <a href="https://infosec.exchange/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a>

Mason PinesSo I am seriously considering moving to <a href="https://universeodon.com/tags/FreeBSD16" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeBSD16</a> and away from <a href="https://universeodon.com/tags/Debian" class="mention hashtag" rel="nofollow noopener" target="_blank">#Debian</a> Not because I don't like <a href="https://universeodon.com/tags/Debian" class="mention hashtag" rel="nofollow noopener" target="_blank">#Debian</a>, because I do. <a href="https://universeodon.com/tags/Debian13" class="mention hashtag" rel="nofollow noopener" target="_blank">#Debian13</a> is a great release, and so have the last 10+ years of releases been (mostly) great.I'm conscious I have limited requirements, use <a href="https://universeodon.com/tags/XFCE" class="mention hashtag" rel="nofollow noopener" target="_blank">#XFCE</a> as my desktop, plus a few common apps that are all in FreeBSD or available via ports.The only niggle is around <a href="https://universeodon.com/tags/Docker" class="mention hashtag" rel="nofollow noopener" target="_blank">#Docker</a> and <a href="https://universeodon.com/tags/KVM" class="mention hashtag" rel="nofollow noopener" target="_blank">#KVM</a>, which I do use both of today, although for the latter I can just go with <a href="https://universeodon.com/tags/qemu" class="mention hashtag" rel="nofollow noopener" target="_blank">#qemu</a> and <a href="https://universeodon.com/tags/virtmanager" class="mention hashtag" rel="nofollow noopener" target="_blank">#virtmanager</a> <a href="https://universeodon.com/tags/Docker" class="mention hashtag" rel="nofollow noopener" target="_blank">#Docker</a> is a bit more of a challenge as I understand it.Before I start any bare-metal testing, I was wondering if anyone out there has any suggestions on what I could or should do around <a href="https://universeodon.com/tags/Docker" class="mention hashtag" rel="nofollow noopener" target="_blank">#Docker</a> when using a <a href="https://universeodon.com/tags/BSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#BSD</a>

diesUndDasMitTassen 🇺🇦Beim Upgrade eines Notebook auf <a href="https://mastodon.social/tags/debian13" class="mention hashtag" rel="nofollow noopener" target="_blank">#debian13</a> ist der Prozess bei der Installation der Grafikkartentreiber abgebrochen, das System hart ausgestiegen und war dann nur noch im "rescue mode" startbar. Das upgrade ließ sich auf der Konsole fortsetzen mit sudo dpkg --configure -a sudo apt --fix-broken installSpäter waren die virtuellen Maschinen nicht startbar, wegen fehlender spice Unterstützung. libspice-Server war nicht installiert.<a href="https://mastodon.social/tags/debiantrixie" class="mention hashtag" rel="nofollow noopener" target="_blank">#debiantrixie</a> <a href="https://mastodon.social/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a> <a href="https://mastodon.social/tags/virtmanager" class="mention hashtag" rel="nofollow noopener" target="_blank">#virtmanager</a> <a href="https://mastodon.social/tags/qemu" class="mention hashtag" rel="nofollow noopener" target="_blank">#qemu</a>

Kurt KremitzkiOkay, so <a href="https://mastodon.social/tags/VirtManager" class="mention hashtag" rel="nofollow noopener" target="_blank">#VirtManager</a> (a <a href="https://mastodon.social/tags/libvirt" class="mention hashtag" rel="nofollow noopener" target="_blank">#libvirt</a> frontend) is now offering both "internal" and "external" snapshots, defaulting to the latter, except apparently you can't then go on to delete those in the UI...? And it creates a foo.snapshot1 in addition to foo.qcow2, except if you delete the former, your VM breaks? Make it make sense

Droppie<a href="https://snabelen.no/@hopland" class="u-url mention" rel="nofollow noopener" target="_blank">@hopland@snabelen.no</a> Thanks... but i'm beginning to suspect i'm not good enough to make this [or any other immutable] distro do what i need...<blockquote>systemd-sysext is meant to allow other vendors to provide their own image</blockquote>"Vendors"? So is this command not intended for mere ordinary users? All i hoped to be able to do is to use this command to be able to install non-Flatpak apps, like my <a href="https://blahaj.zone/tags/VPN" rel="nofollow noopener" target="_blank">#VPN</a> app, & <a href="https://blahaj.zone/tags/Firejail" rel="nofollow noopener" target="_blank">#Firejail</a>, etc. Also, though ofc i cannot test this in a VM, if <a href="https://blahaj.zone/tags/KDELinux" rel="nofollow noopener" target="_blank">#KDELinux</a> would have any chance of eventually becoming my main system, i would need to be able to use <a href="https://blahaj.zone/tags/KVM" rel="nofollow noopener" target="_blank">#KVM</a> <a href="https://blahaj.zone/tags/QEMU" rel="nofollow noopener" target="_blank">#QEMU</a> <a href="https://blahaj.zone/tags/VirtManager" rel="nofollow noopener" target="_blank">#VirtManager</a> for my VMs, for which i had assumed i would also need this command. Unless i could solve these sorts of scenarios, this distro could never become my real system. I am really attracted to it conceptually, but would not compromise on my needs that it would have to support.

Multi Purr Puss :verified:🧵 2/n i'm quite chuffed with my "Rack", though!Most of it is my <a href="https://layer8.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://layer8.space/tags/NAS" class="mention hashtag" rel="nofollow noopener" target="_blank">#NAS</a>, that <a href="https://layer8.space/tags/HP" class="mention hashtag" rel="nofollow noopener" target="_blank">#HP</a> box, running <a href="https://layer8.space/tags/NextCloud" class="mention hashtag" rel="nofollow noopener" target="_blank">#NextCloud</a> and <a href="https://layer8.space/tags/HomeAssistant" class="mention hashtag" rel="nofollow noopener" target="_blank">#HomeAssistant</a> VMs. (<a href="https://layer8.space/tags/libvirt" class="mention hashtag" rel="nofollow noopener" target="_blank">#libvirt</a> <a href="https://layer8.space/tags/VirtManager" class="mention hashtag" rel="nofollow noopener" target="_blank">#VirtManager</a> 🥰)All of that, including 2 spinning HDDs, only draws around 47 Watts, ~58-64 when <a href="https://layer8.space/tags/ZFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#ZFS</a> scrubs the spinning mirror! 👀 see pic alt txt for details.

AerynOS.comA 5 minute video guide on installing our latest AerynOS 2025.08 ISO in virt-manager. Key requirements:1) Firmware: UEFI mode (not BIOS) 2) 3d acceleration 3) Need to pre-format your VM disk 4) You need an active internet connection (if your distro does not automatically set up an internet connection for VM's, please follow guides on how to do it)<a href="https://hachyderm.io/tags/AerynOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#AerynOS</a> <a href="https://hachyderm.io/tags/virtual_machines" class="mention hashtag" rel="nofollow noopener" target="_blank">#virtual_machines</a> <a href="https://hachyderm.io/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://hachyderm.io/tags/DistroRelease" class="mention hashtag" rel="nofollow noopener" target="_blank">#DistroRelease</a> <a href="https://hachyderm.io/tags/virtmanager" class="mention hashtag" rel="nofollow noopener" target="_blank">#virtmanager</a>

Multi Purr Puss :verified:Because i'm an extra special kinda weirdo, who insists on using <a href="https://layer8.space/tags/ZFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#ZFS</a> zvols, i'm deviating from the <a href="https://layer8.space/tags/HomeAssistant" class="mention hashtag" rel="nofollow noopener" target="_blank">#HomeAssistant</a> install manual::terminal: unxz haos_ova-16.1.qcow2.xz :terminal: qemu-img convert -f qcow2 -O raw haos_ova-16.1.qcow2 haos_ova-16.1.qcow2.raw :terminal: cat haos_ova-16.1.qcow2.raw | pv > /dev/zvol/nvme/vm/homeassistant :terminal: efibootmgr --create --disk /dev/vda --part 1 --label "HAOS" --loader '\EFI\BOOT\bootx64.efi'That wörks on my box, using <a href="https://layer8.space/tags/VirtManager" class="mention hashtag" rel="nofollow noopener" target="_blank">#VirtManager</a> <a href="https://layer8.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a>

Machin Machine - Agence WebFreelance Web/Graphisme & Linux vs macOS vs Windows quelques hashtags en complément du sondage du dessus<a href="https://mastodon.social/tags/graphisme" class="mention hashtag" rel="nofollow noopener" target="_blank">#graphisme</a> <a href="https://mastodon.social/tags/adobe" class="mention hashtag" rel="nofollow noopener" target="_blank">#adobe</a> <a href="https://mastodon.social/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a> <a href="https://mastodon.social/tags/macOs" class="mention hashtag" rel="nofollow noopener" target="_blank">#macOs</a> <a href="https://mastodon.social/tags/gimp" class="mention hashtag" rel="nofollow noopener" target="_blank">#gimp</a> <a href="https://mastodon.social/tags/inkscape" class="mention hashtag" rel="nofollow noopener" target="_blank">#inkscape</a> <a href="https://mastodon.social/tags/photoshop" class="mention hashtag" rel="nofollow noopener" target="_blank">#photoshop</a> <a href="https://mastodon.social/tags/illustrator" class="mention hashtag" rel="nofollow noopener" target="_blank">#illustrator</a> <a href="https://mastodon.social/tags/CMJN" class="mention hashtag" rel="nofollow noopener" target="_blank">#CMJN</a> <a href="https://mastodon.social/tags/imac" class="mention hashtag" rel="nofollow noopener" target="_blank">#imac</a> <a href="https://mastodon.social/tags/macbook" class="mention hashtag" rel="nofollow noopener" target="_blank">#macbook</a> <a href="https://mastodon.social/tags/windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#windows</a> <a href="https://mastodon.social/tags/Photopea" class="mention hashtag" rel="nofollow noopener" target="_blank">#Photopea</a> <a href="https://mastodon.social/tags/Scribus" class="mention hashtag" rel="nofollow noopener" target="_blank">#Scribus</a> <a href="https://mastodon.social/tags/nextcloud" class="mention hashtag" rel="nofollow noopener" target="_blank">#nextcloud</a> <a href="https://mastodon.social/tags/icloud" class="mention hashtag" rel="nofollow noopener" target="_blank">#icloud</a> <a href="https://mastodon.social/tags/git" class="mention hashtag" rel="nofollow noopener" target="_blank">#git</a> <a href="https://mastodon.social/tags/figma" class="mention hashtag" rel="nofollow noopener" target="_blank">#figma</a> <a href="https://mastodon.social/tags/penpot" class="mention hashtag" rel="nofollow noopener" target="_blank">#penpot</a> <a href="https://mastodon.social/tags/flyer" class="mention hashtag" rel="nofollow noopener" target="_blank">#flyer</a> <a href="https://mastodon.social/tags/affiche" class="mention hashtag" rel="nofollow noopener" target="_blank">#affiche</a> <a href="https://mastodon.social/tags/webdesign" class="mention hashtag" rel="nofollow noopener" target="_blank">#webdesign</a> <a href="https://mastodon.social/tags/devops" class="mention hashtag" rel="nofollow noopener" target="_blank">#devops</a> <a href="https://mastodon.social/tags/pulsar" class="mention hashtag" rel="nofollow noopener" target="_blank">#pulsar</a> <a href="https://mastodon.social/tags/virtmanager" class="mention hashtag" rel="nofollow noopener" target="_blank">#virtmanager</a> <a href="https://mastodon.social/tags/Krita" class="mention hashtag" rel="nofollow noopener" target="_blank">#Krita</a> <a href="https://mastodon.social/tags/illustration" class="mention hashtag" rel="nofollow noopener" target="_blank">#illustration</a> <a href="https://mastodon.social/tags/Darktable" class="mention hashtag" rel="nofollow noopener" target="_blank">#Darktable</a> <a href="https://mastodon.social/tags/vscode" class="mention hashtag" rel="nofollow noopener" target="_blank">#vscode</a> <a href="https://mastodon.social/tags/vscodium" class="mention hashtag" rel="nofollow noopener" target="_blank">#vscodium</a> <a href="https://mastodon.social/tags/Blender" class="mention hashtag" rel="nofollow noopener" target="_blank">#Blender</a> <a href="https://mastodon.social/tags/3D" class="mention hashtag" rel="nofollow noopener" target="_blank">#3D</a> <a href="https://mastodon.social/tags/Bottles" class="mention hashtag" rel="nofollow noopener" target="_blank">#Bottles</a> <a href="https://mastodon.social/tags/wine" class="mention hashtag" rel="nofollow noopener" target="_blank">#wine</a> <a href="https://mastodon.social/tags/flatpak" class="mention hashtag" rel="nofollow noopener" target="_blank">#flatpak</a> <a href="https://mastodon.social/tags/debian" class="mention hashtag" rel="nofollow noopener" target="_blank">#debian</a> <a href="https://mastodon.social/tags/fedora" class="mention hashtag" rel="nofollow noopener" target="_blank">#fedora</a> <a href="https://mastodon.social/tags/GNU" class="mention hashtag" rel="nofollow noopener" target="_blank">#GNU</a> <a href="https://mastodon.social/tags/X11" class="mention hashtag" rel="nofollow noopener" target="_blank">#X11</a> <a href="https://mastodon.social/tags/Wayland" class="mention hashtag" rel="nofollow noopener" target="_blank">#Wayland</a>

AerynOS.comPictorial of how to transition from the default repo in our Gnome 25.03 iso to the new CDN accelerated repo and then to install an appropriate pkgset.Oh and screenshots taken from within virt-manager which is now working on AerynOS!!Virt-manager is important for our internal ISO testing. It will significantly make the process easier going forwards before we are ready to announce new releases!<a href="https://hachyderm.io/tags/AerynOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#AerynOS</a> <a href="https://hachyderm.io/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://hachyderm.io/tags/virtmanager" class="mention hashtag" rel="nofollow noopener" target="_blank">#virtmanager</a>

AerynOS.comCurrently testing and working towards including virt-manager in our repo.Our aim is to deliver the right tools to enable developers to work on <a href="https://hachyderm.io/@AerynOS" class="u-url mention" rel="nofollow noopener" target="_blank">@AerynOS</a>.We have also been doing further enabling to improve running AerynOS from within virtual environments with a new iso coming soon.Having a polished VM experience is important to our distro development journey<a href="https://hachyderm.io/tags/AerynOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#AerynOS</a> <a href="https://hachyderm.io/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://hachyderm.io/tags/virtmanager" class="mention hashtag" rel="nofollow noopener" target="_blank">#virtmanager</a>

MikaDo any <a href="https://sakurajima.social/tags/Linux" rel="nofollow noopener" target="_blank">#Linux</a>/<a href="https://sakurajima.social/tags/KDE" rel="nofollow noopener" target="_blank">#KDE</a> users have an idea why an app, on a <a href="https://sakurajima.social/tags/KDEPlasma" rel="nofollow noopener" target="_blank">#KDEPlasma</a> desktop, might start fine on the terminal, and application launcher, but not on <a href="https://sakurajima.social/tags/KRunner" rel="nofollow noopener" target="_blank">#KRunner</a>? This has been happening for a long time now for me with <a href="https://sakurajima.social/tags/virt-manager" rel="nofollow noopener" target="_blank">#virt-manager</a> - tho that wasn't the case in the past for just as long. That being said, IIRC it's happened with the application launcher too, tho that works for me atm, but KRunner almost always fails to launch it - only the app icon appears to be loading on the dock/panel, then it disappears. When it does happen, journalctl would report this error: <pre><code>ModuleNotFoundError: No module named 'libvirt'</code></pre> --- Update: found the culprit - <a href="https://sakurajima.social/tags/toshy" rel="nofollow noopener" target="_blank">#toshy</a>, which is a really cool keymapping tool I use on my desktop that replicates <a href="https://sakurajima.social/tags/macOS" rel="nofollow noopener" target="_blank">#macOS</a> like keybinds on a Linux desktop. It's something to do with their <a href="https://sakurajima.social/tags/Python" rel="nofollow noopener" target="_blank">#Python</a> virtualenv that's somehow being used by KRunner, that isn't being used elsewhere like on my shell terminal or application launcher. The missing python library isn't installed on that Toshy virtual env - expectedly. Not sure what to do about it just yet.

bison ✅okay i have installed windows11 today in 3 different VM-system (LXD, virt-manager, VirtualBox) and I am back in virtual box, the classic. so, now exploring win11 and... where the fuck is the X on the settings screen?! Yes, I have installed all updates and restarted. Wheres the X? How do I close this window? Spoiler: i found out, can you guess?<a href="https://mastodon.social/tags/windows11" class="mention hashtag" rel="nofollow noopener" target="_blank">#windows11</a> <a href="https://mastodon.social/tags/windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#windows</a> <a href="https://mastodon.social/tags/virtualisation" class="mention hashtag" rel="nofollow noopener" target="_blank">#virtualisation</a> <a href="https://mastodon.social/tags/vm" class="mention hashtag" rel="nofollow noopener" target="_blank">#vm</a> <a href="https://mastodon.social/tags/virtualbox" class="mention hashtag" rel="nofollow noopener" target="_blank">#virtualbox</a> <a href="https://mastodon.social/tags/lxd" class="mention hashtag" rel="nofollow noopener" target="_blank">#lxd</a> <a href="https://mastodon.social/tags/virtmanager" class="mention hashtag" rel="nofollow noopener" target="_blank">#virtmanager</a>

postmodernLabWC's solution is to use a <code>ToggleKeybindings</code> keybinding to temporarily disable all keybindings globally while you use the VM, then re-enable keybindings when your done. This is obviously not optimal if you're constantly switching between VMs and other windows.<a href="https://github.com/labwc/labwc/issues/810" rel="nofollow noopener" translate="no" target="_blank">https://github.com/labwc/labwc/issues/810</a><a href="https://infosec.exchange/tags/labwc" class="mention hashtag" rel="nofollow noopener" target="_blank">#labwc</a> <a href="https://infosec.exchange/tags/virtmanager" class="mention hashtag" rel="nofollow noopener" target="_blank">#virtmanager</a> <a href="https://infosec.exchange/tags/virtviewer" class="mention hashtag" rel="nofollow noopener" target="_blank">#virtviewer</a> <a href="https://infosec.exchange/tags/remoteviewer" class="mention hashtag" rel="nofollow noopener" target="_blank">#remoteviewer</a>

postmodernWhat solutions do Wayland users use for passing keybindings (ex: Alt-Tab) through to a VM being viewed with <code>virt-viewer</code> or <code>remote-viewer</code> in a Wayland WM? X11 had some kind of special hint to tell the WM to pass all keybindings through to the VM's viewer window. Do you just temporarily disable keybindings while viewing a VM? Is it possible to run <code>virt-viewer</code> or <code>remote-viewer</code> in a separate instance of Wayland/wlroots that only displays that windows and passes all keyboard input to it (e.g. the Wayland equivalent of <code>xinit virt-viewer ... -- :1</code>)?<a href="https://infosec.exchange/tags/virtviewer" class="mention hashtag" rel="nofollow noopener" target="_blank">#virtviewer</a> <a href="https://infosec.exchange/tags/remoteviewer" class="mention hashtag" rel="nofollow noopener" target="_blank">#remoteviewer</a> <a href="https://infosec.exchange/tags/virtmanager" class="mention hashtag" rel="nofollow noopener" target="_blank">#virtmanager</a> <a href="https://infosec.exchange/tags/libvirt" class="mention hashtag" rel="nofollow noopener" target="_blank">#libvirt</a> <a href="https://infosec.exchange/tags/qemu" class="mention hashtag" rel="nofollow noopener" target="_blank">#qemu</a> <a href="https://infosec.exchange/tags/wayland" class="mention hashtag" rel="nofollow noopener" target="_blank">#wayland</a> <a href="https://infosec.exchange/tags/labwc" class="mention hashtag" rel="nofollow noopener" target="_blank">#labwc</a>

postmodernContinuing my LabWC testing. Appears that LabWC or Wayland has issues with not allowing <code>virt-manager</code> to capture keys/mouse when viewing a VM in fullscreen mode. Apparently this was a known <a href="https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2548" rel="nofollow noopener" target="_blank">bug</a> in Gnome/Wayland that was fixed two years ago, but for some reason I'm running into the same issue on labwc 0.7.1 (latest version available on Ubuntu)?<a href="https://infosec.exchange/tags/wayland" class="mention hashtag" rel="nofollow noopener" target="_blank">#wayland</a> <a href="https://infosec.exchange/tags/labwc" class="mention hashtag" rel="nofollow noopener" target="_blank">#labwc</a> <a href="https://infosec.exchange/tags/virtmanager" class="mention hashtag" rel="nofollow noopener" target="_blank">#virtmanager</a>

jablkoziemne<a href="https://fosstodon.org/@ProfessorCode" class="u-url mention" rel="nofollow noopener" target="_blank">@ProfessorCode</a> I believe more people are using <a href="https://101010.pl/tags/kvm" class="mention hashtag" rel="nofollow noopener" target="_blank">#kvm</a> based <a href="https://101010.pl/tags/virtualization" class="mention hashtag" rel="nofollow noopener" target="_blank">#virtualization</a> instead of <a href="https://101010.pl/tags/virtualbox" class="mention hashtag" rel="nofollow noopener" target="_blank">#virtualbox</a>. So there should be more, and better guides for installing <a href="https://101010.pl/tags/virtmanager" class="mention hashtag" rel="nofollow noopener" target="_blank">#virtmanager</a>, <a href="https://101010.pl/tags/gnomeboxes" class="mention hashtag" rel="nofollow noopener" target="_blank">#gnomeboxes</a> or using <a href="https://101010.pl/tags/Virsh" class="mention hashtag" rel="nofollow noopener" target="_blank">#Virsh</a>. But also why these guides are unnecessary verbose I suspect its because of <a href="https://101010.pl/tags/seo" class="mention hashtag" rel="nofollow noopener" target="_blank">#seo</a> so the webpages get ranked higher in <a href="https://101010.pl/tags/google" class="mention hashtag" rel="nofollow noopener" target="_blank">#google</a> index, and have more views which should corespond to increased <a href="https://101010.pl/tags/ad" class="mention hashtag" rel="nofollow noopener" target="_blank">#ad</a> revenue.

Droppie [infosec] 🐨:archlinux: :kde: :firefox_nightly: :thunderbird: :vegan:In the wee small hours i decided to give <a href="https://infosec.space/tags/GnomeBoxes" class="mention hashtag" rel="nofollow noopener" target="_blank">#GnomeBoxes</a> another chance as a possible alternative. Chose to install via <a href="https://infosec.space/tags/flatpak" class="mention hashtag" rel="nofollow noopener" target="_blank">#flatpak</a>, coz my Host is :archlinux: :kde: :plasma: <a href="https://infosec.space/tags/ArchLinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#ArchLinux</a> <a href="https://infosec.space/tags/KDEPlasma" class="mention hashtag" rel="nofollow noopener" target="_blank">#KDEPlasma</a> & i did not wish to risk possible gnome vs plasma file conflicts. It did a fine job of installing an <a href="https://infosec.space/tags/ArchLinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#ArchLinux</a> VM [which i completed using the latest <a href="https://infosec.space/tags/ArchInstall" class="mention hashtag" rel="nofollow noopener" target="_blank">#ArchInstall</a> v3.0.3], so then in an act of gross stupidity i ridiculously chose to see if it could handle a win10 VM via a 3-yr old ISO i have lying around. As i abandoned windoze "for real" in 2014, i had forgotten the many hours of time-wasting bullshit involved, at the end of which instead of getting something decent, you just get... windoze, ugh. Anyway, so far it seems that GnomeBoxes is going ok, which makes a nice change as all prior tests of older versions failed to work properly. Doubt though atm that it'll persuade me to give up on <a href="https://infosec.space/tags/qemu" class="mention hashtag" rel="nofollow noopener" target="_blank">#qemu</a> / <a href="https://infosec.space/tags/kvm" class="mention hashtag" rel="nofollow noopener" target="_blank">#kvm</a> / <a href="https://infosec.space/tags/libvirt" class="mention hashtag" rel="nofollow noopener" target="_blank">#libvirt</a> / <a href="https://infosec.space/tags/VirtManager" class="mention hashtag" rel="nofollow noopener" target="_blank">#VirtManager</a>. GB has no facility to Suspend VMs, so they need to be fully shutdown, which is a drag. Also, the FP version does not support USB transfer, which is a bugger, & so far i've not made <a href="https://infosec.space/tags/SharedFolders" class="mention hashtag" rel="nofollow noopener" target="_blank">#SharedFolders</a> work [but think i know why].

DennisA VM surprised me by going into paused state. But it has no choice, the zfs pool had no space available :( Time to move some old datasets to another pool<a href="https://mastodon.wormhole.eu/tags/zfs" class="mention hashtag" rel="nofollow noopener" target="_blank">#zfs</a> <a href="https://mastodon.wormhole.eu/tags/qemu" class="mention hashtag" rel="nofollow noopener" target="_blank">#qemu</a> <a href="https://mastodon.wormhole.eu/tags/virtmanager" class="mention hashtag" rel="nofollow noopener" target="_blank">#virtmanager</a>

TuxStoryJe ne comprenais pas pourquoi je n'arrivais pas à créer un pont avec virt-manager (QEMU/KVM) pour accéder à mes VMs. J'ai créé mes VMs en QEMU/KVM session utilisateur. Il m'a fallut du temps pour comprendre que le problème venait de là.La solution et l'explication se trouvent ici: <a href="https://stackoverflow.com/questions/67163568/cant-ping-linux-image-running-on-qemu" rel="nofollow noopener" translate="no" target="_blank">https://stackoverflow.com/questions/67163568/cant-ping-linux-image-running-on-qemu</a><a href="https://mastodon.social/tags/virtmanager" class="mention hashtag" rel="nofollow noopener" target="_blank">#virtmanager</a> <a href="https://mastodon.social/tags/qemu" class="mention hashtag" rel="nofollow noopener" target="_blank">#qemu</a> <a href="https://mastodon.social/tags/kvm" class="mention hashtag" rel="nofollow noopener" target="_blank">#kvm</a> <a href="https://mastodon.social/tags/proxmox" class="mention hashtag" rel="nofollow noopener" target="_blank">#proxmox</a> <a href="https://mastodon.social/tags/virtualbox" class="mention hashtag" rel="nofollow noopener" target="_blank">#virtualbox</a> <a href="https://mastodon.social/tags/almalinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#almalinux</a> <a href="https://mastodon.social/tags/cockpit" class="mention hashtag" rel="nofollow noopener" target="_blank">#cockpit</a> <a href="https://mastodon.social/tags/virtualisation" class="mention hashtag" rel="nofollow noopener" target="_blank">#virtualisation</a>

Frühere Suchanfragen

Suchoptionen

Verwaltet von:

Serverstatistik:

#virtmanager