The pastebin output has LIBGUESTFS_TRACE and LIBGUESTFS_DEBUG enabled, or did you want libguestfs-test-tool with trace on? -- while (!asleep) {sheep++;} On Thursday, February 28, 2013 at 8:49 AM, Matthew Booth wrote:

Attaching the mystery-log so we have a permanent record of it. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones libguestfs lets you edit virtual machines. Supports shell scripting, bindings from many languages. http://libguestfs.org

Hi,Richard Recently I met this error when I execute virt-v2v on rhel7,but I can not reproduce on another machine with even the same packages. # LIBGUESTFS_ATTACH_METHOD=appliance virt-v2v -ic xen+ssh://10.66.72.23 -os default xen-pv-rhel4.9-i386 root(a)10.66.72.23&#39;s password: root(a)10.66.72.23&#39;s password: root(a)10.66.72.23&#39;s password: xen-pv-rhel4.9-i386.img: 100% [========================================================================]D 0h02m10s inspect_os: mount_ro: /dev/sda on / (options: 'ro'): mount: /dev/sda is already mounted or /sysroot busy at /usr/share/perl5/vendor_perl/Sys/VirtConvert/GuestfsHandle.pm line 197. at /usr/bin/virt-v2v line 691. Best regards, Tingting Zheng（郑婷婷） ----- Original Message ----- From: "Richard W.M. Jones" <rjones(a)redhat.com&gt; To: libguestfs(a)redhat.com Sent: Friday, March 1, 2013 1:48:08 AM Subject: Re: [Libguestfs] virt-v2v F18 guest on F18 failure I think I've *discounted* IDE as a potential problem: $ rm /tmp/test1.img $ truncate -s1G /tmp/test1.img $ guestfish <<EOF set-attach-method appliance add-drive-opts /tmp/test1.img iface:ide readonly:true run mount /dev/sda / EOF libguestfs: error: mount: /dev/sda on / (options: ''): mount: wrong fs type, bad option, bad superblock on /dev/sda, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so (the expected error) vs: $ guestfish <<EOF set-attach-method appliance add-drive-opts /tmp/test1.img iface:ide readonly:true run mkfs ext2 /dev/sda mount /dev/sda / EOF (no error) Also tried: - Adding name:vda - Running isoinfo-device before the mount. - Running vfs-type before the mount. I still couldn't reproduce this. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Fedora Windows cross-compiler. Compile Windows programs, test, and build Windows installers. Over 100 libraries supported. http://fedoraproject.org/wiki/MinGW _______________________________________________ Libguestfs mailing list Libguestfs(a)redhat.com https://www.redhat.com/mailman/listinfo/libguestfs

On Thu, Feb 28, 2013 at 08:15:08AM -0700, Ryan Barry wrote: util-linux prints this when the mount syscall returns -EBUSY. The man page for mount(2) gives these reasons: EBUSY source is already mounted. [probably not] Or, it cannot be remounted read-only, because it still holds files open for writing. [while we are mounting r/o, we're not *re*mounting, and in any case we shouldn't have any files open for write] Or, it cannot be mounted on target because target is still busy (it is the working directory of some thread, the mount point of another device, has open files, etc.). [Could some other process have /sysroot open? The only candidate is udev.] I also looked at the Linux kernel code to see if there are any other reasons why do_mount would return -EBUSY. The only obvious ones are: - remounting read-only with files open for write - mounting the same filesystem a second time on the same mountpoint - mountpoint has open files, current working directories, chroots or sub-mounts None of these seem as if they are likely reasons. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming blog: http://rwmj.wordpress.com Fedora now supports 80 OCaml packages (the OPEN alternative to F#)