September 2014 - Libguestfs - libguestfs List Archives

Bind mounts
by Richard W.M. Jones 26 Sep '14

26 Sep '14

The test program below demonstrates how to use bind mounts to mount a subdirectory over the root directory. It is using the debug backdoor, but I guess we could consider adding a bind-mount API instead. [Note that guestfs_mount_options doesn't work because it expects the third argument to be a device, not a directory name.] Rich. ---------------------------------------------------------------------- guestfish -N fs -m /dev/sda1 <<EOF mkdir /root touch /root/test # Use -o rbind if there are submounts. debug sh "mount -o bind /sysroot/root /sysroot" ls / # The above command prints "test" as expected. # Check that umount-all still works. umount-all debug sh "grep /sysroot /proc/mounts ||:" EOF -- 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/

1 0

missing symbol
by Hilko Bengen 25 Sep '14

25 Sep '14

Hi, when pushing libguestfs 1.27.53 (1:1.27.53-1) through my build setup befor uploading it to Debian, I noticed that "guestfs_internal_lstatlist@Base", a symbol that has been there since 1.20, is now missing. This causes dpkg-gensymbols(1) whose job it is to compare the symbols from the newly-built libraries to the known state to fail. If the guestfs_internal_* functions are not considered to be part of the ABI (as explained in the 8664337cc39c8575ccb60abb8c6e30f92828ea51 commit message), why are they exported? Cheers, -Hilko

2 2

virt-v2v -ic question
by Shahar Havivi 25 Sep '14

25 Sep '14

Hi, I am trying to convert from esx server to local directory a VM names CSB, Its build from source 77b371b18b6a7ad37105a595931514f542a04396 When running: LIBGUESTFS_BACKEND=direct ./run ./v2v/virt-v2v -ic "esx://root@10.35.5.45/?no_verify=1" -o local -of raw -os /tmp/v2v CSB I get the following: --------------------------------------------------------------------------- [ 0.0] Opening the source -i libvirt -ic esx://root@10.35.5.45/?no_verify=1 CSB Enter root's password for 10.35.5.45: Enter host password for user 'root': [ 4.0] Creating an overlay to protect the source from being modified qemu-img: /tmp/v2vovl2305ba.qcow2: Could not open 'json: { "file.cookie" : "vmware_soap_session=\"52d44642-3451-51db-dc36-7621bbc387bd\"", "file.sslverify" : "off", "file.driver" : "https", "file.url" : "https://10.35.5.45/folder/CSB/CSB-flat.vmdk?dcPath=ha-datacenter&dsName=dat…", "file.timeout" : 60 }': Unknown driver 'https': No such file or directory virt-v2v: error: qemu-img command failed, see earlier errors If reporting bugs, run virt-v2v with debugging enabled and include the complete output: virt-v2v -v -x [...] --------------------------------------------------------------------------- As you can see first I am propmt twice for roots password, I am able to connect with the same uri via 'vish -c' cli. Thanks, Shahar Havivi.

4 12

Virt-v2v conversion issue
by VONDRA Alain 24 Sep '14

24 Sep '14

Hi, I am running virt-v2v under CentOS 7, I use the new libguestfs-1.27.48-1.1, and when I try to import my Windows 2008 (running perfectly using virt-manager) in my cloud oVirt, I encounter this issue : ........ libguestfs: trace: mkdir_p = 0 libguestfs: trace: case_sensitive_path "/Windows/system32/drivers/viostor.sys" libguestfs: trace: case_sensitive_path = "/Windows/System32/drivers/viostor.sys" libguestfs: trace: cp "/usr/share/virtio-win/drivers/amd64/Win2008/viostor.sys" "/Windows/System32/drivers/viostor.sys" libguestfs: trace: cp = -1 (error) libguestfs: trace: hivex_close libguestfs: trace: hivex_close = 0 virt-v2v: error: libguestfs error: cp: cp: cannot stat '/sysroot/usr/share/virtio-win/drivers/amd64/Win2008/viostor.sys': No such file or directory If reporting bugs, run virt-v2v with debugging enabled and include the complete output: virt-v2v -v -x [...] libguestfs: trace: close libguestfs: trace: internal_autosync libguestfs: trace: internal_autosync = 0 The virtio-win folder is present and viostor.sys also. Can you help me to debug this issue ? Thank you and have a nice day Alain ________________________________ Alain VONDRA Charg? d'exploitation des Syst?mes d'Information Direction Administrative et Financi?re +33 1 44 39 77 76 UNICEF France 3 rue Duguay Trouin 75006 PARIS www.unicef.fr<http://www.unicef.fr/> [cid:urgence_ebola258bf0]<http://www.unicef.fr> ________________________________

3 7

Another possible bug in the preview version of virt-v2v for RHEL/CentOS 7.1
by Jeff Forbes 24 Sep '14

24 Sep '14

I have been able to get a litle further with converting a windows VM. After getting the updated virt-v2v code and rhsrvany, I now get this error: libguestfs: trace: hivex_node_set_value = 0 libguestfs: trace: upload "/usr/share/virtio-win/drivers/amd64/Win2012R2/netkvm.cat" "/Windows/Drivers/VirtIO" guestfsd: main_loop: proc 365 (hivex_node_set_value) took 0.01 seconds guestfsd: main_loop: new request, len 0x44 guestfsd: receive_file: reading length word libguestfs: got daemon cancellation guestfsd: receive_file: got chunk: cancel = 0x1, len = 0, buf = (nil) guestfsd: receive_file: received cancellation from library guestfsd: error: /Windows/Drivers/VirtIO: Is a directory libguestfs: trace: upload = -1 (error) libguestfs: trace: hivex_close guestfsd: main_loop: proc 66 (upload) took 0.03 seconds guestfsd: main_loop: new request, len 0x28 hivex: hivex_close: hivex_close guestfsd: main_loop: proc 351 (hivex_close) took 0.00 seconds libguestfs: trace: hivex_close = 0 virt-v2v: error: libguestfs error: upload: /Windows/Drivers/VirtIO: Is a directory

2 1

Why is virt-resize designed to involve two disks?
by Zhi Yong Wu 24 Sep '14

24 Sep '14

HI, As you've known, vhd-util and qemu-img both provide the capacity for resizing the original disk, but why is virt-resize designed to involve two disks, not only original disk? Is there any concern? Is it possible that only one original disk is involved in virt-resize? -- Regards, Zhi Yong Wu

2 2

[PATCH 00/13] syntax-check
by Hu Tao 24 Sep '14

24 Sep '14

3 30

Why is virt-resize designed to involve two disks?
by 吴志勇 23 Sep '14

23 Sep '14

HI, As you've known, vhd-util and qemu-img both provide the capacity for resizing the original disk, but why is virt-resize designed to involve two disks, not only original disk? Is there any concern? Is it possible that only one original disk is involved in virt-resize? -- Regards, Zhi Yong Wu

2 1

[PATCH] inspect: map Hurd devices, and enable fstab introspection
by Pino Toscano 23 Sep '14

23 Sep '14

Add a mapping for the Hurd device names, so it is possible to enable the inspection of /etc/fstab. --- src/inspect-fs-unix.c | 25 ++++++++++++++++++++++++- 1 file changed, 24 insertions(+), 1 deletion(-) diff --git a/src/inspect-fs-unix.c b/src/inspect-fs-unix.c index 3f57cd5..b629508 100644 --- a/src/inspect-fs-unix.c +++ b/src/inspect-fs-unix.c @@ -78,6 +78,7 @@ static pcre *re_opensuse_version; static pcre *re_sles_version; static pcre *re_sles_patchlevel; static pcre *re_minix; +static pcre *re_hurd_dev; static void compile_regexps (void) __attribute__((constructor)); static void free_regexps (void) __attribute__((destructor)); @@ -137,6 +138,7 @@ compile_regexps (void) COMPILE (re_sles_version, "^VERSION = (\\d+)", 0); COMPILE (re_sles_patchlevel, "^PATCHLEVEL = (\\d+)", 0); COMPILE (re_minix, "^(\\d+)\\.(\\d+)(\\.(\\d+))?", 0); + COMPILE (re_hurd_dev, "^/dev/(h)d(\\d+)s(\\d+)$", 0); } static void @@ -170,6 +172,7 @@ free_regexps (void) pcre_free (re_sles_version); pcre_free (re_sles_patchlevel); pcre_free (re_minix); + pcre_free (re_hurd_dev); } static void check_architecture (guestfs_h *g, struct inspect_fs *fs); @@ -776,7 +779,11 @@ guestfs___check_hurd_root (guestfs_h *g, struct inspect_fs *fs) /* Determine the architecture. */ check_architecture (g, fs); - /* XXX Check for /etc/fstab. */ + if (guestfs_is_file (g, "/etc/fstab") > 0) { + const char *configfiles[] = { "/etc/fstab", NULL }; + if (inspect_with_augeas (g, fs, configfiles, check_fstab) == -1) + return -1; + } /* Determine hostname. */ if (check_hostname_unix (g, fs) == -1) @@ -1635,6 +1642,22 @@ resolve_fstab_device (guestfs_h *g, const char *spec, Hash_table *md_map) if (r == -1) return NULL; } + else if (match3 (g, spec, re_hurd_dev, &type, &disk, &part)) { + /* Hurd disk devices are like /dev/hdNsM, where hdN is the + * N-th disk and M is the M-th partition on that disk. + * Turn the disk number into a letter-based identifier, so + * we can resolve it easily. + */ + int disk_i = guestfs___parse_unsigned_int (g, disk); + char disk_as_letter[2] = { 0 }; + disk_as_letter[0] = disk_i + 'a'; + r = resolve_fstab_device_xdev (g, type, disk_as_letter, part, &device); + free (type); + free (disk); + free (part); + if (r == -1) + return NULL; + } /* Didn't match device pattern, return original spec unchanged. */ if (device == NULL) -- 1.9.3

