similar to: [PATCH] hotplug/Linux: close lockfd after lock attempt

On Sat, Aug 06, 2016 at 03:43:48AM +0000, Eric Wong wrote: > Eric Wong <e at 80x24.org> wrote: > > I'm trying to test a trivial patch to set FD_CLOEXEC on the > > flintlock lockfd when using F_OFD_SETLK > > Fwiw, this is the patch I was originally going to test. > (but now I see maybe my F_SETFD might only need to be > called on F_OFD_SETLK success)

I'm trying to test a trivial patch to set FD_CLOEXEC on the flintlock lockfd when using F_OFD_SETLK and am running into a build failure even in an unpatched state. This is on a Debian jessie amd64 system building the jessie-backports version. The stable version (1.2.19-1+deb8u1) works and builds fine using the same commands, however I also encountered a similar build problem in a sid chroot

Currently virtio_scsi is forced if qemu in the host supports this feature. This test does however not take the capabilities of the started guest into account. As a result no disks will be found if the guest kernel is older than 3.4. I forced qemu_supports_virtio_scsi to return always 0, which seem to work well for the kernel versions as shipped in SLES11SP2, openSuSE 12.1 and older. Is there any

The xencommons runlevel script has a few modprobe calls to load drivers for dom0. Recently also the backend drivers for vbd and vif were added. Unfortunately without an explanation why that is (suddenly) needed. Now that I have been hitting such missing backend driver issue as well with a xenlinux based dom0 kernel I wonder how to handle the situation. The pvops kernel has 3 backend drivers

# HG changeset patch # User Ian Campbell <ian.campbell@citrix.com> # Date 1317367995 -3600 # Node ID 4b98868690218126b90620d9b43fdd4140145a43 # Parent e50da6b98e3d5933b9c98e8f43096fd3ebbae00d tools/check: check for yajl (needed by libxl) Signed-off-by: Ian Campbell <ian.campbell@citrix.com> --- (note to committer, ensure the new file is executable) diff -r e50da6b98e3d -r

We currently run xen on sles11sp1 and sles11sp2. Our hardware is HP Compaq DL360''s. We originally started with G6''s, but now we''ve grown and have G7''s and G8''s in the mix. We don''t do a lot of live migrations but is convenient to be able to at times. Is there any type of cpu leveling that can be done so live migrations will work with servers

Odd question I know. I am looking for source for as recent a kernel as possible running the old style xenlinux/xenified kernel (i.e. capable of running the xen3.3.x hypervisor). Any ideas where I can get this - preferably in git form? I think Stefano Stabellini had something that worked up to 2.6.36 (from memory). And yes, we would all prefer all our customers moved to xen4 but this is difficult

In no particular order. Some of these need further investigation. ---------------------------------------------------------------------- I had to patch libguestfs not to use febootstrap-supermin-helper --copy-kernel option. See attachment #1. This could be avoided by providing a newer febootstrap in Wheezy. I had to patch libguestfs to make it not use the (not working) virtio-scsi in old

Fulvio.Corno@polito.it wrote: > > I found the (possible) source of the error, in smbpass.c line 620+ .... > > If no entry is found, the procedure returns without releasing the lock. > I modified the last statement as: > > if (!found_entry) /* line 707 */ > { > fclose(fp); > pw_file_unlock(lockfd); >

Hello, I try to set up a clustered samba server (on Novell SLES11SP2) based upon CTDB and NFS. My problem is that I do not yet understand the structure of the setup when using NFS. I followed the documentation in http://wiki.samba.org/index.php/CTDB_Setup#Setting_up_CTDB_for_clustered_NFS As far as I understand this documentation, it should be possible to set up a samba cluster say having 3

I've set up a lab for testing Samba 4.1 as an RODC emulating a satellite office setup, using the sernet packages on SLES11SP2. ## Problem 1 samba_dnsupdate is failing: ==> /var/log/samba/log.samba <== [2013/11/18 13:22:37.416193, 0] ../lib/util/util_runcmd.c:317(samba_runcmd_io_handler) /usr/sbin/samba_dnsupdate: ; TSIG error with server: tsig verify failure [2013/11/18

I have a physical SLES11SP2/OES11 system that I''ve converted to a domU. It''s boots ok as an HVM, but when I try to boot as a PV it gets stuck. I have the kernel-xen packages installed and confident the menu.lst is correct. If I look at xm console for the VM I get the output below: Any ideas? Thanks James [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000]

Hi all. I'm experiencing long connect delays due to password file locking errors. For each connection samba logs the following errors: do_pw_lock: failed to lock SMB passwd file. mod_smbpwd_entry: unable to lock file /usr/local/samba-1.9.18p10/private/smbpasswd In the archives I found some other messages reporting the problem (on May this year), but no solution. Did I

This patch series adds support for network buffering in the Remus codebase in libxl. Changes in V3: [1/5] Fix redundant checks in configure scripts (based on Ian Campbell''s suggestions) [2/5] Introduce locking in the script, during IFB setup. Add xenstore paths used by netbuf scripts to xenstore-paths.markdown [3/5] Hotplug scripts setup/teardown invocations are now

This patch isn't ready to go upstream. In fact, I think we might do a quick 1.30 release soon, and save this patch, and also the extensive changes proposed for the test suite[1], to after 1.30. Currently it is not safe to use the same handle from multiple threads, unless you implement your own mutexes. See: http://libguestfs.org/guestfs.3.html#multiple-handles-and-multiple-threads These

YaST2 sysconfig can logically group the various sysconfig settings if the files are tagged. Add the missing (YaST specific) tags to xencommons. See for a description http://old-en.opensuse.org/Packaging/SUSE_Package_Conventions/Sysconfig Signed-off-by: Olaf Hering <olaf@aepfle.de> --- Resending: http://lists.xen.org/archives/html/xen-devel/2012-10/msg01140.html

Hey, There has been some discussion about EFI and SecureBoot and such. Most of the time I get questions in the form of "How do I get Fedora 17 with Xen to do EFI", I am going to concentrate on Fedora, but I think this applies to other distros too. From my reading (I hadn't actually tried EFI yet), there are two ways to bootup a system: - Using grub2.efi. Grub2 does the EFI API

This patch fixes IO deadlocks in the vtpm hotplug scripts. Signed off by: Matthew Fioravante matthew.fioravante@jhuapl.edu --- Changed since previous: * rebased off of latest xen stable * replaced instances of gawk with awk diff --git a/tools/hotplug/Linux/vtpm b/tools/hotplug/Linux/vtpm --- a/tools/hotplug/Linux/vtpm +++ b/tools/hotplug/Linux/vtpm @@ -1,22 +1,18 @@ #!/bin/bash +export

# HG changeset patch # User Olaf Hering <olaf@aepfle.de> # Date 1336153082 -7200 # Node ID 9a430b7e2df2893f7f4f75d10e66d52bdffa7efa # Parent 113fd57259b91af06a5352404dd94b484a98d2bc tools/hotplug: remove 4 from default runlevel in xen-watchdog, xend and xendomains Similar to what changeset 24847:0900b1c905f1 does in xencommons, remove runlevel 4 from the other runlevel scripts. LSB defines

Package: xen-utils-common Version: 4.0.0-1 Severity: normal After upgrading xen-utils-common from 3.4.2-4 to 4.0.0-1, I could not create a guest domain defined with a DRBD file type. The xm create command would fail with "Error: Device 51713 (vbd) could not be connected. Hotplug scripts not working.". After some research I realized the /etc/xen/scripts/block-drbd helper script was