similar to: Bug#622096: xen-utils-common: error in script "block" by checking loop device sharing prevents DomU from start

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

From: Karel Zak <kzak at redhat.com> ported to klibc losetup version from util-linux 108591d2b7860ca0b8d27d114bed1e504a31fa72, also add -h option. -maks Reported-by: Kamalesh Babulal <kamalesh at linux.vnet.ibm.com> Signed-off-by: Karel Zak <kzak at redhat.com> Signed-off-by: maximilian attems <max at stro.at> --- Other patches might be useful too, that one just

Commit-ID: 8443e57e5ba71e462e31e3b5aad9f7dd1b4736f5 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=8443e57e5ba71e462e31e3b5aad9f7dd1b4736f5 Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Tue, 5 Nov 2019 00:39:53 +0000 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Tue, 5 Nov 2019 00:44:32 +0000 [klibc] losetup: Fix char signedness

Commit-ID: 209676c9a3d057c0eba48f633eb541b17c7d1eba Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=209676c9a3d057c0eba48f633eb541b17c7d1eba Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Tue, 5 Nov 2019 00:33:37 +0000 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Tue, 5 Nov 2019 19:55:37 +0000 [klibc] losetup: Delete fallbacks to

Commit-ID: 333ef3af1dcef61a6bc5dba531453e5e0cb27da1 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=333ef3af1dcef61a6bc5dba531453e5e0cb27da1 Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Tue, 5 Nov 2019 19:52:19 +0000 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Tue, 5 Nov 2019 20:03:26 +0000 [klibc] losetup: Use

Hi, I have Xen 3.3.1 dom0 on Debian with 2.6.26-2-xen-amd64 kernel and I had to "xm destroy" my domU. Now when I try to start it again it fails like this: # xm list | grep n39 # # xm create -c /xen/conf/n39 Using config file "/xen/conf/n39". ROOT xen1:~> Error: Device 4 (vbd) could not be connected. losetup -r /dev/loop1 /xen/iso/amd64-netbsd-6.iso failed # losetup -a

hello hpa, please review this unsorted patch queue, as I wasn't sure about them they didn't land yet in todays pull request. thanks max git clone git://git.debian.org/users/maks/klibc.git test Thomas B?chler (1): klcc: compile shared by default jeremy buisson (1): [klibc] sparc64: fix bad 32 bits socket syscalls maximilian attems (1): [klibc] add losetup utils the

dd if=/dev/null of=img5 bs=1 seek=2G dd if=/dev/null of=img6 bs=1 seek=2G mkfs.btrfs -d raid1 -m raid1 img5 img6 losetup /dev/loop4 img5 losetup /dev/loop5 img6 btrfs device scan mount -t btrfs /dev/loop4 dir umount dir losetup -d /dev/loop5 mount -t btrfs -o degraded /dev/loop4 dir umount dir losetup -d /dev/loop4 ioctl: LOOP_CLR_FD: Device or resource busy mkfs.ext3 /dev/loop4 mke2fs 1.39

linux/loop.h header is exported by linux, for userspace to consume. This would prevent issues with struct sizes incompatibilities. References: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1850184 Signed-off-by: Michael Hudson-Doyle <michael.hudson at ubuntu.com> Signed-off-by: Adam Conrad <adconrad at ubuntu.com> Signed-off-by: Dimitri John Ledkov <xnox at ubuntu.com>

Commit-ID: 547b7cf241d4bcf518759d06cff694b9738c57b0 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=547b7cf241d4bcf518759d06cff694b9738c57b0 Author: Dimitri John Ledkov <xnox at ubuntu.com> AuthorDate: Thu, 31 Oct 2019 15:59:02 -0700 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Tue, 5 Nov 2019 00:42:26 +0000 [klibc] loop: switch to

I have problem with smbmount and losetup working together. The data seems to be corrupted. Description: I have an NT4 server with a share. On my linux box i use smbmount to mount the share. I have created a big file on the share and use losetup to configure a loop-back device on which i try to create/use a filesystem. It seems to work at first with ext2fs, but after copying some files to the

I have released version 2.0.8. This is available in the git repository at: https://git.kernel.org/pub/scm/libs/klibc/klibc.git and as a tarball at: https://mirrors.kernel.org/pub/linux/libs/klibc/2.0/ New features: - Support for building with clang and lld, at least on x86 - Defined sysconf(), initially supporting only _SC_PAGE_SIZE - Defined clearerr() as extern - Defined stdio

Hey I had the same problem some time ago. But here is a solution how to do that, but it''s a bit tricky! REQUIREMENT: THE SYSTEM PARTITION ON THE IMAGE MUST BE THE FIRST PARTITION, AFTER THAT THERE MUST BE ONLY SWAP PARTITIONS!!!! This setup would work, there should be no risk at all: Partition 1 on the image: / Partition 2 on the image: swap space This setup WONT''T WORK, YOU

Hi, This left me puzzled for a while: 22:29 borg:/ # losetup /dev/loop1 /.B.disk 22:29 borg:/ # mount /dev/loop1 /B mount: /dev/loop1: can''t read superblock 22:29 borg:/ # blkid /dev/loop1 /dev/loop1: UUID="e19fe89b-cde3-4ccc-bc70-b759a57bd1c9" UUID_SUB="f29c6218-d040-4546-a227-4dd2d2142817" TYPE="btrfs" 22:29 borg:/ # losetup -d /dev/loop1 22:29 borg:/ #

Hi all, This small patch enables you to loopback disk image files on readonly nfs filesystem on some system. When we losetup a file on readonly nfs filesystem, it fails with: # losetup /dev/loop7 /data/vm/xen_el5_i386_para/system.raw /data/vm/xen_el5_i386_para/system.raw: Permission denied New version of losetup has add a "-r" option for readonly loop, which Linux kernel has

# uname -a Linux dhcppc1 3.0.1-xxxx-std-ipv6-64 #1 SMP Sun Aug 14 17:06:21 CEST 2011 x86_64 x86_64 x86_64 GNU/Linux mkdir test5 cd test5 dd if=/dev/null of=img5 bs=1 seek=2G dd if=/dev/null of=img6 bs=1 seek=2G losetup /dev/loop2 img5 losetup /dev/loop3 img6 mkfs.btrfs -d raid1 -m raid1 /dev/loop2 /dev/loop3 btrfs device scan btrfs filesystem show Label: none uuid:

Hi, I have a legacy AES excrypted file system with a 256 key size. RHEL kernel is cryptoloop enabled but the losetup package is not. It needs additional patch. Does anybody have a patched losetup rpm I could use? Thank you! A. Georgiev

xend will not start a domain if one of the block devices is currently mounted elsewhere, but it will not detect if the device is currently attached to a loopback device. I wouldn''t have thought this a problem, provided that the loop device itself wasn''t in use, but it causes all sorts of strange things to happen. My loop device was mounted with the following command

hello hpa, stuff keeps piling up, but shaping up too. :) Louis Rilling debugged the ipconfig failure that I was wondering about lately and fixed it. so his fixes got added to previous pull request v2: please pull git pull git://git.debian.org/users/maks/klibc.git maks for the changes: Louis Rilling (2): [klibc] ipconfig: Fix missing dhcp_end field [klibc] ipconfig: Fix null ciaddr

Hey, guys. I have a problem when installing syslinux 4.06, and I'd be grateful if someone could tell me how to solve the problem. My task - to install the bootloader on the virtual machine image. The image contains the MBR and the only partition with the file system ext4. The file system contains all the files for the guest OS. To install bootloader into the image of the guest OS, I use the