similar to: Why is virt-resize designed to involve two disks?

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

On Tue, Sep 23, 2014 at 06:19:21PM +0800, Zhi Yong Wu wrote: > As you've known, vhd-util and qemu-img both provide the capacity for > resizing the original disk, .. although they only resize the container, not the contents which is what virt-resize does. So these tools are not really comparable. > but why is virt-resize designed to involve > two disks, not only original disk? Is

On Mon, Sep 29, 2014 at 12:36 AM, Richard W.M. Jones <rjones@redhat.com> wrote: > On Sun, Sep 28, 2014 at 11:43:17PM +0800, Zhi Yong Wu wrote: >> Yeah, but why did it happen when i directly issue guest VM via above command? > > OK I see. When libguestfs runs qemu-kvm, it sets up a TCP socket > first [on RHEL 5 -- it works differently upstream]. Without the > socket

On Mon, Sep 29, 2014 at 1:14 AM, Richard W.M. Jones <rjones@redhat.com> wrote: > On Mon, Sep 29, 2014 at 12:55:04AM +0800, Zhi Yong Wu wrote: >> On Mon, Sep 29, 2014 at 12:36 AM, Richard W.M. Jones <rjones@redhat.com> wrote: >> > On Sun, Sep 28, 2014 at 11:43:17PM +0800, Zhi Yong Wu wrote: >> >> Yeah, but why did it happen when i directly issue guest VM

HI, Do anyone know where btrfs_print_tree is invoked? thanks. -- Regards, Zhi Yong Wu -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

On Fri, Oct 10, 2014 at 04:03:26PM +0800, Zhi Yong Wu wrote: > On Fri, Oct 10, 2014 at 3:39 PM, Richard W.M. Jones <rjones@redhat.com> wrote: > > On Fri, Oct 10, 2014 at 11:40:03AM +0800, Zhi Yong Wu wrote: > >> HI, Richard > >> > >> Is there any plan to make daemon to directly run on the hypervisor, > >> not starting a guest? e.g. directly export

On Fri, Oct 10, 2014 at 11:40:03AM +0800, Zhi Yong Wu wrote: > HI, Richard > > Is there any plan to make daemon to directly run on the hypervisor, > not starting a guest? e.g. directly export a guest image to be a block > device on the hypervisor? Not in 1.28, but adding lxc:// support to the libvirt backend (src/launch-libvirt.c) would be fairly easy. It's an idea that has

On Mon, Sep 29, 2014 at 1:27 AM, Richard W.M. Jones <rjones@redhat.com> wrote: > On Mon, Sep 29, 2014 at 01:22:19AM +0800, Zhi Yong Wu wrote: >> Yes, I am trying to run it in Xen Domain0. I thought that we can use >> Domain0 as a public libguestfs VM, This will avoid starting a new >> guest for virt-xxx every time, But Domain0 has no corresponding qemu >> task. So

From: Nicholas Bellinger <nab at linux-iscsi.org> This QEMU patch sets VirtIOSCSIConfig->max_target=0 for vhost-scsi operation to restrict virtio-scsi LLD guest scanning to max_id=0 (a single target ID instance) when connected to individual tcm_vhost endpoints as requested by Paolo. This ensures that virtio-scsi LLD only attempts to scan target IDs up to VIRTIO_SCSI_MAX_TARGET when

From: Nicholas Bellinger <nab at linux-iscsi.org> This QEMU patch sets VirtIOSCSIConfig->max_target=0 for vhost-scsi operation to restrict virtio-scsi LLD guest scanning to max_id=0 (a single target ID instance) when connected to individual tcm_vhost endpoints as requested by Paolo. This ensures that virtio-scsi LLD only attempts to scan target IDs up to VIRTIO_SCSI_MAX_TARGET when

I have try to resize one vhd file with vhd-util, i did some test... For example i have try: vhd-util resize -n /mnt/vm/disks/ring-12.disk1.vhd -s 6000 but output always: options: <-n name> <-j journal> <-s size (in MB)> [-h help] I not understand what i wrong, someone can help me please? -- View this message in context:

