如何完全删除 QEMU/KVM？

Question

我安装了 QEMU，但由于我并没有真正使用它，而且最近发现了很多安全漏洞，所以我想完全删除它。sudo apt-get install qemu据我所知，我安装了它。当我运行sudo apt-get purge qemu它时，它只说它删除了，qemu但是当它有最新的更新时，我看到它有许多依赖项和其他包qemu，它们被称为它没有随qemu包一起删除的东西。

那么我怎样才能完全删除它，以便删除它安装的所有配置文件和包？显然，如果依赖项被它使用的其他程序使用，那么我也不想删除它们，而只想删除它安装的并且其他程序不需要的东西。我尝试运行sudo apt-get autoremove这相当于这里的答案所说的那样没有帮助（它没有删除任何东西）。

我正在使用 GNOME 3.18 运行 Ubuntu GNOME 15.10。

信息更新：

我用 GNOME 3.20 将我的机器升级到 Ubuntu GNOME 16.04，我不记得我是qemu在升级之前还是之后重新安装的，但是我qemu-kvm和virt-manager包一起做了。但是现在即使在清除了所有三个并似乎删除了他们安装的所有依赖项之后，我仍然有问题。它似乎并没有真正删除他们对我的系统所做的所有更改。

例如，这是来自的输出systemctl status qemu-kvm.service：

