[libvirt-users] live migration taking forever
by Xu (Simon) Chen
Hey folks,
I am running libvirt 1.2.4 and qemu 2.1 on a 3.14.27 kernel. I've found
that live migrating a relatively large VM (16 cores and 64G ram) is taking
forever - close to 15 hours now, and still not done...
With "lsof -i", I can see a connection is established from my source
hypervisor to a target hypervisor, likely for the purpose of copying data.
nettop shows that this connection is constantly sending 50-60MBps traffic.
The VM being migrated has a disk on ceph by using librbd.
I wonder if anyone has seen similar issues, and how I could troubleshoot
further. (I tried but failed to get qemu monitor to work on the VM...)
Thanks.
-Simon
9 years, 4 months
[libvirt-users] Probem with Windows 2012 R2 server
by Dominique Ramaekers
Hi,
I'm having a lot of trouble with a Server 2012R2 evaluation version. I'm testing it to see how good it works in libvirt-kvm. It seems the server won't run longer than a few days. After a few days, when I shut down the server, she won't start again.
Has anybody have experienced the same???
My Windows 8.1, and Linux VM's works perfectly...
Greetings
9 years, 4 months
[libvirt-users] questions around using numatune/numa/schedinfo
by Chris Friesen
Hi,
I'm running into some problems with libvirt and hoping someone can point me at
some instructions or maybe even help me out.
First, are there any requirements on qemu version in order to use the "numatune"
and/or "cpu/numa/cell" elements? Or do they use cgroups and not the native qemu
numa support?
Second, are there any instructions on how to set up cgroups? I initially hadn't
had cgroups mounted and running "virsh schedinfo <domain>" gave an error. So I
mounted "/sys/fs/cgroup/memory" and "/sys/fs/cgroup/cpu" and restarted libvirtd
but running "virsh schedinfo <domain>" still gives an error:
root@compute-1:~# virsh schedinfo 8
Scheduler : Unknown
error: Requested operation is not valid: cgroup CPU controller is not mounted
What am I missing?
Thanks,
Chris
9 years, 4 months
[libvirt-users] libvirt + xen assertion
by CloudPatch Staff
We're hitting an assert whenever we try to create an HVM instance under Xen
via libvirtd.
System is running on Gentoo, package information as follows:
app-emulation/xen-4.5.0 USE="api debug flask hvm pam pygrub python qemu
screen"
app-emulation/xen-tools-4.5.0 USE="api debug flask hvm pam pygrub python
qemu screen"
app-emulation/libvirt-1.2.11-r2:0/1.2.11 USE="caps libvirtd lvm macvtap nls
qemu udev vepa virtualbox xen"
The following commands are run in parallel:
vmmachine ~ # libvirtd --listen
2015-01-22 16:33:13.596+0000: 2620: info : libvirt version: 1.2.11
2015-01-22 16:33:13.596+0000: 2620: error : udevGetDMIData:1607 : Failed to
get udev device for syspath '/sys/devices/virtual/dmi/id' or
'/sys/class/dmi/id'
libvirtd: libxl_fork.c:350: sigchld_installhandler_core: Assertion
`((void)"application must negotiate with libxl about SIGCHLD",
!(sigchld_saved_action.sa_flags & 4) &&
(sigchld_saved_action.__sigaction_handler.sa_handler == ((__sighandler_t)
0) || sigchld_saved_action.__sigaction_handler.sa_handler ==
((__sighandler_t) 1)))' failed.
Aborted
vmmachine ~ # VIRSH_DEBUG=0 virsh create xml
create: file(optdata): xml
libvirt: XML-RPC error : End of file while reading data: Input/output error
error: Failed to create domain from xml
error: End of file while reading data: Input/output error
libvirt: Domain Config error : Requested operation is not valid: A
different callback was requested
9 years, 4 months
[libvirt-users] openvswitch port with no ip
by Yaron Illouz
I used openvswitch with virt-intall
I defined a network
<network>
<name>private</name>
<bridge name='virbr0'/>
<forward mode='bridge'/>
<virtualport type='openvswitch'/>
</network>
But get no ip for the ovs port when I launch the instance. Is this
correct?
ci-info: +++++++++++++++++++++++++Net device
info++++++++++++++++++++++++++
ci-info:
+--------+------+--------------+-------------+-------------------+
ci-info: | Device | Up | Address | Mask |
Hw-Address |
ci-info:
+--------+------+--------------+-------------+-------------------+
ci-info: | lo | True | 127.0.0.1 | 255.0.0.0 | .
|
ci-info: | eth1 | True | . | . |
52:54:00:24:16:29 |
ci-info: | eth0 | True | 172.16.5.136 | 255.255.0.0 |
52:54:00:44:01:28 |
In the bridge port vnet1 get assigned to virbr0
Bridge "virbr0"
Port "virbr0"
Interface "virbr0"
type: internal
Port "vnet1"
Interface "vnet1"
And i launch the instance the following way
virt-install --name probe9 --ram 4096 --vcpus=4 --check-cpu
--os-type=linux --import --disk
/data/KVM/Probe2-cloud3.qcow2,format=qcow2 --network network=ext
--network network=private --graphics vnc,listen=0.0.0.0 --noautoconsole
--disk vol=default/configuration2.iso,bus=virtio
Regards
9 years, 4 months
Re: [libvirt-users] [libvirt] libvirt 1.2.10 and latest EL6 qemu-kvm
by Kashyap Chamarthy
[Dropping libvir list and adding libvir-users list.]
On Mon, Jan 19, 2015 at 04:12:46PM +0100, liedekef(a)telenet.be wrote:
> Hi all,
>
> I had libvirt 1.2.10 running without issues together with the qemu package
> qemu-kvm-0.12.1.2-2.415.el6_5.14.x86_64.rpm
That's a really old QEMU and the libvirt you're using is relatively
newer.
> Now, after updating my server, qemu-kvm became version
> qemu-kvm-0.12.1.2-2.448.el6_6.x86_64
>
> And as a result, when doing 'virsh start' (virsh define worked ok), the following error occured:
>
> 2015-01-19 15:05:26.539+0000: 4347: error : qemuMonitorJSONCheckError:379 : internal error: unable to execute QEMU command 'qom-list': The command qom-list has not been
You seem to be hitting this bug (although the bug is for RHEL7, looks
like the same behavior):
https://bugzilla.redhat.com/show_bug.cgi?id=1082124
Where Michal Privoznik says, it should already be fixed with these
commits in libvirt:
730af8f2cd7bc0e4c98b97200857909f42ea817f --
qemuMonitorJSONGetCPUx86Data: Don't fail on ancient qemus
84f69602143551433e3e0a5226dc572ecb33c059 -- qemu: Check for presence
of device and properities when getting CPUID
a6a6f84af92a506f83fdecf56f292bcb89905492 -- qemu: Change return type
of qemuMonitorGetGuestCPU()
>
> The only thing I could do (even downgrading libvirt to 1.2.9 didn't
> work), was to downgrade qemu-kvm to the older version again ... Any
> hints on this?
For the EL distrubtione you're using, I think using whatever the newest
supported combination of libvirt and QEMU should help.
--
/kashyap
9 years, 4 months
[libvirt-users] Guests using more ram than specified
by Dennis Jacobfeuerborn
Hi,
today I noticed that one of my HVs started swapping aggressively and
noticed that the two guests running on it use quite a bit more ram than
I assigned to them. They respectively were assigned 124G and 60G with
the idea that the 192G system then has 8G for other purposes. In top I
see the VMs using about 128G and 64G which means there is nothing left
for the system. This is on a CentOS 7 system.
Any ideas what causes this or how I can calculate the actual maximum
amount of RAM I can assign to the guests on a HV without overcommitting RAM?
Regards,
Dennis
9 years, 4 months
[libvirt-users] volume can't be attached after libvirt upgrade
by Chengyuan Li
Hi,
My nova-compute nodes was running libvirt 0.9.13 and QEMU 1.0, after
libvirt was upgraded to 1.2.2, the VMs launched by libvirt 0.9.13 can't
attach volume any more, i.e. "nova volume-attach <vm-uuid> <volume-uuid>"
doesn't work. But before the libvirt upgrade, the same VM can attach volume
disk.
I did some debuging and find that, it failed in QEMU when try to open the
volume device, and the return errno is EPERM. QEMU instances is running as
user libvirt-qemu always, so is that possible some problem in Linux
capabilites or libvirt apparmor?
-------------------------------------
int qemu_open(const char *name, int flags, ...)
{
int ret;
int mode = 0;
long euid, egid;
if (flags & O_CREAT) {
va_list ap;
va_start(ap, flags);
mode = va_arg(ap, int);
va_end(ap);
}
euid = (long)geteuid();
egid = (long)getegid();
#ifdef O_CLOEXEC
ret = open(name, flags | O_CLOEXEC, mode);
#else
ret = open(name, flags, mode);
if (ret >= 0) {
qemu_set_cloexec(ret);
}
#endif
return ret;
}
Regards,
CY.
9 years, 4 months
[libvirt-users] Suggest to update python binding information on libvirt.org
by Lingyu Zhu
Hello.
I am new libvirt user. I downloaded and compile the source code with
default configuration. I had a lot of trouble before finally found out that
python bindings is now a separated package. However the web site still
states that python binding is directly supported, and that install extra
binding package when libvirt is installed as a binary package.
Please consider updating this misleading information.
Regards
Lingyu Zhu
9 years, 4 months
[libvirt-users] [libvirt]configuration question about usinf for [xen4.5][libxl]
by Doug McMillan
What configuration should be set in a custom compiled libvirt to get the most out of the xen libxl?
[ -f Makefile ] || ./configure --prefix=/usr --libexec=/usr/lib/"$pkgname" --sbindir=/usr/bin \ --with-storage-lvm=yes --with-udev=yes --without-hal --disable-static \ --with-init-script=systemd --with-systemctl=yes --with-systemd-daemon=yes \ --with-qemu-user=nobody --with-qemu-group=nobody \ --without-netcf --with-interface --with-lxc --with-storage-iscsi \ --with-xen=yes --with-libxl=yes # --with-audit
After compiling what needs done to configure libvirt to work with xen libxl because all I seem to be getting is:
error: failed to connect to the hypervisorerror: no connection driver available for //libxl[dragon@archxen ~]$
9 years, 4 months
