similar to: [PATCH] Fix for udev >= 176

https://bugzilla.redhat.com/show_bug.cgi?id=1165785 Since the --boot option is relatively new (added 2013-12), I suspect this will break older versions of systemd. However it should be fine for all currently supported versions of Fedora. Rich.

Tools could require the use of pseudo-terminals, so make sure we have /dev/pts available in the appliance. The "command" API already bind-mounts it when running commands, so this is the only bit needed. --- appliance/init | 2 ++ 1 file changed, 2 insertions(+) diff --git a/appliance/init b/appliance/init index e678e42..8be27a2 100755 --- a/appliance/init +++ b/appliance/init @@ -72,6

I spent the last couple of days rethinking how we go about building the appliance, and the difficulties we have porting that to other Linux distros. I've come up with a much better way that works better and faster on (so far) Fedora and Debian (probably on Ubuntu too, not tried it), and should be much simpler to port to other distros. The current way is to do: +------------------+

From: "Richard W.M. Jones" <rjones at redhat.com> In Linux, close (fd) closes the file descriptor even if it returns an error. --- daemon/file.c | 2 -- 1 files changed, 0 insertions(+), 2 deletions(-) diff --git a/daemon/file.c b/daemon/file.c index e0f8794..91746e0 100644 --- a/daemon/file.c +++ b/daemon/file.c @@ -483,7 +483,6 @@ pread_fd (int fd, int count, int64_t

Hello all.. I'm trying to run CentOS 7 in a LXC container and need to disable udev so that we can manage the devices ourselves. I believe that I've disabled all of the systemd related udev services, but udev is still taking over and mounting /dev. What is the proper way to disable this? Thanks...Paul... -- --- Paul B Schroeder <paul.schroeder "at" nimbix "dot"

We've recently discovered that libguestfs can't handle guests which use md. There are (at least) 2 reasons for this: Firstly, the appliance doesn't include mdadm. Without this, md devices aren't detected during the boot process. Simply adding mdadm to the appliance package list fixes this. Secondly, md devices referenced in fstab as, e.g. /dev/md0, aren't handled

Building is broken in Rawhide. I have fixed everything but we're waiting for one kernel change to go upstream. The issues were: * https://bugzilla.redhat.com/show_bug.cgi?id=710882 parted failed to parse the Linux "3.0" string Fixed upstream, and I have added the patch to the Rawhide parted package. * https://bugzilla.redhat.com/show_bug.cgi?id=710921 ftrace doesn't

This is a possibly better work-around for bug 769304, the bug where blkid runs from udev whenever a device closes, causing the subsequent operation to fail. For background to this change, see: https://rwmj.wordpress.com/2012/01/19/udev-unexpectedness/#content So far we have noticed this problem in two places (although I'm fairly certain it affects many more): - in virt-resize, after

Hi, I have a KVM host running ubuntu 18.04 with libguestfs-tools version 1.36.13-1ubuntu3.3 installed from the Ubuntu's repo and when I try to use virt-cat for example on a VM it fails with: libguestfs: error: appliance closed the connection unexpectedly. > libguestfs: error: guestfs_launch failed. After doing "export LIBGUESTFS_DEBUG=1 LIBGUESTFS_TRACE=1" and running the

v1 was here: https://www.redhat.com/archives/libguestfs/2016-March/thread.html#00157 Not running the 'hwclock' command reduces boot times considerably. However I'm not sure if it is safe. See the question I posted on qemu-devel: http://thread.gmane.org/gmane.comp.emulators.qemu/402194 At the moment, about 50% of the time is consumed by SeaBIOS. Of this, about ⅓rd is SGABIOS

Hi all, below a configuration for udev/initramfs which I propose to scan the block devices looking for a multi-volume btrfs filesystem. Btrfs has the capability to span a file-system on multiple device. In order to do that, the involved devices have to be "registered" in the kernel. In order to do that there are two options: # btrfs device scan <device> (or the old

Hi, I have some issues with libguestfs. I download the libguestfs-0.18.3 source code and read the README file. it requested qemu >= 0.13, my qemu version is qemu-1.0.1 requested kernel version >= 2.6.34, my kernel version is 3.1.4 the most of requirement for compiling I reached. but I completed compiltion and executed command. the guestfish hang there. the following was my operating steps:

Hello, I've found a problem running libguestfs on my system. The system has /var mounted with a symbolic link to /mnt/bigdata/var root@red1:/var/log/nova# ls -ld /mnt/bigdata/var drwxrwxr-x 15 root users 4096 jul 7 17:55 /mnt/bigdata/var root@red1:/var/log/nova# ls -ld /var lrwxrwxrwx 1 root root 16 oct 30 2012 /var -> /mnt/bigdata/var Any help here? this is test tool output:

v4: - Lots more analysis of the /init script and other parts. - Display a list of the longest to shortest activities. - Rebase on top of current head. Rich.

Provide /var/lock as symlink to /run/lock, as it might be used by applications. --- appliance/init | 1 + 1 file changed, 1 insertion(+) diff --git a/appliance/init b/appliance/init index b25ea26..aac3f5a 100755 --- a/appliance/init +++ b/appliance/init @@ -32,6 +32,7 @@ mount -t sysfs /sys /sys mkdir -p /run mount -t tmpfs -o "nosuid,size=20%,mode=0755" tmpfs /run mkdir -p

Previous attempt: https://www.redhat.com/archives/libguestfs/2015-April/msg00013.html supermin needs to download packages (eg. RPMs) when preparing the appliance. After a lot of work, 'dnf download' can now be used as a replacement for the (deprecated) 'yumdownloader' program. This only affects the 'supermin --prepare' phase, which means it only affects people building

Hello all, I am having an issue with guestmount in respect to live instances and I was hoping someone might have an idea where I've gone wrong. The following output is from my shell session, if there's any more information needed please let me know and I'll happily provide it. [root at longitude ~]# virt-filesystems -d F16-rawhide/dev/sda2 /dev/sda3 [root at longitude ~]#

2017-07-29 18:00 GMT+08:00 Richard W.M. Jones <rjones@redhat.com>: > > > I download the newset package and extract in my > > path(/share/CACHEDEV1_DATA/appliance/) and set env > > It doesn't work. > > and I run the libugestfs-test-tool: > > Please don't provide partial information. Include the command you > type and *all* the output, without

On Mon, Feb 15, 2016 at 10:40:11AM +0100, Martin Kletzander wrote: > On Mon, Feb 15, 2016 at 03:05:00AM -0500, Han Han wrote: > >I compile the latest libvirt from fedora rawhide, but failed. > >The version of my software: > >wireshark-devel-2.0.1-2.fc24.x86_64 > >glib2-2.47.5-2.fc24.x86_64 > >gcc-5.1.1-4.fc23.x86_64 > >binutils-2.26-10.fc24.x86_64 > >

On Mon, May 25, 2015 at 10:22:35PM +0200, Kashyap Chamarthy wrote: > I just built `supermin` from source on my Fedora 22 machine, and somehow > it can't seem to detect RPM (but `supermin` from Rawhide detects it). > Exact error: > > supermin: could not detect package manager used by this system or > distro. > > which is coming from: