安装:

sudo apt-add-repository main
sudo apt-get update
sudo apt-get install qemu-kvm qemu virt-manager virt-viewer libvirt-bin bridge-utils

安装中基本不会出现依赖的问题,如果出现了,可以使用sudo apt-get install -f去解决,然后重新运行安装命令。

安装过程中的错误解决:

1、如果出现如下错误:

正在读取软件包列表... 完成
正在分析软件包的依赖关系树
正在读取状态信息... 完成
将会同时安装下列软件:
cpu-checker ipxe-qemu libboost-random1.58.0 libboost-thread1.58.0 libcacard0
libfdt1 libiscsi2 librados2 librbd1 libsdl1.2debian libspice-server1
libusbredirparser1 libxen-4.6 libxenstore3.0 msr-tools 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
建议安装:
qemu-user-static samba vde2 openbios-ppc openhackware sgabios ovmf
debootstrap
下列【新】软件包将被安装:
cpu-checker ipxe-qemu libboost-random1.58.0 libboost-thread1.58.0 libcacard0
libfdt1 libiscsi2 librados2 librbd1 libsdl1.2debian 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
升级了 0 个软件包,新安装了 30 个软件包,要卸载 0 个软件包,有 331 个软件包未被升级。
有 1 个软件包没有被完全安装或卸载。
需要下载 0 B/39.8 MB 的归档。
解压缩后会消耗 248 MB 的额外空间。
您希望继续执行吗? [Y/n] y
正在选中未选择的软件包 libiscsi2:amd64。
(正在读取数据库 ... 系统当前共安装有 224632 个文件和目录。)
正准备解包 .../libiscsi2_1.12.0-2_amd64.deb ...
正在解包 libiscsi2:amd64 (1.12.0-2) ...
正在选中未选择的软件包 libboost-random1.58.0:amd64。
正准备解包 .../libboost-random1.58.0_1.58.0+dfsg-5ubuntu3.1_amd64.deb ...
正在解包 libboost-random1.58.0:amd64 (1.58.0+dfsg-5ubuntu3.1) ...
正在选中未选择的软件包 libboost-thread1.58.0:amd64。
正准备解包 .../libboost-thread1.58.0_1.58.0+dfsg-5ubuntu3.1_amd64.deb ...
正在解包 libboost-thread1.58.0:amd64 (1.58.0+dfsg-5ubuntu3.1) ...
正在选中未选择的软件包 librados2。
正准备解包 .../librados2_10.2.7-0ubuntu0.16.04.1_amd64.deb ...
正在解包 librados2 (10.2.7-0ubuntu0.16.04.1) ...
正在选中未选择的软件包 librbd1。
正准备解包 .../librbd1_10.2.7-0ubuntu0.16.04.1_amd64.deb ...
正在解包 librbd1 (10.2.7-0ubuntu0.16.04.1) ...
正在选中未选择的软件包 qemu-block-extra:amd64。
正准备解包 .../qemu-block-extra_1%3a2.5+dfsg-5ubuntu10.14_amd64.deb ...
正在解包 qemu-block-extra:amd64 (1:2.5+dfsg-5ubuntu10.14) ...
正在选中未选择的软件包 qemu-system-common。
正准备解包 .../qemu-system-common_1%3a2.5+dfsg-5ubuntu10.14_amd64.deb ...
正在解包 qemu-system-common (1:2.5+dfsg-5ubuntu10.14) ...
正在选中未选择的软件包 msr-tools。
正准备解包 .../msr-tools_1.3-2_amd64.deb ...
正在解包 msr-tools (1.3-2) ...
正在选中未选择的软件包 cpu-checker。
正准备解包 .../cpu-checker_0.7-0ubuntu7_amd64.deb ...
正在解包 cpu-checker (0.7-0ubuntu7) ...
正在选中未选择的软件包 ipxe-qemu。
正准备解包 .../ipxe-qemu_1.0.0+git-20150424.a25a16d-1ubuntu1_all.deb ...
正在解包 ipxe-qemu (1.0.0+git-20150424.a25a16d-1ubuntu1) ...
正在选中未选择的软件包 libcacard0:amd64。
正准备解包 .../libcacard0_1%3a2.5.0-2_amd64.deb ...
正在解包 libcacard0:amd64 (1:2.5.0-2) ...
正在选中未选择的软件包 libsdl1.2debian:amd64。
正准备解包 .../libsdl1.2debian_1.2.15+dfsg1-3_amd64.deb ...
正在解包 libsdl1.2debian:amd64 (1.2.15+dfsg1-3) ...
正在选中未选择的软件包 libspice-server1:amd64。
正准备解包 .../libspice-server1_0.12.6-4ubuntu0.3_amd64.deb ...
正在解包 libspice-server1:amd64 (0.12.6-4ubuntu0.3) ...
正在选中未选择的软件包 libusbredirparser1:amd64。
正准备解包 .../libusbredirparser1_0.7.1-1_amd64.deb ...
正在解包 libusbredirparser1:amd64 (0.7.1-1) ...
正在选中未选择的软件包 libxenstore3.0:amd64。
正准备解包 .../libxenstore3.0_4.6.5-0ubuntu1.2_amd64.deb ...
正在解包 libxenstore3.0:amd64 (4.6.5-0ubuntu1.2) ...
正在选中未选择的软件包 libxen-4.6:amd64。
正准备解包 .../libxen-4.6_4.6.5-0ubuntu1.2_amd64.deb ...
正在解包 libxen-4.6:amd64 (4.6.5-0ubuntu1.2) ...
正在选中未选择的软件包 libfdt1:amd64。
正准备解包 .../libfdt1_1.4.0+dfsg-2_amd64.deb ...
正在解包 libfdt1:amd64 (1.4.0+dfsg-2) ...
正在选中未选择的软件包 qemu-system-arm。
正准备解包 .../qemu-system-arm_1%3a2.5+dfsg-5ubuntu10.14_amd64.deb ...
正在解包 qemu-system-arm (1:2.5+dfsg-5ubuntu10.14) ...
正在选中未选择的软件包 qemu-system-mips。
正准备解包 .../qemu-system-mips_1%3a2.5+dfsg-5ubuntu10.14_amd64.deb ...
正在解包 qemu-system-mips (1:2.5+dfsg-5ubuntu10.14) ...
正在选中未选择的软件包 qemu-slof。
正准备解包 .../qemu-slof_20151103+dfsg-1ubuntu1_all.deb ...
正在解包 qemu-slof (20151103+dfsg-1ubuntu1) ...
正在选中未选择的软件包 qemu-system-ppc。
正准备解包 .../qemu-system-ppc_1%3a2.5+dfsg-5ubuntu10.14_amd64.deb ...
正在解包 qemu-system-ppc (1:2.5+dfsg-5ubuntu10.14) ...
正在选中未选择的软件包 qemu-system-sparc。
正准备解包 .../qemu-system-sparc_1%3a2.5+dfsg-5ubuntu10.14_amd64.deb ...
正在解包 qemu-system-sparc (1:2.5+dfsg-5ubuntu10.14) ...
正在选中未选择的软件包 seabios。
正准备解包 .../seabios_1.8.2-1ubuntu1_all.deb ...
正在解包 seabios (1.8.2-1ubuntu1) ...
正在选中未选择的软件包 qemu-system-x86。
正准备解包 .../qemu-system-x86_1%3a2.5+dfsg-5ubuntu10.14_amd64.deb ...
正在解包 qemu-system-x86 (1:2.5+dfsg-5ubuntu10.14) ...
正在选中未选择的软件包 qemu-system-misc。
正准备解包 .../qemu-system-misc_1%3a2.5+dfsg-5ubuntu10.14_amd64.deb ...
正在解包 qemu-system-misc (1:2.5+dfsg-5ubuntu10.14) ...
正在选中未选择的软件包 qemu-system。
正准备解包 .../qemu-system_1%3a2.5+dfsg-5ubuntu10.14_amd64.deb ...
正在解包 qemu-system (1:2.5+dfsg-5ubuntu10.14) ...
正在选中未选择的软件包 qemu-user。
正准备解包 .../qemu-user_1%3a2.5+dfsg-5ubuntu10.14_amd64.deb ...
正在解包 qemu-user (1:2.5+dfsg-5ubuntu10.14) ...
正在选中未选择的软件包 qemu-utils。
正准备解包 .../qemu-utils_1%3a2.5+dfsg-5ubuntu10.14_amd64.deb ...
正在解包 qemu-utils (1:2.5+dfsg-5ubuntu10.14) ...
正在选中未选择的软件包 qemu。
正准备解包 .../qemu_1%3a2.5+dfsg-5ubuntu10.14_amd64.deb ...
正在解包 qemu (1:2.5+dfsg-5ubuntu10.14) ...
正在选中未选择的软件包 qemu-user-binfmt。
正准备解包 .../qemu-user-binfmt_1%3a2.5+dfsg-5ubuntu10.14_amd64.deb ...
正在解包 qemu-user-binfmt (1:2.5+dfsg-5ubuntu10.14) ...
正在处理用于 libc-bin (2.23-0ubuntu9) 的触发器 ...
正在处理用于 ureadahead (0.100.0-19) 的触发器 ...
正在处理用于 systemd (229-4ubuntu10) 的触发器 ...
正在处理用于 man-db (2.7.5-1) 的触发器 ...
正在处理用于 doc-base (0.10.7) 的触发器 ...
Processing 2 added doc-base files...
正在设置 binfmt-support (2.1.6-1) ...
insserv: warning: script 'S20tomcat8' missing LSB tags and overrides
insserv: warning: script 'tomcat8' missing LSB tags and overrides
insserv: There is a loop between service plymouth and mountdevsubfs if started
insserv: loop involving service mountdevsubfs at depth 2
insserv: loop involving service udev at depth 1
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Max recursions depth 99 reached
insserv: There is a loop at service plymouth if started
insserv: loop involving service hwclock at depth 4
insserv: There is a loop at service tomcat8 if started
insserv: loop involving service tomcat8 at depth 1
insserv: exiting now without changing boot order!
update-rc.d: error: insserv rejected the script header
dpkg: 处理软件包 binfmt-support (--configure)时出错:
子进程 已安装 post-installation 脚本 返回错误状态 1
正在设置 libiscsi2:amd64 (1.12.0-2) ...
正在设置 libboost-random1.58.0:amd64 (1.58.0+dfsg-5ubuntu3.1) ...
正在设置 libboost-thread1.58.0:amd64 (1.58.0+dfsg-5ubuntu3.1) ...
正在设置 librados2 (10.2.7-0ubuntu0.16.04.1) ...
正在设置 librbd1 (10.2.7-0ubuntu0.16.04.1) ...
正在设置 qemu-block-extra:amd64 (1:2.5+dfsg-5ubuntu10.14) ...
正在设置 qemu-system-common (1:2.5+dfsg-5ubuntu10.14) ...
insserv: warning: script 'S20tomcat8' missing LSB tags and overrides
insserv: warning: script 'tomcat8' missing LSB tags and overrides
insserv: There is a loop between service plymouth and mountdevsubfs if started
insserv: loop involving service mountdevsubfs at depth 2
insserv: loop involving service udev at depth 1
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting tomcat8 depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Max recursions depth 99 reached
insserv: There is a loop at service plymouth if started
insserv: loop involving service hwclock at depth 4
insserv: There is a loop at service tomcat8 if started
insserv: loop involving service tomcat8 at depth 1
insserv: exiting now without changing boot order!
update-rc.d: error: insserv rejected the script header
dpkg: 处理软件包 qemu-system-common (--configure)时出错:
子进程 已安装 post-installation 脚本 返回错误状态 1
正在设置 msr-tools (1.3-2) ...
正在设置 cpu-checker (0.7-0ubuntu7) ...
正在设置 ipxe-qemu (1.0.0+git-20150424.a25a16d-1ubuntu1) ...
正在设置 libcacard0:amd64 (1:2.5.0-2) ...
正在设置 libsdl1.2debian:amd64 (1.2.15+dfsg1-3) ...
正在设置 libspice-server1:amd64 (0.12.6-4ubuntu0.3) ...
正在设置 libusbredirparser1:amd64 (0.7.1-1) ...
正在设置 libxenstore3.0:amd64 (4.6.5-0ubuntu1.2) ...
正在设置 libxen-4.6:amd64 (4.6.5-0ubuntu1.2) ...
正在设置 libfdt1:amd64 (1.4.0+dfsg-2) ...
dpkg: 依赖关系问题使得 qemu-system-arm 的配置工作不能继续:
qemu-system-arm 依赖于 qemu-system-common (>> 2.0.0+dfsg-7~);然而:
软件包 qemu-system-common 尚未配置。 dpkg: 处理软件包 qemu-system-arm (--configure)时出错:
依赖关系问题 - 仍未被配置
因为错误消息指示这是由于上一个问题导致的错误,没有写入 apport 报告。
dpkg: 依赖关系问题使得 qemu-system-mips 的配置工作不能继续:
qemu-system-mips 依赖于 qemu-system-common (>> 2.0.0+dfsg-7~);然而:
软件包 qemu-system-common 尚未配置。 dpkg: 处理软件包 qemu-system-mips (--configure)时出错:
依赖关系问题 - 仍未被配置
由于已经达到 MaxReports 限制,没有写入 apport 报告。
正在设置 qemu-slof (20151103+dfsg-1ubuntu1) ...
dpkg: 依赖关系问题使得 qemu-system-ppc 的配置工作不能继续:
qemu-system-ppc 依赖于 qemu-system-common (>> 2.0.0+dfsg-7~);然而:
软件包 qemu-system-common 尚未配置。 dpkg: 处理软件包 qemu-system-ppc (--configure)时出错:
依赖关系问题 - 仍未被配置
由于已经达到 MaxReports 限制,没有写入 apport 报告。
dpkg: 依赖关系问题使得 qemu-system-sparc 的配置工作不能继续:
qemu-system-sparc 依赖于 qemu-system-common (>> 2.0.0+dfsg-7~);然而:
软件包 qemu-system-common 尚未配置。 dpkg: 处理软件包 qemu-system-sparc (--configure)时出错:
依赖关系问题 - 仍未被配置
由于已经达到 MaxReports 限制,没有写入 apport 报告。
正在设置 seabios (1.8.2-1ubuntu1) ...
dpkg: 依赖关系问题使得 qemu-system-x86 的配置工作不能继续:
qemu-system-x86 依赖于 qemu-system-common (>> 2.0.0+dfsg-7~);然而:
软件包 qemu-system-common 尚未配置。 dpkg: 处理软件包 qemu-system-x86 (--configure)时出错:
依赖关系问题 - 仍未被配置
dpkg: 依赖关系问题使得 qemu-system-misc 的配置工作不能继续:
qemu-system-misc 依赖于 qemu-system-common (>> 2.0.0+dfsg-7~);然而:
软件包 qemu-system-common 尚未配置。 dpkg: 处理软件包 qemu-system-misc (--configure)时出错:
依赖关系问题 - 仍未被配置
dpkg: 依赖关系问题使得 qemu-system 的配置工作不能继续:
qemu-system 依赖于 qemu-system-arm;然而:
软件包 qemu-system-arm 尚未配置。
qemu-system 依赖于 qemu-system-mips;然而:
软件包 qemu-system-mips 尚未配置。
qemu-system 依赖于 qemu-system-ppc;然而:
软件包 qemu-system-ppc 尚未配置。
qemu-system 依赖于 qemu-sys由于已经达到 MaxReports 限制,没有写入 apport 报告。
由于已经达到 MaxReports 限制,没有写入 apport 报告。
由于已经达到 MaxReports 限制,没有写入 apport 报告。
tem-sparc;然而:
软件包 qemu-system-sparc 尚未配置。
qemu-system 依赖于 qemu-system-x86;然而:
软件包 qemu-system-x86 尚未配置。
qemu-system 依赖于 qemu-system-misc;然而:
软件包 qemu-system-misc 尚未配置。 dpkg: 处理软件包 qemu-system (--configure)时出错:
依赖关系问题 - 仍未被配置
正在设置 qemu-user (1:2.5+dfsg-5ubuntu10.14) ...
正在设置 qemu-utils (1:2.5+dfsg-5ubuntu10.14) ...
dpkg: 依赖关系问题使得 qemu 的配置工作不能继续:
qemu 依赖于 qemu-system (>= 1:2.5+dfsg-5ubuntu10.14);然而:
软件包 qemu-system 尚未配置。 dpkg: 处理软件包 qemu (--configure)时出错:
依赖关系问题 - 仍未被配置
dpkg: 依赖关系问题使得 qemu-user-binfmt 的配置工作不能继续:
qemu-user-binfmt 依赖于 binfmt-support;然而:
软件包 binfmt-support 尚未配置。 dpkg: 处理软件包 qemu-user-binfmt (--configure)时出错:
依赖关系问题 - 仍未被配置
正在处理用于 libc-bin (2.23-0ubuntu9) 的触发器 ...
由于已经达到 MaxReports 限制,没有写入 apport 报告。
由于已经达到 MaxReports 限制,没有写入 apport 报告。
在处理时有错误发生:
binfmt-support
qemu-system-common
qemu-system-arm
qemu-system-mips
qemu-system-ppc
qemu-system-sparc
qemu-system-x86
qemu-system-misc
qemu-system
qemu
qemu-user-binfmt
E: Sub-process /usr/bin/dpkg returned an error code (1)

