similar to: snapshot-create error

Hi Laine, Sorry to disturb you. It seemed this issue had been fixed in libvirt-1.2.2/libnl-3.2.22/linux-3.12. But we still got the error on PowerPC platform. I'll appreciate if you could give any suggestion. We are not sure if any netlink implementation in kernel space is missed. The scenario is a little complicated. We installed internal PF and VF kernel modules and want to use

Hi, I tried to use libvirt to run KVM/QEMU on Freescale PowerPC platforms. So far there's only one serial device (spapr-vty) defined in QEMU to work as console for IBM PSeries platform. There's no serial device support in QEMU for Freescale PowerPC (ePAPR). libvirt/src/qemu/qemu_command.c /* This function generates the correct '-device' string for character * devices of each

Hi, I tried to use libvirt to run KVM/QEMU on Freescale PowerPC platforms. So far there's only one serial device (spapr-vty) defined in QEMU to work as console for IBM PSeries platform. There's no serial device support in QEMU for Freescale PowerPC (ePAPR). libvirt/src/qemu/qemu_command.c /* This function generates the correct '-device' string for character * devices of each

Hi Rich I'm noe getting the below logs after running libguestfs-test-tool.. SUPERMIN_MODULES=/lib/modules/3.8.13-rt9-QorIQ-SDK-V1.4 SUPERMIN_KERNEL=/boot/vmlinuz-3.8.13-rt9-QorIQ-SDK-V1.4 PATH=/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/sbin:/usr/local/bin SELinux: sh: getenforce: command not found guestfs_get_append: (null) guestfs_get_autosync: 1 guestfs_get_backend: direct

On Wed, Jun 04, 2014 at 03:29:11PM +0530, abhishek jain wrote: > supermin: kernel: SUPERMIN_KERNEL environment variable /boot/uImage > supermin: failed to find a suitable kernel (host_cpu=powerpc64). > > I looked for kernels in /boot and modules in /lib/modules. If you follow the code in src/kernel.ml you'll see that this means supermin was unable to get the kernel version from

Hi all, experimenting with vol-create-as, I think it should autodetect some data - filesize and backing file format, specifically. However, the current implementation require us to specify both filesize and backing file format. Considering that qemu-img already autodetects these data, there are any reason for the lack of autodetect by libvirt? Should I open a bugzilla issue? Below you can

On Tue, Jun 02, 2015 at 09:14:03AM +0530, Jatin Davey wrote: > Hi All > > I was reading through this: > > http://kashyapc.com/2011/12/02/little-more-disk-io-perf-improvement-with-fallocateing-a-qcow2-disk/ In my testing, the above method gives near-raw performance as it preallocated all the space ahead of time. The above test can now be done in a single command -- see option (3)

After snapshot-delete, the qcow2 image file size doesn't decrease, isn't that a waste of disk space? Would someone please tell me how to decrease the file size when snapshot-delete, if that's possible? The image file name of my virtual machine is d0.qcow As follows: [root at test1 ]# virsh list Id Name State

On Sun, Mar 15, 2015 at 10:28:30PM +0800, Yitao Jiang wrote: > Hi,guys > I wanna to get the disk snapshot size, but found nothing libvirt commands > related,except qemu-img. > I create two disk snapshots, but nothing return its' size The below does not seem like snapshots. They're *internal* qcow2 snapshots (original and delta are on the same file). A quick example of disk

Thank you, Rich, This was the issue indeed. export LIBGUESTFS_BACKEND=direct fixed it. The next step I tried was to integrate libguestfs in collectd virt plugin to collect this data automatically. In this case I'm having an unknown error in add_libvirt_dom() (same with add_domain) when it's invoking qemu-img to create overlay image. There is no difference between manual and service

Hello Thanks heaps for your suggestions. responses inline. On 10 Apr 2014, at 10:34 pm, Eric Blake <eblake@rehost1hat.com> wrote: > > [ … ] > [Can you convince your mailer to wrap long lines? It makes it easier > for other readers] I’ll try and keep the lines short. I don’t see any obvious setting to change the wrap. >> >> Using RHEL 6.4 and libvirt version

Hi (Eric?), A couple of questions while using the 'virsh blockpull' Summary: 1] Created snapshots this way: base<-snap1<-snap2<-snap3 (online, external snapshot --disk-only) 2] I did a 'virsh blockpull' from snap2 into snap3 3] Next, did another 'virsh blockpull' from snap1 into snap3 - Here, 'qemu-img info /path/to/snap3' shows its backing file

On 06/10/2013 01:20 PM, Thomas Stein wrote: > Am 10.06.13 09:07, schrieb Kashyap Chamarthy: >> On 06/09/2013 02:46 PM, Thomas Stein wrote: >>> Hello. >>> >>> I just tried the following: >>> >>> virsh dumpxml --security-info gentoo-template > gentoo-template.xml >>> virsh snapshot-create gentoo-template >>> virsh undefine

Am 10.06.13 10:40, schrieb Kashyap Chamarthy: > On 06/10/2013 01:20 PM, Thomas Stein wrote: >> Am 10.06.13 09:07, schrieb Kashyap Chamarthy: >>> On 06/09/2013 02:46 PM, Thomas Stein wrote: >>>> Hello. >>>> >>>> I just tried the following: >>>> >>>> virsh dumpxml --security-info gentoo-template > gentoo-template.xml

I am unable to convert a vm using virt-v2v. From the trace and debug logs I am unable to understand the cause of the problem. I assume it is a permission or configuration issue but I don't know where to start looking. The following command was issued: LIBGUESTFS_TRACE=1 LIBGUESTFS_DEBUG=1 virt-v2v -ic qemu+ssh://xxx at 192.168.xxx.xxx/system -o rhev -os 192.168.xxx.xxx:/mnt/exports -of

Hi there. I can't understand why I am having this different values: proxmox01:/vms/images# df Sist. Arq. Tam. Usado Disp. Uso% Montado em udev 252G 0 252G 0% /dev tmpfs 51G 9,4M 51G 1% /run /dev/sda4 433G 20G 413G 5% / tmpfs 252G 63M 252G 1% /dev/shm tmpfs 5,0M 0 5,0M 0% /run/lock efivarfs 496K 335K

On Wed, Jun 04, 2014 at 02:25:58PM +0530, abhishek jain wrote: > Hi RIch > > > Below are the details of the powerpc ubuntu system ... > > ls -l /boot/ > total 10200 > -rw-r--r-- 1 root root 5224765 Nov 22 2013 uImage > -rw-r--r-- 1 root root 5192861 Nov 22 2013 uImage.orig > > > ls -l /lib/modules/ > total 4 > drwxr-xr-x 3 ubuntu ubuntu 4096 Jun 3

qemu-img info 100/vm-100-disk-0.qcow2 image: 100/vm-100-disk-0.qcow2 file format: qcow2 virtual size: 120 GiB (128849018880 bytes) disk size: 916 GiB cluster_size: 65536 Format specific information: compat: 1.1 compression type: zlib lazy refcounts: false refcount bits: 16 corrupt: false extended l2: false Child node '/file': filename: 100/vm-100-disk-0.qcow2

What's your gluster version ? Best Regards,Strahil Nikolov ? ??????????, 11 ??????? 2024 ?. ? 20:57:50 ?. ???????+2, Gilberto Ferreira <gilberto.nunes32 at gmail.com> ??????: Hi there. I can't understand why I am having? this different values: proxmox01:/vms/images# df Sist. Arq. ? ? ?Tam. Usado Disp. Uso% Montado em udev ? ? ? ? ? ?252G ? ? 0 ?252G ? 0% /dev tmpfs ? ? ?

> Delete what you've done and start from the beginning. Describe > exactly how you created the guest. Use 'qemu-img info' to show the > format of the input file. Show precisely the virt-sparsify command > you are running. And use 'qemu-img info' on the output file too. Okay, here goes. Start off with an install root@testingbox:~ # virt-install --name