[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] virsh list not working with xen 4
by Rogério Vinhal Nunes
Hi, I'm having some trouble to get libvirt to show the correct power state
of my virtual machines. I'm using Ubuntu 10.04 + Xen 4.1.1 + libvirt 0.8.8.
virsh list --all only shows turned off machines registered in xend. If I
turn them on, they just "disappear", and when I start machines directly from
xml, they just doesn't appear at all.
Libvirt is correctly connecting to xen as I can use the other commands fine,
just the list option doesn't seem to work at all. What can I do to change
that?
# virsh version
Compiled against library: libvir 0.8.8
Using library: libvir 0.8.8
Using API: Xen 3.0.1
Running hypervisor: Xen 4.1.0
12 years, 3 months
[libvirt-users] Live Block Migration with additional attached storage
by Chun-Hung Chen
Dear all,
I am planning to use live block migration with one VM running on local disk
and also attached additional disk from iSCSI or other shared storage.
When block migration, not only local VM disk is copied to the destination
but also the attached additional disk from shared storage. It is not
desired in this situation.
I just want the local VM disk is copied. Is there anyway to do this
scenario? Does the concept of storage pool help this? I browse the source
code but don't find hints right now.
Thanks.
Regards,
Arnose
12 years, 3 months
[libvirt-users] live migration causes guest system to crash when accessing the network
by Sebastian J. Bronner
Hi all,
we've been using libvirt/KVM ever since it was included in Ubuntu 10.04
LTS. At first, it wasn't possible to do live block migrations. We got
used to that.
And now block migration has been possible since Ubuntu 12.04 LTS. And
we're excited.
There's just one hitch:
Many of migrations have the result that the system is successfully
migrated, but will no longer run. Sometimes, it still runs but can't
access the network. Sometimes it just freezes completely, and doesn't
even show a kernel panic on the console. And sometimes the network still
works but will crash when sending ICMP messages from within the guest.
And every once in a while the guest system will continue to run.
Most of our guests use virtio for both networking and storage. The guest
OS's are mostly Ubuntu 12.04, but also one 11.04 and several 10.04's. A
few older ones are still around, as well. The older ones don't support
virtio though, so here we use the emulated intel e1000 network card and
IDE storage. The guests are connected to a common bridge on the node,
which provides access to the outside network. There is no NAT.
Oh, and I read that different CPU capabilities (flags, etc.) can cause
live migrations to fail. So I used the recommended procedure to
determine the least common denominator of the CPUs on our nodes and
configured all the guests to use only those CPU capabilities. After a
restart, I verified that the kernel correctly identified the configured
CPU type and flags.
Does anyone have an idea how I can go about debugging the issue? Or has
anyone experienced this issue and found a solution?
Cheers,
Sebastian
--
*Sebastian J. Bronner*
Administrator
D9T GmbH - Magirusstr. 39/1 - D-89077 Ulm
Tel: +49 731 1411 696-0 - Fax: +49 731 3799-220
Geschäftsführer: Daniel Kraft
Sitz und Register: Ulm, HRB 722416
Ust.IdNr: DE 260484638
http://d9t.de - D9T High Performance Hosting
info(a)d9t.de
12 years, 4 months
[libvirt-users] mouse pointer not in sync after live migration
by Stefan
Hi everybody,
I am using Opennebula 3.6 on a Debian Squeeze system. My configuration:
Node-A
kvm --version
QEMU emulator version 1.0 (qemu-kvm-1.0 Debian 1.0+dfsg-8~bpo60+1), Copyright (c) 2003-2008 Fabrice Bellard
virsh --version
0.9.11.3
Node-B
kvm --version
QEMU emulator version 1.0 (qemu-kvm-1.0 Debian 1.0+dfsg-8~bpo60+1), Copyright (c) 2003-2008 Fabrice Bellard
virsh --version
0.9.11.3
After live-migration, my mouse pointer is not in sync. I just write an email to the opennebula-mailinglist, but maybe this a problem from libvirt or kvm?
http://lists.opennebula.org/pipermail/users-opennebula.org/2012-July/0096...
thanks in advance
Stefan
12 years, 4 months
Re: [libvirt-users] libvirt-users Digest, Vol 31, Issue 39
by Borden Rhodes
Hey everybody,
Thanks for the help. It turns out that net.ipv4.ip_forward was set to
= 0 and I had to change it to = 1, which I found from the excellent
http://wiki.libvirt.org/page/Guest_can_reach_host%2C_but_can%27t_reach_ou...
guide. All's well in the state of Denmark and I should be able to set
to figuring out how to get libvirt to play nicely with Firestarter and
Network Manager.
Speaking from my own experience, when people are fooling around with
the documentation, they may want to consider the following things:
1) In Debian (and probably Ubuntu by association), the command to
restart libvirtd is (sudo) service libvirt-bin restart. For *tards
like me who get easily confused and might think that a libvirt daemon
is something specific to Red Hat, etc., it might be worth making this
distinction. I'll probably also whine to the Debian to make this point
clearer in their own documentation since it's not the libvirt
project's fault that Debian feels compelled to 'improve' things.
2) Again, a *tard like me didn't think to look for the Troubleshooting
page under the General Project Documentation section of the Wiki.
Granted, I realise that makes me especially *tarded because it's,
like, the first item after the table of contents, but someone like me
expects Troubleshooting to be its own section in the ToC and/or linked
generously within the sections discussing networking concepts. Perhaps
it might be more useful to start a Troubleshooting sub-subsection
under SS 1.7 and link all of the network troubleshooting docs to that?
3) One of the frustrations I had was trying to figure out what the
responsibilities were for each of libvirt, virt-manager and qemu/kvm,
especially in the context of seeing all of the settings jumbled
together in virt-manager (I'm a little bash-phobic). So I'm not sure
if this is libvirt's 'problem,' but as good as Virtual Networking
concepts page is, it doesn't quite explain the difference between what
appears in virt-manager as 'Virtual Networks' and 'Network Interfaces'
under the connection settings. I think the difference is that the
former is for simple NAT routing whereas the latter is for advanced
bridging, but when I was setting up my virtual machines, I didn't
understand which I had to configure and whether I had to set up both.
Again, thanks for the help. I really appreciate it.
Borden
12 years, 4 months
[libvirt-users] Can't NAT in KVM
by Borden Rhodes
Good morning, list,
I've been trying to get my KVM virtual machines to connect to the
Interwebs for the last 3 hours with no success. I'm running Debian
Wheezy (fully patched) and building virtual machines using KVM in Virt
Manager.
With the default, factory settings shown in virt manager, I have a
default virtual network with the device name virbr0, which starts on
boot and uses the default IPv4 subnets. I also have the default lo
(loopback) network interface.
I have tried creating a Windows 8 Release Preview machine and a
Kubuntu Live CD machine. Despite recognising the hardware and network
interface, neither machine will connect to the Internet. From what I
can see in both virtual machines, it seems that neither is getting a
DHCP lease from virbr0. I'm not sure what's broken or where to start
looking for trouble because both the logs and the documentation are
fairly sparse.
Other possibly relevant information: I have a simple firewall
configured with Firestarter in Wheezy. I use Network Manager to manage
my only wireless connection to the world. I don't want to set up any
fancy bridging or override /etc/interfaces because I only use virtual
machines rarely but I rely on Network Manager to set up my laptop's
networks so I don't have to.
Any suggestions on how I can plug the v-machines to the web?
With thanks,
Borden
12 years, 4 months
[libvirt-users] How can I make sVirt work with LXC (libvirt-0.9.13)?
by David Kang
Hi,
I've installed libvirt-0.9.13 on RHEL6.2 from the source code.
I cannot make sVirt working with LXC. (sVirt works well with KVM, though.)
I can start an LXC instance, but the label of the process is not right.
Can someone help me?
I tried to change /etc/libvirtd/lxc.conf file to explicitly enable
security_driver = "selinux".
But it ends up with error saying "error : virSecurityDriverLookup:74 : internal error Security driver selinux not found".
SELinux is in a permissive mode but is not enforcing.
The current situation is as follows:
* The label of an LXC container is not properly done:
$ ps auxZ | grep lxc
unconfined_u:system_r:virtd_t:s0-s0:c0.c1023 root 27998 0.0 0.0 34716 1160 ? Ss 11:54 0:00 /usr/libexec/libvirt_lxc --name instance-0000001f --console 16 --security=none --handshake 19 --background --veth veth1
* This is the lable of libvirtd process:
$ ps auxZ | grep libvirtd
unconfined_u:system_r:virtd_t:s0-s0:c0.c1023 root 27376 0.1 0.0 919052 5324 ? Sl 11:51 0:00 libvirtd --daemon
* Here is the xml file that I used to run LXC instance, which was generated by OpenStack:
<domain type="lxc">
<uuid>621adc56-2103-465c-bafd-1d0b51bea3a0</uuid>
<name>instance-0000001f</name>
<memory>2097152</memory>
<vcpu>1</vcpu>
<os>
<type>exe</type>
<cmdline>console=ttyS0</cmdline>
<init>/sbin/init</init>
</os>
<clock offset="utc"/>
<devices>
<filesystem type="mount">
<source dir="/usr/local/nova/instances/instance-0000001f/rootfs"/>
<target dir="/"/>
</filesystem>
<interface type="bridge">
<mac address="fa:16:3e:1e:33:f4"/>
<model type="virtio"/>
<source bridge="br100"/>
<filterref filter="nova-instance-instance-0000001f-fa163e1e33f4">
<parameter name="IP" value="10.0.0.4"/>
<parameter name="DHCPSERVER" value="10.0.0.3"/>
<parameter name="PROJNET" value="10.0.0.0"/>
<parameter name="PROJMASK" value="255.255.0.0"/>
</filterref>
</interface>
<console type="pty"/>
</devices>
</domain>
* Svirt works well with KVM as is shown below:
$ ps auxZ | grep qemu
system_u:system_r:svirt_t:s0:c128,c132 root 22710 6.9 0.2 895040 34332 ? Sl 11:17 0:07 /usr/libexec/qemu-kvm -name instance-0000001b -S -M pc-0.14 -cpu core2duo,+lahf_lm,+dca,+pdcm,+xtpr,+cx16,+tm2,+est,+vmx,+ds_cpl,+dtes64,+pbe,+tm,+ht,+ss,+acpi,+ds -enable-kvm -m 512 -smp 1,sockets=1,cores=1,threads=1 -uuid 12716b13-001c-40de-9537-ca847aead70b -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/instance-0000001b.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -no-kvm-pit-reinjection -kernel /usr/local/nova/instances/instance-0000001b/kernel -initrd /usr/local/nova/instances/instance-0000001b/ramdisk -append root=/dev/vda console=ttyS0 -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/usr/local/nova/instances/instance-0000001b/disk,if=none,id=drive-virtio-disk0,format=qcow2,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=17,id=hostnet0 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=fa:16:3e:7a:5e:b6,bus=pci.0,addr=0x3 -chardev file,id=charserial0,path=/usr/local/nova/instances/instance-0000001b/console.log -device isa-serial,chardev=charserial0,id=serial0 -chardev pty,id=charserial1 -device isa-serial,chardev=charserial1,id=serial1 -device usb-tablet,id=input0 -vnc 127.0.0.1:0 -k en-us -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5
Thanks,
David
----------------------
Dr. Dong-In "David" Kang
Computer Scientist
USC/ISI
12 years, 5 months
