January 2013 - Users - libvirt List Archives

[libvirt-users] some problem with snapshot by libvirt
by xingxing gao 22 Nov '14

22 Nov '14

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

4 8

[libvirt-users] Managing Live Snapshots with Libvirt 1.0.1
by Andrew Martin 05 Feb '13

05 Feb '13

Hello, I recently compiled libvirt 1.0.1 and qemu 1.3.0 on Ubuntu 12.04. I have performed live snapshots on VMs using "virsh snapshot-create-as" and then later re-merge the images together using "virsh blockpull". I am wondering how I can do a couple of other operations on the images while the VM is running. For example, VM1 is running from the snap3 image, with the following snapshot history (backing files): [orig] <-- [snap1] <-- [snap2] <-- [snap3] 1. Can I revert VM1 to use snap2 while it is live, or must it be shutdown? After shutting it down, is the best way to revert to snap2 to just edit the xml file and change the block device to point to snap2? Afterwards, I believe snap3 would become unusable and should be deleted? 2. If I would like to start a new VM from snap1, is there a way to extract a copy of this snapshot from the chain, to an independent image file? I tried to use "virsh blockcopy" but it returned this error: # virsh blockcopy VM1 vda snap1.qcow2 --wait --verbose error: Requested operation is not valid: domain is not transient Thanks, Andrew

2 5

[libvirt-users] Sanlock gives up lock when VM is paused
by Michael Rodrigues 02 Feb '13

02 Feb '13

Hello, I'm using libvirt and sanlock on qemu-kvm guests. Each guest has it's own Logical Volume for it's root filesystem. Sanlock is configured and working and prevents me from starting the same VM twice on multiple nodes and corrupting it's root filesystem. Each VM's domain XML resides on 2 servers that share the LVM volume group over fiber channel. In testing, I noticed that if I pause a VM on node 1, the sanlock lock is relinquished, and I am able to start the same VM, using the same root filesystem, on node 2. I get a lock error when unpausing node 1's VM if node 2's copy is still running, but by this point, the disk may already be corrupted. Is it necessary that paused VMs don't get to keep their locks? Is there a way to configure sanlock to lock when a VM is paused? Versions: sanlock(-devel, -lib) 2.3-1.el6 libvirt(-lock-sanlock, -client) 0.9.10-21.el6_3.8 I'm using NFS for the lockspace. Thanks, Michael -- Michael Rodrigues Interim Help Desk Manager Gevirtz Graduate School of Education Education Building 4203 (805) 893-8031 help(a)education.ucsb.edu

2 7

Re: [libvirt-users] windows 2008 guest causing rcu_shed to emit NMI
by Andrey Korolyov 01 Feb '13

01 Feb '13

