[libvirt-users] [offtopic] OpenNebulaConf2013: Extended keynote lineup and deadline for talk proposals
by Javier Fontan
Hello,
I hope you don't find this email too offtopic.
We have just published an expanded keynote line-up for the OpenNebula
Conference 2013 (http://blog.opennebula.org/?p=4707) that includes
experts from leading institutions using OpenNebula. The first ever
OpenNebula Conference will be held on Sept. 24-26 in Berlin and is
intended to serve as a meeting point for OpenNebula cloud users,
developers, administrators, builders, integrators and researchers.
As you may know OpenNebula uses libvirt to manage KVM and VMware VMs
and some of you may be using it in production. I think your
experiences will be very valuable. There are only 10 days left to
submit talk proposals (the deadline is June 15th).
We are looking forward to welcoming you personally in Berlin!.
Cheers
--
Join us at OpenNebulaConf2013 in Berlin from the 24th to the 26th of
September 2013!
Javier Fontán Muiños
Project Engineer
OpenNebula - The Open Source Toolkit for Data Center Virtualization
www.OpenNebula.org | jfontan(a)opennebula.org | @OpenNebula
11 years, 6 months
[libvirt-users] a problem about nested vm
by denghuancong
hi, I have a problem that confuse me so long.
I run a guest os(VM1) on a physical machine(PM1) that had enabled virtualization . Now, I also want to run a guest os (VM2) under VM1,but VM1 print the following message to me:
[2013-06-05 10:43:04,379][ERROR] machine:init_vm(57271)|state:init_vm|Create domain failed, unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.[2013-06-05 10:43:04,382][ERROR] machine:init_vm(57271)|state:init_vm|Create domain failed, unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.[2013-06-05 10:43:04,409][ERROR] machine:init_vm(57271)|state:init_vm|Create domain failed, unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.[2013-06-05 10:43:04,412][ERROR] machine:init_vm(57271)|state:init_vm|Create domain failed, unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.[2013-06-05 10:43:04,414][ERROR] machine:init_vm(57271)|state:init_vm|Create domain failed, unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.[2013-06-05 10:43:04,418][ERROR] machine:init_vm(57271)|state:init_vm|Create domain failed, unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.[2013-06-05 10:43:04,421][ERROR] machine:init_vm(57271)|state:init_vm|Create domain failed, unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.[2013-06-05 10:43:04,426][ERROR] machine:init_vm(57271)|state:init_vm|Create domain failed, unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.[2013-06-05 10:43:04,428][ERROR] machine:init_vm(57271)|state:init_vm|Create domain failed, unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.[2013-06-05 10:43:04,432][ERROR] machine:init_vm(57271)|state:init_vm|Create domain failed, unsupported configuration: Domain requires KVM, but it is not available. Check that virtualization is enabled in the host BIOS, and host configuration is setup to load the kvm modules.
so, how can i enable the virtualization option in vm1???
thanks a lot. :)
11 years, 6 months
[libvirt-users] libvirt tls error
by yue
centos6.3,libvirt 0.9.10.
[root@ovirtdev private]# virsh -c qemu+tls://ovirtdev.localhost/system list
2013-04-22 03:37:09.362+0000: 9898: info : libvirt version: 0.9.10, package: 21.el6_3.8 (CentOS BuildSystem <http://bugs.centos.org>, 2013-01-28-19:24:16, c6b10.bsys.dev.centos.org)
2013-04-22 03:37:09.362+0000: 9898: warning : virNetClientIncomingEvent:1665 : Something went wrong during async message processing
error: Unable to read TLS confirmation: Input/output error
error: failed to connect to the hypervisor
thanks
11 years, 6 months
[libvirt-users] About the change of a VM's vcpu count in runtime?
by Dennis Chen
Hi,
We know that there is a command "setvcpus" in virsh used to "change
number of virtual CPUs", now we just have the need to change vcpu count
dynamically for a running VM, so I tried this command (the vcpu count is
2 in the VM xml file), below is the result:
virsh # setvcpus 3 --count 4
error: invalid argument: requested vcpus is greater than max allowable
vcpus for the domain: 4 > 2
virsh # setvcpus 3 --count 1
error: Operation not supported: qemu didn't unplug the vCPUs properly
So I tried another way: log into the running VM, and "echo 0 >
/sys/devices/system/cpu/cpu1/online", after that I can find only one
processor in the vm through '/proc/cpuinfo', but in virsh, the vcpuinfo
still shows:
virsh # vcpuinfo 3
VCPU: 0
CPU: 0
State: running
CPU time: 13.5s
CPU Affinity: yyyy
VCPU: 1
CPU: 1
State: running
CPU time: 6.9s
CPU Affinity: yyyy
So the question is: is there any method I can't find yet to change the
vcpu count of a running vm dynamically?
BRs,
Dennis
11 years, 6 months
