| Message ID | 20230629080234.179687-1-thuth@redhat.com |
|---|---|
| State | New |
| Headers | show |
| Series | [qemu-web] Fix installation instructions for Debian/Ubuntu | expand |
29.06.2023 11:02, Thomas Huth wrote: > There is no package called "qemu" here - thus use the two meta-packages > "qemu-system" and "qemu-user" instead. There are 2 questions here. 1. Do we really want to suggest users to install the whole thing? qemu-user and qemu-system are two entirely different beasts, used for entirely different purposes. This is exactly the reason why I dropped `qemu' package from debian/ubuntu, - because effectively there are two independent, entirely different packages. Also 1.a, - again, whole qemu-system usually isn't needed. There are another 2 big different classes here, - native thing (probably with kvm), and foreign thing. > Resolves: https://gitlab.com/qemu-project/qemu-web/-/issues/8 ..> -* <strong>Debian/Ubuntu:</strong> `apt-get install qemu` > +* <strong>Debian/Ubuntu:</strong> `apt-get install qemu-system qemu-user` 2. There are 2 qemu-user packages on debian/ubuntu: it is qemu-user and qemu-user-static. My guess is that most users actually need the latter, at least this one lets to run foreign chroots without copying anything from host system to a chroot. In rare cases when one wants to install and run foreign binaries directly into the host system, qemu-user is okay. But it is a really rare case, and usually combined with running foreign chroots anyway. So I'd say this whole thing needs a bit more explanation, like, when you want to run qemu-system emulation, install qemu-system (meta)package. when you want user-mode emulation, install qemu-user-static package. Or something like this. This is actually a question to QEMU upstream, - I think the same reasoning applies there as well. Thanks, /mjt
On 29/6/23 10:12, Michael Tokarev wrote: > 29.06.2023 11:02, Thomas Huth wrote: >> There is no package called "qemu" here - thus use the two meta-packages >> "qemu-system" and "qemu-user" instead. > > There are 2 questions here. > > 1. Do we really want to suggest users to install the whole thing? > qemu-user and qemu-system are two entirely different beasts, used > for entirely different purposes. This is exactly the reason why > I dropped `qemu' package from debian/ubuntu, - because effectively > there are two independent, entirely different packages. > > Also 1.a, - again, whole qemu-system usually isn't needed. There are > another 2 big different classes here, - native thing (probably with > kvm), and foreign thing. > >> Resolves: https://gitlab.com/qemu-project/qemu-web/-/issues/8 > ..> -* <strong>Debian/Ubuntu:</strong> `apt-get install qemu` >> +* <strong>Debian/Ubuntu:</strong> `apt-get install qemu-system >> qemu-user` > > 2. There are 2 qemu-user packages on debian/ubuntu: it is qemu-user > and qemu-user-static. My guess is that most users actually need the latter, > at least this one lets to run foreign chroots without copying anything from > host system to a chroot. In rare cases when one wants to install and run > foreign binaries directly into the host system, qemu-user is okay. But it > is a really rare case, and usually combined with running foreign chroots > anyway. > > So I'd say this whole thing needs a bit more explanation, like, > > when you want to run qemu-system emulation, install qemu-system > (meta)package. > when you want user-mode emulation, install qemu-user-static package. > > Or something like this. Or link to the Debian wiki where the qemu packages are explained :) > This is actually a question to QEMU upstream, - I think the same reasoning > applies there as well. > > Thanks, > > /mjt > >
On 29/06/2023 10.12, Michael Tokarev wrote: > 29.06.2023 11:02, Thomas Huth wrote: >> There is no package called "qemu" here - thus use the two meta-packages >> "qemu-system" and "qemu-user" instead. > > There are 2 questions here. > > 1. Do we really want to suggest users to install the whole thing? > qemu-user and qemu-system are two entirely different beasts, used > for entirely different purposes. This is exactly the reason why > I dropped `qemu' package from debian/ubuntu, - because effectively > there are two independent, entirely different packages. > > Also 1.a, - again, whole qemu-system usually isn't needed. There are > another 2 big different classes here, - native thing (probably with > kvm), and foreign thing. > >> Resolves: https://gitlab.com/qemu-project/qemu-web/-/issues/8 > ..> -* <strong>Debian/Ubuntu:</strong> `apt-get install qemu` >> +* <strong>Debian/Ubuntu:</strong> `apt-get install qemu-system qemu-user` > > 2. There are 2 qemu-user packages on debian/ubuntu: it is qemu-user > and qemu-user-static. My guess is that most users actually need the latter, > at least this one lets to run foreign chroots without copying anything from > host system to a chroot. In rare cases when one wants to install and run > foreign binaries directly into the host system, qemu-user is okay. But it > is a really rare case, and usually combined with running foreign chroots > anyway. > > So I'd say this whole thing needs a bit more explanation, like, > > when you want to run qemu-system emulation, install qemu-system > (meta)package. > when you want user-mode emulation, install qemu-user-static package. Ok, thanks, makes sense, I sent a v2 where I've split it. > This is actually a question to QEMU upstream, - I think the same reasoning > applies there as well. Looking at our docs, it seems like we're lacking an introduction to the the "configure" switches like --enable-system and --enable-user completely, indeed :-( Thomas
29.06.2023 12:31, Thomas Huth wrote: .. >> This is actually a question to QEMU upstream, - I think the same reasoning >> applies there as well. > > Looking at our docs, it seems like we're lacking an introduction to the the "configure" switches like --enable-system and --enable-user completely, > indeed :-( When I come to qemu 10+ years ago, it was somehow very difficult to understand what's qemu-user and what's qemu-system. Now it is obvious, like breathing, but that's after 10+ years.. ;)) /mjt
diff --git a/_download/linux.md b/_download/linux.md index 11ed695..bb76425 100644 --- a/_download/linux.md +++ b/_download/linux.md @@ -2,7 +2,7 @@ QEMU is packaged by most Linux distributions: * <strong>Arch:</strong> `pacman -S qemu` -* <strong>Debian/Ubuntu:</strong> `apt-get install qemu` +* <strong>Debian/Ubuntu:</strong> `apt-get install qemu-system qemu-user` * <strong>Fedora:</strong> `dnf install @virtualization`
There is no package called "qemu" here - thus use the two meta-packages "qemu-system" and "qemu-user" instead. Resolves: https://gitlab.com/qemu-project/qemu-web/-/issues/8 Signed-off-by: Thomas Huth <thuth@redhat.com> --- _download/linux.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)