** Changed in: qemu (Ubuntu)
Status: New => Invalid
** Changed in: qemu
Status: New => Invalid
** Changed in: virtinst (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu
@arges -- installation of qemu-kvm has fixed the problem.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1387881
Title:
qemu fails to recognize full virtualization
To manage notificat
@Serge
Gotcha, I misinterpreted your statement. Yes we are in agreement.
@dpb:
Have you had any further failures after installing qemu-kvm?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs
Nested on Intel should be much improved in newer kernel versions
(especially with regard to nested ept as the original report seems to
indicate is in use.
So if the original emulation failure is reproducible, I'd suggest
testing on a newer kernel.
--
You received this bug notification because yo
Answers to some of your questions:
Can you only get this on one particular host (i.e. hardware type)?
- No as I can repro in KVM
-Is there anything in syslog?
- Nothing relevant
Which packages (dpkg -l | grep qemu)
ii qemu-utils 2.0.0+dfsg-2ubuntu1.6 amd64
** Also affects: virtinst (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1387881
Title:
qemu fails to recognize full virtualization
I can reproduce this in a VM:
1) boot a clean cloud images (uvt-kvm create lp1387881)
2) apt-get install virtinst
3) sudo virt-install --name juju-bootstrap --ram=2048 --vcpus=1 --hvm
--virt-type=kvm --pxe --boot network,hd --os-variant=ubuntutrusty --graphics
vnc --noautoconsole --os-type=linux
I don't think however that we can claim this is notabug. Based on the
Description, the kvm modules appears to be loaded and enabled, per kvm-ok
output. You shouldn't be getting the
KVM internal error. Suberror: 1
emulation failure
that you're getting, and it's not clear to me what part of insta
I just added qemu-kvm as a dependency for the openstack installer. It is
probably correct in assuming that virtinst shouldn't depend on qemu-kvm
since you can do paravirtualized.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in U
So I'm not completely sure virtinst should depend on qemu-kvm, since we
assume one can use it without --virt-type=kvm, so my thoughts would be
you should install additional package as necessary to use qemu w/ KVM.
I'll let hallyn comment as well.
--
You received this bug notification because you
apt history.log for packages installed on top of base system. Note that
only the last entry was done by me, the others were done in preparation
of the image:
http://paste.ubuntu.com/8761810/
Basically, I booted a curtain installed maas node with an amd64 trusty
image from maas. Logged in, ran
This is a package dependency issue and not a kernel issue. Once
davidpbritton installed 'qemu-kvm' he was able to install using virt-
install just fine.
So overall either the packages davidpbritton was installing weren't
sufficient to use qemu with KVM, or we have a dependency problem in the
Ubunt
dpkg -l |grep qemu:
ii qemu-utils 2.0.0+dfsg-2ubuntu1.6
amd64QEMU utilities
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1387881
Title:
qemu fails
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k3.13.0-39-generic.
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v
David,
Could you attach the collection of:
apport-collect 1387881
Also the output of:
dpkg -l |grep qemu
On the affected NUCs if the problem still persists?
Thanks,
Adam
** Tags added: kernel-unable-to-test-upstream
--
You received this bug notification because you are a member of Ubuntu
S
So adding qemu-kvm fixed the issue with running nested KVM. I think
though the problem still exists on a non nested environment.
I'll get with the user who encountered this and see if I can get some
more logs.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Serve
Also please show the results of:
dpkg -l | grep qemu
Does a reboot or a 'rmmod kvm_intel kvm; modprobe kvm kvm_intel' fix
it?
You said earlier (in irc) that 'sudo apt-get install qemu-kvm' fixes it.
Is that still the case?
** Also affects: qemu (Ubuntu)
Importance: Undecided
Status:
17 matches
Mail list logo
