search for: vda4

...ms to be something that is not possible at the moment. I was just wondering if that has changed or if there are plans to change that? Here is the issue I'm experiencing: ~# guestmount --rw -a ${disk_path}/${disk_name} -m /dev/sda4 /tmp/freebsd-master libguestfs: error: mount_options: /dev/vda4 on /: mount: wrong fs type, bad option, bad superblock on /dev/vda4, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so guestmount: '/dev/sda4' could not be mounted. Did you mean one of these?...

...> ... > Disklabel type: gpt > ... > Device Start End Sectors Size Type > /dev/vda1 2048 411647 409600 200M EFI System > /dev/vda2 411648 1435647 1024000 500M Linux filesystem > /dev/vda3 1435648 22646783 21211136 10.1G Linux filesystem > /dev/vda4 22646784 25163775 2516992 1.2G Linux swap > > > # fatlabel /dev/vda1 > labelefi > > # e2label /dev/vda2 > labelboot > > # e2label /dev/vda3 > labelroot > > # swaplabel /dev/vda4 > LABEL: labelswap > ... > > > Filesystem *label* and *l...

...t_get_filesystems and inspect_get_mountpoints can't express a btrfs subvolume as they're expected to be the names of block devices. As a starter for 10, I propose the addition of parallel apis suffixed _ext which return annotated device descriptions, e.g.: block:/dev/vda2 btrfsvol:/dev/vda4,root The string before the colon is a descriptor. The format of the string after the colon is custom to the descriptor, and is described in the API. A client program can ignore strings with unknown descriptors. New descriptors can be added as required. The old apis would return the same as the...

...P System Partition # fdisk -l /dev/vda ... Disklabel type: gpt ... Device Start End Sectors Size Type /dev/vda1 2048 411647 409600 200M EFI System /dev/vda2 411648 1435647 1024000 500M Linux filesystem /dev/vda3 1435648 22646783 21211136 10.1G Linux filesystem /dev/vda4 22646784 25163775 2516992 1.2G Linux swap # fatlabel /dev/vda1 labelefi # e2label /dev/vda2 labelboot # e2label /dev/vda3 labelroot # swaplabel /dev/vda4 LABEL: labelswap ... Filesystem *label* and *label* of a swap area distinguish from GPT *name* of a partition Therefore -if- you...

...just uses the Linux kernel's ufs driver. If the Linux kernel gets fixed, we get the ability automatically. > Here is the issue I'm experiencing: > > ~# guestmount --rw -a ${disk_path}/${disk_name} -m /dev/sda4 > /tmp/freebsd-master > libguestfs: error: mount_options: /dev/vda4 on /: mount: wrong fs > type, bad option, bad superblock on /dev/vda4, > missing codepage or helper program, or other error > In some cases useful info is found in syslog - try > dmesg | tail or so > guestmount: '/dev/sda4' could not be mounted. Did you...

...type: gpt >> ... >> Device Start End Sectors Size Type >> /dev/vda1 2048 411647 409600 200M EFI System >> /dev/vda2 411648 1435647 1024000 500M Linux filesystem >> /dev/vda3 1435648 22646783 21211136 10.1G Linux filesystem >> /dev/vda4 22646784 25163775 2516992 1.2G Linux swap >> >> >> # fatlabel /dev/vda1 >> labelefi >> >> # e2label /dev/vda2 >> labelboot >> >> # e2label /dev/vda3 >> labelroot >> >> # swaplabel /dev/vda4 >> LABEL: labelswap >...

The exisiting label= option offer to boot on a gpt partition that have a particular label. The existing guuid= option offer to boot on a disk or partition with a particular label. This new option offer to boot the disk that have a partition which have a given label. The label is so just a way to detect a disk to boot. A typical use is for making an intelligent localboot like : label

Hi,everyone: As the subject says, why chinese characters are shown as '?' by using ls function? Did anyone encounter the same problem and does resolution exist? Looking forward to your reply. Thanks in advance. -------------- next part -------------- An HTML attachment was scrubbed... URL:

...3: device not found libguestfs: error: check_for_daemon_cancellation_or_eof: read 0x34 from daemon, expected 0xffffeeee guestmount: '/dev/sda3' could not be mounted. Did you mean one of these? /dev/vda1 (unknown) /dev/vda2 (unknown) /dev/vda3 (unknown) /dev/vda4 (unknown) libguestfs: error: check_for_daemon_cancellation_or_eof: read 0x0 from daemon, expected 0xffffeeee [root at longitude ~]# guestmount --live -d F16-rawhide -m /dev/vda3:/ /mnt/guestfs/ libguestfs: error: mount_options: mount_options_stub: /dev/vda3: device not found libguestfs: error: une...

...with the versions of packages in the Fedora 27 image. There are several (mostly related to iptables and ebtables), but one in particular prevents dhcp from getting an IP address: audit[509]: AVC avc: denied { read } for pid=509 comm="dhclient" name="ld.so.cache" dev="vda4" ino=4513574 scontext=system_u:system_r:dhcpc_t:s0 tcontext=system_u:object_r:unlabeled_t:s0 tclass=file permissive=0 I'm guessing that redoing the OS install of the image with updates enabled will fix this (and most/all of the other AVCs) 2) The virt-builder images are created usi...

...gt; >> Device Start End Sectors Size Type > >> /dev/vda1 2048 411647 409600 200M EFI System > >> /dev/vda2 411648 1435647 1024000 500M Linux filesystem > >> /dev/vda3 1435648 22646783 21211136 10.1G Linux filesystem > >> /dev/vda4 22646784 25163775 2516992 1.2G Linux swap > >> > >> > >> # fatlabel /dev/vda1 > >> labelefi > >> > >> # e2label /dev/vda2 > >> labelboot > >> > >> # e2label /dev/vda3 > >> labelroot > >> > >&...