如何完全删除QEMU / KVM？

debugcn 发表于 Dev

用户名

我已经安装了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

因此，似乎它在那里，即使它可能没有处于活动状态也可能因为它当前似乎未在运行，而且我认为该-标志可能表示其当前状态，因为许多其他服务都带有+标志。那么，仅删除此服务是否安全？如果是这样，该怎么办？

网络盒

首先要弄清楚：qemu是一个metapackage，取决于所有其他与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。

我已经检查了包wily上packages.ubuntu.com，我发现一个包有不同的名称：libxen-4.6这wily是libxen-4.5-所以你必须在替换此purge命令。您也可以考虑保留lib包装，只是为了安全起见。

更新以解决您的评论，即您仍然没有列出qemu-kvm服务：

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

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

本文收集自互联网，转载请注明来源。

如有侵权，请联系[email protected] 删除。

编辑于2021-06-1

我来说两句

0条评论

登录后参与评论

来自分类Dev

Related 相关文章

文章