[libvirt-users] some problem with snapshot by libvirt
by xingxing gao
Hi,all,i am using libvirt to manage my vm,in these days i am testing
the libvirt snapshot ,but meet some problem:
the snapshot was created from this command:
snapshot-create-as win7 --disk-only --diskspec
vda,snapshot=external --diskspec hda,snapshot=no
but when i tried to revert from the snapshot which created from the
above command ,i got error below:
virsh # snapshot-revert win7 1338041515 --force
error: unsupported configuration: revert to external disk snapshot not
supported yet
version:
virsh # version
Compiled against library: libvir 0.9.4
Using library: libvir 0.9.4
Using API: QEMU 0.9.4
Running hypervisor: QEMU 1.0.93
10 years, 1 month
[libvirt-users] libvirt, lvm thin provisioning
by Michael Mol
I know that lvm supports thin provisioning, and I think I have a pretty
good grasp on how that works. Does libvirt support lvm thin
provisioning and thin snapshots?
I know that in order to set up lvm thin provisioning by hand, I have to
create a thin-provisioning pool within the volume group, and then
thin-provisioned logical volumes and thin-provisioned snapshots can be
created within that thin-provision pool.
I also know that it's possible to have more than one thin-provisioning
pool within the same volume group, which tells me that in order to
properly set up any lvm-aware application to use thin-provisioning, I
may need to inform it which thin-provisioning pool it should base LVs
and snapshots from.
When I look at the example here:
http://libvirt.org/storage.html#StorageBackendLogical
I don't see anything particular which tells me it supports building off
a thin-provisioning pool if I specify such by name.
Checking here:
http://libvirt.org/formatstorage.html#StoragePool
I again don't see anything specific about logical thick vs thin
provisioning. I would expect to see *something*, as there are
performance consequences when making such choices, so I'm again not
sure libvirt recognizes a difference.
So is this something that libvirt can do? And is there good
documentation somewhere on the subject?
11 years
[libvirt-users] Socket getting closed automatically after destroying vm.
by cool dharma06
hi all,
i am experimenting libvirt-1.1.4 with my xen-4.2.1. virsh working fine when
creating the vm. but it getting crashed or closed after destroying vm.
the output is as follows:
virsh # create /opt/i-47FD0798/libvirt_sec.xml
Domain Customer1_Db_domU created from /opt/i-47FD0798/libvirt_sec.xml
virsh # list
Id Name State
----------------------------------------------------
1 Sample running
virsh # destroy 5
error: Failed to destroy domain 5
error: End of file while reading data: Input/output error
error: One or more references were leaked after disconnect from the
hypervisor
error: Failed to reconnect to the hypervisor
virsh # version
error: failed to connect to the hypervisor
error: no valid connection
error: Failed to connect socket to '/var/run/libvirt/libvirt-sock':
Connection refused
11 years
[libvirt-users] Fw:Migration errors
by Tony Gong
have found the cause..migration goes well
-------- Forwarding messages --------
From: "Tony Gong" <gong790802715(a)163.com>
Date: 2013-11-26 09:15:08
To: libvirt-users(a)redhat.com
Subject: Migration errors
hi everyone:
when I exc command: virsh migrate --live --unsafe --persistent --undefinesource --verbose winxp32 qemu+ssh://192.168.20.149/system tcp://192.168.20.149:16000
or
virsh migrate --live --unsafe --persistent --verbose winxp32 qemu+ssh://192.168.20.149/system tcp://192.168.20.149:16000
some errors output:
1.Migration: error: Domain not found: no domain with matching name 'VM-****'
2.Migration: error: Requested operation is not valid: domain 'VM-***' is not processing incoming migrtion
3.Migration: error: Unable to read from monitor: Connection reset by peer
:i think it is that connection broken:modles restart,FW destroy the connection
4.Migration: error: operation failed: domain is no longer running
5.warning: virGetHostname:2265: getaddrinfo failed for 'nc02':Temporary failure in name resolution
11 years
[libvirt-users] Migration errors
by Tony Gong
hi everyone:
when I exc command: virsh migrate --live --unsafe --persistent --undefinesource --verbose winxp32 qemu+ssh://192.168.20.149/system tcp://192.168.20.149:16000
or
virsh migrate --live --unsafe --persistent --verbose winxp32 qemu+ssh://192.168.20.149/system tcp://192.168.20.149:16000
some errors output:
1.Migration: error: Domain not found: no domain with matching name 'VM-****'
2.Migration: error: Requested operation is not valid: domain 'VM-***' is not processing incoming migrtion
3.Migration: error: Unable to read from monitor: Connection reset by peer
:i think it is that connection broken:modles restart,FW destroy the connection
4.Migration: error: operation failed: domain is no longer running
5.warning: virGetHostname:2265: getaddrinfo failed for 'nc02':Temporary failure in name resolution
11 years
[libvirt-users] Help required in simulating libvirt TLS server
by Arun Viswanath
Hi All,
Will some one explain how is this tls libvirt server is implemented. For my
testing purpose I need to implement the similar TLS server in Java or
Python and this server is capable to receive all libvirt calls like
getCapabilities, hostname etc and return response as I'm configured.
Basically I need to simulate the libvirt TLS server. I tried creating many
TLS server but none of the my TLS server implemenation is capable to do
proper handshake with python libvirt client and do successful calls. Any
ideas or help will be appreciable.
Thanks In Advance,
Arun V
11 years
[libvirt-users] Hypervisor load much greater than that of the guest
by Damion Parry
Hello,
I've got a situation where I have a couple of vm's running at 300+% cpu on the hypervisor:
9893 qemu 20 0 13.0g 8.2g 4256 S 328.0 4.3 59793:17 qemu-kvm
Yet the load within the vm is in the regions of:
1.00, 1.02, 0.98
Everything is reporting OK on both the hypervisor & guest, guest is a qcow2 image on local storage.
If anyone could point me in the right direction to start debugging this I'd be grateful.
Hypervisor: CentOS release 6.4 (Final) 2.6.32-358.23.2.el6.x86_64
qemu-kvm-0.12.1.2-2.355.0.1.el6_4.9.x86_64
libvirt-0.10.2-18.el6_4.14.x86_64
Guest: CentOS release 6.4 (Final) 2.6.32-358.14.1.el6.x86_64
Thanks in advance,
Damion.
Fubra is a company limited by shares and registered in England and Wales with number 3967214 at Manor Coach House, Church Hill, Aldershot, Hampshire, GU12 4RQ. We are registered for VAT with number GB733667024, and as a data controller with number Z5193400. We are members of RIPE, Nominet, The Italian RA and registered with OfCom as a provider of electronic communications service.
11 years
[libvirt-users] Help with Vrbr0
by Sherin A
Hello,
I am not able to see vrbr0 in my box. Can some one help me with
this ? . I am trying KVM+libvirt and planing to use Routed mode. I
hope this virbr0 must be up for using this . I can give an strace too.
OS : Debian , kernel 3.12.0
libvrit version : 0.9.8
____________________________________________________________________
root@:~# ifconfig
br0 Link encap:Ethernet HWaddr 4c:72:b9:32:32:86
inet addr:10.0.0.12 Bcast:10.0.0.255 Mask:255.255.255.0
inet6 addr: fe80::4e72:b9ff:fe32:3286/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4523 errors:0 dropped:0 overruns:0 frame:0
TX packets:4068 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2286336 (2.2 MB) TX bytes:411238 (411.2 KB)
eth0 Link encap:Ethernet HWaddr 4c:72:b9:32:32:86
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:17044 errors:0 dropped:0 overruns:0 frame:0
TX packets:14253 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:12594945 (12.5 MB) TX bytes:1902456 (1.9 MB)
Interrupt:20 Memory:f7c00000-f7c20000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:4 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:240 (240.0 B) TX bytes:240 (240.0 B)
-------------------------------------------------------------------
root@:~# virsh net-start default
error: Failed to start network default
error: failed to add iptables rule to enable masquerading
root@:~# virsh net-list --all
Name State Autostart
-----------------------------------------
default inactive yes
root@:~# virsh net-start default
error: Failed to start network default
error: failed to add iptables rule to enable masquerading
root@:~# id
uid=0(root) gid=0(root) groups=0(root)
---------------
--
--------------------------------------
Sherin A
11 years, 1 month