similar to: Detecting deadlocks with hypervisor..

Two machines (NFS Server: running ZFS / Client: disk-less), both are running FreeBSD r253506. The NFS client starts to deadlock processes within a few hours. It usually gets worse from there on. The processes stay in "D" state. I haven't been able to reproduce it when I want it to happen. I only have to wait a few hours until the deadlocks occur when traffic to the client machine

+thread-sanitizer mailing list On Mon, Sep 7, 2015 at 6:41 PM, Vaivaswatha Nagaraj <vn at compilertree.com> wrote: > Hi, > > I am interested in understand the compiler-rt thread sanitizer tool and have > recently started experimenting with it. In particular, I'm interested in the > deadlock detector. > > I see that deadlock detection currently don't work. (I

Here''s the first snapshot of the USB code after updating to the new xenbus. The xenidc code provides a much higher level of abstraction than the new xenbus code so the changes didn''t affect the usb driver much. I had to put in empty frontend_changed and backend_changed functions because the new xenbus code segfaults without them. The USB code doesn''t need them because

This seems exceptionally evil and is definitely a PITA. What was the original problem that led us to do this? I''d like to take a stab at correcting it so we can have a more sane installation. Regards, Anthony Liguori _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hi, I had a problem trying to migrate domains, in trying to locate it I noticed that saving domains doesn''t work either, which I believe explains why the receiving xfrd doesn''t actually receive anything. So here it goes... xenone:/tmp# xm list Name Id Mem(MB) CPU State Time(s) Console Domain-0 0 123 0 r---- 900.6 sky 9

Commit 9e6d990f exposed a pre-existing deadlock between the nbd plugin as client and parallel nbdkit as server. Prior to that commit, the deadlock was "resolved" because we unloaded the .so in parallel to a .close callback that never completed (yes, it's nasty that it usually? let the testsuite pass), but now we correctly refuse to unload a plugin that has not returned from .close,

Attached patch fixes a problem in marshaling large integers. It seems to only occur on systems with very large memory. However, on those systems, it''s a show-stopper. I see this as a temporary solution until we can sanitize the XML-RPC functions and get rid of all the S-Expression stuff. I''ll run xm-test tomorrow against it. Right now I''ve only done basic

https://bugzilla.samba.org/show_bug.cgi?id=10527 Summary: Rsync Deadlock when copying files Product: rsync Version: 3.1.0 Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: dah4k0r at gmail.com

Hi, The following patch implements a secure XML-RPC protocol for Xend. Instead of using HTTPS with basic authentication and dealing with all that nasty OpenSSL/PAM integration, it just uses SSH. This gives you all the properties you want (great security and PAM integration) with very little code. There are some minor issues so I''d rather it not be applied immediately.

This fixes a number of problems introduces in the recent XML-RPC check-in. The higher level errors are a great idea and I''ve also extended it a bit to have a slightly nicer interface. Please apply. Regards, Anthony Liguori _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

I'm running Dovecot 1.1 RC1. I believe I've done all the due diligence for making things working correctly over nfs. But I run into locking issues if I run over nfs. procmail is doing the delivery over nfs. uw-imap was ruining over nfs. dovecot is fine if its on the nfs server (i.e. it has local access to the disk, no nfs) I run into lock deadlocks if I run dovecot over nfs Users

Hi All, i have a problem with the SMBD processes on my clustered Samba setup. The setup contains: - 2 gentoo linux nodes (kernel 2.6.33.2) - ctdb 1.0.114_p1 - samba 3.5.8 - glusterfs 2.0.8 sometimes i want to do some maitenance on one of the nodes, then i do the following: - /etc/init.d/samba stop (to stop samba, and move all the users to the other nodes) - /etc/iniit.d/ctdb stop (to move the

Hi, I am observing a deadlock with llvm-lit on windows 7. When I attached a debugger, the communicate() call is blocked. In file utils/lit/lit/TestRunner.py > # FIXME: There is probably still deadlock potential here. Yawn. > procData = [None] * len(procs) > procData[-1] = procs[-1].communicate() I am invoking python directly on windows to run the unit tests.

Just wondering if this is a known bug? Trying to migrate the VM off to a diff dom0 results in the below error. Other VMs migrated off fine (started at around the same time as this vm) and I''ve tried a few different target servers, all resulting in the same thing. [2011-09-13 13:48:24 3996] DEBUG (XendCheckpoint:124) [xc_save]: /usr/lib/xen/bin/xc_save 29 77 0 0 1 [2011-09-13

Hi Sriram, Once again, thanks for your timely reply.... I tested as your suggesstion and i found that i don''t have any file in the location "/var/lib/xen" [root@globushead xen]# pwd /var/lib/xen [root@globushead xen]# ls -ll total 0 Further i tested the command "xm save " and results as follows Terminal 1: xm save -c TestVM1 TestVM1.chkpt

Hi all, I am using Xen 4.0.0 on top of Ubuntu Lucid (amd64), with the Jeremy kernel taken from git (xen/stable-2.6.32.x branch, 2.6.32.12 when I am writing this email). This kernel is also used in my domu. I can save a domu without any problem, but restoring it may need from 2 to 5 minutes, from a 1G checkpoint file (domu has 1GB RAM). There also errors in /var/log/xen/xend.log :

Hi all, I am using Xen 4.0.0 on top of Ubuntu Lucid (amd64), with the Jeremy kernel taken from git (xen/stable-2.6.32.x branch, 2.6.32.12 when I am writing this email). This kernel is also used in my domu. I can save a domu without any problem, but restoring it may need from 2 to 5 minutes, from a 1G checkpoint file (domu has 1GB RAM). There also errors in /var/log/xen/xend.log :

Hello again, now my xen works. But a strange thing: Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 2514 4 r----- 76.2 vx1 1 256 1 -b---- 6.1 vx2 2 256 1 -b---- 5.8 vx3 3 256 1 -b---- 5.3 vx4

I got latest (13601) yesterday evening. This doesn''t seem to work to do Restore (at least of the Windows test-image that I''ve been using for testing previously). The VM restores reasonably OK, but it jumps to an invalid address shortly after restoring, giving a D1 blue-screen error (DRIVER_IRQL_LESS_OR_EQUAL), which turns out to be "page-fault in driver" after I

Hi, I have three Xen hosts running Xen 4.0.2 (OpenSuSE 11.4 based). I also have one ''NFS'' server with an NFS export holding VM images and configuration files. Each host has a dedicated LAN link directly to the NFS server. I have another separated NFS export for VM locking (but I had the same issues before). When I attempt to live migrate a VM, it *looks''*like