Debian User Forums

Debian-installer is one of the parts of debian that I try to avoid touching, don't have any easy solutions for this. Quick searching finds https://wiki.debian.org/DebianInstaller/Build which you probably already found.

@lindi: Thanks for the tip. Not something I've seen mentioned in any of my research. Is there an advantage to doing it that way rather than adding users to the libvirt group? I guess the main advantage is that if you have multiple users on the machine they can have their own VMs completely isolated...

Got it, thanks. Will correct when I do my first round of clean-up edits. And btw, you can use libvirtd without root privileges as well. Just select File->Add Connection... and choose QEMU/KVM user session . In fact, this is the default setting for gnome-boxes which is also a good GUI for libvirtd (...

pbear wrote: ↑2024-04-22 05:27
Authorization. By default, VirtMan runs as user-root. Generally, though, you want to run it as a regular user.

VirtMan is the GUI, it runs as normal user by default. What is running as root is libvirtd.

Are you planning to sign the kernels with your own key and add that to every machine using secure boot in your organization?

Are you trying to rebuild the kernel and also the installer? What's the actual problem you are trying to solve? Yes. i practically need to create full iso from the packages rebuilt with strace from the examined sources. I am trying to create an installation iso with my custom kernel from scratch. N...

Are you trying to rebuild the kernel and also the installer? What's the actual problem you are trying to solve?

Then if it's really not meant to be installed on the host, then its' only use case would be if the guest system were Debian or a Debian derivative (Ubuntu, Mint, etc). It cant be assumed that all non-Debian based distros will be guaranteed to have an installable package called "qemu-guest-agen...

This is very contradictory..."should be used on the host", and then apt-cache's description "it is not used on the host". My understanding is that it's meant to be installed on the host, to facilitate guest agent communication between the host (Debian) and guest (whatever OS it ...

Correct. qemu-guest-agent should not be used on the host: $ apt-cache show qemu-guest-agent ... Install this package on a system which is running as guest inside qemu virtual machine. It is not used on the host. This is very contradictory..."should be used on the host", and then apt-cache...

Here are my notes on how to get good performance from a Windows virtual machine and without having to play around as root: Download virtio-win-0.1.229.iso (sha256 c88a0dde34605eaee6cf889f3e2a0c2af3caeb91b5df45a125ca4f701acbbbe0) Download Win10_22H2_EnglishInternational_x64.iso (sha256 3ac5522f9db9f4...

You have a Windows guest and Debian host? And you installed the guest agent on the Debian host? Correct. qemu-guest-agent should be used on the host: $ apt-cache show qemu-guest-agent ... Install this package on a system which is running as guest inside qemu virtual machine. It is not used on the h...

You have a Windows guest and Debian host? And you installed the guest agent on the Debian host?

As for whether the failure of "firmware=never" to block non-free-firmware is a bug, my testing over the last couple days reveals that the issue actually existed in Debian 11 as well. But it didn't matter much because that release only included free-firmware. But now that Debian 12 include...

1) Above all, avoid using Debian 12 Bookworm's "Live" DVD images for installation. Those will install non-free firmware on your system no matter what you do. Even when I followed Debian.org's instructions for adding "firmware=never" before installing that way, I still ended up w...

I've been a Debian user for 10+ years because I'm a Free Software supporter. I wasn't aware of the "vote" last year to change Debian's policy on non-free, and was shocked to discover I've been running a bunch of non-free drivers on my] Good to hear from a long-time free software supporter...

There are many possibilities. In Debian upstream software is often split to multiple packages so that it is possible to take only the parts you need and avoid embedded code copies. However, this means you need to know what each of these packages do, or just install a sane default collection of packa...

Redirect also standard error to journal and check what is written there with journalctl?