search for: dotslash

Hi all, It seems guestmount always fails to flush changes to the mounted qcow2 snapshot. To reproduce this problem: 1. take an external snapshot for a qcow2 2. guestmount the snapshot 3. do some changes, for example: `echo 123 > /test; cat /test`, right now /test can be seen created and containing the right content 4. fusermount -u {mount-point} 5. virt-cat changed file, for the example

Hi all, is it possible to monitor guest's interface's stat which uses SR-IOV virtual function? I don't know how qemu/libvirt implement monitoring, if functions like interfaceStats are implemented in the host, I think there's little chance to do this due to SR-IOV's nature, is it right? If i can't use libvirt to monitor SR-IOV interfaces, is there another way to do

Hi all. Can snapshots of identical images being blocked committed to the base images that are not the original ones? For example, suppose I have base0 and made a snapshot of it called SN0, then I copy base0 as base0', can SN0 be block committed into base0'? I think it's possible in theory but the block commit command just takes vm, base, and top as parameters, since the snapshot file

Hi everyone, I incidentally configured two IDE controller for my machine-1.2 VM(it might be virsh attach-disk to blame), and I got the error message "Only a single IDE controller is unsupported...". I can't understand this error message, I think it means I HAVE to configure two or more IDE controllers until I looked it up in the source. At libvirt-1.2.22/src/qemu/qemu_command.c:

Hi all, I was trying to take live snapshot of VMs, but I got the following error: [root@localhost ~]# virsh snapshot-create-as 1 test desc --live --memspec file=mem.bak,snapshot=external --diskspec vda,snapshot=external,file=/root/root.bak.qcow2 error: Operation not supported: live disk snapshot not supported with this QEMU binary I upgraded my qemu-kvm 0.12.1 to qemu 1.2, the error still

Hi all, Our kernel is 2.6.32-358.14.1.x86_64, recently dozens of them panicked, since it's been OK for a long time and the problem emerged all of a sudden, I'm not sure if an upgrade caused this problem. Here's what I got from backtracing: PID: 8136 TASK: ffff8803341aead0 CPU: 2 COMMAND: "" #0 [ffff880028283610] panic at ffffffff815286b8 #1 [ffff880028283690]