On Tue, Oct 28, 2014 at 11:22:47PM +0800, Zhi Yong Wu wrote: > HI, Richard > > Can you know what is missing when the following issue took place? > > #gcc mount-local.c -o mount-local -lguestfs > /usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../lib64/libguestfs.so: > undefined reference to `guestfs__internal_test_rconstoptstring' >

On Mon, Sep 29, 2014 at 1:41 AM, Richard W.M. Jones <rjones@redhat.com> wrote: > On Mon, Sep 29, 2014 at 01:35:08AM +0800, Zhi Yong Wu wrote: >> On Mon, Sep 29, 2014 at 1:27 AM, Richard W.M. Jones <rjones@redhat.com> wrote: >> > User-Mode Linux is also a possibility. Slow but consistent >> Slow is a big concern... > > There are some measurements here:

On Sun, Sep 28, 2014 at 11:31 PM, Richard W.M. Jones <rjones@redhat.com> wrote: > On Sun, Sep 28, 2014 at 11:04:11PM +0800, Zhi Yong Wu wrote: >> On Sun, Sep 28, 2014 at 6:48 PM, Richard W.M. Jones <rjones@redhat.com> wrote: >> > On Sun, Sep 28, 2014 at 06:33:53PM +0800, Zhi Yong Wu wrote: >> >> On Sun, Sep 28, 2014 at 6:26 PM, Richard W.M. Jones

Hi, I have two guest vm instance running CentOS 5 with ext3 partition. I will like to reduce 1 VM harddisk space and using the 'release' harddisk space to add onto my second VM. Basically I need to know how can I reduce and increase an ext3 partition in CentOS KVM. I did a search and basically i can do it by booting the VM using Knoppix and use Gparted to reduce and increase the

On Wed, Dec 17, 2014 at 03:07:11PM +0800, Hu Tao wrote: > On Thu, Oct 30, 2014 at 10:46:52AM +0800, Hu Tao wrote: > > Hi Rich, > > > > This is rebase of v5 series. Meanwhile, I found a bug when shrinking > > partitions, and the fix is incuded in this version (patch 2). > > Hi, > > When support to resizing logical partitions is enabled, there is a >

On Wed, Jan 28, 2015 at 03:43:19PM +0000, Richard W.M. Jones wrote: > On Wed, Jan 28, 2015 at 02:24:15PM +0800, Hu Tao wrote: > > On Wed, Dec 17, 2014 at 03:07:11PM +0800, Hu Tao wrote: > > > On Thu, Oct 30, 2014 at 10:46:52AM +0800, Hu Tao wrote: > > > > Hi Rich, > > > > > > > > This is rebase of v5 series. Meanwhile, I found a bug when

From: Nicholas Bellinger <nab at linux-iscsi.org> Hi Anthony + QEMU storage folks, The following is a reviewable RFC series of vhost-scsi against yesterday's QEMU.git/master @ commit 401a66357d. The series is available directly from: git://git.kernel.org/pub/scm/virt/kvm/nab/qemu-kvm.git vhost-scsi-merge It contains the squashed + re-ordered patches from Stefan -> Zhi's

From: Nicholas Bellinger <nab at linux-iscsi.org> Hi Anthony + QEMU storage folks, The following is a reviewable RFC series of vhost-scsi against yesterday's QEMU.git/master @ commit 401a66357d. The series is available directly from: git://git.kernel.org/pub/scm/virt/kvm/nab/qemu-kvm.git vhost-scsi-merge It contains the squashed + re-ordered patches from Stefan -> Zhi's

From: Nicholas Bellinger <nab at linux-iscsi.org> This patch changes virtio-scsi to use a new virtio_driver->scan() callback so that scsi_scan_host() can be properly invoked once virtio_dev_probe() has set add_status(dev, VIRTIO_CONFIG_S_DRIVER_OK) to signal active virtio-ring operation, instead of from within virtscsi_probe(). This fixes a bug where SCSI LUN scanning for both