similar to: Bug#658606: Further information on this bug

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-4 After an upgrade to squeeze I've installed Xen 4.0, but when trying to boot the Xen kernel the boot freezes at the message: Waiting for /dev to be fully populated... Nothing further usually [*] appears after this message, and after a short time the screen becomes blank (and power saves, as if there is no signal) and there appears to be

On Thursday, 13 April 2017 16:55:26 CEST Pavel Butsykin wrote: > Add udev_settle_file() to run 'udevadm settle' with --exit-if-exists option. It > will slightly reduce the waiting-time for pending events if we need to wait > for events related to a particular device/file. > > Signed-off-by: Pavel Butsykin <pbutsykin@virtuozzo.com> > --- > daemon/daemon.h | 2

Hi all, Sorry for bothering you in this dev mailing list, I'm using libguestfs to customize some vm using as bases the ubuntu cloud images. But I noticed that it takes a lot and then fails when trying to install a packet. Same behaviour on Ubuntu 18.04 and Centos 7.5 Ubuntu: virt-customize 1.36.13 libvirtd (libvirt) 4.0.0 Centos: virt-customize 1.36.10rhel=7,release=6.el7_5.2,libvirt

I'm getting a lot of this at boottime: udev still not settled. Waiting. udevadm settle - timeout of 0 seconds reached, the event queue contains: /sys/module/scsi_wait_scan (11707) udev still not settled. Waiting. udevadm settle - timeout of 0 seconds reached, the event queue contains: /sys/module/scsi_wait_scan (11709) udev still not settled. Waiting. udevadm settle - timeout of 0

