Displaying 20 results from an estimated 200 matches similar to: "Libvirt 4.2.0 hang on destination on live migration cancel"
2018 Jan 25
2
Re: libvirtd hangs
Ján Tomko wrote 2018-01-18 14:27:
> On Thu, Jan 18, 2018 at 11:30:16AM +0700, Artem Likhachev wrote:
>> # strace -p 5786
>> read(53, "\0\0\0\34", 4) = 4
>> read(53, "keep\0\0\0\1\0\0\0\2\0\0\0\2\0\0\0\0\0\0\0\0", 24) = 24
>> poll([{fd=5, events=POLLIN}, {fd=7, events=POLLIN}, {fd=12,
>> events=POLLIN}, {fd=13, events=POLLIN},
2018 Jan 18
2
libvirtd hangs
Hello everybody!
We have a cluster of servers managed by VMmanager 5 KVM (by ispsystem).
A typical node:
# cat /etc/redhat-release
CentOS Linux release 7.3.1611 (Core)
# uname -r
3.10.0-693.11.6.el7.x86_64
# rpm -qa |grep libvirt
libvirt-daemon-driver-qemu-3.7.0-1.el7.centos.x86_64
libvirt-daemon-driver-storage-disk-3.7.0-1.el7.centos.x86_64
libvirt-3.7.0-1.el7.centos.x86_64
2018 Jun 13
0
"virsh" list
Hello,
I installed libvirt from package manager(debian apt) and want to modify
feture in it, so i git clone from https://libvirt.org/git/?p=libvirt.git;a=summary
But now i have trouble to start virsh.
I have traced the email:
https://www.redhat.com/archives/libvirt-users/2017-February/msg00074.html
Here is output of command below:
strace -o libvirt.log -f -s 1000 /usr/sbin/libvirtd
2017 Dec 22
2
Re: [BUG] Not exiting media forced a promptly close of libvirt 3.10
Hi Daniel,
sorry. Here the requested stack trace.
Best regards
Holger
=====================================================================================
Thread 18 (Thread 0x7f0d495e0700 (LWP 10742)):
#0 0x00007f0d55e690bf in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
No symbol table info available.
#1 0x00007f0d5892176a in virCondWait (c=c@entry=0x5557f238db28,
2017 Dec 22
2
[BUG] Not exiting media forced a promptly close of libvirt 3.10
Hello,
In the .xml file I use a media which is no longer available.
In the past, I got the information media not available and the
creation of the VM was stopped - O.k. behavior.
Since 3.10 the libvirtd stopped promptly and all open
consoles windows and the virt-manager closed promptly.
For diagnose:
etcsvms1:/kvm/CS8200/M5 # coredumpctl
TIME PID UID GID SIG
2018 Jan 18
0
Re: libvirtd hangs
On Thu, Jan 18, 2018 at 11:30:16AM +0700, Artem Likhachev wrote:
>Hello everybody!
>
>We have a cluster of servers managed by VMmanager 5 KVM (by ispsystem).
>
>A typical node:
>
># cat /etc/redhat-release
>CentOS Linux release 7.3.1611 (Core)
># uname -r
>3.10.0-693.11.6.el7.x86_64
>
># rpm -qa |grep libvirt
2018 Apr 04
2
Re: error : virHashForEach:597 : Hash operation not allowed during iteration
❦ 4 avril 2018 11:17 +0200, Michal Privoznik <mprivozn@redhat.com> :
> Dunno, this is the first time I hear about this issue. Maybe you can try
> to set a break point on virHashIterationError() and when it's hit get
> stacktrace of all threads 't a a bt'. That might shed more light into
> the issue. Smells like we are not locking somewhere properly.
So, we have two
2017 Sep 13
2
Compile libvirt on OSX 10.12
I'm having issues with compiling libvirt on OSX 10.12
~/Development/github/libvirt/ [master] make
/Library/Developer/CommandLineTools/usr/bin/make all-recursive
Making all in .
Making all in gnulib/lib
/Library/Developer/CommandLineTools/usr/bin/make all-am
make[3]: Nothing to be done for `all-am'.
Making all in include/libvirt
make[2]: Nothing to be done for `all'.
Making all in
2017 Nov 15
1
Re: Urgent: virsh - change-media run into a promptly close of libvirt
On 11/15/2017 06:54 AM, Holger Schranz wrote:
> Thread 1 (Thread 0x7f4a069cc700 (LWP 10178)):
> #0 0x00007f49ff969170 in qemuDomainChangeEjectableMedia (
> driver=driver@entry=0x7f49f841b700, vm=vm@entry=0x7f49ec02fbd0,
> disk=disk@entry=0x7f49ec0375d0, newsrc=0x7f49e8014d10, force=force@entry=false)
> at qemu/qemu_hotplug.c:303
This is fixed in current upstream by
2018 Apr 04
0
Re: error : virHashForEach:597 : Hash operation not allowed during iteration
On 04/04/2018 02:59 PM, Vincent Bernat wrote:
> ❦ 4 avril 2018 11:17 +0200, Michal Privoznik <mprivozn@redhat.com> :
>
>> Dunno, this is the first time I hear about this issue. Maybe you can try
>> to set a break point on virHashIterationError() and when it's hit get
>> stacktrace of all threads 't a a bt'. That might shed more light into
>> the
2018 Apr 04
3
error : virHashForEach:597 : Hash operation not allowed during iteration
Hey!
On many of our servers, we often have the following error:
error : virHashForEach:597 : Hash operation not allowed during iteration
When querying the list of domains, this means libvirt will silently
return 0 domain (most uses of virHashForEach don't handle the return
code).
We are using a hook, but the hook doesn't query libvirt back, so it
should be safe from this point of view.
2015 Nov 04
0
xen/libvirt freeze while attching network-device to vm´s
Hi,
first sorry for the cross-posting, but i don ́t known exactly if my
problem belongs to xen or libvirt.
I have an VM-Host with Xen 4.6.0 und libvirt 1.2.19. The Job of the
Host is to resume in parallel 20 VM ́s (HVM WinXp) attach a
block-device to each VM , wait 60 Seconds, kill the VM and start from
beginning. For that, a python script create for each vm a thread and
each thread get a
2013 Dec 19
1
Re: About debugging of libvirt.
i did the debugging as you said. Kindly refer the following logs:
(gdb) c
Continuing.
thread apply all bt
[New Thread 0x7fc337c6b700 (LWP 29520)]
Program received signal SIGSEGV, Segmentation fault.
0x0000000000000000 in ?? ()
(gdb) thread apply all bt
Thread 12 (Thread 0x7fc337c6b700 (LWP 29520)):
#0 0x00007fc33509f18d in read () from /lib/x86_64-linux-gnu/libpthread.so.0
#1
2017 Apr 20
2
Re: libvirtd segfault when using oVirt 4.1 with graphic console - CentOS7.3
hello,
I attached core dump - not sure if it was what you have asked for
I am rather just admin not developer :)
Regards,
Rafal Wojciechowski
W dniu 20.04.2017 o 16:44, Pavel Hrdina pisze:
> On Thu, Apr 20, 2017 at 07:36:42AM +0200, Rafał Wojciechowski wrote:
>> hello,
>>
>> I am getting such error:
>> libvirtd[27218]: segfault at 0 ip 00007f4940725721 sp
2013 Dec 19
2
Re: About debugging of libvirt.
I am newbie to this gdb debugging. now i did the bt in the debugging. In my
side still it showing the error. Following are the stacktrace which i got.
Kindly refer the following logs for full information:
****
[New Thread 0x7f8503695700 (LWP 20012)]
Program received signal SIGSEGV, Segmentation fault.
0x0000000000000000 in ?? ()
(gdb) bt
#0 0x0000000000000000 in ?? ()
#1 0x00007f84f671281e in
2017 Nov 15
2
Re: Urgent: virsh - change-media run into a promptly close of libvirt
On Tue, Nov 14, 2017 at 07:19:01PM +0100, Holger Schranz wrote:
> Ups ... my fault ...
>
> libvirtd instead libvirt ....
>
>
> etcsvms5:/var/lib/systemd/coredump # coredumpctl info libvirtd
> PID: 10177 (libvirtd)
> UID: 0 (root)
> GID: 0 (root)
> Signal: 11 (SEGV)
> Timestamp: Tue 2017-11-14 10:11:32 CET (9h ago)
2017 Sep 14
0
Re: Compile libvirt on OSX 10.12
On Wed, 2017-09-13 at 17:20 -0400, Homie Pawlowski wrote:
> I'm having issues with compiling libvirt on OSX 10.12
>
> ~/Development/github/libvirt/ [master] make
> /Library/Developer/CommandLineTools/usr/bin/make all-recursive
> Making all in .
> Making all in gnulib/lib
> /Library/Developer/CommandLineTools/usr/bin/make all-am
> make[3]: Nothing to be done for
2019 Aug 05
2
Vm in state "in shutdown"
Description of problem:
libvirt 3.9 on CentOS Linux release 7.4.1708 (kernel 3.10.0-693.21.1.el7.x86_64) on Qemu version 2.10.0
I’m currently facing a strange situation. Sometimes my vm is shown by ‘virsh list’ as in state “in shutdown” but there is no qemu-kvm process linked to it.
Libvirt log when “in shutdown” state occur is as follows:
“d470c3b284425b9bacb34d3b5f3845fe” is vm’s name,
2017 Apr 21
0
Re: libvirtd segfault when using oVirt 4.1 with graphic console - CentOS7.3
On Thu, Apr 20, 2017 at 06:10:04PM +0200, Rafał Wojciechowski wrote:
> hello,
>
> I attached core dump - not sure if it was what you have asked for
> I am rather just admin not developer :)
>
> Regards,
>
> Rafal Wojciechowski
The attached core send in private mail helped to figure out where the crash
happened. Backtrace:
Thread 1 (Thread 0x7f194b99d700 (LWP 5631)):
2006 Aug 28
2
winbind issue
i was able to successfully joined the linux machine ie. RHEL 3 to windows
2003 domain and able to pull the AD users and groups using
wbinfo -u and wbinfo -g command.
Am trying to authenticate the AD user using radtest, a command tool used in
freeradius to authenticate the user logon credentials. It rejects AD
user logon credentials.
I have linux nis server running under same subnet. This