On Thu, Jan 31, 2013 at 12:11 AM, Marcelo Tosatti <mtosatti(a)redhat.com> wrote: > On Wed, Jan 30, 2013 at 11:21:08AM +0300, Andrey Korolyov wrote: >> On Wed, Jan 30, 2013 at 3:15 AM, Marcelo Tosatti <mtosatti(a)redhat.com> wrote: >> > On Tue, Jan 29, 2013 at 02:35:02AM +0300, Andrey Korolyov wrote: >> >> On Mon, Jan 28, 2013 at 5:56 PM, Andrey Korolyov <andrey(a)xdel.ru> wrote: >> >> > On Mon, Jan 28, 2013 at 3:14 AM, Marcelo Tosatti <mtosatti(a)redhat.com> wrote: >> >> >> On Mon, Jan 28, 2013 at 12:04:50AM +0300, Andrey Korolyov wrote: >> >> >>> On Sat, Jan 26, 2013 at 12:49 AM, Marcelo Tosatti <mtosatti(a)redhat.com> wrote: >> >> >>> > On Fri, Jan 25, 2013 at 10:45:02AM +0300, Andrey Korolyov wrote: >> >> >>> >> On Thu, Jan 24, 2013 at 4:20 PM, Marcelo Tosatti <mtosatti(a)redhat.com> wrote: >> >> >>> >> > On Thu, Jan 24, 2013 at 01:54:03PM +0300, Andrey Korolyov wrote: >> >> >>> >> >> Thank you Marcelo, >> >> >>> >> >> >> >> >>> >> >> Host node locking up sometimes later than yesterday, bur problem still >> >> >>> >> >> here, please see attached dmesg. Stuck process looks like >> >> >>> >> >> root 19251 0.0 0.0 228476 12488 ? D 14:42 0:00 >> >> >>> >> >> /usr/bin/kvm -no-user-config -device ? -device pci-assign,? -device >> >> >>> >> >> virtio-blk-pci,? -device >> >> >>> >> >> >> >> >>> >> >> on fourth vm by count. >> >> >>> >> >> >> >> >>> >> >> Should I try upstream kernel instead of applying patch to the latest >> >> >>> >> >> 3.4 or it is useless? >> >> >>> >> > >> >> >>> >> > If you can upgrade to an upstream kernel, please do that. >> >> >>> >> > >> >> >>> >> >> >> >>> >> With vanilla 3.7.4 there is almost no changes, and NMI started firing >> >> >>> >> again. External symptoms looks like following: starting from some >> >> >>> >> count, may be third or sixth vm, qemu-kvm process allocating its >> >> >>> >> memory very slowly and by jumps, 20M-200M-700M-1.6G in minutes. Patch >> >> >>> >> helps, of course - on both patched 3.4 and vanilla 3.7 I`m able to >> >> >>> >> kill stuck kvm processes and node returned back to the normal, when on >> >> >>> >> 3.2 sending SIGKILL to the process causing zombies and hanged ``ps'' >> >> >>> >> output (problem and workaround when no scheduler involved described >> >> >>> >> here http://www.spinics.net/lists/kvm/msg84799.html) >> >> >>> > >> >> >>> > Try disabling pause loop exiting with ple_gap=0 kvm-intel.ko module parameter. >> >> >>> > >> >> >>> >> >> >>> Hi Marcelo, >> >> >>> >> >> >>> thanks, this parameter helped to increase number of working VMs in a >> >> >>> half of order of magnitude, from 3-4 to 10-15. Very high SY load, 10 >> >> >>> to 15 percents, persists on such numbers for a long time, where linux >> >> >>> guests in same configuration do not jump over one percent even under >> >> >>> stress bench. After I disabled HT, crash happens only in long runs and >> >> >>> now it is kernel panic :) >> >> >>> Stair-like memory allocation behaviour disappeared, but other symptom >> >> >>> leading to the crash which I have not counted previously, persists: if >> >> >>> VM count is ``enough'' for crash, some qemu processes starting to eat >> >> >>> one core, and they`ll panic system after run in tens of minutes in >> >> >>> such state or if I try to attach debugger to one of them. If needed, I >> >> >>> can log entire crash output via netconsole, now I have some tail, >> >> >>> almost the same every time: >> >> >>> http://xdel.ru/downloads/btwin.png >> >> >> >> >> >> Yes, please log entire crash output, thanks. >> >> >> >> >> > >> >> > Here please, 3.7.4-vanilla, 16 vms, ple_gap=0: >> >> > >> >> > http://xdel.ru/downloads/oops-default-kvmintel.txt >> >> >> >> Just an update: I was able to reproduce that on pure linux VMs using >> >> qemu-1.3.0 and ``stress'' benchmark running on them - panic occurs at >> >> start of vm(with count ten working machines at the moment). Qemu-1.1.2 >> >> generally is not able to reproduce that, but host node with older >> >> version crashing on less amount of Windows VMs(three to six instead >> >> ten to fifteen) than with 1.3, please see trace below: >> >> >> >> http://xdel.ru/downloads/oops-old-qemu.txt >> > >> > Single bit memory error, apparently. Try: >> > >> > 1. memtest86. >> > 2. Boot with slub_debug=ZFPU kernel parameter. >> > 3. Reproduce on different machine >> > >> > >> >> Hi Marcelo, >> >> I always follow the rule - if some weird bug exists, check it on >> ECC-enabled machine and check IPMI logs too before start complaining >> :) I have finally managed to ``fix'' the problem, but my solution >> seems a bit strange: >> - I have noticed that if virtual machines started without any cgroup >> setting they will not cause this bug under any conditions, >> - I have thought, very wrong in my mind, that the >> CONFIG_SCHED_AUTOGROUP should regroup the tasks without any cgroup and >> should not touch tasks already inside any existing cpu cgroup. First >> sight on the 200-line patch shows that the autogrouping always applies >> to all tasks, so I tried to disable it, >> - wild magic appears - VMs didn`t crashed host any more, even in count >> 30+ they work fine. >> I still don`t know what exactly triggered that and will I face it >> again under different conditions, so my solution more likely to be a >> patch of mud in wall of the dam, instead of proper fixing. >> >> There seems to be two possible origins of such error - a very very >> hideous race condition involving cgroups and processes like qemu-kvm >> causing frequent context switches and simple incompatibility between >> NUMA, logic of CONFIG_SCHED_AUTOGROUP and qemu VMs already doing work >> in the cgroup, since I have not observed this errors on single numa >> node(mean, desktop) on relatively heavier condition. > > Yes, it would be important to track it down though. Enabling > slub_debug=ZFPU kernel parameter should help. > > Hi Marcelo, I have finally beat that one. As I have mentioned before in the off-list message, nested cgroups for vcpu/emulator threads created by libvirt was a root cause of this problem. Today we`ve disabled creation of cgroup deeper than qemu/vm/ level and trace didn`t showed up under different workloads. So for libvirt itself, it may be a feature request to create thread-based cgroups iff any element of the VM` config requires that. As for cgroups, seems it is fatal to have very large amount of nested elements inside cpu on qemu-kvm, or on very large amount of threads - since I have limited core amount on each node, I can`t prove what exactly, complicated cgroup hierarchy or some side effects putting threads on the dedicated cgroup, caused all this pain. And, of course, without Windows(tm) bug is very hard to observe in the wild, since almost no synthetic test I have put on the linux VMs is able to show it.

1 0

[libvirt-users] There's no output when connecting to console of domain on PowerPC
by Yin Olivia-R63875 31 Jan '13