My network installation via PXE breaks when graphical installation starts, here my program.log: Running... /bin/mount -n -t auto -o ro,loop=/dev/loop0 /tmp/install.img /mnt/runtime 07:51:29,617 INFO : Running... ['udevadm', 'trigger', '--action=add', '--subsystem-match=net'] 07:51:29,660 INFO : Running... ['udevadm', 'trigger',

udevadm is included in all reasonable recent distributions. This avoids 'command not found' errors in verbose mode. Signed-off-by: Olaf Hering <olaf at aepfle.de> diff --git a/daemon/guestfsd.c b/daemon/guestfsd.c index e6d5fde..0db56e4 100644 --- a/daemon/guestfsd.c +++ b/daemon/guestfsd.c @@ -54,7 +54,6 @@ #include "daemon.h" GUESTFSD_EXT_CMD(str_udevadm, udevadm);

Hey, When downloading a file whose path contains multi-byte utf-8, libguestfs sometimes crashes. This reproduces when using python, and not when using guestfish. Code to reproduce: for i in range(2000): g.download ('/xxx?', '/tmp/1') #0 raise (sig=<optimized out>) at ../sysdeps/unix/sysv/linux/raise.c:50 #1 0x00007ffff7fac140 in <signal handler called> () at

There is GUESTFSD_EXT_CMD defining a string for udevadm (so it is marked as "used tool" in the appliance), but it is not actually used when starting udevadm. There should be no behaviour change. --- daemon/guestfsd.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/daemon/guestfsd.c b/daemon/guestfsd.c index 7b33a3a..4502190 100644 --- a/daemon/guestfsd.c +++

On Wed, Apr 12, 2017 at 05:01:10PM +0300, Pavel Butsykin wrote: > Add udev_settle_file() to run 'udevadm settle' with --exit-if-exists option. It > will slightly reduce the waiting-time for pending events if we need to wait > for events related to a particular device/file. > > Signed-off-by: Pavel Butsykin <pbutsykin@virtuozzo.com> > --- > daemon/daemon.h |

On Tue, Feb 14, 2023 at 08:02:59PM +0200, Yonatan Shtarkman wrote: > The attached code snippet?reproduces the issue when running: > python3 libugestfs_segfault_repro.py > > With: > guestfs version: 1.48.6 > guestfs-python version: 1.48.6 Can confirm with {python3-,}libguestfs-1.51.1-1.fc39.x86_64 The stack trace is roughly the same as yours. Rich. > Stacktrace: > #0

On Sun, Feb 12, 2023 at 03:31:08PM +0200, Yonatan Shtarkman wrote: > Hey, > When downloading a file whose path contains multi-byte utf-8, libguestfs > sometimes crashes. > This reproduces when using python, and not when using guestfish. > > Code to reproduce: > for i in range(2000): > ? ? g.download ('/xxx?', '/tmp/1') 'i' is not used inside the

I've just installed CentOS 4.2 on a brand-new PC. It appears to be working fine except for one thing: When the system is first powered on, the boot sequence hangs after Starting udev: Initializing hardware ... storage network audio If I then hit the reset button, it reboots and successfully proceeds. Looking at rc.sysinit and the output of kmodule, it would appear that the problem is

Hi, I reported a bug to anaconda (rhbz 901905), but it might be btfs related. Anaconda does this: 18:49:10,317 INFO program: Running... mkfs.btrfs --data=single --label=fedora /dev/vdb1 /dev/vdc1 /dev/vdd1 /dev/vde1 18:49:10,742 INFO program: 18:49:10,746 INFO program: WARNING! - Btrfs Btrfs v0.19 IS EXPERIMENTAL 18:49:10,746 INFO program: WARNING! - see http://btrfs.wiki.kernel.org before

Hi all, I encountered the following error when I tried to run virt-sysprep on a qcow2 image. virt-sysprep: error: no operating systems were found in the guest image The version I used for libguest is as follows: [libguestfs-1.36.5] The same issue happened on other versions such as libguestfs-1.32.7. # ./run ./sysprep/virt-sysprep -v -x -a

Read the content of /proc/cmdline using bash features, and use its [[ ... ]] expression to find texts in a variable. This shaves off 5 grep invocations. --- appliance/init | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/appliance/init b/appliance/init index f6fe9b9..8d662fa 100755 --- a/appliance/init +++ b/appliance/init @@ -75,7 +75,9 @@ $UDEVD --daemon

Builds in Koji currently fail with: /sbin/udevsettle missing or unknown command which means that we don't wait long enough after partitions etc have been created. In Fedora >= 12, we shouldn't use /sbin/udevsettle. It's been deprecated in favour of 'udevadm settle'. The relevant code is:

Hi list, the problem that I'm having seems to be between libvirtd and udev I have two hosts with LVM. The root partition run over this LVM. After booting the machine, if I do "udevadm settle" it responds almost instantly but then if I launch libvirtd the "udevadm settle" command doesn't respond for about 2 to 3 minutes and the only way to solve this is to restart the

Windows server 2012 sets partition names with spaces. ><fs> part-get-name /dev/sda 3 libguestfs: trace: part_get_name "/dev/sda" 3 guestfsd: main_loop: new request, len 0x38 parted -s -m /dev/null Error: The device /dev/null is so small that it cannot possibly store a file system or partition table. Perhaps you selected the wrong device? Warning: Error fsyncing/closing

--- appliance/init | 30 +++++++++++++++--------------- 1 file changed, 15 insertions(+), 15 deletions(-) diff --git a/appliance/init b/appliance/init index f4f6333..5d43c71 100755 --- a/appliance/init +++ b/appliance/init @@ -75,21 +75,6 @@ $UDEVD --daemon #--debug udevadm trigger udevadm settle --timeout=600 -if grep -sq selinux=1 /proc/cmdline; then - mount -t selinuxfs none

On Mon, Sep 11, 2017 at 04:27:30PM +0000, Seth Tanner wrote: > Rich, > Here you go > I also noticed that if I use the direct backend rather than libvirt, the conversion gets farther, but still does not complete, when pulling directly from vSphere. please let me know if you would like the output of direct as well. > starting version 233 > + udevadm trigger > + udevadm settle