那么可能是服务自启动有关造成的,比如上面的就是我tomcat8的问题,我使用sysv-rc-conf把tomcat8的开机启动都关闭

通过以上设置之后再次安装基本全部通过。

千万不要尝试这种方法:http://www.cnblogs.com/EasonJim/p/7215988.html,因为通过这种方式安装成功后表面是成功了,但是实质上是无法运行的。

2、安装好时候,在Dash启动virt-manage时出现:无法连接到 libvirt。的问题,如下所示:

sudo virt-manager

或者使用Alt+F2

gksu gksu virt-manager

输入管理员密码就不会出现上面提示。

或者使用愚蠢的办法,重启电脑会发现神奇的好了。

3、在命令行上输入qemu,出现:qemu:未找到命令,如下所示:

这个问题是由于在12.04之后的qemu版本不在/usr/bin下创建qemu,取代的是qemu-system-i386和qemu-system-x86-64,如果想要用回qemu命令,可以通过创建链接的方式,如下:

sudo ln -s /usr/bin/qemu-system-i386 /usr/bin/qemu

参考:

https://www.unixmen.com/how-to-install-and-configure-qemu-in-ubuntu/

https://askubuntu.com/questions/345218/virt-manager-cant-connect-to-libvirt

http://yang19890314.blog.51cto.com/1620466/1139551

