similar to: Virt-resize error (ntfs) : Fatal error: exception Guestfs.Error("ntfsresize_opts: /dev/vda2)

Hi To deploy KVM vms I use a KVM template + script - which is cloned, then cloned again and resized - using virt-resize. i.e ---------------------------------------------------- virt-clone --original debian6template-DONTSTART --name NAME.test -f /dev/vgpool/NAME.test virsh vol-create-as vgpool NAME 8G virt-clone --original NAME.test --name NAME -f /dev/vgpool/NAME virt-resize --expand

I use python-guestfs to mount windows image it have some problems .Here is my code: [root@mfsdata1 ~]# python Python 2.6.6 (r266:84292, Sep 11 2012, 08:34:23) [GCC 4.4.6 20120305 (Red Hat 4.4.6-4)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import os >>> sheepfs_dir="/tmp/sheepfs"

trace: >>> g.inspect_os() libguestfs: trace: inspect_os libguestfs: trace: umount_all libguestfs: trace: umount_all = 0 libguestfs: trace: list_devices libguestfs: trace: list_devices = ["/dev/vda"] libguestfs: trace: vfs_type "/dev/vda" libguestfs: trace: vfs_type = "" libguestfs: trace: mount_ro "/dev/vda" "/" libguestfs: trace:

OK, that seam to work however it is not exactly the correct solution for me since I need to make it one command to be able to call it from an API I have no name!@(none):/# ntfsresize /dev/sda1 ntfsresize v2012.1.15AR.5 (libntfs-3g) ERROR: Volume is scheduled for check. Run chkdsk /f and please try again, or see option -f. I have no name!@(none):/# chkdsk /f bash: chkdsk: command not found I have

Unfortunately I cannot use the latest version of libguestfs therefore I am stuck with the 1.20 since the newest versions need augeas 1.0.0 where debian wheezy has only 0.7 in it’s repository. But I will try to compile the ocaml 4.01 and see what is the result. Keresztes Péter-Zoltán zozo@z0z0.tk I haven’t lost my mind, I know exactly where I left it. On 01 Jul 2014, at 18:19, Richard W.M. Jones

Add a macro DUP_RESOLVE_DEVICE_OR_PATH to resolve path or device. Signed-off-by: Wanlong Gao <gaowanlong at cn.fujitsu.com> --- daemon/daemon.h | 18 ++++++++++++++++++ daemon/mount.c | 13 ++----------- po/POTFILES | 8 ++++++++ 3 files changed, 28 insertions(+), 11 deletions(-) diff --git a/daemon/daemon.h b/daemon/daemon.h index 85eec45..39cc3f3 100644 --- a/daemon/daemon.h +++

Hello, I have an issue with virt-resize on the newest version of proxmox which is running on debian wheezy. when I run the virt-resize on a windows 2008 qemu image I got an error. Here is the last part of the debug message: Copying /dev/sda1 ... libguestfs: trace: copy_device_to_device "/dev/sda1" "/dev/sdb1" "size:32210026496" 100%

This first factors out all the partition sizing, and then resizes the images created to be 1GB instead of 512MB, to work around a size limitation with btrfs: mkfs_btrfs: /dev/vda2: device /dev/vda2 is too small (must be at least 256 MB)

Greetings - I am going through some testing steps to expand a logical volume and the corresponding filesystem on a KVM guest and have run across a deficiency in my knowledge. I spent the afternoon yesterday googling for answers, but had have come up blank still. What I am trying to do is resize the file system to use the additional disk space that I added to the logical volume that the

This rather complex set of patches allow non-optargs functions to gain optional arguments, while preserving source and binary backwards compatibility. The problem is that we cannot add an optional argument to an existing function. For example, we might want to add flags to the 'lvresize' API which currently has no optional arguments.

I have a Windows 2000 domU running in an LVM partition. I need to move it to another host, but none of my other xen servers have lvm or free space to create an lvm. So I''d like to convert it to a sparse img file. The file system in the domU is ntfs. Can anyone suggest how to do this? Thanks, James _______________________________________________ Xen-users mailing list

--- daemon/daemon.h | 1 + daemon/labels.c | 3 +++ daemon/swap.c | 21 +++++++++++++++++++++ generator/actions.ml | 4 ++++ 4 files changed, 29 insertions(+) diff --git a/daemon/daemon.h b/daemon/daemon.h index 79a5288..2379e31 100644 --- a/daemon/daemon.h +++ b/daemon/daemon.h @@ -254,6 +254,7 @@ extern int64_t ntfs_minimum_size (const char *device); /*-- in swap.c --*/

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:

Hi, this small patch series exposes one of the utility in f2fs-tools, and use it to expand f2fs partitions in virt-resize. Thanks, Pino Toscano (2): New API: f2fs_expand resize: expand f2fs partitions daemon/Makefile.am | 1 + daemon/f2fs.c | 49 +++++++++++++++++++++++++++++++++++++++++++++++ generator/actions_core.ml | 9 +++++++++ generator/proc_nr.ml | 1 +

> On 30.06.2016 19:41, Erwan Velu via Syslinux wrote: > > 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. >

Tried to make it in accordance with your comments. Difference to v1: Added reply_with_error where necessary. Changed name get_min_size -> vfs_min_size. Maxim Perevedentsev (2): New API: vfs_min_size Include resize2fs_P into vfs_min_size. daemon/Makefile.am | 1 + daemon/daemon.h | 2 ++ daemon/ext2.c | 45 ++++++++++++++++++++++++++----- daemon/fs-min-size.c | 49

Hi, I am struggling with kickstart. What I want to achieve is a reinstall, but some data partitions should survive the install, i.e. they should not be formatted. With a single disk this works, here is the relevant part from the kickstart file (I shortened the name of the volume group) ... zerombr clearpart --none --initlabel part /boot --fstype="xfs" --label=boot --onpart=vda1 part

On 5/5/2017 1:19 ??, Gianluca Cecchi wrote: > Could you verify, if /dev/sda is your boot disk, with the command > > fdisk -l /dev/sda > ? It's /dev/vda in my case: # fdisk -l /dev/vda Disk /dev/vda: 21.5 GB, 21474836480 bytes, 41943040 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512

Hi, I have a working windows lvm of 1.62GB size. I just do an lvextend +1Gb on it, and then the Guest gets stuck at ''booting from harddisk'' the initial stage. Is there something more I should do? I had tried getting it working with parted etc, but it doesn''t seem to work. Is there some documentation on manipulating windows image files and the partitions inside them?

On Fri, May 5, 2017 at 12:52 PM, Nikolaos Milas <nmilas at noa.gr> wrote: > On 5/5/2017 1:42 ??, Nikolaos Milas wrote: > > Hmm, it seems that the boot flag should be removed from /dev/vda2 >> partition? >> > > Actually, I tried this and left the boot flag only to /dev/vda1. I > rebooted and I am still getting the same error. :-( > > I was hoping we were