Re: [Libguestfs] [ovirt-users] OVA import of FC21 VM hangs during virt-v2v conversion?
On 7 Nov 2016, at 22:16, Derek Atkins <derek@ihtfp.com> wrote:
Hi,
My last VM imported in 2 minutes. This one has been sitting for three hours. I think this is a bug.
well, some time it does take a long time. Are you sure it was hung? No I/O going on? adding libguestfs list Thanks, michal
Just in case it helps, here's a larger piece of the virt-v2v log (see the end)
-derek
On Mon, November 7, 2016 12:54 pm, Derek Atkins wrote:
Hi,
I've successfully imported several VMs already, so I thought I had the process down. Each import completed relatively quickly. So that's why this one was such a surprise.
I've got a Fedora 21 VM packaged into an OVA. I copy it to my ovirt host and then [Virtual Machines] -> Import -> [OVA] and select the ova file. Follow the process, assign the correct storage location, and let it go. Usually it takes only a few minutes, but it's been sitting in the conversion process for over 20 minutes already (multiple attempts end in the same place). It's only a 4GB disk; the other imports were all around the same size and took significantly longer.
I tried running virt-v2v by hand:
LIBGUESTFS_BACKEND=direct virt-v2v -v -x -i ova fedora21.ova -of raw -o null
and it hung here:
guestfsd: main_loop: new request, len 0x28 guestfsd: main_loop: proc 26 (aug_close) took 0.03 seconds libguestfs: trace: v2v: aug_close = 0 libguestfs: trace: v2v: selinux_relabel "/etc/selinux/targeted/contexts/files/file_contexts" "/" "force:true" guestfsd: main_loop: new request, len 0x6c commandrvf: stdout=n stderr=y flags=0x0 commandrvf: setfiles -F -e /sysroot/dev -e /sysroot/proc -e /sysroot/selinux -e /sysroot/sys -r /sysroot -q /sysroot/etc/selinux/targeted/contexts/files/file_contexts /sysroot/ Can't stat exclude path "/sysroot/selinux", No such file or directory - ignoring. ^C
Any ideas why this VM is different from all the other VMs?
-derek
[snip] installed kernel packages in this guest: (kernel-core, 3.17.8-300.fc21, x86_64, /boot/vmlinuz-3.17.8-300.fc21.x86_64, /boot/initramfs-3.17.8-300.fc21.x86_64.img, virtio=true, xen=false, debug=false) (kernel-core, 3.17.4-301.fc21, x86_64, /boot/vmlinuz-3.17.4-301.fc21.x86_64, /boot/initramfs-3.17.4-301.fc21.x86_64.img, virtio=true, xen=false, debug=false) libguestfs: trace: v2v: glob_expand "/vmlinuz-*" guestfsd: main_loop: new request, len 0x3c guestfsd: main_loop: proc 113 (glob_expand) took 0.00 seconds libguestfs: trace: v2v: glob_expand = [] libguestfs: trace: v2v: glob_expand "/boot/vmlinuz-*" guestfsd: main_loop: new request, len 0x40 guestfsd: main_loop: proc 113 (glob_expand) took 0.00 seconds libguestfs: trace: v2v: glob_expand = ["/boot/vmlinuz-0-rescue-aebaf0a54c334c40a3f2a001266b032e", "/boot/vmlinuz-3.17.4-301.fc21.x86_64", "/boot/vmlinuz-3.17.8-300.fc21.x86_64"] libguestfs: trace: v2v: glob_expand "/boot/kernel-*" guestfsd: main_loop: new request, len 0x40 guestfsd: main_loop: proc 113 (glob_expand) took 0.00 seconds libguestfs: trace: v2v: glob_expand = [] libguestfs: trace: v2v: exists "/sbin/grubby" guestfsd: main_loop: new request, len 0x38 libguestfs: trace: v2v: exists = 1 libguestfs: trace: v2v: command "grubby --default-kernel" guestfsd: main_loop: proc 36 (exists) took 0.00 seconds guestfsd: main_loop: new request, len 0x4c commandrvf: stdout=n stderr=n flags=0x0 commandrvf: mount --bind /dev /sysroot/dev commandrvf: stdout=n stderr=n flags=0x0 commandrvf: mount --bind /dev/pts /sysroot/dev/pts mount: mount point /sysroot/dev/pts does not exist commandrvf: stdout=n stderr=n flags=0x0 commandrvf: mount --bind /proc /sysroot/proc commandrvf: stdout=n stderr=n flags=0x0 commandrvf: mount --bind /sys/fs/selinux /sysroot/selinux mount: mount point /sysroot/selinux does not exist commandrvf: stdout=n stderr=n flags=0x0 commandrvf: mount --bind /sys /sysroot/sys commandrvf: stdout=n stderr=n flags=0x0 commandrvf: mount --bind /sys/fs/selinux /sysroot/sys/fs/selinux mount: mount point /sysroot/sys/fs/selinux does not exist renaming /sysroot/etc/resolv.conf to /sysroot/etc/bojotzks commandrvf: stdout=n stderr=n flags=0x0 commandrvf: cp /etc/resolv.conf /sysroot/etc/resolv.conf commandrvf: stdout=y stderr=y flags=0x40000 commandrvf: grubby --default-kernel commandrvf: stdout=n stderr=n flags=0x0 commandrvf: umount /sysroot/sys commandrvf: stdout=n stderr=n flags=0x0 commandrvf: umount /sysroot/proc commandrvf: stdout=n stderr=n flags=0x0 commandrvf: umount /sysroot/dev renaming /sysroot/etc/bojotzks to /sysroot/etc/resolv.conf guestfsd: main_loop: proc 50 (command) took 0.13 seconds libguestfs: trace: v2v: command = "/boot/vmlinuz-3.17.8-300.fc21.x86_64\n" libguestfs: trace: v2v: statns "/boot/vmlinuz-3.17.8-300.fc21.x86_64" guestfsd: main_loop: new request, len 0x50 guestfsd: main_loop: proc 421 (statns) took 0.00 seconds libguestfs: trace: v2v: statns = <struct guestfs_statns = st_dev: 2049, st_ino: 340, st_mode: 33261, st_nlink: 1, st_uid: 0, st_gid: 0, st_rdev: 0, st_size: 5757864, st_blksize: 4096, st_blocks: 11248, st_atime_sec: 1420760440, st_atime_nsec: 0, st_mtime_sec: 1420760440, st_mtime_nsec: 0, st_ctime_sec: 1421863850, st_ctime_nsec: 600025468, st_spare1: 0, st_spare2: 0, st_spare3: 0, st_spare4: 0, st_spare5: 0, st_spare6: 0, > libguestfs: trace: v2v: statns "/boot/vmlinuz-0-rescue-aebaf0a54c334c40a3f2a001266b032e" guestfsd: main_loop: new request, len 0x64 guestfsd: main_loop: proc 421 (statns) took 0.00 seconds libguestfs: trace: v2v: statns = <struct guestfs_statns = st_dev: 2049, st_ino: 23, st_mode: 33261, st_nlink: 1, st_uid: 0, st_gid: 0, st_rdev: 0, st_size: 5751144, st_blksize: 4096, st_blocks: 11240, st_atime_sec: 1421862777, st_atime_nsec: 612123495, st_mtime_sec: 1421862777, st_mtime_nsec: 801108478, st_ctime_sec: 1421862777, st_ctime_nsec: 801108478, st_spare1: 0, st_spare2: 0, st_spare3: 0, st_spare4: 0, st_spare5: 0, st_spare6: 0, > libguestfs: trace: v2v: statns "/boot/vmlinuz-3.17.4-301.fc21.x86_64" guestfsd: main_loop: new request, len 0x50 guestfsd: main_loop: proc 421 (statns) took 0.00 seconds libguestfs: trace: v2v: statns = <struct guestfs_statns = st_dev: 2049, st_ino: 20, st_mode: 33261, st_nlink: 1, st_uid: 0, st_gid: 0, st_rdev: 0, st_size: 5751144, st_blksize: 4096, st_blocks: 11240, st_atime_sec: 1421862777, st_atime_nsec: 619122938, st_mtime_sec: 1417115668, st_mtime_nsec: 0, st_ctime_sec: 1421861378, st_ctime_nsec: 221208355, st_spare1: 0, st_spare2: 0, st_spare3: 0, st_spare4: 0, st_spare5: 0, st_spare6: 0, > libguestfs: trace: v2v: statns "/boot/vmlinuz-3.17.8-300.fc21.x86_64" guestfsd: main_loop: new request, len 0x50 guestfsd: main_loop: proc 421 (statns) took 0.00 seconds libguestfs: trace: v2v: statns = <struct guestfs_statns = st_dev: 2049, st_ino: 340, st_mode: 33261, st_nlink: 1, st_uid: 0, st_gid: 0, st_rdev: 0, st_size: 5757864, st_blksize: 4096, st_blocks: 11248, st_atime_sec: 1420760440, st_atime_nsec: 0, st_mtime_sec: 1420760440, st_mtime_nsec: 0, st_ctime_sec: 1421863850, st_ctime_nsec: 600025468, st_spare1: 0, st_spare2: 0, st_spare3: 0, st_spare4: 0, st_spare5: 0, st_spare6: 0, > grub kernels in this guest (first in list is default): (kernel-core, 3.17.8-300.fc21, x86_64, /boot/vmlinuz-3.17.8-300.fc21.x86_64, /boot/initramfs-3.17.8-300.fc21.x86_64.img, virtio=true, xen=false, debug=false) (kernel-core, 3.17.4-301.fc21, x86_64, /boot/vmlinuz-3.17.4-301.fc21.x86_64, /boot/initramfs-3.17.4-301.fc21.x86_64.img, virtio=true, xen=false, debug=false) (kernel-core, 3.17.8-300.fc21, x86_64, /boot/vmlinuz-3.17.8-300.fc21.x86_64, /boot/initramfs-3.17.8-300.fc21.x86_64.img, virtio=true, xen=false, debug=false) libguestfs: trace: v2v: is_file "/var/lib/VBoxGuestAdditions/config" "followsymlinks:true" guestfsd: main_loop: new request, len 0x54 guestfsd: main_loop: proc 37 (is_file) took 0.00 seconds libguestfs: trace: v2v: is_file = 0 libguestfs: trace: v2v: is_file "/etc/init.d/kudzu" "followsymlinks:true" guestfsd: main_loop: new request, len 0x44 guestfsd: main_loop: proc 37 (is_file) took 0.00 seconds libguestfs: trace: v2v: is_file = 0 libguestfs: trace: v2v: is_file "/etc/sysconfig/kernel" "followsymlinks:true" guestfsd: main_loop: new request, len 0x48 guestfsd: main_loop: proc 37 (is_file) took 0.00 seconds libguestfs: trace: v2v: is_file = 1 libguestfs: trace: v2v: aug_match "/files/etc/sysconfig/kernel/DEFAULTKERNEL/value" guestfsd: main_loop: new request, len 0x5c guestfsd: main_loop: proc 24 (aug_match) took 0.00 seconds libguestfs: trace: v2v: aug_match = ["/files/etc/sysconfig/kernel/DEFAULTKERNEL/value"] libguestfs: trace: v2v: aug_set "/files/etc/sysconfig/kernel/DEFAULTKERNEL/value" "kernel-core" guestfsd: main_loop: new request, len 0x6c guestfsd: main_loop: proc 20 (aug_set) took 0.00 seconds libguestfs: trace: v2v: aug_set = 0 libguestfs: trace: v2v: aug_save guestfsd: main_loop: new request, len 0x28 guestfsd: main_loop: proc 25 (aug_save) took 0.00 seconds libguestfs: trace: v2v: aug_save = 0 libguestfs: trace: v2v: aug_match "/files/etc/inittab/*/process" guestfsd: main_loop: new request, len 0x48 guestfsd: main_loop: proc 24 (aug_match) took 0.00 seconds libguestfs: trace: v2v: aug_match = [] libguestfs: trace: v2v: aug_match "/files/etc/securetty/*" guestfsd: main_loop: new request, len 0x44 guestfsd: main_loop: proc 24 (aug_match) took 0.00 seconds libguestfs: trace: v2v: aug_match = [] libguestfs: trace: v2v: aug_save guestfsd: main_loop: new request, len 0x28 guestfsd: main_loop: proc 25 (aug_save) took 0.00 seconds libguestfs: trace: v2v: aug_save = 0 libguestfs: trace: v2v: aug_match "/files/etc/sysconfig/grub/GRUB_CMDLINE_LINUX" guestfsd: main_loop: new request, len 0x58 guestfsd: main_loop: proc 24 (aug_match) took 0.00 seconds libguestfs: trace: v2v: aug_match = [] libguestfs: trace: v2v: aug_match "/files/etc/default/grub/GRUB_CMDLINE_LINUX" guestfsd: main_loop: new request, len 0x58 guestfsd: main_loop: proc 24 (aug_match) took 0.00 seconds libguestfs: trace: v2v: aug_match = ["/files/etc/default/grub/GRUB_CMDLINE_LINUX"] libguestfs: trace: v2v: aug_match "/files/etc/default/grub/GRUB_CMDLINE_LINUX_DEFAULT" guestfsd: main_loop: new request, len 0x60 guestfsd: main_loop: proc 24 (aug_match) took 0.00 seconds libguestfs: trace: v2v: aug_match = [] libguestfs: trace: v2v: aug_get "/files/etc/default/grub/GRUB_CMDLINE_LINUX" guestfsd: main_loop: new request, len 0x58 guestfsd: main_loop: proc 19 (aug_get) took 0.00 seconds libguestfs: trace: v2v: aug_get = ""rhgb quiet"" libguestfs: trace: v2v: is_file "/etc/X11/xorg.conf" "followsymlinks:true" guestfsd: main_loop: new request, len 0x44 guestfsd: main_loop: proc 37 (is_file) took 0.00 seconds libguestfs: trace: v2v: is_file = 0 libguestfs: trace: v2v: is_file "/etc/X11/XF86Config" "followsymlinks:true" guestfsd: main_loop: new request, len 0x44 guestfsd: main_loop: proc 37 (is_file) took 0.00 seconds libguestfs: trace: v2v: is_file = 0 libguestfs: trace: v2v: aug_match "/files/etc/X11/xorg.conf/Device/Driver" guestfsd: main_loop: new request, len 0x54 guestfsd: main_loop: proc 24 (aug_match) took 0.00 seconds libguestfs: trace: v2v: aug_match = [] libguestfs: trace: v2v: aug_match "/files/etc/X11/xorg.conf/Device/VendorName" guestfsd: main_loop: new request, len 0x58 guestfsd: main_loop: proc 24 (aug_match) took 0.00 seconds libguestfs: trace: v2v: aug_match = [] libguestfs: trace: v2v: aug_match "/files/etc/X11/xorg.conf/Device/BoardName" guestfsd: main_loop: new request, len 0x58 guestfsd: main_loop: proc 24 (aug_match) took 0.00 seconds libguestfs: trace: v2v: aug_match = [] libguestfs: trace: v2v: aug_save guestfsd: main_loop: new request, len 0x28 guestfsd: main_loop: proc 25 (aug_save) took 0.00 seconds libguestfs: trace: v2v: aug_save = 0 block device map: sda -> vda xvda -> vda libguestfs: trace: v2v: aug_match "/files/etc/fstab/*/spec" guestfsd: main_loop: new request, len 0x44 guestfsd: main_loop: proc 24 (aug_match) took 0.00 seconds libguestfs: trace: v2v: aug_match = ["/files/etc/fstab/1/spec", "/files/etc/fstab/2/spec", "/files/etc/fstab/3/spec"] libguestfs: trace: v2v: aug_match "/files/boot/grub2/grub.cfg/*/kernel/root" guestfsd: main_loop: new request, len 0x54 guestfsd: main_loop: proc 24 (aug_match) took 0.00 seconds libguestfs: trace: v2v: aug_match = [] libguestfs: trace: v2v: aug_match "/files/boot/grub2/grub.cfg/*/kernel/resume" guestfsd: main_loop: new request, len 0x58 guestfsd: main_loop: proc 24 (aug_match) took 0.00 seconds libguestfs: trace: v2v: aug_match = [] libguestfs: trace: v2v: aug_match "/files/boot/grub/device.map/*[label() != "#comment"]" guestfsd: main_loop: new request, len 0x60 guestfsd: main_loop: proc 24 (aug_match) took 0.00 seconds libguestfs: trace: v2v: aug_match = [] libguestfs: trace: v2v: aug_match "/files/etc/sysconfig/grub/boot" guestfsd: main_loop: new request, len 0x4c guestfsd: main_loop: proc 24 (aug_match) took 0.00 seconds libguestfs: trace: v2v: aug_match = [] libguestfs: trace: v2v: aug_match "/files/etc/sysconfig/grub/GRUB_CMDLINE_LINUX" guestfsd: main_loop: new request, len 0x58 guestfsd: main_loop: proc 24 (aug_match) took 0.00 seconds libguestfs: trace: v2v: aug_match = [] libguestfs: trace: v2v: aug_match "/files/etc/default/grub/GRUB_CMDLINE_LINUX" guestfsd: main_loop: new request, len 0x58 guestfsd: main_loop: proc 24 (aug_match) took 0.00 seconds libguestfs: trace: v2v: aug_match = ["/files/etc/default/grub/GRUB_CMDLINE_LINUX"] libguestfs: trace: v2v: aug_match "/files/etc/default/grub/GRUB_CMDLINE_LINUX_DEFAULT" guestfsd: main_loop: new request, len 0x60 guestfsd: main_loop: proc 24 (aug_match) took 0.00 seconds libguestfs: trace: v2v: aug_match = [] libguestfs: trace: v2v: aug_match "/files/boot/grub2/device.map/*[label() != "#comment"]" guestfsd: main_loop: new request, len 0x64 guestfsd: main_loop: proc 24 (aug_match) took 0.00 seconds libguestfs: trace: v2v: aug_match = ["/files/boot/grub2/device.map/hd0", "/files/boot/grub2/device.map/hd1"] libguestfs: trace: v2v: aug_get "/files/etc/fstab/1/spec" guestfsd: main_loop: new request, len 0x44 guestfsd: main_loop: proc 19 (aug_get) took 0.00 seconds libguestfs: trace: v2v: aug_get = "UUID=88eeab88-7e17-4df7-b36e-876b6fc9c14f" libguestfs: trace: v2v: aug_get "/files/etc/fstab/2/spec" guestfsd: main_loop: new request, len 0x44 guestfsd: main_loop: proc 19 (aug_get) took 0.00 seconds libguestfs: trace: v2v: aug_get = "UUID=089a81b0-a74b-42dd-b145-ac54fa6e49a4" libguestfs: trace: v2v: aug_get "/files/etc/fstab/3/spec" guestfsd: main_loop: new request, len 0x44 guestfsd: main_loop: proc 19 (aug_get) took 0.00 seconds libguestfs: trace: v2v: aug_get = "UUID=bb65f0f7-7992-4a42-9b47-b952fa815207" libguestfs: trace: v2v: aug_get "/files/etc/default/grub/GRUB_CMDLINE_LINUX" guestfsd: main_loop: new request, len 0x58 guestfsd: main_loop: proc 19 (aug_get) took 0.00 seconds libguestfs: trace: v2v: aug_get = ""rhgb quiet"" libguestfs: trace: v2v: aug_get "/files/boot/grub2/device.map/hd0" guestfsd: main_loop: new request, len 0x4c guestfsd: main_loop: proc 19 (aug_get) took 0.00 seconds libguestfs: trace: v2v: aug_get = "/dev/sda" libguestfs: trace: v2v: aug_set "/files/boot/grub2/device.map/hd0" "/dev/vda" guestfsd: main_loop: new request, len 0x58 guestfsd: main_loop: proc 20 (aug_set) took 0.00 seconds libguestfs: trace: v2v: aug_set = 0 libguestfs: trace: v2v: aug_get "/files/boot/grub2/device.map/hd1" guestfsd: main_loop: new request, len 0x4c guestfsd: main_loop: proc 19 (aug_get) took 0.00 seconds libguestfs: trace: v2v: aug_get = "/dev/sda" libguestfs: trace: v2v: aug_set "/files/boot/grub2/device.map/hd1" "/dev/vda" guestfsd: main_loop: new request, len 0x58 guestfsd: main_loop: proc 20 (aug_set) took 0.00 seconds libguestfs: trace: v2v: aug_set = 0 libguestfs: trace: v2v: aug_save guestfsd: main_loop: new request, len 0x28 libguestfs: trace: v2v: aug_save = 0 libguestfs: trace: v2v: command "grub2-mkconfig -o /boot/grub2/grub.cfg" guestfsd: main_loop: proc 25 (aug_save) took 0.00 seconds guestfsd: main_loop: new request, len 0x60 commandrvf: stdout=n stderr=n flags=0x0 commandrvf: mount --bind /dev /sysroot/dev commandrvf: stdout=n stderr=n flags=0x0 commandrvf: mount --bind /dev/pts /sysroot/dev/pts mount: mount point /sysroot/dev/pts does not exist commandrvf: stdout=n stderr=n flags=0x0 commandrvf: mount --bind /proc /sysroot/proc commandrvf: stdout=n stderr=n flags=0x0 commandrvf: mount --bind /sys/fs/selinux /sysroot/selinux mount: mount point /sysroot/selinux does not exist commandrvf: stdout=n stderr=n flags=0x0 commandrvf: mount --bind /sys /sysroot/sys commandrvf: stdout=n stderr=n flags=0x0 commandrvf: mount --bind /sys/fs/selinux /sysroot/sys/fs/selinux mount: mount point /sysroot/sys/fs/selinux does not exist renaming /sysroot/etc/resolv.conf to /sysroot/etc/6c3fqtab commandrvf: stdout=n stderr=n flags=0x0 commandrvf: cp /etc/resolv.conf /sysroot/etc/resolv.conf commandrvf: stdout=y stderr=y flags=0x40000 commandrvf: grub2-mkconfig -o /boot/grub2/grub.cfg Generating grub configuration file ... Found linux image: /boot/vmlinuz-3.17.8-300.fc21.x86_64 Found initrd image: /boot/initramfs-3.17.8-300.fc21.x86_64.img Found linux image: /boot/vmlinuz-3.17.4-301.fc21.x86_64 Found initrd image: /boot/initramfs-3.17.4-301.fc21.x86_64.img Found linux image: /boot/vmlinuz-0-rescue-aebaf0a54c334c40a3f2a001266b032e Found initrd image: /boot/initramfs-0-rescue-aebaf0a54c334c40a3f2a001266b032e.img ERROR: mkdir /var/lock/dmraid ERROR: mkdir /var/lock/dmraid ERROR: mkdir /var/lock/dmraid done commandrvf: stdout=n stderr=n flags=0x0 commandrvf: umount /sysroot/sys commandrvf: stdout=n stderr=n flags=0x0 commandrvf: umount /sysroot/proc commandrvf: stdout=n stderr=n flags=0x0 commandrvf: umount /sysroot/dev renaming /sysroot/etc/6c3fqtab to /sysroot/etc/resolv.conf guestfsd: main_loop: proc 50 (command) took 0.57 seconds libguestfs: trace: v2v: command = "" libguestfs: trace: v2v: aug_load guestfsd: main_loop: new request, len 0x28 guestfsd: main_loop: proc 27 (aug_load) took 0.01 seconds libguestfs: trace: v2v: aug_load = 0 libguestfs: trace: v2v: aug_match "/augeas/files//error" guestfsd: main_loop: new request, len 0x40 guestfsd: main_loop: proc 24 (aug_match) took 0.00 seconds libguestfs: trace: v2v: aug_match = [] libguestfs: trace: v2v: rm_f "/etc/blkid/blkid.tab" guestfsd: main_loop: new request, len 0x40 guestfsd: main_loop: proc 367 (rm_f) took 0.00 seconds libguestfs: trace: v2v: rm_f = 0 libguestfs: trace: v2v: rm_f "/etc/blkid.tab" guestfsd: main_loop: new request, len 0x3c guestfsd: main_loop: proc 367 (rm_f) took 0.00 seconds libguestfs: trace: v2v: rm_f = 0 libguestfs: trace: v2v: rm_f "/etc/lvm/cache/.cache" guestfsd: main_loop: new request, len 0x44 guestfsd: main_loop: proc 367 (rm_f) took 0.00 seconds libguestfs: trace: v2v: rm_f = 0 libguestfs: trace: v2v: aug_match "/files/etc/conf.modules/alias[. =~ regexp('eth[0-9]+')]" guestfsd: main_loop: new request, len 0x64 guestfsd: main_loop: proc 24 (aug_match) took 0.00 seconds libguestfs: trace: v2v: aug_match = [] libguestfs: trace: v2v: aug_match "/files/etc/modules.conf/alias[. =~ regexp('eth[0-9]+')]" guestfsd: main_loop: new request, len 0x64 guestfsd: main_loop: proc 24 (aug_match) took 0.00 seconds libguestfs: trace: v2v: aug_match = [] libguestfs: trace: v2v: aug_match "/files/etc/modprobe.conf/alias[. =~ regexp('eth[0-9]+')]" guestfsd: main_loop: new request, len 0x64 guestfsd: main_loop: proc 24 (aug_match) took 0.00 seconds libguestfs: trace: v2v: aug_match = [] libguestfs: trace: v2v: aug_match "/files/etc/modprobe.d/*/alias[. =~ regexp('eth[0-9]+')]" guestfsd: main_loop: new request, len 0x64 guestfsd: main_loop: proc 24 (aug_match) took 0.00 seconds libguestfs: trace: v2v: aug_match = [] libguestfs: trace: v2v: aug_match "/files/etc/conf.modules/alias[. =~ regexp('scsi_hostadapter.*')]" guestfsd: main_loop: new request, len 0x6c guestfsd: main_loop: proc 24 (aug_match) took 0.00 seconds libguestfs: trace: v2v: aug_match = [] libguestfs: trace: v2v: aug_match "/files/etc/modules.conf/alias[. =~ regexp('scsi_hostadapter.*')]" guestfsd: main_loop: new request, len 0x6c guestfsd: main_loop: proc 24 (aug_match) took 0.00 seconds libguestfs: trace: v2v: aug_match = [] libguestfs: trace: v2v: aug_match "/files/etc/modprobe.conf/alias[. =~ regexp('scsi_hostadapter.*')]" guestfsd: main_loop: new request, len 0x70 guestfsd: main_loop: proc 24 (aug_match) took 0.00 seconds libguestfs: trace: v2v: aug_match = [] libguestfs: trace: v2v: aug_match "/files/etc/modprobe.d/*/alias[. =~ regexp('scsi_hostadapter.*')]" guestfsd: main_loop: new request, len 0x6c guestfsd: main_loop: proc 24 (aug_match) took 0.00 seconds libguestfs: trace: v2v: aug_match = [] libguestfs: trace: v2v: is_dir "/etc/modprobe.d" "followsymlinks:true" guestfsd: main_loop: new request, len 0x40 guestfsd: main_loop: proc 38 (is_dir) took 0.00 seconds libguestfs: trace: v2v: is_dir = 1 libguestfs: trace: v2v: aug_set "/files/etc/modprobe.d/virt-v2v-added.conf/alias[last()+1]" "scsi_hostadapter" guestfsd: main_loop: new request, len 0x7c guestfsd: main_loop: proc 20 (aug_set) took 0.00 seconds libguestfs: trace: v2v: aug_set = 0 libguestfs: trace: v2v: aug_set "/files/etc/modprobe.d/virt-v2v-added.conf/alias[last()]/modulename" "virtio_blk" guestfsd: main_loop: new request, len 0x80 guestfsd: main_loop: proc 20 (aug_set) took 0.00 seconds libguestfs: trace: v2v: aug_set = 0 libguestfs: trace: v2v: aug_match "/files/etc/conf.modules/alias[modulename =~ regexp('xennet|xen-vnif|xenblk|xen-vbd')]" guestfsd: main_loop: new request, len 0x84 guestfsd: main_loop: proc 24 (aug_match) took 0.00 seconds libguestfs: trace: v2v: aug_match = [] libguestfs: trace: v2v: aug_match "/files/etc/modules.conf/alias[modulename =~ regexp('xennet|xen-vnif|xenblk|xen-vbd')]" guestfsd: main_loop: new request, len 0x84 guestfsd: main_loop: proc 24 (aug_match) took 0.00 seconds libguestfs: trace: v2v: aug_match = [] libguestfs: trace: v2v: aug_match "/files/etc/modprobe.conf/alias[modulename =~ regexp('xennet|xen-vnif|xenblk|xen-vbd')]" guestfsd: main_loop: new request, len 0x84 guestfsd: main_loop: proc 24 (aug_match) took 0.00 seconds libguestfs: trace: v2v: aug_match = [] libguestfs: trace: v2v: aug_match "/files/etc/modprobe.d/*/alias[modulename =~ regexp('xennet|xen-vnif|xenblk|xen-vbd')]" guestfsd: main_loop: new request, len 0x84 guestfsd: main_loop: proc 24 (aug_match) took 0.00 seconds libguestfs: trace: v2v: aug_match = [] libguestfs: trace: v2v: aug_save guestfsd: main_loop: new request, len 0x28 libguestfs: trace: v2v: aug_save = 0 libguestfs: trace: v2v: mv "/boot/initramfs-3.17.8-300.fc21.x86_64.img" "/boot/initramfs-3.17.8-300.fc21.x86_64.img.pre-v2v" guestfsd: main_loop: proc 25 (aug_save) took 0.00 seconds guestfsd: main_loop: new request, len 0x90 commandrvf: stdout=n stderr=y flags=0x0 commandrvf: mv /sysroot/boot/initramfs-3.17.8-300.fc21.x86_64.img /sysroot/boot/initramfs-3.17.8-300.fc21.x86_64.img.pre-v2v libguestfs: trace: v2v: mv = 0 libguestfs: trace: v2v: is_file "/sbin/dracut" "followsymlinks:true" guestfsd: main_loop: proc 89 (mv) took 0.00 seconds guestfsd: main_loop: new request, len 0x3c libguestfs: trace: v2v: is_file = 1 libguestfs: trace: v2v: command "/sbin/dracut --verbose --add-drivers virtio virtio_ring virtio_blk virtio_net virtio_pci /boot/initramfs-3.17.8-300.fc21.x86_64.img 3.17.8-300.fc21.x86_64" guestfsd: main_loop: proc 37 (is_file) took 0.00 seconds guestfsd: main_loop: new request, len 0xe4 commandrvf: stdout=n stderr=n flags=0x0 commandrvf: mount --bind /dev /sysroot/dev commandrvf: stdout=n stderr=n flags=0x0 commandrvf: mount --bind /dev/pts /sysroot/dev/pts mount: mount point /sysroot/dev/pts does not exist commandrvf: stdout=n stderr=n flags=0x0 commandrvf: mount --bind /proc /sysroot/proc commandrvf: stdout=n stderr=n flags=0x0 commandrvf: mount --bind /sys/fs/selinux /sysroot/selinux mount: mount point /sysroot/selinux does not exist commandrvf: stdout=n stderr=n flags=0x0 commandrvf: mount --bind /sys /sysroot/sys commandrvf: stdout=n stderr=n flags=0x0 commandrvf: mount --bind /sys/fs/selinux /sysroot/sys/fs/selinux mount: mount point /sysroot/sys/fs/selinux does not exist renaming /sysroot/etc/resolv.conf to /sysroot/etc/fvo9h3q7 commandrvf: stdout=n stderr=n flags=0x0 commandrvf: cp /etc/resolv.conf /sysroot/etc/resolv.conf commandrvf: stdout=y stderr=y flags=0x40000 commandrvf: /sbin/dracut --verbose --add-drivers "virtio virtio_ring virtio_blk virtio_net virtio_pci" /boot/initramfs-3.17.8-300.fc21.x86_64.img 3.17.8-300.fc21.x86_64 No '/dev/log' or 'logger' included for syslog logging [ 13.635451] dracut[966] No '/dev/log' or 'logger' included for syslog logging Executing: /sbin/dracut --verbose --add-drivers "virtio virtio_ring virtio_blk virtio_net virtio_pci" /boot/initramfs-3.17.8-300.fc21.x86_64.img 3.17.8-300.fc21.x86_64 [ 13.665763] dracut[966] Executing: /sbin/dracut --verbose --add-drivers "virtio virtio_ring virtio_blk virtio_net virtio_pci" /boot/initramfs-3.17.8-300.fc21.x86_64.img 3.17.8-300.fc21.x86_64 dracut module 'busybox' will not be installed, because command 'busybox' could not be found! [ 13.783635] dracut[966] dracut module 'busybox' will not be installed, because command 'busybox' could not be found! dracut module 'fcoe' will not be installed, because command 'dcbtool' could not be found! [ 13.876843] dracut[966] dracut module 'fcoe' will not be installed, because command 'dcbtool' could not be found! dracut module 'fcoe' will not be installed, because command 'fipvlan' could not be found! [ 13.879013] dracut[966] dracut module 'fcoe' will not be installed, because command 'fipvlan' could not be found! dracut module 'fcoe' will not be installed, because command 'lldpad' could not be found! [ 13.881179] dracut[966] dracut module 'fcoe' will not be installed, because command 'lldpad' could not be found! dracut module 'fcoe-uefi' will not be installed, because command 'dcbtool' could not be found! [ 13.885860] dracut[966] dracut module 'fcoe-uefi' will not be installed, because command 'dcbtool' could not be found! dracut module 'fcoe-uefi' will not be installed, because command 'fipvlan' could not be found! [ 13.888081] dracut[966] dracut module 'fcoe-uefi' will not be installed, because command 'fipvlan' could not be found! dracut module 'fcoe-uefi' will not be installed, because command 'lldpad' could not be found! [ 13.890369] dracut[966] dracut module 'fcoe-uefi' will not be installed, because command 'lldpad' could not be found! dracut module 'iscsi' will not be installed, because command 'iscsistart' could not be found! [ 13.896999] dracut[966] dracut module 'iscsi' will not be installed, because command 'iscsistart' could not be found! dracut module 'iscsi' will not be installed, because command 'iscsi-iname' could not be found! [ 13.899112] dracut[966] dracut module 'iscsi' will not be installed, because command 'iscsi-iname' could not be found! dracut module 'nbd' will not be installed, because command 'nbd-client' could not be found! [ 13.903211] dracut[966] dracut module 'nbd' will not be installed, because command 'nbd-client' could not be found! dracut module 'biosdevname' will not be installed, because command 'biosdevname' could not be found! [ 13.938682] dracut[966] dracut module 'biosdevname' will not be installed, because command 'biosdevname' could not be found! dracut module 'busybox' will not be installed, because command 'busybox' could not be found! [ 14.007359] dracut[966] dracut module 'busybox' will not be installed, because command 'busybox' could not be found! dracut module 'fcoe' will not be installed, because command 'dcbtool' could not be found! [ 14.055331] dracut[966] dracut module 'fcoe' will not be installed, because command 'dcbtool' could not be found! dracut module 'fcoe' will not be installed, because command 'fipvlan' could not be found! [ 14.057940] dracut[966] dracut module 'fcoe' will not be installed, because command 'fipvlan' could not be found! dracut module 'fcoe' will not be installed, because command 'lldpad' could not be found! [ 14.059984] dracut[966] dracut module 'fcoe' will not be installed, because command 'lldpad' could not be found! dracut module 'fcoe-uefi' will not be installed, because command 'dcbtool' could not be found! [ 14.063472] dracut[966] dracut module 'fcoe-uefi' will not be installed, because command 'dcbtool' could not be found! dracut module 'fcoe-uefi' will not be installed, because command 'fipvlan' could not be found! [ 14.065623] dracut[966] dracut module 'fcoe-uefi' will not be installed, because command 'fipvlan' could not be found! dracut module 'fcoe-uefi' will not be installed, because command 'lldpad' could not be found! [ 14.067865] dracut[966] dracut module 'fcoe-uefi' will not be installed, because command 'lldpad' could not be found! dracut module 'iscsi' will not be installed, because command 'iscsistart' could not be found! [ 14.072897] dracut[966] dracut module 'iscsi' will not be installed, because command 'iscsistart' could not be found! dracut module 'iscsi' will not be installed, because command 'iscsi-iname' could not be found! [ 14.075040] dracut[966] dracut module 'iscsi' will not be installed, because command 'iscsi-iname' could not be found! dracut module 'nbd' will not be installed, because command 'nbd-client' could not be found! [ 14.078622] dracut[966] dracut module 'nbd' will not be installed, because command 'nbd-client' could not be found! *** Including module: bash *** [ 14.142802] dracut[966] *** Including module: bash *** *** Including module: i18n *** [ 14.148588] dracut[966] *** Including module: i18n *** *** Including module: network *** [ 14.336325] dracut[966] *** Including module: network *** *** Including module: ifcfg *** [ 16.015612] dracut[966] *** Including module: ifcfg *** *** Including module: drm *** [ 16.021035] dracut[966] *** Including module: drm *** *** Including module: plymouth *** [ 17.051328] dracut[966] *** Including module: plymouth *** *** Including module: kernel-modules *** [ 17.274162] dracut[966] *** Including module: kernel-modules *** *** Including module: rootfs-block *** [ 24.046556] dracut[966] *** Including module: rootfs-block *** *** Including module: terminfo *** [ 24.055831] dracut[966] *** Including module: terminfo *** *** Including module: udev-rules *** [ 24.069906] dracut[966] *** Including module: udev-rules *** Skipping udev rule: 91-permissions.rules [ 24.238349] dracut[966] Skipping udev rule: 91-permissions.rules Skipping udev rule: 80-drivers-modprobe.rules [ 24.240008] dracut[966] Skipping udev rule: 80-drivers-modprobe.rules *** Including module: systemd *** [ 24.258293] dracut[966] *** Including module: systemd *** *** Including module: usrmount *** [ 24.446001] dracut[966] *** Including module: usrmount *** *** Including module: base *** [ 24.449400] dracut[966] *** Including module: base *** *** Including module: fs-lib *** [ 24.506200] dracut[966] *** Including module: fs-lib *** *** Including module: shutdown *** [ 24.519959] dracut[966] *** Including module: shutdown *** *** Including modules done *** [ 24.554250] dracut[966] *** Including modules done *** *** Installing kernel module dependencies and firmware *** [ 24.583486] dracut[966] *** Installing kernel module dependencies and firmware *** *** Installing kernel module dependencies and firmware done *** [ 24.900621] dracut[966] *** Installing kernel module dependencies and firmware done *** *** Resolving executable dependencies *** [ 24.917031] dracut[966] *** Resolving executable dependencies *** *** Resolving executable dependencies done*** [ 25.482622] dracut[966] *** Resolving executable dependencies done*** *** Hardlinking files *** [ 25.495828] dracut[966] *** Hardlinking files *** *** Hardlinking files done *** [ 25.505896] dracut[966] *** Hardlinking files done *** *** Stripping files *** [ 25.507966] dracut[966] *** Stripping files *** *** Stripping files done *** [ 25.607024] dracut[966] *** Stripping files done *** *** Generating early-microcode cpio image *** [ 25.609139] dracut[966] *** Generating early-microcode cpio image *** *** Constructing GenuineIntel.bin **** [ 25.616820] dracut[966] *** Constructing GenuineIntel.bin **** *** Store current command line parameters *** [ 25.630768] dracut[966] *** Store current command line parameters *** *** Creating image file *** [ 25.633892] dracut[966] *** Creating image file *** *** Creating image file done *** [ 33.376016] dracut[966] *** Creating image file done *** commandrvf: stdout=n stderr=n flags=0x0 commandrvf: umount /sysroot/sys commandrvf: stdout=n stderr=n flags=0x0 commandrvf: umount /sysroot/proc commandrvf: stdout=n stderr=n flags=0x0 commandrvf: umount /sysroot/dev renaming /sysroot/etc/fvo9h3q7 to /sysroot/etc/resolv.conf guestfsd: main_loop: proc 50 (command) took 22.81 seconds libguestfs: trace: v2v: command = "" libguestfs: trace: v2v: is_file "/usr/sbin/load_policy" "followsymlinks:true" guestfsd: main_loop: new request, len 0x48 guestfsd: main_loop: proc 37 (is_file) took 0.00 seconds libguestfs: trace: v2v: is_file = 1 libguestfs: trace: v2v: is_file "/etc/selinux/config" "followsymlinks:true" guestfsd: main_loop: new request, len 0x44 guestfsd: main_loop: proc 37 (is_file) took 0.00 seconds libguestfs: trace: v2v: is_file = 1 libguestfs: trace: v2v: feature_available "selinuxrelabel" libguestfs: trace: v2v: internal_feature_available "selinuxrelabel" guestfsd: main_loop: new request, len 0x3c guestfsd: main_loop: proc 458 (internal_feature_available) took 0.00 seconds libguestfs: trace: v2v: internal_feature_available = 0 libguestfs: trace: v2v: feature_available = 1 libguestfs: trace: v2v: aug_init "/" 48 guestfsd: main_loop: new request, len 0x34 guestfsd: main_loop: proc 16 (aug_init) took 0.33 seconds libguestfs: trace: v2v: aug_init = 0 libguestfs: trace: v2v: aug_rm "/augeas/load/*["/etc/selinux/config/" !~ regexp('^') + glob(incl) + regexp('/.*')]" guestfsd: main_loop: new request, len 0x80 guestfsd: main_loop: proc 22 (aug_rm) took 0.01 seconds libguestfs: trace: v2v: aug_rm = 1329 libguestfs: trace: v2v: aug_load guestfsd: main_loop: new request, len 0x28 guestfsd: main_loop: proc 27 (aug_load) took 0.01 seconds libguestfs: trace: v2v: aug_load = 0 libguestfs: trace: v2v: aug_match "/augeas/files//error" guestfsd: main_loop: new request, len 0x40 guestfsd: main_loop: proc 24 (aug_match) took 0.00 seconds libguestfs: trace: v2v: aug_match = [] libguestfs: trace: v2v: aug_get "/files/etc/selinux/config/SELINUXTYPE" guestfsd: main_loop: new request, len 0x54 guestfsd: main_loop: proc 19 (aug_get) took 0.00 seconds libguestfs: trace: v2v: aug_get = "targeted" libguestfs: trace: v2v: aug_close guestfsd: main_loop: new request, len 0x28 guestfsd: main_loop: proc 26 (aug_close) took 0.03 seconds libguestfs: trace: v2v: aug_close = 0 libguestfs: trace: v2v: selinux_relabel "/etc/selinux/targeted/contexts/files/file_contexts" "/" "force:true" guestfsd: main_loop: new request, len 0x6c commandrvf: stdout=n stderr=y flags=0x0 commandrvf: setfiles -F -e /sysroot/dev -e /sysroot/proc -e /sysroot/selinux -e /sysroot/sys -r /sysroot -q /sysroot/etc/selinux/targeted/contexts/files/file_contexts /sysroot/ Can't stat exclude path "/sysroot/selinux", No such file or directory - ignoring. [HANG HERE]
-- Derek Atkins 617-623-3745 derek@ihtfp.com <mailto:derek@ihtfp.com> www.ihtfp.com <http://www.ihtfp.com/> Computer and Internet Security Consultant
_______________________________________________ Users mailing list Users@ovirt.org <mailto:Users@ovirt.org> http://lists.ovirt.org/mailman/listinfo/users <http://lists.ovirt.org/mailman/listinfo/users>
On Wed, Nov 16, 2016 at 09:06:29AM +0200, Michal Skrivanek wrote:
On 7 Nov 2016, at 22:16, Derek Atkins <derek@ihtfp.com> wrote:
Hi,
My last VM imported in 2 minutes. This one has been sitting for three hours. I think this is a bug.
well, some time it does take a long time. Are you sure it was hung? No I/O going on?
adding libguestfs list
The most likely reason for virt-v2v to hang (actually it's qemu which is hanging) is that you've run out of disk space. Most probably in /var/tmp but best to check all your host filesystems. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com Fedora Windows cross-compiler. Compile Windows programs, test, and build Windows installers. Over 100 libraries supported. http://fedoraproject.org/wiki/MinGW
"Richard W.M. Jones" <rjones@redhat.com> writes:
On Wed, Nov 16, 2016 at 09:06:29AM +0200, Michal Skrivanek wrote:
On 7 Nov 2016, at 22:16, Derek Atkins <derek@ihtfp.com> wrote:
Hi,
My last VM imported in 2 minutes. This one has been sitting for three hours. I think this is a bug.
well, some time it does take a long time. Are you sure it was hung? No I/O going on?
adding libguestfs list
The most likely reason for virt-v2v to hang (actually it's qemu which is hanging) is that you've run out of disk space. Most probably in /var/tmp but best to check all your host filesystems.
No, the filesystem had plenty of space. It eventually did complete, after several hours. But I don't understand why this particular VM took so long when others (with similar disk sizes/usages/configurations) completed in only 1-2 minutes. Each VM is effectively exactly the same (it's a build slave), so it's just the basic installation of the particular Fedora release, the build tools, and the build slave configuration. Beyond the underlying fedora release version, the systems are configured exactly the same. I migrated four similar VMs. Three of them completed almost immediately. The last too much longer. The ONLY thing different about the one that took longer was that I decided to pack the disk first, so I ran: vmware-toolbox-cmd disk shrink / in the VM prior to packaging it up as an OVA. All the OVA files are relatively small and similar in size: -rw------- 1 warlord warlord 1959553024 Nov 7 10:40 fc20-64.ova -rw------- 1 warlord warlord 1794907648 Nov 7 12:27 fc21-64.ova -rw------- 1 warlord warlord 2023595520 Nov 6 10:04 fc22-64.ova -rw------- 1 warlord warlord 3381622272 Nov 5 16:18 fc23-64.ova The FC23 and FC22 migrations took the least amount of time, even though they were the largest.
Rich.
-derek -- Derek Atkins 617-623-3745 derek@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant
On Wed, Nov 16, 2016 at 10:56:39AM -0500, Derek Atkins wrote:
"Richard W.M. Jones" <rjones@redhat.com> writes:
On Wed, Nov 16, 2016 at 09:06:29AM +0200, Michal Skrivanek wrote:
On 7 Nov 2016, at 22:16, Derek Atkins <derek@ihtfp.com> wrote:
Hi,
My last VM imported in 2 minutes. This one has been sitting for three hours. I think this is a bug.
well, some time it does take a long time. Are you sure it was hung? No I/O going on?
adding libguestfs list
The most likely reason for virt-v2v to hang (actually it's qemu which is hanging) is that you've run out of disk space. Most probably in /var/tmp but best to check all your host filesystems.
No, the filesystem had plenty of space.
It eventually did complete, after several hours. But I don't understand why this particular VM took so long when others (with similar disk sizes/usages/configurations) completed in only 1-2 minutes. Each VM is effectively exactly the same (it's a build slave), so it's just the basic installation of the particular Fedora release, the build tools, and the build slave configuration. Beyond the underlying fedora release version, the systems are configured exactly the same.
I migrated four similar VMs. Three of them completed almost immediately. The last too much longer. The ONLY thing different about the one that took longer was that I decided to pack the disk first, so I ran:
vmware-toolbox-cmd disk shrink /
I'm not familiar with this command. In general terms, conversions take a time proportional to the amount of disk space in use by the guest. Running `virt-v2v -v -x ...' and observing the output will give you a good idea of what precisely it was doing for those hours. Rich.
in the VM prior to packaging it up as an OVA. All the OVA files are relatively small and similar in size:
-rw------- 1 warlord warlord 1959553024 Nov 7 10:40 fc20-64.ova -rw------- 1 warlord warlord 1794907648 Nov 7 12:27 fc21-64.ova -rw------- 1 warlord warlord 2023595520 Nov 6 10:04 fc22-64.ova -rw------- 1 warlord warlord 3381622272 Nov 5 16:18 fc23-64.ova
The FC23 and FC22 migrations took the least amount of time, even though they were the largest.
Rich.
-derek
-- Derek Atkins 617-623-3745 derek@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant
-- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-builder quickly builds VMs from scratch http://libguestfs.org/virt-builder.1.html
Hi, On Wed, November 16, 2016 11:10 am, Richard W.M. Jones wrote:
It eventually did complete, after several hours. But I don't understand why this particular VM took so long when others (with similar disk sizes/usages/configurations) completed in only 1-2 minutes. Each VM is effectively exactly the same (it's a build slave), so it's just the basic installation of the particular Fedora release, the build tools, and the build slave configuration. Beyond the underlying fedora release version, the systems are configured exactly the same.
I migrated four similar VMs. Three of them completed almost immediately. The last too much longer. The ONLY thing different about the one that took longer was that I decided to pack the disk first, so I ran:
vmware-toolbox-cmd disk shrink /
I'm not familiar with this command. In general terms, conversions take a time proportional to the amount of disk space in use by the guest.
This command is a disk defragment + shrink inside VMware. Basically, the .vmdk was about 36G even though the system was only using about 3G. Running this command released all that free space and then reduced the VMDK file. I figured the time should be proportional to disk usage, which is why I was so surprised that it took orders of magnitude longer than other systems with similar disk usage (and indeed, in some cases the other systems that completed in minutes had MORE disk usage).
Running `virt-v2v -v -x ...' and observing the output will give you a good idea of what precisely it was doing for those hours.
Well, as I said in my original email, it was hanging at running setfiles: commandrvf: stdout=n stderr=y flags=0x0 commandrvf: setfiles -F -e /sysroot/dev -e /sysroot/proc -e /sysroot/selinux -e /sysroot/sys -r /sysroot -q /sysroot/etc/selinux/targeted/contexts/files/file_contexts /sysroot/ Can't stat exclude path "/sysroot/selinux", No such file or directory - ignoring. There's no timestamp in the output or logs so it's hard to tell exactly what happens when or how long each step takes. For example, I wouldn't know how long the setfiles step takes unless I sit there for hours watching to see when it completes. Is there some way to add timestamps to each output line? FWIW, here's the disk usage from within that VM: Filesystem Size Used Avail Use% Mounted on /dev/vda3 44G 4.6G 37G 12% / devtmpfs 487M 0 487M 0% /dev tmpfs 497M 0 497M 0% /dev/shm tmpfs 497M 348K 496M 1% /run tmpfs 497M 0 497M 0% /sys/fs/cgroup tmpfs 497M 4.0K 496M 1% /tmp /dev/vda1 969M 130M 773M 15% /boot tmpfs 100M 0 100M 0% /run/user/1000 tmpfs 100M 0 100M 0% /run/user/0 For the record, Fedora 23, which imported in 2 minutes, has the following disk usage: Filesystem Size Used Avail Use% Mounted on devtmpfs 486M 0 486M 0% /dev tmpfs 496M 0 496M 0% /dev/shm tmpfs 496M 536K 496M 1% /run tmpfs 496M 0 496M 0% /sys/fs/cgroup /dev/vda3 45G 7.9G 37G 18% / tmpfs 496M 4.0K 496M 1% /tmp /dev/vda1 969M 136M 767M 15% /boot tmpfs 100M 0 100M 0% /run/user/1000 tmpfs 100M 0 100M 0% /run/user/0
Rich.
-derek
in the VM prior to packaging it up as an OVA. All the OVA files are relatively small and similar in size:
-rw------- 1 warlord warlord 1959553024 Nov 7 10:40 fc20-64.ova -rw------- 1 warlord warlord 1794907648 Nov 7 12:27 fc21-64.ova -rw------- 1 warlord warlord 2023595520 Nov 6 10:04 fc22-64.ova -rw------- 1 warlord warlord 3381622272 Nov 5 16:18 fc23-64.ova
The FC23 and FC22 migrations took the least amount of time, even though they were the largest.
Rich.
-derek
-- Derek Atkins 617-623-3745 derek@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant
-- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-builder quickly builds VMs from scratch http://libguestfs.org/virt-builder.1.html
-- Derek Atkins 617-623-3745 derek@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant
On Wed, Nov 16, 2016 at 11:31:40AM -0500, Derek Atkins wrote:
Running `virt-v2v -v -x ...' and observing the output will give you a good idea of what precisely it was doing for those hours.
Well, as I said in my original email, it was hanging at running setfiles:
commandrvf: stdout=n stderr=y flags=0x0 commandrvf: setfiles -F -e /sysroot/dev -e /sysroot/proc -e /sysroot/selinux -e /sysroot/sys -r /sysroot -q /sysroot/etc/selinux/targeted/contexts/files/file_contexts /sysroot/ Can't stat exclude path "/sysroot/selinux", No such file or directory - ignoring.
OK that's interesting. setfiles is doing SELinux labelling of the filesystem. The time taken should be approximately proportional to the number of files in the filesystem. What it precisely does is to run the host's /usr/sbin/setfiles command over the whole guest filesystem, using the guest's /etc/selinux/targeted/contexts/files/file_contexts to control the labelling. So if either of the guest filesystem or the guest's file_contexts is particularly large, or setfiles has a bug, then it might take a long time.
There's no timestamp in the output or logs so it's hard to tell exactly what happens when or how long each step takes. For example, I wouldn't know how long the setfiles step takes unless I sit there for hours watching to see when it completes. Is there some way to add timestamps to each output line?
Run it through the annotate-output program. https://linux.die.net/man/1/annotate-output Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-p2v converts physical machines to virtual machines. Boot with a live CD or over the network (PXE) and turn machines into KVM guests. http://libguestfs.org/virt-v2v
Hi Rich, On Wed, November 16, 2016 1:34 pm, Richard W.M. Jones wrote:
On Wed, Nov 16, 2016 at 11:31:40AM -0500, Derek Atkins wrote:
Running `virt-v2v -v -x ...' and observing the output will give you a good idea of what precisely it was doing for those hours.
Well, as I said in my original email, it was hanging at running setfiles:
commandrvf: stdout=n stderr=y flags=0x0 commandrvf: setfiles -F -e /sysroot/dev -e /sysroot/proc -e /sysroot/selinux -e /sysroot/sys -r /sysroot -q /sysroot/etc/selinux/targeted/contexts/files/file_contexts /sysroot/ Can't stat exclude path "/sysroot/selinux", No such file or directory - ignoring.
OK that's interesting. setfiles is doing SELinux labelling of the filesystem. The time taken should be approximately proportional to the number of files in the filesystem.
What it precisely does is to run the host's /usr/sbin/setfiles command over the whole guest filesystem, using the guest's /etc/selinux/targeted/contexts/files/file_contexts to control the labelling. So if either of the guest filesystem or the guest's file_contexts is particularly large, or setfiles has a bug, then it might take a long time.
I suppose there could be a bug. I just verified that it's absolutely setfiles: 14:06:20 I: Started virt-v2v -v -x -i ova /ovirt/import/fc21-64.ova -of raw -o null 14:06:20 O: [ 0.0] Opening the source -i ova /ovirt/import/fc21-64.ova [snip] 14:07:25 E: libguestfs: trace: v2v: aug_get = "targeted" 14:07:25 E: libguestfs: trace: v2v: aug_close 14:07:25 E: guestfsd: main_loop: new request, len 0x28 14:07:25 E: guestfsd: main_loop: proc 26 (aug_close) took 0.03 seconds 14:07:25 E: libguestfs: trace: v2v: aug_close = 0 14:07:25 E: libguestfs: trace: v2v: selinux_relabel "/etc/selinux/targeted/contexts/files/file_contexts" "/" "force:true" 14:07:25 E: guestfsd: main_loop: new request, len 0x6c 14:07:25 E: commandrvf: stdout=n stderr=y flags=0x0 14:07:25 E: commandrvf: setfiles -F -e /sysroot/dev -e /sysroot/proc -e /sysroot/selinux -e /sysroot/sys -r /sysroot -q /sysroot/etc/selinux/targeted/contexts/files/file_contexts /sysroot/ 14:07:25 E: Can't stat exclude path "/sysroot/selinux", No such file or directory - ignoring. [ Spacing Emphasis Mine -- there is no break (except time) here ] 16:00:42 E: libguestfs: trace: v2v: selinux_relabel = 0 16:00:42 O: virt-v2v: This guest has virtio drivers installed. 16:00:42 E: libguestfs: trace: v2v: rm_f "/.autorelabel" 16:00:42 E: guestfsd: main_loop: proc 467 (selinux_relabel) took 6797.01 seconds 16:00:42 E: guestfsd: main_loop: new request, len 0x3c [SNIP] 16:01:13 I: Finished with exitcode 0 So it looks like it took almost two hours to run the setfiles on a 4GB filesystem. The rest of the import was only a minute or three. I'm happy to help debug this however I can in order to fix any potential bugs. However I admit it probably wont affect me any more -- I don't expect to migrate many more VMs. Still, I'm happy to work towards the common good. :)
Rich.
-- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-p2v converts physical machines to virtual machines. Boot with a live CD or over the network (PXE) and turn machines into KVM guests. http://libguestfs.org/virt-v2v
-derek -- Derek Atkins 617-623-3745 derek@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant
On Wed, Nov 16, 2016 at 04:49:46PM -0500, Derek Atkins wrote:
I suppose there could be a bug. I just verified that it's absolutely setfiles:
14:06:20 I: Started virt-v2v -v -x -i ova /ovirt/import/fc21-64.ova -of raw -o null 14:06:20 O: [ 0.0] Opening the source -i ova /ovirt/import/fc21-64.ova [snip] 14:07:25 E: libguestfs: trace: v2v: aug_get = "targeted" 14:07:25 E: libguestfs: trace: v2v: aug_close 14:07:25 E: guestfsd: main_loop: new request, len 0x28 14:07:25 E: guestfsd: main_loop: proc 26 (aug_close) took 0.03 seconds 14:07:25 E: libguestfs: trace: v2v: aug_close = 0 14:07:25 E: libguestfs: trace: v2v: selinux_relabel "/etc/selinux/targeted/contexts/files/file_contexts" "/" "force:true" 14:07:25 E: guestfsd: main_loop: new request, len 0x6c 14:07:25 E: commandrvf: stdout=n stderr=y flags=0x0 14:07:25 E: commandrvf: setfiles -F -e /sysroot/dev -e /sysroot/proc -e /sysroot/selinux -e /sysroot/sys -r /sysroot -q /sysroot/etc/selinux/targeted/contexts/files/file_contexts /sysroot/ 14:07:25 E: Can't stat exclude path "/sysroot/selinux", No such file or directory - ignoring.
[ Spacing Emphasis Mine -- there is no break (except time) here ]
16:00:42 E: libguestfs: trace: v2v: selinux_relabel = 0
Yes, this is conclusive. The guest is Fedora 21? Does it have an unusually large number of files in the filesystem? Is the host RHEL or Fedora and which version? I will see if I can reproduce it. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-df lists disk usage of guests without needing to install any software inside the virtual machine. Supports Linux and Windows. http://people.redhat.com/~rjones/virt-df/
Hi, On Wed, November 16, 2016 5:03 pm, Richard W.M. Jones wrote:
On Wed, Nov 16, 2016 at 04:49:46PM -0500, Derek Atkins wrote:
I suppose there could be a bug. I just verified that it's absolutely setfiles:
14:07:25 E: commandrvf: setfiles -F -e /sysroot/dev -e /sysroot/proc -e /sysroot/selinux -e /sysroot/sys -r /sysroot -q /sysroot/etc/selinux/targeted/contexts/files/file_contexts /sysroot/ 14:07:25 E: Can't stat exclude path "/sysroot/selinux", No such file or directory - ignoring.
[ Spacing Emphasis Mine -- there is no break (except time) here ]
16:00:42 E: libguestfs: trace: v2v: selinux_relabel = 0
Yes, this is conclusive.
The guest is Fedora 21? Does it have an unusually large number of files in the filesystem? Is the host RHEL or Fedora and which version?
Guest is Fedora 21. Host is CentOS 7.2 Guest not have an unusual number of files. At least looking at the number of inodes used: Filesystem Inodes IUsed IFree IUse% Mounted on /dev/vda3 2894304 164989 2729315 6% / So... 165,000 files? My F23 system which imported in 2 minutes has 174,442 inodes used, albeit significantly more free: Filesystem Inodes IUsed IFree IUse% Mounted on /dev/vda3 23080448 174442 22906006 1% / Another difference is ext4 (F21) vs xfs (F23).
I will see if I can reproduce it.
Thanks. Worst case I can probably provide you the OVA. -derek
Rich.
-- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-df lists disk usage of guests without needing to install any software inside the virtual machine. Supports Linux and Windows. http://people.redhat.com/~rjones/virt-df/
-- Derek Atkins 617-623-3745 derek@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant
On Wed, Nov 16, 2016 at 05:09:56PM -0500, Derek Atkins wrote:
Guest is Fedora 21. Host is CentOS 7.2
Guest not have an unusual number of files. At least looking at the number of inodes used: Filesystem Inodes IUsed IFree IUse% Mounted on /dev/vda3 2894304 164989 2729315 6% /
So... 165,000 files? My F23 system which imported in 2 minutes has 174,442 inodes used, albeit significantly more free:
Filesystem Inodes IUsed IFree IUse% Mounted on /dev/vda3 23080448 174442 22906006 1% /
Another difference is ext4 (F21) vs xfs (F23).
I'll try to reproduce the issue here, but you can also do the following command directly on the guest disk image if you want to test something: time LIBGUESTFS_BACKEND=direct guestfish --ro -a fc21-64.qcow2 -i selinux-relabel /etc/selinux/targeted/contexts/files/file_contexts / force:true As long as you make sure you use the '--ro' flag, this will not make any changes to the disk image. For me that command only takes ~15 seconds to run on a Fedora 21 disk image with minimal (@Core) packages installed. I'm using a RHEL 7.3 host. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-df lists disk usage of guests without needing to install any software inside the virtual machine. Supports Linux and Windows. http://people.redhat.com/~rjones/virt-df/
Hi, On Wed, November 16, 2016 5:15 pm, Richard W.M. Jones wrote:
On Wed, Nov 16, 2016 at 05:09:56PM -0500, Derek Atkins wrote:
I'll try to reproduce the issue here, but you can also do the following command directly on the guest disk image if you want to test something:
time LIBGUESTFS_BACKEND=direct guestfish --ro -a fc21-64.qcow2 -i selinux-relabel /etc/selinux/targeted/contexts/files/file_contexts / force:true
As long as you make sure you use the '--ro' flag, this will not make any changes to the disk image.
The OVA has a .vmdk file inside it. I have no idea where ovirt put the .qcow2 file. I suppose I would need to track it down through the VM GUID? Can I run this command on the disk image of a running VM that's already been imported? Or... better, can I run it on a .vmdk file? Or, worst case, is there a way to convert the .vmdk to a .qcow2?
For me that command only takes ~15 seconds to run on a Fedora 21 disk image with minimal (@Core) packages installed. I'm using a RHEL 7.3 host.
So noted. Like I said, I can supply you the ova file if you think it would help. It's only 1.7GB ;) Thanks, -derek
Rich.
-- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-df lists disk usage of guests without needing to install any software inside the virtual machine. Supports Linux and Windows. http://people.redhat.com/~rjones/virt-df/
-- Derek Atkins 617-623-3745 derek@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant
On Wed, Nov 16, 2016 at 05:30:55PM -0500, Derek Atkins wrote:
Hi,
On Wed, November 16, 2016 5:15 pm, Richard W.M. Jones wrote:
On Wed, Nov 16, 2016 at 05:09:56PM -0500, Derek Atkins wrote:
I'll try to reproduce the issue here, but you can also do the following command directly on the guest disk image if you want to test something:
time LIBGUESTFS_BACKEND=direct guestfish --ro -a fc21-64.qcow2 -i selinux-relabel /etc/selinux/targeted/contexts/files/file_contexts / force:true
As long as you make sure you use the '--ro' flag, this will not make any changes to the disk image.
The OVA has a .vmdk file inside it. I have no idea where ovirt put the .qcow2 file. I suppose I would need to track it down through the VM GUID?
Safest and easiest would be to run the command on the .vmdk file. The command creates an overlay and works in roughly the same was as virt-v2v itself does.
Can I run this command on the disk image of a running VM that's already been imported?
As long as you use --ro it's safe to use. However I'd suggest running it on the source .vmdk to be as close as possible to what virt-v2v was doing. [...]
So noted. Like I said, I can supply you the ova file if you think it would help. It's only 1.7GB ;)
Let's see if this command takes a long time first. It could be the cause is elsewhere. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://people.redhat.com/~rjones/virt-top
Hi, On Wed, November 16, 2016 5:39 pm, Richard W.M. Jones wrote:
On Wed, Nov 16, 2016 at 05:30:55PM -0500, Derek Atkins wrote:
Hi,
On Wed, November 16, 2016 5:15 pm, Richard W.M. Jones wrote:
On Wed, Nov 16, 2016 at 05:09:56PM -0500, Derek Atkins wrote:
I'll try to reproduce the issue here, but you can also do the following command directly on the guest disk image if you want to test something:
time LIBGUESTFS_BACKEND=direct guestfish --ro -a fc21-64.qcow2 -i selinux-relabel /etc/selinux/targeted/contexts/files/file_contexts / force:true
As long as you make sure you use the '--ro' flag, this will not make any changes to the disk image.
The OVA has a .vmdk file inside it. I have no idea where ovirt put the .qcow2 file. I suppose I would need to track it down through the VM GUID?
Safest and easiest would be to run the command on the .vmdk file. The command creates an overlay and works in roughly the same was as virt-v2v itself does.
Can I run this command on the disk image of a running VM that's already been imported?
As long as you use --ro it's safe to use. However I'd suggest running it on the source .vmdk to be as close as possible to what virt-v2v was doing.
[...]
So noted. Like I said, I can supply you the ova file if you think it would help. It's only 1.7GB ;)
Let's see if this command takes a long time first. It could be the cause is elsewhere.
I found the disk image for the running VM, created a symlink, and then ran the command above. It took a while: # time LIBGUESTFS_BACKEND=direct guestfish --ro -a fc21-64.qcow2 -i selinux-relabel /etc/selinux/targeted/contexts/files/file_contexts / force:true real 114m17.757s user 114m16.476s sys 0m6.042s I could do it off the vmdk if you wish, but I'm sure there haven't been many significant changes to the VM since it was imported. Besides, I suspect it wouldn't change the outcome of the test.
Rich.
-derek -- Derek Atkins 617-623-3745 derek@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant
On Wed, Nov 16, 2016 at 08:07:15PM -0500, Derek Atkins wrote:
I found the disk image for the running VM, created a symlink, and then ran the command above. It took a while:
# time LIBGUESTFS_BACKEND=direct guestfish --ro -a fc21-64.qcow2 -i selinux-relabel /etc/selinux/targeted/contexts/files/file_contexts / force:true
real 114m17.757s user 114m16.476s sys 0m6.042s
That certainly demonstrates the bug. I'm unclear why it would be happening, but perhaps you can run the following commands and send me the results: LIBGUESTFS_BACKEND=direct guestfish --ro -a fc21-64.qcow2 -i find / > files LIBGUESTFS_BACKEND=direct virt-cat -a fc21-64.qcow2 /etc/selinux/targeted/contexts/files/file_contexts / > file_contexts rpm -qf /usr/sbin/setfiles > setfiles.version Note that the first command produces a list of all filenames within the virtual machine, which might be sensitive information, so you may wish to send me that file privately. Thanks, Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com Fedora Windows cross-compiler. Compile Windows programs, test, and build Windows installers. Over 100 libraries supported. http://fedoraproject.org/wiki/MinGW
Hi, On Thu, November 17, 2016 4:11 am, Richard W.M. Jones wrote:
On Wed, Nov 16, 2016 at 08:07:15PM -0500, Derek Atkins wrote:
I found the disk image for the running VM, created a symlink, and then ran the command above. It took a while:
# time LIBGUESTFS_BACKEND=direct guestfish --ro -a fc21-64.qcow2 -i selinux-relabel /etc/selinux/targeted/contexts/files/file_contexts / force:true
real 114m17.757s user 114m16.476s sys 0m6.042s
That certainly demonstrates the bug. I'm unclear why it would be happening, but perhaps you can run the following commands and send me the results:
LIBGUESTFS_BACKEND=direct guestfish --ro -a fc21-64.qcow2 -i find / > files
LIBGUESTFS_BACKEND=direct virt-cat -a fc21-64.qcow2 /etc/selinux/targeted/contexts/files/file_contexts / > file_contexts
See attached.. There are 184,431 entries in the file list.
rpm -qf /usr/sbin/setfiles > setfiles.version
Did you want this on the host or in the guest? On the host I get: policycoreutils-2.2.5-20.el7.x86_64 On the guest: policycoreutils-2.3-7.1.fc21.x86_64
Note that the first command produces a list of all filenames within the virtual machine, which might be sensitive information, so you may wish to send me that file privately.
There's really nothing private in the list of files on this machine. It's an openafs build slave. :)
Thanks,
Rich.
Thank you.. -derek -- Derek Atkins 617-623-3745 derek@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant
On Thu, Nov 17, 2016 at 09:57:47AM -0500, Derek Atkins wrote:
Hi,
On Thu, November 17, 2016 4:11 am, Richard W.M. Jones wrote:
On Wed, Nov 16, 2016 at 08:07:15PM -0500, Derek Atkins wrote:
I found the disk image for the running VM, created a symlink, and then ran the command above. It took a while:
# time LIBGUESTFS_BACKEND=direct guestfish --ro -a fc21-64.qcow2 -i selinux-relabel /etc/selinux/targeted/contexts/files/file_contexts / force:true
real 114m17.757s user 114m16.476s sys 0m6.042s
That certainly demonstrates the bug. I'm unclear why it would be happening, but perhaps you can run the following commands and send me the results:
LIBGUESTFS_BACKEND=direct guestfish --ro -a fc21-64.qcow2 -i find / > files
LIBGUESTFS_BACKEND=direct virt-cat -a fc21-64.qcow2 /etc/selinux/targeted/contexts/files/file_contexts / > file_contexts
See attached.. There are 184,431 entries in the file list.
rpm -qf /usr/sbin/setfiles > setfiles.version
Did you want this on the host or in the guest? On the host I get: policycoreutils-2.2.5-20.el7.x86_64
This is the same version I have.
There's really nothing private in the list of files on this machine. It's an openafs build slave. :)
Indeed there's a large number of .ccache files (over 50000). However even recreating this directory structure locally and using the same version of setfiles, I wasn't able to reproduce the problem. Runs of setfiles never took more than about 15 seconds. So, I don't know .. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://people.redhat.com/~rjones/virt-top
Hi, On Thu, November 17, 2016 10:51 am, Richard W.M. Jones wrote:
On Thu, Nov 17, 2016 at 09:57:47AM -0500, Derek Atkins wrote:
Hi,
On Wed, Nov 16, 2016 at 08:07:15PM -0500, Derek Atkins wrote:
I found the disk image for the running VM, created a symlink, and
On Thu, November 17, 2016 4:11 am, Richard W.M. Jones wrote: then
ran the command above. It took a while:
# time LIBGUESTFS_BACKEND=direct guestfish --ro -a fc21-64.qcow2 -i selinux-relabel /etc/selinux/targeted/contexts/files/file_contexts / force:true
real 114m17.757s user 114m16.476s sys 0m6.042s
That certainly demonstrates the bug. I'm unclear why it would be happening, but perhaps you can run the following commands and send me the results:
LIBGUESTFS_BACKEND=direct guestfish --ro -a fc21-64.qcow2 -i find / > files
LIBGUESTFS_BACKEND=direct virt-cat -a fc21-64.qcow2 /etc/selinux/targeted/contexts/files/file_contexts / > file_contexts
See attached.. There are 184,431 entries in the file list.
rpm -qf /usr/sbin/setfiles > setfiles.version
Did you want this on the host or in the guest? On the host I get: policycoreutils-2.2.5-20.el7.x86_64
This is the same version I have.
There's really nothing private in the list of files on this machine. It's an openafs build slave. :)
Indeed there's a large number of .ccache files (over 50000).
But that shouldn't be an issue, right? In the scheme of things, 50,000 files isn't a lot.
However even recreating this directory structure locally and using the same version of setfiles, I wasn't able to reproduce the problem. Runs of setfiles never took more than about 15 seconds.
So, I don't know ..
Would you like a copy of the VMDK? If so I can figure out how to make it available to you (privately).
Rich.
-derek -- Derek Atkins 617-623-3745 derek@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant
On Thu, Nov 17, 2016 at 11:06:48AM -0500, Derek Atkins wrote:
Would you like a copy of the VMDK? If so I can figure out how to make it available to you (privately).
I can certainly have a go. Can you post it on a website somewhere? Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-p2v converts physical machines to virtual machines. Boot with a live CD or over the network (PXE) and turn machines into KVM guests. http://libguestfs.org/virt-v2v
Hi, On Thu, November 17, 2016 1:07 pm, Richard W.M. Jones wrote:
On Thu, Nov 17, 2016 at 11:06:48AM -0500, Derek Atkins wrote:
Would you like a copy of the VMDK? If so I can figure out how to make it available to you (privately).
I can certainly have a go. Can you post it on a website somewhere?
Yep. I'll send you the URL privately.
Rich.
-derek -- Derek Atkins 617-623-3745 derek@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant
Thanks for supplying the disk image. I am able to reproduce this with the version of setfiles in RHEL 7.3, but not with the version in Fedora 24, so I guess this was fixed somewhere in between. I'll try to narrow it down to a particular commit and send a bug report. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com Fedora Windows cross-compiler. Compile Windows programs, test, and build Windows installers. Over 100 libraries supported. http://fedoraproject.org/wiki/MinGW
Hi, On Thu, November 17, 2016 5:14 pm, Richard W.M. Jones wrote:
Thanks for supplying the disk image.
you're welcome.
I am able to reproduce this with the version of setfiles in RHEL 7.3, but not with the version in Fedora 24, so I guess this was fixed somewhere in between.
Oh, so it's setfiles on the HOST that gets run, not setfiles within the guest? Interesting.
I'll try to narrow it down to a particular commit and send a bug report.
Can you please CC me on the bug report once you send it? (my BZ id is warlord AT mit DOT edu) Or I can CC myself if you supply me the bug#. Thanks!
Rich.
-derek -- Derek Atkins 617-623-3745 derek@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant
The bug is: https://bugzilla.redhat.com/show_bug.cgi?id=1396297 Let's continue discussion there, if needed. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-df lists disk usage of guests without needing to install any software inside the virtual machine. Supports Linux and Windows. http://people.redhat.com/~rjones/virt-df/
participants (3)
-
Derek Atkins -
Michal Skrivanek -
Richard W.M. Jones