Ubuntu 16.04通过APT源安装QUEM虚拟机调试Linux内核的更多相关文章

  1. Ubuntu 16.04通过源码安装QUEM虚拟机

    下载编译安装: wget http://download.qemu-project.org/qemu-2.9.0.tar.xz tar xvJf qemu-2.9.0.tar.xz cd qemu-2 ...

  2. Ubuntu 16.04 更改apt源

    1 修改apt源配置文件,把/etc/apt/sources.list替换为以下内容: sudo gedit /etc/apt/sources.list deb http://mirrors.aliy ...

  3. 制作 Ubuntu 16.04 离线apt源

    1.下载离线安装包 ubuntu下安装包都会下载到/var/cache/apt/archives下,首先清空该目录 sudo apt-get clean 下载需要安装包 sudo apt-get in ...

  4. 怎样在 Ubuntu 16.04 强制 APT 包管理器使用 IPv4 | Linux 中国

    版权声明:本文为博主原创文章.未经博主同意不得转载. https://blog.csdn.net/F8qG7f9YD02Pe/article/details/82879401 https://mmbi ...

  5. Ubuntu 16.04 python和OpenCV安装

    Ubuntu 16.04 python和OpenCV安装:最进在做深度学习和计算机视觉的有关内容,因此要在python中用到opencv.我的电脑装的是Ubuntu 16.04,python 2.7和 ...

  6. 在Ubuntu 16.04 LTS下编译安装OpenCV 4.1.1

    目录 一 安装前的准备 二 编译并安装OpenCV 4.1.1 注:原创不易,转载请务必注明原作者和出处,感谢支持! OpenCV目前(2019-8-1)的最新版本为4.1.1.本文将介绍如何在Ubu ...

  7. 阿里云ECS服务器环境搭建(1) —— ubuntu 16.04 图形界面的安装

    阿里云ECS服务器环境搭建(1) —— ubuntu 16.04 图形界面的安装1. 背景在我们购买阿里云ECS服务器之后,默认的系统环境是很干净的,我购买的是ubuntu16.04,远程登录进入之后 ...

  8. Ubuntu 16.04.3 Server 版安装过程图文详解

    Ubuntu 16.04.3 Server 版安装过程图文详解 首先,我们会进入系统安装的第一个界面,开始系统的安装操作.每一步的操作,左下角都会提示操作方式! 1.选择系统语言-English2.选 ...

  9. 给Ubuntu 16.04更换更新源

    给自家的Ubuntu下载软件速度有点慢,毕竟是从国外下载软件,就想更换到国内比较好的更新源(就是这些软件所在的服务器),一般直接百度Ubuntu更新源就能出来一大堆,这时候最好是找和自己Ubuntu版 ...

