similar to: xen/libvirt freeze while attching network-device to vm´s

Cole Robinson wrote: > On 02/18/2014 10:45 PM, Jim Fehlig wrote: > >> Cole Robinson wrote: >> >>> On 02/18/2014 05:12 AM, Kim Larry wrote: >>> >>> >>>> The thing I found today is that if libvirt uses xend driver, shutdown events >>>> are delivered, but if libvirt uses libxl drvier, doesn't show up anything.

On 02/18/2014 10:45 PM, Jim Fehlig wrote: > Cole Robinson wrote: >> On 02/18/2014 05:12 AM, Kim Larry wrote: >> >>> The thing I found today is that if libvirt uses xend driver, shutdown events >>> are delivered, but if libvirt uses libxl drvier, doesn't show up anything. It >>> seems there are bugs on shutdown event, so I did dig into the 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

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

❦ 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

On Thu, 2013-04-11 at 05:09 +0100, Jim Fehlig wrote: > > + /* This will fill xenstore info about free and dom0 memory - if missing, > > + * should be called before starting first domain */ > > + if (libxl_get_free_memory(libxl_driver->ctx, &free_mem)) { > > + VIR_ERROR(_("cannot get free memory info")); > > + goto error; >

On Thu, 11 Apr 2013, Ian Campbell wrote: > On Thu, 2013-04-11 at 05:09 +0100, Jim Fehlig wrote: > > > + /* This will fill xenstore info about free and dom0 memory - if missing, > > > + * should be called before starting first domain */ > > > + if (libxl_get_free_memory(libxl_driver->ctx, &free_mem)) { > > > + VIR_ERROR(_("cannot

https://bugs.freedesktop.org/show_bug.cgi?id=99282 Bug ID: 99282 Summary: KDE kontact crashes always Product: Mesa Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: critical Priority: medium Component: Drivers/DRI/nouveau Assignee: nouveau at

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

Cole Robinson wrote: > On 02/18/2014 05:12 AM, Kim Larry wrote: > >> The thing I found today is that if libvirt uses xend driver, shutdown events >> are delivered, but if libvirt uses libxl drvier, doesn't show up anything. It >> seems there are bugs on shutdown event, so I did dig into the libvirt source >> briefly, but I couldn't find where libxl driver

Hello Xen Users, Been experimenting with upstream-qemu and wanted to try out the OVMF bios option, but I seem to be missing something. Are there additional steps to installing OVMF beyond compiling Xen? I saw notes on patching back in february, but I thought the package was included with Xen 4.2 on release. When I attempt to set it as my bios option, the machine boots then immediately closes.

I''ve been trying to have all spice features working on xen domUs since the end of 2011. Basic functions were already working. Adding qemu parameters manually for vdagent and usbredirection was and is also working (I made the patches to support them directly on xl). Qxl was never working: one bug on xen and one on qemu about qxl are fixed, the other xen bug found months ago on the

https://bugzilla.mindrot.org/show_bug.cgi?id=3598 Bug ID: 3598 Summary: Dead lock of sshd and Defunct of sshd Product: Portable OpenSSH Version: 9.1p1 Hardware: ix86 OS: Linux Status: NEW Severity: normal Priority: P5 Component: sshd Assignee: unassigned-bugs at mindrot.org

Package: xen-utils-4.3 Version: 4.3.0-3 Severity: normal II'm install xen-4.3 from official repository. When i try create virtulal machine got error: xl -vvvv create /etc/xen/xlexample.hvm Parsing config from /etc/xen/xlexample.hvm libxl: debug: libxl_create.c:1230:do_domain_create: ao 0x19811c0: create: how=(nil) callback=(nil) poller=0x1981220 libxl: verbose:

Hi! I have just made the 0.9.0 release of PRNGD available. PRNGD is the Pseudo Random Number Generator Daemon. It has an EGD compatible interface and is designed to provide entropy on systems not having /dev/*random devices. Software supporting EGD style entropy requests are openssh, Apache/mod_ssl, Postfix/TLS... Automatic querying of EGD sockets at fixed locations has been introduced in the

hi, all I do a hotplug detach a network in a thread, because virDomainDetachDeviceFlags maybe asynchronous, so I do like follow: cb_para->cluster_id = info->cluster_id; cb_para->group_id = info->group_id; cb_para->vsys_id = info->vsysid; cb_para->vnf_id = info->vnf_id; cb_para->conn = conn; cb_para->time_out = 20*1000;//20s

Dear, I need to attach some ceph (0.94.6) block devices to our openstack (kilo) running instances (xen 4.4) . Nova is able to create volumes, attach a detach (alt least there are no errors) The hypervisor can see the blockdevice: # rbd -p volumes ls volume-xxxxxxxx-7342-434b-9xx1-d046bcxxxxfd And the instance xml seems to be ok: ................. <disk

When I try to start hvm qemu-xen I get this error It seems that the path my be off. Can someone point me were in source code path to qemu pid is defined .It seems that qeum-xen points to loacation I don''t see were it is defined. xc: detail: elf_load_binary: phdr 0 at 0x0x7f71cac72000 -> 0x0x7f71cad079d5 libxl: error: libxl_dom.c:612:libxl__build_hvm: hvm building failed libxl: error:

Hi, I am trying to VGA passthrough Intel HD Graphics 4600 IGD with Xen-unstable 4.4 changeset 27214 and Linux kernel 3.10.0 but was not successful. Details are as follows: =============================================================================================== teo-en-ming@intel-core-i5-4430-desktop:~$ sudo xl info [sudo] password for teo-en-ming: host :

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.