** Changed in: vm-builder (Ubuntu)
Assignee: (unassigned) = devendra (devedevendra)
** Changed in: vm-builder (Ubuntu)
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in Ubuntu.
** Changed in: vm-builder (Ubuntu)
Assignee: Itraju Devendra Babu (itraju-babu) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in Ubuntu.
https://bugs.launchpad.net/bugs/445253
Title:
I had this same problem. kvm-ok was reporting success, but the VM
creation was still failing. I had to power off the server after changing
the BIOS in order for the 'hvm' type to be valid.
--
libvirt.libvirtError: internal error no supported architecture for os type 'hvm'
I just added a node-controller which doesn't have a virt.accelerated
processor in it and I'm getting libvirt: internal error no supported
architecture for os type 'hvm' (code=1)
Can I use a node-controller which doesn't have virt.acceleration??
--
libvirt.libvirtError: internal error no
I'm getting the exact same error on Jaunty on an AMD x86_64
** Changed in: vm-builder (Ubuntu)
Status: Invalid = Confirmed
--
libvirt.libvirtError: internal error no supported architecture for os type 'hvm'
https://bugs.launchpad.net/bugs/445253
You received this bug notification because
H I suspect that this may be due to the hardware virtualisation not
being enabled in the BIOS. Unfortunately I don't have immediate physical
access to that server to check. I only have ssh access to it right now.
Anyone know a command I can run to check if hardwar virtualisation is
enabled?
I haven't been able to confirm that it is the BIOS setting thats the
problem, but running virsh capabilities doesn't show anything for guest,
and from I've found in other forums I think it should.
is it possible for vmbuilder to run virsh capabilities to make sure
hvm is working (throwing up an
oh and it seems that this error only comes up if you use the
--libvirt=qemu:///system option. So if someone uses that option the
virsh capabilities needs to be checked.
--
libvirt.libvirtError: internal error no supported architecture for os type 'hvm'
https://bugs.launchpad.net/bugs/445253
You
Hey all,
The problem still exists even with kvm enabled in the bios.
:~/vm1$ kvm-ok
INFO: Your CPU supports KVM extensions
INFO: /dev/kvm exists
KVM acceleration can be used
grep ' lm ' /proc/cpuinfo
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36
virtualization was disabled in the BIOS (default settings):
kernel: [ 476.938973] kvm: disabled by bios
I think this is what caused the problem, closing...
** Changed in: vm-builder (Ubuntu)
Status: New = Invalid
--
libvirt.libvirtError: internal error no supported architecture for os
10 matches
Mail list logo