随机推荐

  1. ios上传图片显示方向错误问题

    IOS 上传图片方向显示错误问题 问题描述 在使用苹果手机上传图片的时候,发现传完的图片显示出来方向是错误的,竖着的图片会变成横着显示(少部分安卓手机也存在这个问题) 产生原因 ios 相机加入了方向 ...

  2. [bzoj3697]采药人的路径——点分治

    Brief Description 采药人的药田是一个树状结构,每条路径上都种植着同种药材. 采药人以自己对药材独到的见解,对每种药材进行了分类.大致分为两类,一种是阴性的,一种是阳性的. 采药人每天 ...

  3. Apache多网站虚拟目录域名

    一台服务器安装了Apache,如何绑定多个域名或网站呢? 最简单高效的方法如下: 1. 先打开Apache的配置文件httpd.conf,在这个文件, 找到这句:“#Include etc/extra ...

  4. mysql 四 表操作

    表介绍 表相当于文件,表中的一条记录就相当于文件的一行内容,不同的是,表中的一条记录有对应的标题,称为表的字段 id,name,qq,age称为字段,其余的,一行内容称为一条记录 本节重点: 1 创建 ...

  5. return 与 exit() 的区别

    return是一个关键字,返回函数值:exit()是一个函数: return是语言级的:exit()是操作系统提供的函数: return表示函数退出:exit()表示进程退出: 非主函数中调用retu ...

  6. js 各种取整方式及方法

    1.直接丢弃小数部分,保留整数部分 a:parseInt(1.5555) b: 0|1.5555 2.向上取整 a: Math.ceil(1.5555) b: (1.5555+0.5).toFixed ...

  7. 几种常用排序算法的python实现

    1:快速排序 思想: 任意选取一个数据(通常选用数组的第一个数)作为关键数据,然后将所有比它小的数都放到它前面,所有比它大的数都放到它后面,这个过程称为一趟快速排序. 一趟快速排序的算法是: 1)设置 ...

  8. 《Java编程思想》笔记 第九章 接口

    1.抽象类和抽象方法 抽象方法,仅有方法声明没有方法体 abstract class AbstractClass{ abstract void f(); //没有 {} } 只要有一个或者多个抽象方法 ...

  9. ros 如何使用 openni2_launch

    There is very little actual code/etc in openni2_launch, it is mostly a thin wrapper around openni2_c ...

  10. MATLAB规划问题——线性规划和非线性规划

    1.线性规划 求线性规划问题的最优解有两种方法,一种方法是使用linprog命令,另一种是使用optimtool工具箱,下面分别介绍这两种方法. ①linprog命令 一般情况下,Linprog命令的 ...