2 1

libguestfs fails on FreeBSD9.3, MINIX3 qcow2 images
by Assaf Gordon 23 Sep '14

23 Sep '14

Hello Richard and all, (continuing from https://www.redhat.com/archives/libguestfs/2014-September/msg00112.html ). I'm experimenting with libguestfs on non-linux VMs, encountered errors on FreeBSD9.3 and MINIX3 (and few others, but these ones are easy to share), with host Ubuntu 14.04.01 LTS x86-64. Attached are logs from "virt-inspector -v -x" for each VM. The images are here: http://files.housegordon.org/libguestfs/minixR330.qcow2.clean_install.xz (44MB) http://files.housegordon.org/libguestfs/freebsd93.qcow2.clean_install.xz (161MB) To run them: xz -dc < minix3/minixR330.qcow2.clean_install.xz > minixR330.qcow2 kvm -drive file=minixR330.qcow2,if=virtio,media=disk,index=0 \ -m 384 -curses -net user -net nic,model=virtio xz -dc < freebsd93.qcow2.clean_install.xz > freebsd93.qcow2 kvm -drive file=freebsd93.qcow2,if=virtio,media=disk,index=0 \ -m 384 -curses -net user -net nic,model=virtio Root password for freebsd is "12345". Root in Minix does not require a password. Regards, - Assaf ==== Disk structure from within MINIX3 VM guest ==== # fdisk /dev/c0d0 Geometry of /dev/c0d0: 10402x16x63 Inconsistent size in partition 1. Suspect head and sector parameters. Disk appears to have mis-specified number of heads or sectors. Try fdisk -h256 -s63 /dev/c0d0 instead of fdisk -h16 -s63 /dev/c0d0 Do not write the table if you are not sure!. ----first---- -----last---- --------sectors------- Num Sorted Act Type Cyl Head Sec Cyl Head Sec Base Last Size 1 1 A MINIX 0 1 1 649 255 63 63+10483199 10483137 - 2 2 None 0 0 0 0 0 0 0 0 0 3 3 None 0 0 0 0 0 0 0 0 0 4 4 None 0 0 0 0 0 0 0 0 0 # df Filesystem 512-blocks Used Avail %Cap Mounted on /dev/c0d0p0s0 4194304 111632 4082672 2% / none 0 0 0 100% /proc /dev/c0d0p0s2 3831200 805792 3025408 21% /usr /dev/c0d0p0s1 2457600 25784 2431816 1% /home none 0 0 0 100% /sys # mount /dev/c0d0p0s0 on / type mfs (rw) none on /proc type procfs (rw) /dev/c0d0p0s2 on /usr type mfs (rw) /dev/c0d0p0s1 on /home type mfs (rw) none on /sys type devman (rw) ====== Disk structure from within FreeBSD 9.3 VM guest ====== # df Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/vtbd0p2 4818524 777212 3655832 18% / devfs 1 1 0 100% /dev # mount /dev/vtbd0p2 on / (ufs, local, journaled soft-updates) devfs on /dev (devfs, local, multilabel) # fdisk /dev/vtbd0 ******* Working on device /dev/vtbd0 ******* parameters extracted from in-core disklabel are: cylinders=10402 heads=16 sectors/track=63 (1008 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=10402 heads=16 sectors/track=63 (1008 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 238 (0xee),(EFI GPT) start 1, size 10485759 (5119 Meg), flag 0 beg: cyl 0/ head 0/ sector 2; end: cyl 1023/ head 255/ sector 63 The data for partition 2 is: <UNUSED> The data for partition 3 is: <UNUSED> The data for partition 4 is: <UNUSED>

3 4