? qemu-kvm.service - LSB: QEMU KVM module loading script
   Loaded: loaded (/etc/init.d/qemu-kvm; bad; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sun 2016-08-14 13:19:28 BST; 33min ago
     Docs: man:systemd-sysv-generator(8)
  Process: 2099 ExecStart=/etc/init.d/qemu-kvm start (code=exited, status=5)

Aug 14 13:19:28 <Computer-Name> systemd[1]: Starting LSB: QEMU KVM module loading script...
Aug 14 13:19:28 <Computer-Name> systemd[1]: qemu-kvm.service: Control process exited, code=exited status=5
Aug 14 13:19:28 <Computer-Name> systemd[1]: Failed to start LSB: QEMU KVM module loading script.
Aug 14 13:19:28 <Computer-Name> systemd[1]: qemu-kvm.service: Unit entered failed state.
Aug 14 13:19:28 <Computer-Name> systemd[1]: qemu-kvm.service: Failed with result 'exit-code'.

这是来自的输出journalctl | grep qemu：

Aug 14 13:19:23 <Computer-Name> ureadahead[866]: ureadahead:/lib/udev/rules.d/60-qemu-system-common.rules: No such file or directory
Aug 14 13:19:24 <Computer-Name> ureadahead[866]: ureadahead:/usr/bin/qemu-system-alpha: No such file or directory
Aug 14 13:19:24 <Computer-Name> ureadahead[866]: ureadahead:/usr/lib/x86_64-linux-gnu/qemu/block-curl.so: No such file or directory
Aug 14 13:19:24 <Computer-Name> ureadahead[866]: ureadahead:/usr/bin/qemu-system-arm: No such file or directory
Aug 14 13:19:24 <Computer-Name> ureadahead[866]: ureadahead:/usr/lib/x86_64-linux-gnu/qemu/block-iscsi.so: No such file or directory
Aug 14 13:19:24 <Computer-Name> ureadahead[866]: ureadahead:/usr/lib/x86_64-linux-gnu/qemu/block-dmg.so: No such file or directory
Aug 14 13:19:24 <Computer-Name> ureadahead[866]: ureadahead:/usr/lib/x86_64-linux-gnu/qemu/block-rbd.so: No such file or directory
Aug 14 13:19:24 <Computer-Name> ureadahead[866]: ureadahead:/usr/bin/qemu-system-aarch64: No such file or directory
Aug 14 13:19:24 <Computer-Name> ureadahead[866]: ureadahead:/usr/bin/qemu-system-cris: No such file or directory
Aug 14 13:19:24 <Computer-Name> ureadahead[866]: ureadahead:/usr/bin/qemu-system-i386: No such file or directory
Aug 14 13:19:24 <Computer-Name> ureadahead[866]: ureadahead:/usr/bin/qemu-system-lm32: No such file or directory
Aug 14 13:19:24 <Computer-Name> ureadahead[866]: ureadahead:/usr/bin/qemu-system-m68k: No such file or directory
Aug 14 13:19:24 <Computer-Name> ureadahead[866]: ureadahead:/usr/bin/qemu-system-microblaze: No such file or directory
Aug 14 13:19:24 <Computer-Name> ureadahead[866]: ureadahead:/usr/bin/qemu-system-microblazeel: No such file or directory
Aug 14 13:19:24 <Computer-Name> ureadahead[866]: ureadahead:/usr/bin/qemu-system-x86_64: No such file or directory
Aug 14 13:19:24 <Computer-Name> ureadahead[866]: ureadahead:/usr/bin/qemu-system-ppc64: No such file or directory
Aug 14 13:19:24 <Computer-Name> ureadahead[866]: ureadahead:/usr/bin/qemu-system-ppcemb: No such file or directory
Aug 14 13:19:24 <Computer-Name> ureadahead[866]: ureadahead:/usr/bin/qemu-system-sh4: No such file or directory
Aug 14 13:19:24 <Computer-Name> ureadahead[866]: ureadahead:/usr/bin/qemu-system-sh4eb: No such file or directory
Aug 14 13:19:24 <Computer-Name> ureadahead[866]: ureadahead:/usr/bin/qemu-system-sparc: No such file or directory
Aug 14 13:19:24 <Computer-Name> ureadahead[866]: ureadahead:/usr/bin/qemu-system-sparc64: No such file or directory
Aug 14 13:19:24 <Computer-Name> ureadahead[866]: ureadahead:/usr/bin/qemu-system-unicore32: No such file or directory
Aug 14 13:19:24 <Computer-Name> ureadahead[866]: ureadahead:/usr/bin/qemu-system-xtensaeb: No such file or directory
Aug 14 13:19:24 <Computer-Name> ureadahead[866]: ureadahead:/usr/bin/qemu-system-mips: No such file or directory
Aug 14 13:19:24 <Computer-Name> ureadahead[866]: ureadahead:/usr/bin/qemu-system-mips64el: No such file or directory
Aug 14 13:19:24 <Computer-Name> ureadahead[866]: ureadahead:/usr/bin/qemu-system-mipsel: No such file or directory
Aug 14 13:19:24 >Computer-Name> ureadahead[866]: ureadahead:/usr/bin/qemu-system-or32: No such file or directory
Aug 14 13:19:24 <Computer-Name> ureadahead[866]: ureadahead:/usr/bin/qemu-system-ppc: No such file or directory
Aug 14 13:19:24 <Computer-Name> ureadahead[866]: ureadahead:/usr/bin/qemu-system-xtensa: No such file or directory
Aug 14 13:19:24 <Computer-Name> ureadahead[866]: ureadahead:/usr/bin/qemu-system-mips64: No such file or directory
Aug 14 13:19:25 <Computer-Name> systemd[1]: qemu-kvm.service: Control process exited, code=exited status=5
Aug 14 13:19:25 <Computer-Name> systemd[1]: qemu-kvm.service: Unit entered failed state.
Aug 14 13:19:25 <Computer-Name> systemd[1]: qemu-kvm.service: Failed with result 'exit-code'.
Aug 14 13:19:25 <Computer-Name> ureadahead[866]: ureadahead:/usr/share/qemu/init/qemu-kvm-init: No such file or directory
Aug 14 13:19:27 <Computer-Name> systemd[1]: qemu-kvm.service: Control process exited, code=exited status=5
Aug 14 13:19:27 <Computer-Name> systemd[1]: qemu-kvm.service: Unit entered failed state.
Aug 14 13:19:27 <Computer-Name> systemd[1]: qemu-kvm.service: Failed with result 'exit-code'.
Aug 14 13:19:28 <Computer-Name> systemd[1]: qemu-kvm.service: Control process exited, code=exited status=5
Aug 14 13:19:28 <Computer-Name> systemd[1]: qemu-kvm.service: Unit entered failed state.
Aug 14 13:19:28 <Computer-Name> systemd[1]: qemu-kvm.service: Failed with result 'exit-code'.
Aug 14 13:19:31 <Computer-Name> ureadahead[866]: ureadahead:/var/lib/binfmts/qemu-arm: No such file or directory
Aug 14 13:19:31 <Computer-Name> ureadahead[866]: ureadahead:/var/lib/binfmts/qemu-armeb: No such file or directory
Aug 14 13:19:31 <Computer-Name> ureadahead[866]: ureadahead:/var/lib/binfmts/qemu-cris: No such file or directory
Aug 14 13:19:31 <Computer-Name> ureadahead[866]: ureadahead:/var/lib/binfmts/qemu-m68k: No such file or directory
Aug 14 13:19:31 <Computer-Name> ureadahead[866]: ureadahead:/var/lib/binfmts/qemu-mips: No such file or directory
Aug 14 13:19:31 <Computer-Name> ureadahead[866]: ureadahead:/var/lib/binfmts/qemu-mips64: No such file or directory
Aug 14 13:19:31 <Computer-Name> ureadahead[866]: ureadahead:/var/lib/binfmts/qemu-mipsel: No such file or directory
Aug 14 13:19:31 <Computer-Name> ureadahead[866]: ureadahead:/var/lib/binfmts/qemu-mips64el: No such file or directory
Aug 14 13:19:31 <Computer-Name> ureadahead[866]: ureadahead:/var/lib/binfmts/qemu-ppc: No such file or directory
Aug 14 13:19:31 <Computer-Name> ureadahead[866]: ureadahead:/var/lib/binfmts/qemu-ppc64: No such file or directory
Aug 14 13:19:31 <Computer-Name> ureadahead[866]: ureadahead:/var/lib/binfmts/qemu-ppc64abi32: No such file or directory
Aug 14 13:19:31 <Computer-Name> ureadahead[866]: ureadahead:/var/lib/binfmts/qemu-ppc64le: No such file or directory
Aug 14 13:19:31 <Computer-Name> ureadahead[866]: ureadahead:/var/lib/binfmts/qemu-s390x: No such file or directory
Aug 14 13:19:31 <Computer-Name> ureadahead[866]: ureadahead:/var/lib/binfmts/qemu-sh4: No such file or directory
Aug 14 13:19:31 <Computer-Name> ureadahead[866]: ureadahead:/var/lib/binfmts/qemu-sh4eb: No such file or directory
Aug 14 13:19:31 <Computer-Name> ureadahead[866]: ureadahead:/var/lib/binfmts/qemu-sparc: No such file or directory
Aug 14 13:19:31 <Computer-Name> ureadahead[866]: ureadahead:/var/lib/binfmts/qemu-microblaze: No such file or directory
Aug 14 13:19:31 <Computer-Name> ureadahead[866]: ureadahead:/var/lib/binfmts/qemu-sparc32plus: No such file or directory
Aug 14 13:19:31 <Computer-Name> ureadahead[866]: ureadahead:/var/lib/binfmts/qemu-aarch64: No such file or directory
Aug 14 13:19:31 <Computer-Name> ureadahead[866]: ureadahead:/var/lib/binfmts/qemu-alpha: No such file or directory
Aug 14 13:19:31 <Computer-Name> ureadahead[866]: ureadahead:/var/lib/binfmts/qemu-sparc64: No such file or directory
Aug 14 13:19:32 <Computer-Name> ureadahead[866]: ureadahead:/etc/libvirt/qemu/Ubuntu_GNOME_16-04_GNOME_3-18.xml: No such file or directory
Aug 14 13:19:32 <Computer-Name> ureadahead[866]: ureadahead:/etc/libvirt/qemu/Ubuntu_GNOME_16-10_GNOME_3-21.xml: No such file or directory
Aug 14 13:19:32 <Computer-Name> ureadahead[866]: ureadahead:/etc/libvirt/qemu/Ubuntu_Unity_16-04.xml: No such file or directory
Aug 14 13:19:32 <Computer-Name> ureadahead[866]: ureadahead:/etc/libvirt/qemu/Ubuntu_GNOME_16-04_GNOME_3-20.xml: No such file or directory
Aug 14 13:20:42 <Computer-Name> /usr/lib/gdm3/gdm-x-session[3320]: dbus-update-activation-environment: setting LIBVIRT_DEFAULT_URI=qemu:///system

所以很明显 QEMU 并没有完全消失。但我希望它是这样，我如何完全删除它以及它所做的所有更改？

当我运行时，service --status-all | grep qemu这是输出：

 [ - ]  qemu-kvm

因此，它似乎在那里，即使它可能不处于活动状态，因为它当前似乎没有运行，我认为该-标志可能表明其当前状态，因为许多其他服务都有+标志。那么删除此服务是否安全？如果是这样，如何做到这一点？

Answer 1

首先澄清一下：qemu是一个元包，依赖于所有其他 qemu 相关的包。
当我使用synaptic包管理工具时，它可以保存所有时间的完整安装历史记录，因此我可以告诉您哪些包与qemu.

Commit Log for Thu Apr 21 18:34:38 2016  

Installed the following packages:  

cpu-checker (0.7-0ubuntu7)  
ipxe-qemu (1.0.0+git-20150424.a25a16d-1ubuntu1)  
libaio1 (0.3.110-2)  
libboost-random1.58.0 (1.58.0+dfsg-5ubuntu3)  
libboost-thread1.58.0 (1.58.0+dfsg-5ubuntu3)  
libcacard0 (1:2.5.0-2)  
libfdt1 (1.4.0+dfsg-2)  
libiscsi2 (1.12.0-2)  
librados2 (10.1.2-0ubuntu1)  
librbd1 (10.1.2-0ubuntu1)  
libspice-server1 (0.12.6-4)  
libusbredirparser1 (0.7.1-1)  
libxen-4.6 (4.6.0-1ubuntu4)  
libxenstore3.0 (4.6.0-1ubuntu4)  
msr-tools (1.3-2)  
qemu (1:2.5+dfsg-5ubuntu10)  
qemu-block-extra (1:2.5+dfsg-5ubuntu10)  
qemu-slof (20151103+dfsg-1ubuntu1)  
qemu-system (1:2.5+dfsg-5ubuntu10)  
qemu-system-arm (1:2.5+dfsg-5ubuntu10)  
qemu-system-common (1:2.5+dfsg-5ubuntu10)  
qemu-system-mips (1:2.5+dfsg-5ubuntu10)  
qemu-system-misc (1:2.5+dfsg-5ubuntu10)  
qemu-system-ppc (1:2.5+dfsg-5ubuntu10)  
qemu-system-sparc (1:2.5+dfsg-5ubuntu10)  
qemu-system-x86 (1:2.5+dfsg-5ubuntu10)  
qemu-user (1:2.5+dfsg-5ubuntu10)  
qemu-user-binfmt (1:2.5+dfsg-5ubuntu10)  
qemu-utils (1:2.5+dfsg-5ubuntu10)  
seabios (1.8.2-1ubuntu1)  
sharutils (1:4.15.2-1)

要删除所有qemu相关软件包 - 打开终端并执行以下命令：

sudo apt-get purge cpu-checker ipxe-qemu libaio1 libboost-random1.58.0 libboost-thread1.58.0 libcacard0 libfdt1 libiscsi2 librados2 librbd1 libspice-server1 libusbredirparser1 libxen-4.6 libxenstore3.0 msr-tools qemu qemu-block-extra qemu-slof qemu-system qemu-system-arm qemu-system-common qemu-system-mips qemu-system-misc qemu-system-ppc qemu-system-sparc qemu-system-x86 qemu-user qemu-user-binfmt qemu-utils seabios sharutils  

注意：这是来自 Ubuntu 16.04 - 如果单个软件包（例如：libboost-random1.58.0）在 Ubuntu 15.10 中具有不同的名称，您可以使用 进行检查dpkg --get-selections。但大多数包应该具有相同的名称......现在您已经完全删除了qemu.

我检查了packages.ubuntu.comwily上的软件包，发现一个名称不同的软件包：其中是-所以您必须在命令中替换它。为了安全起见，您也可以考虑保留包裹。libxen-4.6wilylibxen-4.5purgelib

更新解决您的评论，即您仍然列出了未运行的 qemu-kvm 服务：

这是一个启动服务，当您另外安装该软件包时正在运行qemu-kvm。

您有两个选择，可以使用 禁用该服务systemctl disable qemu-kvm，也可以使用 删除该服务sudo rm /etc/init.d/qemu-kvm。要同时删除配置文件，请执行sudo rm /etc/init/qemu-kvm.conf. 现在重新启动系统 - 该服务将消失。