31 Jan '13

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 architecture. */ char * qemuBuildChrDeviceStr(virDomainChrDefPtr serial, virBitmapPtr qemuCaps, char *os_arch, char *machine) { virBuffer cmd = VIR_BUFFER_INITIALIZER; if (STREQ(os_arch, "ppc64") && STREQ(machine, "pseries")) { if (serial->deviceType == VIR_DOMAIN_CHR_DEVICE_TYPE_SERIAL && serial->source.type == VIR_DOMAIN_CHR_TYPE_PTY && serial->info.type == VIR_DOMAIN_DEVICE_ADDRESS_TYPE_SPAPRVIO) { virBufferAsprintf(&cmd, "spapr-vty,chardev=char%s", serial->info.alias); if (qemuBuildDeviceAddressStr(&cmd, &serial->info, qemuCaps) < 0) goto error; } } else virBufferAsprintf(&cmd, "isa-serial,chardev=char%s,id=%s", serial->info.alias, serial->info.alias); if (virBufferError(&cmd)) { virReportOOMError(); goto error; } return virBufferContentAndReset(&cmd); error: virBufferFreeAndReset(&cmd); return NULL; } We usually connect guest with telnet. For instance, /usr/bin/qemu-system-ppc -name demo -M ppce500v2 -enable-kvm -m 256 -nographic -kernel /media/ram/uImage -initrd /media/ram/ramdisk -append "root=/dev/ram rw console=ttyS0,115200" -serial tcp::4445,server Then to run 'telnet 10.193.20.xxx 4445' could connect the guest. The temporary workaround is not add '-device' string after '-serial' option. diff -Nur libvirt-0.10.1.orig/src/qemu/qemu_command.c libvirt-0.10.1/src/qemu/qemu_command.c --- libvirt-0.10.1.orig/src/qemu/qemu_command.c 2012-08-30 15:35:18.000000000 +0530 +++ libvirt-0.10.1/src/qemu/qemu_command.c 2012-10-05 17:19:32.060368755 +0530 @@ -5501,13 +5501,15 @@ virCommandAddArg(cmd, devstr); VIR_FREE(devstr); - virCommandAddArg(cmd, "-device"); - if (!(devstr = qemuBuildChrDeviceStr(serial, qemuCaps, + if (!STREQ(def->os.arch, "ppc")) { + virCommandAddArg(cmd, "-device"); + if (!(devstr = qemuBuildChrDeviceStr(serial, qemuCaps, def->os.arch, def->os.machine))) - goto error; - virCommandAddArg(cmd, devstr); - VIR_FREE(devstr); + goto error; + virCommandAddArg(cmd, devstr); + VIR_FREE(devstr); + } } else { virCommandAddArg(cmd, "-serial"); if (!(devstr = qemuBuildChrArgStr(&serial->source, NULL))) Applying the above patch to libvirt, all the other domain control commands could work except 'virsh console domain'. # cat >demo.args <<EOF > /usr/bin/qemu-system-ppc -name demo -M ppce500v2 -enable-kvm -m 256 -nographic -kernel /media/ram/uImage -initrd /media/ram/ramdisk -append "root=/dev/ram rw console=ttyS0,115200" -serial tcp::4445,server -net nic > EOF # vi demo.args /usr/bin/qemu-system-ppc -name demo -M ppce500v2 -enable-kvm -m 256 -nographic -kernel /media/ram/uImage -initrd /media/ram/ramdisk -append "root=/dev/ram rw console=ttyS0,115200" -serial tcp::4445,server -net nic # virsh domxml-from-native qemu-argv demo.args >demo.xml # vi demo.xml <domain type='kvm'> <name>demo</name> <uuid>985d7154-83c8-0763-cbac-ecd159eee8a6</uuid> <memory unit='KiB'>262144</memory> <currentMemory unit='KiB'>262144</currentMemory> <vcpu placement='static'>1</vcpu> <os> <type arch='ppc' machine='ppce500v2'>hvm</type> <kernel>/media/ram/uImage</kernel> <initrd>/media/ram/ramdisk</initrd> <cmdline>root=/dev/ram rw console=ttyS0,115200</cmdline> </os> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/bin/qemu-system-ppc</emulator> <serial type='tcp'> <source mode='bind' host='' service='4445'/> <protocol type='raw'/> <target port='0'/> </serial> <console type='tcp'> <source mode='bind' host='' service='4445'/> <protocol type='raw'/> <target type='serial' port='0'/> </console> <memballoon model='virtio'/> </devices> </domain> # virsh -c qemu:///system define demo.xml # virsh -c qemu:///system start demo But it seemed that can't connect to the console. # virsh -c qemu:///system console demo Connected to domain test Escape character is ^] error: internal error character device (null) is not using a PTY I tried also use '-serial pty' option, /usr/bin/qemu-system-ppc -name test -M ppce500v2 -enable-kvm -m 256 -nographic -kernel /media/ram/uImage -initrd /media/ram/ramdisk -append "root=/dev/ram rw console=ttyS0,115200" -serial pty Then there's no other output after the below message: # virsh -c qemu:///system console demo Connected to domain test Escape character is ^] It seemed not libvirt group issue. I also tried the LXC. It could connect to the console if <init>/bin/sh/</init> instead of <init>/sbin/init</init> Best Regards, Olivia

1 0

[libvirt-users] VMs fail to start with NUMA configuration
by Doug Goldstein 31 Jan '13

31 Jan '13

I am using libvirt 0.10.2.2 and qemu-kvm 1.2.2 (qemu-kvm 1.2.0 + qemu 1.2.2 applied on top plus a number of stability patches). Having issue where my VMs fail to start with the following message: kvm_init_vcpu failed: Cannot allocate memory Following the instructions at http://libvirt.org/formatdomain.html#elementsNUMATuning I've added the following to my VCPU configuration: <vcpu placement='auto'>2</vcpu> Which libvirt expands out as I'd expect per the documentation to: <vcpu placement='auto'>2</vcpu> <numatune> <memory tune='strict' placement='auto'/> </numatune> However, the VMs won't start and the system is no low on memory. # numactl --hardware available: 8 nodes (0-7) node 0 cpus: 0 4 8 12 16 20 24 28 node 0 size: 16374 MB node 0 free: 11899 MB node 1 cpus: 32 36 40 44 48 52 56 60 node 1 size: 16384 MB node 1 free: 15318 MB node 2 cpus: 2 6 10 14 18 22 26 30 node 2 size: 16384 MB node 2 free: 15766 MB node 3 cpus: 34 38 42 46 50 54 58 62 node 3 size: 16384 MB node 3 free: 15347 MB node 4 cpus: 3 7 11 15 19 23 27 31 node 4 size: 16384 MB node 4 free: 15041 MB node 5 cpus: 35 39 43 47 51 55 59 63 node 5 size: 16384 MB node 5 free: 15202 MB node 6 cpus: 1 5 9 13 17 21 25 29 node 6 size: 16384 MB node 6 free: 15197 MB node 7 cpus: 33 37 41 45 49 53 57 61 node 7 size: 16368 MB node 7 free: 15669 MB The system has 4 Opteron 6272 which add up to a total of 64 cores, 16 cores per socket. These are the CPUs that Dan B noticed issues with in the past regarding topology but I thought this was resolved. But the capabilities are posted below, you'll notice the topology is incorrect. # virsh capabilities <capabilities> <host> <uuid>44454c4c-5300-1038-8031-c4c04f545331</uuid> <cpu> <arch>x86_64</arch> <model>Opteron_G4</model> <vendor>AMD</vendor> <topology sockets='1' cores='8' threads='2'/> <feature name='nodeid_msr'/> <feature name='wdt'/> <feature name='skinit'/> <feature name='ibs'/> <feature name='osvw'/> <feature name='cr8legacy'/> <feature name='extapic'/> <feature name='cmp_legacy'/> <feature name='fxsr_opt'/> <feature name='mmxext'/> <feature name='osxsave'/> <feature name='monitor'/> <feature name='ht'/> <feature name='vme'/> </cpu> <power_management> <suspend_disk/> </power_management> <migration_features> <live/> <uri_transports> <uri_transport>tcp</uri_transport> </uri_transports> </migration_features> <topology> <cells num='8'> <cell id='0'> <cpus num='8'> <cpu id='0'/> <cpu id='4'/> <cpu id='8'/> <cpu id='12'/> <cpu id='16'/> <cpu id='20'/> <cpu id='24'/> <cpu id='28'/> </cpus> </cell> <cell id='1'> <cpus num='8'> <cpu id='32'/> <cpu id='36'/> <cpu id='40'/> <cpu id='44'/> <cpu id='48'/> <cpu id='52'/> <cpu id='56'/> <cpu id='60'/> </cpus> </cell> <cell id='2'> <cpus num='8'> <cpu id='2'/> <cpu id='6'/> <cpu id='10'/> <cpu id='14'/> <cpu id='18'/> <cpu id='22'/> <cpu id='26'/> <cpu id='30'/> </cpus> </cell> <cell id='3'> <cpus num='8'> <cpu id='34'/> <cpu id='38'/> <cpu id='42'/> <cpu id='46'/> <cpu id='50'/> <cpu id='54'/> <cpu id='58'/> <cpu id='62'/> </cpus> </cell> <cell id='4'> <cpus num='8'> <cpu id='3'/> <cpu id='7'/> <cpu id='11'/> <cpu id='15'/> <cpu id='19'/> <cpu id='23'/> <cpu id='27'/> <cpu id='31'/> </cpus> </cell> <cell id='5'> <cpus num='8'> <cpu id='35'/> <cpu id='39'/> <cpu id='43'/> <cpu id='47'/> <cpu id='51'/> <cpu id='55'/> <cpu id='59'/> <cpu id='63'/> </cpus> </cell> <cell id='6'> <cpus num='8'> <cpu id='1'/> <cpu id='5'/> <cpu id='9'/> <cpu id='13'/> <cpu id='17'/> <cpu id='21'/> <cpu id='25'/> <cpu id='29'/> </cpus> </cell> <cell id='7'> <cpus num='8'> <cpu id='33'/> <cpu id='37'/> <cpu id='41'/> <cpu id='45'/> <cpu id='49'/> <cpu id='53'/> <cpu id='57'/> <cpu id='61'/> </cpus> </cell> </cells> </topology> <secmodel> <model>none</model> <doi>0</doi> </secmodel> <secmodel> <model>dac</model> <doi>0</doi> </secmodel> </host> <guest> <os_type>hvm</os_type> <arch name='i686'> <wordsize>32</wordsize> <emulator>/usr/bin/qemu-system-x86_64</emulator> <machine>pc-1.2</machine> <machine canonical='pc-1.2'>pc</machine> <machine>pc-1.1</machine> <machine>pc-1.0</machine> <machine>pc-0.15</machine> <machine>pc-0.14</machine> <machine>pc-0.13</machine> <machine>pc-0.12</machine> <machine>pc-0.11</machine> <machine>pc-0.10</machine> <machine>isapc</machine> <machine>none</machine> <domain type='qemu'> </domain> <domain type='kvm'> <emulator>/usr/bin/qemu-kvm</emulator> <machine>pc-1.2</machine> <machine canonical='pc-1.2'>pc</machine> <machine>pc-1.1</machine> <machine>pc-1.0</machine> <machine>pc-0.15</machine> <machine>pc-0.14</machine> <machine>pc-0.13</machine> <machine>pc-0.12</machine> <machine>pc-0.11</machine> <machine>pc-0.10</machine> <machine>isapc</machine> <machine>none</machine> </domain> </arch> <features> <cpuselection/> <deviceboot/> <pae/> <nonpae/> <acpi default='on' toggle='yes'/> <apic default='on' toggle='no'/> </features> </guest> <guest> <os_type>hvm</os_type> <arch name='x86_64'> <wordsize>64</wordsize> <emulator>/usr/bin/qemu-system-x86_64</emulator> <machine>pc-1.2</machine> <machine canonical='pc-1.2'>pc</machine> <machine>pc-1.1</machine> <machine>pc-1.0</machine> <machine>pc-0.15</machine> <machine>pc-0.14</machine> <machine>pc-0.13</machine> <machine>pc-0.12</machine> <machine>pc-0.11</machine> <machine>pc-0.10</machine> <machine>isapc</machine> <machine>none</machine> <domain type='qemu'> </domain> <domain type='kvm'> <emulator>/usr/bin/qemu-kvm</emulator> <machine>pc-1.2</machine> <machine canonical='pc-1.2'>pc</machine> <machine>pc-1.1</machine> <machine>pc-1.0</machine> <machine>pc-0.15</machine> <machine>pc-0.14</machine> <machine>pc-0.13</machine> <machine>pc-0.12</machine> <machine>pc-0.11</machine> <machine>pc-0.10</machine> <machine>isapc</machine> <machine>none</machine> </domain> </arch> <features> <cpuselection/> <deviceboot/> <acpi default='on' toggle='yes'/> <apic default='on' toggle='no'/> </features> </guest> </capabilities> Any suggestions are appreciated. -- Doug Goldstein

3 14

[libvirt-users] Libvirt support for windows
by varun bhatnagar 31 Jan '13

31 Jan '13

Hi, I want to use libvirt for windows but when i try to launch virsh it gives an error message saying "*error: invalid argument in transport methods unix, ssh and ext are not supported under Windows"* The version which I downloaded is libvirt-0.8.8.exe. I want to connect to two virtualization techniques --- *Virtualbox* and *VMWare* If libvirt is not supported on windows then is there any other tool or API which supports multiple virtualization technology? Thanks in advance..!!!!

1 0

[libvirt-users] Fail to build libvirt-sandbox under ubuntu 12.10
by pablo platt 30 Jan '13

30 Jan '13

I'm trying to build libvirt-sandbox under ubuntu 12.10 sudo apt-get install git build-essential lxc libvirt-bin libvirt-glib-1.0 libglib2.0-0 libglib2.0-dev gtk-doc-tools libxml2-dev libselinux-dev git clone git://libvirt.org/libvirt-sandbox.git cd libvirt-sandbox sudo ./autobuild The error I'm getting: make[2]: Entering directory `/home/user/libvirt-sandbox/build/bin' CC virt_sandbox-virt-sandbox.o CCLD virt-sandbox CC virt_sandbox_service_util-virt-sandbox-service-util.o make[2]: *** No rule to make target `container.c', needed by `virt_sandbox_service_util-container.o'. Stop. Am I doing something wrong? Thanks

2 5

[libvirt-users] http problem with (a particular url) and default (nat) networking
by John McFarlane 29 Jan '13

29 Jan '13

At work I have a script that provisions a vm for use by employees. One step in this process is to fetch hadoop, which we happen to get from cloudera. I noticed the script always failed when I used libvirt's default networking (nat) but worked fine when I used user mode networking. My instinct is that this is related to (potentially uncommon) network traffic from the server in question, and the iptables rules added by libvirt. Repro steps: 1. Create a vm (I tested with linux and freebsd guests) using default libvirt networking settings (<interface type='network'>). 2. wget, curl, fetch: http://archive.cloudera.com/one-click-install/lucid/cdh3-repository_1.0_all… Observe it will "hang". If you use strace you'll see it block on the select call. My particular host is using a virbr0 network bridge, with the following iptables rules: $ iptables -S -v -Z -P INPUT ACCEPT -c 404828 91071544 -P FORWARD ACCEPT -c 0 0 -P OUTPUT ACCEPT -c 402905 45139291 -A INPUT -i virbr0 -p udp -m udp --dport 53 -c 26 1703 -j ACCEPT -A INPUT -i virbr0 -p tcp -m tcp --dport 53 -c 0 0 -j ACCEPT -A INPUT -i virbr0 -p udp -m udp --dport 67 -c 70 22960 -j ACCEPT -A INPUT -i virbr0 -p tcp -m tcp --dport 67 -c 0 0 -j ACCEPT -A FORWARD -d 192.168.122.0/24 -o virbr0 -m state --state RELATED,ESTABLISHED -c 1191 1495856 -j ACCEPT -A FORWARD -s 192.168.122.0/24 -i virbr0 -c 853 64266 -j ACCEPT -A FORWARD -i virbr0 -o virbr0 -c 6 1968 -j ACCEPT -A FORWARD -o virbr0 -c 0 0 -j REJECT --reject-with icmp-port-unreachable -A FORWARD -i virbr0 -c 0 0 -j REJECT --reject-with icmp-port-unreachable Zeroing chain `INPUT' Zeroing chain `FORWARD' Zeroing chain `OUTPUT' I'm not sure how best to diagnose this problem. Any ideas or tips? Thanks! John M.

2 1

[libvirt-users] not able to stop vmware player node through libvirt API
by varun bhatnagar 29 Jan '13

29 Jan '13

Hi, I have started one node through libvirt API using its start method. I am trying to stop that node using the *destroy *method provided by the API but I am not able to do so. Instead, I am getting one message saying: *libvir: error: internal error Child process (vmrun -T player stop /root/test_folder/myImage.vmx soft) unexpected exit status 255* Can anybody tell me why I am not able to stop the node. Thanks in advance. :)

3 3

[libvirt-users] limit memory and CPU when using libvirt-sandbox
by pablo platt 29 Jan '13

29 Jan '13

I'm considering using virt-sandbox with lxc to sandbox and execute untrusted code like python scripts and compiled C code. Is it possible to limit CPU and Memory like is possible with lxc-execute and a config file? What are the defaults security settings? Is it completely isolated by default? What's the difference between lxc-execute and libvirt-sandbox? How can I use it in ubuntu? Thanks

2 2

[libvirt-users] Not able to do ssh with libvirt
by varun bhatnagar 25 Jan '13

25 Jan '13

Hi, I am having issue while doing *ssh* to a virtual node through libvirt. The nodes's ip address is 192.168.82.1. When I am giving the command it is giving the following error message: *virsh# connect vbox+ssh://192.168.82.1/session* *Password:* *error: Failed to connect to the hypervisor* *error: End of ifle while reading data: sh: nc: command not found: Input/output error.* Can anyone tell me why am I facing this problem and how to resolve it. Thanks in advance.

5 6

[libvirt-users] libvirt -- add virtio-scsi disk with scsi-generic
by 韩诚 25 Jan '13

25 Jan '13

Hi, Paolo, All, I read "virtio-scsi support proposal v2"(http://permalink.gmane.org/gmane.comp.emulators.libvirt/50428) Try to add a virtio-scsi with scsi-generic like this: <hostdev type='scsi'> <source> <adapter name='scsi_host0'/> <address type='scsi' bus='0' target='0' unit='0'/> </source> <target> <address type='scsi' controller='0' bus='0' target='0' unit='2'/> </target> </hostdev> But It turn out to be wrong, showing: error: Failed to define domain from rhel63ga error: XML error: unknown host device source address type 'scsi_host' I'd like to know how shall to add a virtio-scsi disk with scsi-generic option. Thanks~ -- Best regards, Cheng

3 4

[libvirt-users] virtual machine id
by 春祥王 23 Jan '13

23 Jan '13

Below is my start.xml: <domain type='kvm' id='12'> <name>start-ubuntu</name> <memory>1048576</memory> <currentMemory>1048576</currentMemory> <vcpu>1</vcpu> <os> <type>hvm</type> <boot dev='hd'/> ...... I start the machine virsh create start.xml virsh list Id Name State ---------------------------------------------------- 20 start-ubuntu running I set id=12,but it is actually 20,I don't know why. Thanks.

2 1

Re: [libvirt-users] snapshot troubles
by Christian Schmidt 23 Jan '13

23 Jan '13

Hi Juergen, if you are using kvm/qemu with libvirt you can try to delete the snapshot with the qemu monitor commands. The general syntax is virsh qemu-monitor-command --hmp <domain> '<command> [...]' So you can try virsh qemu-monitor-command --hmp DOMINO1-prealloc 'info snapshots' and thne delete it with the provided snapshot ID virsh qemu-monitor-command --hmp DOMINO1-prealloc 'delvm <ID>' This will delete the snapshot from your diskimage. Christian. On Di, 2013-01-22 at 18:00, libvirt-users-request(a)redhat.com wrote: > Message: 3 > Date: Mon, 21 Jan 2013 23:43:57 +0100 > From: jurgen.depicker(a)let.be > To: libvirt-users <libvirt-users(a)redhat.com> > Subject: [libvirt-users] snapshot troubles > Message-ID: > <OF4AE792B7.46B8D599-ONC1257AFA.0073C652-C1257AFA.007D0C38(a)let.be> > Content-Type: text/plain; charset="us-ascii" > > Dear all, > I created some snapshots, a long time ago, using the xml description > option, so the snapshots have a name with a space in it... > Really a bad choice apparently, since it seems impossible to delete > them > now: I cannot find how to enter the snapshot name properly due to the > space. Quotes don't seem to help; escaping the space doesn't help > either. > Anybody knows how to solve this? > eg: > snapshot-delete DOMINO1-prealloc --snapshotname 'W2K3-virgin install' > error: Domain snapshot not found: no snapshot with matching name > ''W2K3-virgin' > (-> notive also the extra ' added ) > > root@VLET3:~# time virsh snapshot-delete DOMINO1-prealloc > "W2K3-virgin\ > install" > error: unexpected data 'install' > > Thanks, Juergen >

3 2

[libvirt-users] snapshot troubles
by jurgen.depicker＠let.be 23 Jan '13

23 Jan '13

Dear all, I created some snapshots, a long time ago, using the xml description option, so the snapshots have a name with a space in it... Really a bad choice apparently, since it seems impossible to delete them now: I cannot find how to enter the snapshot name properly due to the space. Quotes don't seem to help; escaping the space doesn't help either. Anybody knows how to solve this? eg: snapshot-delete DOMINO1-prealloc --snapshotname 'W2K3-virgin install' error: Domain snapshot not found: no snapshot with matching name ''W2K3-virgin' (-> notive also the extra ' added ) root@VLET3:~# time virsh snapshot-delete DOMINO1-prealloc "W2K3-virgin\ install" error: unexpected data 'install' Thanks, Juergen

2 4

[libvirt-users] Fwd: problem with libvirt
by rakshith h p 23 Jan '13

23 Jan '13

HI, i'm rakshith from bangalore. I'm using libvirt in one of my work. I have a problem in using it.So i would request your guidance. I have a controller which uses libvirt to establish the connection to the managed nodes. After the connection is successful, if the network goes down, the control will indefinitely wait inside the libvirt mod functions. It will come out only after the network is back and required data is obtained. In this case i need to add time out and get the control back once the data is not available and throw an exception. Can u please tell if there is any way i can do it.Thanks in advance -- Thanks and regards Rakshith H P Mobile - +919844303929

1 0

[libvirt-users] Fwd problem with libvirt
by rakshith h p 23 Jan '13

23 Jan '13

---------- Forwarded message ---------- From: "rakshith h p" <hpr3929(a)gmail.com> Date: 22 Jan 2013 22:10 Subject: problem with libvirt To: <berrange(a)redhat.com> Cc: HI, i'm rakshith from bangalore. I'm using libvirt in one of my work. I have a problem in using it.So i would request your guidance. I have a controller which uses libvirt to establish the connection to the managed nodes. After the connection is successful, if the network goes down, the control will indefinitely wait inside the libvirt mod functions. It will come out only after the network is back and required data is obtained. In this case i need to add time out and get the control back once the data is not available and throw an exception. Can u please tell if there is any way i can do it.Thanks in advance -- Thanks and regards Rakshith H P Mobile - +919844303929

1 0

[libvirt-users] Question about blkiotune.device_weight
by hzguanqiang 22 Jan '13

22 Jan '13

Hi, Hu Tao I noticed that in your patch about blkiotune.device_weight, You set the device blkio weight value between 100 and 1000. But from the kernel document, I see that the blkio weight can be set from 10 to 1000. Why do you limit the weight minimum to 100 rather than 10 ? Looking forward your explanation, thanks! -------------- Best regards! GuanQiang 2013-01-18

3 2

[libvirt-users] error on startup
by Bryan D. Payne 22 Jan '13

22 Jan '13

I'm running libvirt 1.0.1 and qemu 1.3. I see the following error of libvirtd startup: 2013-01-19 04:51:06.183+0000: 1459: error : virCommandWait:2287 : internal error Child process (LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin HOME=/ /usr/bin/kvm -help) unexpected exit status 1 This is indeed what the return code seems to be for that command. This this just a version issue with libvirt and qemu or ?? root@host:~# kvm -help usage: qemu-x86_64 [options] program [arguments...] Linux CPU emulator (compiled for x86_64 emulation) Options and associated environment variables: Argument Env-variable Description -h print this help -g port QEMU_GDB wait gdb connection to 'port' -L path QEMU_LD_PREFIX set the elf interpreter prefix to 'path' -s size QEMU_STACK_SIZE set the stack size to 'size' bytes -cpu model QEMU_CPU select CPU (-cpu help for list) -E var=value QEMU_SET_ENV sets targets environment variable (see below) -U var QEMU_UNSET_ENV unsets targets environment variable (see below) -0 argv0 QEMU_ARGV0 forces target process argv[0] to be 'argv0' -r uname QEMU_UNAME set qemu uname release string to 'uname' -B address QEMU_GUEST_BASE set guest_base address to 'address' -R size QEMU_RESERVED_VA reserve 'size' bytes for guest virtual address space -d options QEMU_LOG activate log -D logfile QEMU_LOG_FILENAME override default logfile location -p pagesize QEMU_PAGESIZE set the host page size to 'pagesize' -singlestep QEMU_SINGLESTEP run in singlestep mode -strace QEMU_STRACE log system calls -version QEMU_VERSION display version information and exit Defaults: QEMU_LD_PREFIX = /usr/gnemul/qemu-x86_64 QEMU_STACK_SIZE = 8388608 byte QEMU_LOG = /tmp/qemu.log You can use -E and -U options or the QEMU_SET_ENV and QEMU_UNSET_ENV environment variables to set and unset environment variables for the target process. It is possible to provide several variables by separating them by commas in getsubopt(3) style. Additionally it is possible to provide the -E and -U options multiple times. The following lines are equivalent: -E var1=val2 -E var2=val2 -U LD_PRELOAD -U LD_DEBUG -E var1=val2,var2=val2 -U LD_PRELOAD,LD_DEBUG QEMU_SET_ENV=var1=val2,var2=val2 QEMU_UNSET_ENV=LD_PRELOAD,LD_DEBUG Note that if you provide several changes to a single variable the last change will stay in effect. root@host:~# echo $? 1 Thanks, -bryan

2 2

[libvirt-users] Cannot get eth0 to work on libvirt-lxc
by Marco Monteiro 19 Jan '13

19 Jan '13

I'm trying to get an Archlinux guest running on a Archlinux host. Everything works except ethernet. When I boot the host, --- # dmesg |tail [ 8.265493] Bridge firewalling registered [ 8.514547] IPv6: ADDRCONF(NETDEV_UP): virbr0: link is not ready [ 8.645303] ip6_tables: (C) 2000-2006 Netfilter Core Team --- Then I do --- # virsh -c lxc:/// start gitolite Domain gitolite started # dmesg |tail [ 348.793398] device veth0 entered promiscuous mode [ 348.793553] IPv6: ADDRCONF(NETDEV_UP): veth0: link is not ready [ 348.997973] IPv6: ADDRCONF(NETDEV_CHANGE): veth0: link becomes ready [ 348.997998] virbr0: topology change detected, propagating [ 348.998001] virbr0: port 1(veth0) entered forwarding state [ 348.998008] virbr0: port 1(veth0) entered forwarding state [ 348.998017] IPv6: ADDRCONF(NETDEV_CHANGE): virbr0: link becomes ready [ 349.784174] EXT4-fs (xvdg): re-mounted. Opts: (null) --- Then I enter the guest and do --- # ip link 5: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT qlen 1000 link/ether 02:00:00:00:00:17 brd ff:ff:ff:ff:ff:ff 7: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN mode DEFAULT link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 --- So, eth0 exists. Now, still in the guest: --- # systemctl start dhcpcd@eth0 A dependency job for dhcpcd(a)eth0.service failed. See 'journalctl -xn' for details. # journalctl -xn -- Logs begin at Sat 2013-01-19 10:50:45 UTC, end at Sat 2013-01-19 10:56:26 UTC Jan 19 10:54:48 gitolite sudo[38]: pam_unix(sudo:session): session opened for us Jan 19 10:54:48 gitolite systemd[1]: Expecting device sys-subsystem-net-devices- -- Subject: Unit sys-subsystem-net-devices-eth0.device has begun with start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/7d495 -- -- Unit sys-subsystem-net-devices-eth0.device has begun starting up. Jan 19 10:56:18 gitolite systemd[1]: Job sys-subsystem-net-devices-eth0.device/s Jan 19 10:56:18 gitolite systemd[1]: Timed out waiting for device sys-subsystem- -- Subject: Unit sys-subsystem-net-devices-eth0.device has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/be02c -- -- Unit sys-subsystem-net-devices-eth0.device has failed. -- -- The result is timeout. Jan 19 10:56:18 gitolite systemd[1]: Dependency failed for dhcpcd on eth0. -- Subject: Unit dhcpcd(a)eth0.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/be02c -- -- Unit dhcpcd(a)eth0.service has failed. -- -- The result is dependency. --- At this point, nothing new in dmesg. Even though ip link should a eth0 device, the sys-subsystem-net-devices-eth0.device has failed? I don't understand this. This is libvirt 1.0.1 in linux 2.6.11. I tried with both systemd 197 and (thinking that recent changes with device naming could be the problem) with 196. It didn't work on either. The domain configuration is: --- <domain type='lxc'> <name>gitolite</name> <uuid>3122bf1d-11bb-0dd8-be64-7e352b3f8694</uuid> <memory unit='KiB'>262144</memory> <currentMemory unit='KiB'>262144</currentMemory> <vcpu placement='static'>1</vcpu> <os> <type arch='x86_64'>exe</type> <init>/sbin/init</init> </os> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/lib/libvirt/libvirt_lxc</emulator> <filesystem type='mount' accessmode='passthrough'> <source dir='/mnt/gitolite'/> <target dir='/'/> </filesystem> <interface type='network'> <mac address='02:00:00:00:00:17'/> <source network='default'/> </interface> <console type='pty'> <target type='lxc' port='0'/> </console> </devices> </domain> --- I also tried using bridged networking configuration but I see the same problem. What could be causing this? Any ideas? Thanks, Marco

1 0

[libvirt-users] Problems with VM networking on Ubuntu Quantal
by Dale Amon 18 Jan '13

18 Jan '13

I have shifted some VM's to a new server running Quantal and have had a world of trouble. The first one was caused by issues with an apparently compiled in path in their apparmor version which forced VM pools to be in /srv or similar rather than where I wanted them. For now this was not a big issue, and thankfully the server where it would be a big time problem (there are individual drives per major customer or user) is Debian. But... I still have issues. The networking has changed considerably and although I can get my VM running, I cannot reach it. The new quantal machines give you something like this: br0 Link encap:Ethernet HWaddr **** inet addr:10.0.0.xx Bcast:10.0.0.255 Mask:255.255.255.0 inet6 addr: *****/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 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:16436 Metric:1 p6p1 Link encap:Ethernet HWaddr **** UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 virbr0 Link encap:Ethernet HWaddr **** inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 UP BROADCAST MULTICAST MTU:1500 Metric:1 vnet0 Link encap:Ethernet HWaddr fe:54:00:84:3c:4f inet6 addr: fe80::fc54:ff:fe84:3c4f/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 The VM machine has a static ip on the same network, ie 10.0.0.x. It worked fine on the old server but is not reachable (and cannot connect outward). Forwarding is turned on: cat /proc/sys/net/ipv4/ip_forward 1 The VM has eth0 Link encap:Ethernet HWaddr **** inet addr:10.0.0.xx Bcast:10.0.0.255 Mask:255.255.255.0 inet6 addr: *****/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 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:16436 Metric:1 An attempt to ping from the VM to anything outside gives a "Destination host unreachable" message. It has been a long time since I set the old machine up, so I may well have forgotten some step.

2 2

[libvirt-users] how to know one domain is defined or not
by lei yang 18 Jan '13

18 Jan '13

Hi experts I want to write a script to determine one domain named "vm1" is defined or not, if defined, I will undefine it. The question is how could I know it define or not ? Lei

3 3

[libvirt-users] Libvirt node is not getting booted through network with KVM too
by Varun Bhatnagar 18 Jan '13

18 Jan '13

Hi, Sorry for putting the images. Posting this question again. I am trying to boot my node through network with the following configuration (even with KVM it is not getting booted): < domain type='kvm'> < name>Node-2-3</name> < os> < type>hvm</type> < boot dev='network'/> < boot dev='hd'/> < /os> < memory>654321</memory> < vcpu>1</vcpu> < interface type='internal'> < source name='test1'/> < model type='am79c970a'/> < mac address='20:00:00:0F:03:01'/> < /interface> < interface type='internal'> < source name='test2'/> < model type='am79c970a'/> < mac address='20:00:00:0F:03:02'/> < /interface>  < interface type='bridge'> < source bridge='vboxtap0'/> < mac address='20:00:00:0F:03:03'/> < model type='am79c973'/> < /interface> < /domain> But I am getting an error message saying: Fatal: Could not read from the boot medium! System halted. Even my network setting is not getting reflected in the Virtualbox. Can you suggest me what is wrong with this configuration. I think to boot a node from network we need to define a boot server but where shall I add that, I am confused.... Any help will be appreciated. Thanks in advance. Regards, Varun =====-----=====-----===== Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you

2 1

[libvirt-users] firewalld, no dhcp and virsh
by Paul Wouters 18 Jan '13

18 Jan '13

On all of the networks I create, I really don't want libvirt/KVM/virt-manager to do any kind of DHCP. I'm currently using xml files to feed into libvirt via virsh, for example: <network> <name>192_0_1</name> <bridge name='swan01' stp='on' delay='0' /> <mac address='12:00:00:16:16:BA'/> <ip address='192.0.1.127' netmask='255.255.255.0'> </ip> </network> Running this through virsh net-define gives no errors, and virt-manager shows: DHCP Start: disabled DHCP End: disabled But any attempt at starting the network causes: Error starting network '192_0_1': failed to add iptables rule to allow DHCP requests from 'swan01' Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 96, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/asyncjob.py", line 117, in tmpcb callback(*args, **kwargs) File "/usr/share/virt-manager/virtManager/network.py", line 82, in start self.net.create() File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2049, in create if ret == -1: raise libvirtError ('virNetworkCreate() failed', net=self) libvirtError: failed to add iptables rule to allow DHCP requests from 'swan01' I narrowed this down to the fact that firewalld was not running. So I guess there are two bugs: 1) when not specifying dhcp ranges in the xml, it should _not_ try to poke DHCP holes. 2) when firewalld is not running, it should perhaps log a warning, but not abort the network start. Paul

2 1