- Users - libvirt List Archives

[libvirt-users] correct way to hot-add cdrom ?
by Alexandr 06 Dec '13

06 Dec '13

Good day to all. i have problems with cdrom hot adding code. currently i using virDomainAttachDevice with type=file, device=cdrom, dev=hdc, this code works for machine with one ide hdd and one ide cdrom, but this not work for machine with only one ide hdd, and i looking for solution to hot add cdrom to machine independent of existing devices or i need way to determinate which target device can be attached to vm. thanks in advance for any help.

3 3

[libvirt-users] how to add/remove emulated usb removable devices to guests
by Alexandr 06 Dec '13

06 Dec '13

Good day, i was not able to find api to add/remove usb removable devices to guest, i have windows machines and need to plug usb stick with some fs (fat or ntfs) which is image on host, i was found what it is possible and implemented in libvirt https://bugzilla.redhat.com/show_bug.cgi?id=922495, but i can't find how to use this.

2 1

[libvirt-users] libvirt, Open vSwitch and iptables
by Yoann Juet 06 Dec '13

06 Dec '13

Hi all, We're using since a long time libvirt with KVM guest machines and linux bridges. Firewall rules based on iptables and defined on the host server control inbound/outbound traffic to/from each VM. In order to improve remote administration facility and get extra services, it makes sense for us to replace linux bridges with Open vSwitch. However, the side effect is the solution's inability to filter VM traffic since it's impossible to set-up iptables rules with ovs bridges. OpenStack/Quantum circumvents this problem (no talking about performance) by setting an extra linux bridge and veth pair between the guest TAP and ovs. Is there {a simple|an alternative} solution to achieve it without installing the OpenStack/Quantum layer ? Thanks, Regards, -- Université de Nantes - Direction des Systèmes d'Information IM jabber: yoann.juet(a)univ-nantes.fr

1 0

Re: [libvirt-users] Virsh snapshots
by Juraj Melo 05 Dec '13

05 Dec '13

Thanks for your answer, I am trying to make a snapshot of whole virtual machine (disk, CPU state, memory). But I need to make this snapshot in matter of seconds. I have already try to create snapshot of disk, which is not problem. I use qcow2 format, and create new disk image using original disk image as backing file. But still I am not able to assign state of vm with new disk. I have found some commands for creating snapshots in libvirt API, so in my opinion one way how to accomplish my task is to create utility using theese commands, and create snapshot of vm in RAM - I hope it would be faster. But I wonder whether virsh contains similar functionality, so I won't need to programm it again. Dne 2.12.2013 19:32, Eric Blake napsal(a): On 12/02/2013 09:04 AM, Juraj Melo wrote: > Hello, > > I am working on my PhD thesis and it would be really helpfull if someone > could advise me, whether can Virsh create snapshots of VMs using > copy-on-write. What are you trying to copy-on-write? Is it just disk state, or VM memory state? Do you have corresponding qemu commands that you are trying to figure out if virsh maps to those same commands? There's a lot of flexibility in the virsh snapshot XML, but not all of it has been wired up yet (in part because it's still a moving target for what upstream qemu supports), so knowing more details about what you are trying to do will help us better answer whether it can be done now and if so with which commands.

3 2

[libvirt-users] libvirt, lvm thin provisioning
by Michael Mol 04 Dec '13

04 Dec '13

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?

3 5

[libvirt-users] cputune shares with multiple cpu and pinning
by Edoardo Comar 04 Dec '13

04 Dec '13

Hi, I have found the cpu time partitioning based on cpu shares weights not very intuitive. On RHEL64, I deployed two qemu/kvm VMs VM1 with 1 vcpu and 512 cpu shares VM2 with 2 vcpus and 1024 cpu shares I pinned their vcpus to specific host pcpus: VM1 vcpu 0 to host pcpu1 VM2 vcpu 0 to host pcpu1, VM2 vcpu 1 to host pcpu2 I executed inside the VMs a simple process that consume all available cpu, eg # cat /dev/zero > /dev/null on the host, using 'top', the reported cpu usage per qemu process is : with 1 process in VM1 and 1 process on vcpu1 in VM2 VM1 = 100%, VM2=100% explanation - without contention for pcpu2 shares are to be irrelevant (that's ok!) with 1 process in VM1 and 1 process on vcpu0 in VM2 VM1=33%, VM2=66% explanation - with contention on pcpu2, host cpu usage is partitioned according to shares (that's ok!) with 1 process in VM1, and 2 processes in VM2 (one on vcpu0 and on vcpu1 - launched with taskset) VM1=50%, VM2=150% This result was a bit unexpected to me: adding load on VM2 resulted in more cpu time allowed for VM1 - can anyone please explain the logic ? Changing the pinning so that both VMs can use the host pcpuset 1-2 then the CPU usage is 100%/100% when VM2 is executing one task only ( on whatever vcpu ) 50%/150% when VM2 is executing two tasks. again, not intuitive just by looking at the shares weights, I think. -------------------------------------------------- Edoardo Comar WebSphere Application Service Platform for Networks (ASPN) ecomar(a)uk.ibm.com +44 (0)1962 81 5576 IBM UK Ltd, Hursley Park, SO21 2JN Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

1 0

[libvirt-users] virsh iface-list fail
by Slash Sda 04 Dec '13

04 Dec '13

Hi all, I'm using libvirt 1.1.1 on my ubuntu 13.10 minimal. When I try a virsh iface-list i get this message: error: Failed to list interfaces error: internal error: failed to get number of host interfaces I create a BR0 thru my ETH0. On my virt-manager i don't see the computer interfaces What could it be? Thanks

1 0

[libvirt-users] error: Failed to start domain
by Stefan G. Weichinger 04 Dec '13

04 Dec '13

On a gentoo server with libvirt-1.1.3 I get problems with starting VMs. When I do: # virsh start vm180 error: Failed to start domain vm180 error: Input/output error This happens with 1.1.3 and 1.1.4 (I rebuilt the packages and restarted the libvirtd.service). # journalctl -f -u libvirtd.service shows: Dec 03 17:32:56 jupiter libvirtd[24020]: Input/output error Dec 03 17:33:47 jupiter libvirtd[24020]: Input/output error The log for the specific VM shows: 2013-12-03 16:33:47.004+0000: starting up LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin QEMU_AUDIO_DRV=none /usr/bin/qemu-kvm -name vm180 -S -machine pc-i440fx-1.5,accel=kvm,usb=off -cpu Opteron_G5,+bmi1,+perfctr_nb,+perfctr_core,+topoext,+nodeid_msr,+tce,+lwp,+wdt,+skinit,+ibs,+osvw,+cr8legacy,+extapic,+cmp_legacy,+fxsr_opt,+mmxext,+osxsave,+monitor,+ht,+vme -m 3954 -realtime mlock=off -smp 4,sockets=4,cores=1,threads=1 -uuid 646f757f-2ab7-4fdf-2140-a79396200c6f -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/vm180.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime,clock=vm,driftfix=slew -no-kvm-pit-reinjection -no-hpet -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/dev/VG01/vm180_disk0,if=none,id=drive-virtio-disk0,format=raw,cache=none,aio=threads -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive file=/mnt/tests/grml64-full_2013.02.iso,if=none,id=drive-ide0-1-0,readonly=on,format=raw -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev tap,fd=27,id=hostnet0,vhost=on,vhostfd=28 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:8d:3b:af,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -vnc 127.0.0.1:5 -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 2013-12-03 16:33:47.013+0000: shutting down libvirt: error : libvirtd quit during handshake: Input/output error What can I do about this issue? Thanks for any pointers, Stefan

1 2

[libvirt-users] help about migration with libvirt
by lei yang 04 Dec '13

04 Dec '13

Hi experts I want to use libvirt doing the migration migration the guest from core 0 to core 2, Is there a way to do this ? any points? Lei

3 4

[libvirt-users] layer2 tunnel between guests across hosts
by sujay g 04 Dec '13

04 Dec '13

Hi, Is it possible to setup layer2 tunnels between guests across hosts? Using vrbr? -- i.e the Guest is unaware. On Host 1: guest (a) --- vrbr0 ------- | | On Host 2: | guest(b) -- vrbr0 ------ Has there been any work done around it? TIA, -Sujay

2 1

[libvirt-users] run libvirt API on arm hardware platform
by 林佳緯 04 Dec '13

04 Dec '13

Hi all, Is it possible to run libvirt API on arm hardware platform? (i,e. armv7) Or any work done to work around it? Thanks Gavin

3 2

[libvirt-users] Problem booting guest with more than 8 disks
by Jon 03 Dec '13

03 Dec '13

Hello All, On my host machine, I'm using kvm, libvirt, ceph and ubuntu versions as follows: >> QEMU emulator version 1.5.0 (Debian 1.5.0+dfsg-3ubuntu5), Copyright (c) 2003-2008 Fabrice Bellard >> root@kitt:~# virsh --version: 1.1.1 >> ceph version 0.67.4 (ad85b8bfafea6232d64cb7ba76a8b6e8252fa0c7) >> VERSION="13.10, Saucy Salamander" >> Linux kitt 3.11.0-13-generic #20-Ubuntu SMP Wed Oct 23 07:38:26 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux I'm encountering an issue when attempting to boot a VM with more than eight disks, the boot disk is not found and the vm fails to boot with an error "No bootable device". This happens with Archlinux, Ubuntu. and Fedora images. I'm working on a tool [1] to build virtual machines, it creates rbd images named $hostname-os and $hostname-storageX (where X is the "additional disk number" starting at 0, a vm with seven disks would have one named -os and six named -storage{0..5})--the os disk is a clone of a protected COW RBD snapshot--the the tool defines the xml and uses Sys::Virt to define and boot the virtual machine. All os types use grub, ubuntu and fedora use an mbr and arch uses gpt, I'm not certain that matters as vms with less than six disks boot no problem. I've included both my generated and dumped xml for both my booting and non booting vms. The only consistent difference between the vm deployments is the addition on $hostname-storage6. Is there perhaps a way to specify which hd is the boot device? I appreciate any assistance. Thanks, Jon A [1] https://github.com/three18ti/Build-VM non Booting VM: ######################################################### # Generated: | <domain type='kvm'> | <name>arch_test2</name> | <memory unit='KiB'>4194304</memory> | <currentMemory unit='KiB'>4194304</currentMemory> | <vcpu placement='static'>2</vcpu> | <os> | <type arch='x86_64' machine='pc-i440fx-1.4'>hvm</type> | <boot dev='hd'/> | <bootmenu enable='no'/> | </os> | <features> | <acpi/> | <apic/> | <pae/> | </features> | <clock offset='utc'/> | <on_poweroff>destroy</on_poweroff> | <on_reboot>restart</on_reboot> | <on_crash>restart</on_crash> | <devices> | <emulator>/usr/bin/kvm</emulator> | <disk type='network' device='disk'> | <driver name='qemu'/> | <source protocol='rbd' name='libvirt-pool/arch_test2-os'> | <host name='192.168.0.35' port='6789'/> | <host name='192.168.0.2' port='6789'/> | <host name='192.168.0.40' port='6789'/> | </source> | <target dev='vda' bus='virtio' /> | </disk> | <disk type='network' device='disk'> | <driver name='qemu'/> | <source protocol='rbd' name='libvirt-pool/arch_test2-storage0'> | <host name='192.168.0.35' port='6789'/> | <host name='192.168.0.2' port='6789'/> | <host name='192.168.0.40' port='6789'/> | </source> | <target dev='vdb' bus='virtio' /> | </disk> | <disk type='network' device='disk'> | <driver name='qemu'/> | <source protocol='rbd' name='libvirt-pool/arch_test2-storage1'> | <host name='192.168.0.35' port='6789'/> | <host name='192.168.0.2' port='6789'/> | <host name='192.168.0.40' port='6789'/> | </source> | <target dev='vdc' bus='virtio' /> | </disk> | <disk type='network' device='disk'> | <driver name='qemu'/> | <source protocol='rbd' name='libvirt-pool/arch_test2-storage2'> | <host name='192.168.0.35' port='6789'/> | <host name='192.168.0.2' port='6789'/> | <host name='192.168.0.40' port='6789'/> | </source> | <target dev='vdd' bus='virtio' /> | </disk> | <disk type='network' device='disk'> | <driver name='qemu'/> | <source protocol='rbd' name='libvirt-pool/arch_test2-storage3'> | <host name='192.168.0.35' port='6789'/> | <host name='192.168.0.2' port='6789'/> | <host name='192.168.0.40' port='6789'/> | </source> | <target dev='vde' bus='virtio' /> | </disk> | <disk type='network' device='disk'> | <driver name='qemu'/> | <source protocol='rbd' name='libvirt-pool/arch_test2-storage4'> | <host name='192.168.0.35' port='6789'/> | <host name='192.168.0.2' port='6789'/> | <host name='192.168.0.40' port='6789'/> | </source> | <target dev='vdf' bus='virtio' /> | </disk> | <disk type='network' device='disk'> | <driver name='qemu'/> | <source protocol='rbd' name='libvirt-pool/arch_test2-storage5'> | <host name='192.168.0.35' port='6789'/> | <host name='192.168.0.2' port='6789'/> | <host name='192.168.0.40' port='6789'/> | </source> | <target dev='vdg' bus='virtio' /> | </disk> | <disk type='network' device='disk'> | <driver name='qemu'/> | <source protocol='rbd' name='libvirt-pool/arch_test2-storage6'> | <host name='192.168.0.35' port='6789'/> | <host name='192.168.0.2' port='6789'/> | <host name='192.168.0.40' port='6789'/> | </source> | <target dev='vdh' bus='virtio' /> | </disk> | <interface type='bridge'> | <source bridge='ovsbr0'/> | <virtualport type='openvswitch'> | </virtualport> | <model type='virtio'/> | </interface> | | <controller type='usb' index='0'> | </controller> | <controller type='ide' index='0'> | </controller> | <controller type='virtio-serial' index='0'> | </controller> | <serial type='pty'> | <target port='0'/> | </serial> | <console type='pty'> | <target type='serial' port='0'/> | </console> | <input type='mouse' bus='ps2'/> | <graphics type='vnc' port='-1' autoport='yes'/> | <sound model='ich6'> | </sound> | | <video> | <model type='cirrus' vram='9216' heads='1'/> | </video> | | <memballoon model='virtio'> | </memballoon> | | </devices> | </domain> ##### ------------------------------------------------------------------------------------------------------------- ##### # Dumped | <domain type='kvm' id='171'> | <name>arch_test2</name> | <uuid>fcff77f4-0a93-43f9-bf3a-e5863b787400</uuid> | <memory unit='KiB'>4194304</memory> | <currentMemory unit='KiB'>4194304</currentMemory> | <vcpu placement='static'>2</vcpu> | <resource> | <partition>/machine</partition> | </resource> | <os> | <type arch='x86_64' machine='pc-i440fx-1.4'>hvm</type> | <boot dev='hd'/> | <bootmenu enable='no'/> | </os> | <features> | <acpi/> | <apic/> | <pae/> | </features> | <clock offset='utc'/> | <on_poweroff>destroy</on_poweroff> | <on_reboot>restart</on_reboot> | <on_crash>restart</on_crash> | <devices> | <emulator>/usr/bin/kvm</emulator> | <disk type='network' device='disk'> | <driver name='qemu'/> | <source protocol='rbd' name='libvirt-pool/arch_test2-os'> | <host name='192.168.0.35' port='6789'/> | <host name='192.168.0.2' port='6789'/> | <host name='192.168.0.40' port='6789'/> | </source> | <target dev='vda' bus='virtio'/> | <alias name='virtio-disk0'/> | <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> | </disk> | <disk type='network' device='disk'> | <driver name='qemu'/> | <source protocol='rbd' name='libvirt-pool/arch_test2-storage0'> | <host name='192.168.0.35' port='6789'/> | <host name='192.168.0.2' port='6789'/> | <host name='192.168.0.40' port='6789'/> | </source> | <target dev='vdb' bus='virtio'/> | <alias name='virtio-disk1'/> | <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> | </disk> | <disk type='network' device='disk'> | <driver name='qemu'/> | <source protocol='rbd' name='libvirt-pool/arch_test2-storage1'> | <host name='192.168.0.35' port='6789'/> | <host name='192.168.0.2' port='6789'/> | <host name='192.168.0.40' port='6789'/> | </source> | <target dev='vdc' bus='virtio'/> | <alias name='virtio-disk2'/> | <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> | </disk> | <disk type='network' device='disk'> | <driver name='qemu'/> | <source protocol='rbd' name='libvirt-pool/arch_test2-storage2'> | <host name='192.168.0.35' port='6789'/> | <host name='192.168.0.2' port='6789'/> | <host name='192.168.0.40' port='6789'/> | </source> | <target dev='vdd' bus='virtio'/> | <alias name='virtio-disk3'/> | <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> | </disk> | <disk type='network' device='disk'> | <driver name='qemu'/> | <source protocol='rbd' name='libvirt-pool/arch_test2-storage3'> | <host name='192.168.0.35' port='6789'/> | <host name='192.168.0.2' port='6789'/> | <host name='192.168.0.40' port='6789'/> | </source> | <target dev='vde' bus='virtio'/> | <alias name='virtio-disk4'/> | <address type='pci' domain='0x0000' bus='0x00' slot='0x0a' function='0x0'/> | </disk> | <disk type='network' device='disk'> | <driver name='qemu'/> | <source protocol='rbd' name='libvirt-pool/arch_test2-storage4'> | <host name='192.168.0.35' port='6789'/> | <host name='192.168.0.2' port='6789'/> | <host name='192.168.0.40' port='6789'/> | </source> | <target dev='vdf' bus='virtio'/> | <alias name='virtio-disk5'/> | <address type='pci' domain='0x0000' bus='0x00' slot='0x0b' function='0x0'/> | </disk> | <disk type='network' device='disk'> | <driver name='qemu'/> | <source protocol='rbd' name='libvirt-pool/arch_test2-storage5'> | <host name='192.168.0.35' port='6789'/> | <host name='192.168.0.2' port='6789'/> | <host name='192.168.0.40' port='6789'/> | </source> | <target dev='vdg' bus='virtio'/> | <alias name='virtio-disk6'/> | <address type='pci' domain='0x0000' bus='0x00' slot='0x0c' function='0x0'/> | </disk> | <disk type='network' device='disk'> | <driver name='qemu'/> | <source protocol='rbd' name='libvirt-pool/arch_test2-storage6'> | <host name='192.168.0.35' port='6789'/> | <host name='192.168.0.2' port='6789'/> | <host name='192.168.0.40' port='6789'/> | </source> | <target dev='vdh' bus='virtio'/> | <alias name='virtio-disk7'/> | <address type='pci' domain='0x0000' bus='0x00' slot='0x0d' function='0x0'/> | </disk> | <controller type='usb' index='0'> | <alias name='usb0'/> | <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> | </controller> | <controller type='ide' index='0'> | <alias name='ide0'/> | <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> | </controller> | <controller type='virtio-serial' index='0'> | <alias name='virtio-serial0'/> | <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> | </controller> | <controller type='pci' index='0' model='pci-root'> | <alias name='pci0'/> | </controller> | <interface type='bridge'> | <mac address='52:54:00:c2:64:72'/> | <source bridge='ovsbr0'/> | <virtualport type='openvswitch'> | <parameters interfaceid='51324f0c-e98f-419e-aa82-ef9942c27eea'/> | </virtualport> | <target dev='vnet4'/> | <model type='virtio'/> | <alias name='net0'/> | <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> | </interface> | <serial type='pty'> | <source path='/dev/pts/13'/> | <target port='0'/> | <alias name='serial0'/> | </serial> | <console type='pty' tty='/dev/pts/13'> | <source path='/dev/pts/13'/> | <target type='serial' port='0'/> | <alias name='serial0'/> | </console> | <input type='mouse' bus='ps2'/> | <graphics type='vnc' port='5904' autoport='yes' listen='127.0.0.1'> | <listen type='address' address='127.0.0.1'/> | </graphics> | <sound model='ich6'> | <alias name='sound0'/> | <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> | </sound> | <video> | <model type='cirrus' vram='9216' heads='1'/> | <alias name='video0'/> | <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> | </video> | <memballoon model='virtio'> | <alias name='balloon0'/> | <address type='pci' domain='0x0000' bus='0x00' slot='0x0e' function='0x0'/> | </memballoon> | </devices> | <seclabel type='dynamic' model='apparmor' relabel='yes'> | <label>libvirt-fcff77f4-0a93-43f9-bf3a-e5863b787400</label> | <imagelabel>libvirt-fcff77f4-0a93-43f9-bf3a-e5863b787400</imagelabel> | </seclabel> | </domain> -------------------------------------------------------------------------------------------------------------- ############################################################### ############################################################### # Booting VM: # Generated: | <domain type='kvm'> | <name>arch_test</name> | <memory unit='KiB'>4194304</memory> | <currentMemory unit='KiB'>4194304</currentMemory> | <vcpu placement='static'>2</vcpu> | <os> | <type arch='x86_64' machine='pc-i440fx-1.4'>hvm</type> | <boot dev='hd'/> | <bootmenu enable='no'/> | </os> | <features> | <acpi/> | <apic/> | <pae/> | </features> | <clock offset='utc'/> | <on_poweroff>destroy</on_poweroff> | <on_reboot>restart</on_reboot> | <on_crash>restart</on_crash> | <devices> | <emulator>/usr/bin/kvm</emulator> | <disk type='network' device='disk'> | <driver name='qemu'/> | <source protocol='rbd' name='libvirt-pool/arch_test-os'> | <host name='192.168.0.35' port='6789'/> | <host name='192.168.0.2' port='6789'/> | <host name='192.168.0.40' port='6789'/> | </source> | <target dev='vda' bus='virtio' /> | </disk> | <disk type='network' device='disk'> | <driver name='qemu'/> | <source protocol='rbd' name='libvirt-pool/arch_test-storage0'> | <host name='192.168.0.35' port='6789'/> | <host name='192.168.0.2' port='6789'/> | <host name='192.168.0.40' port='6789'/> | </source> | <target dev='vdb' bus='virtio' /> | </disk> | <disk type='network' device='disk'> | <driver name='qemu'/> | <source protocol='rbd' name='libvirt-pool/arch_test-storage1'> | <host name='192.168.0.35' port='6789'/> | <host name='192.168.0.2' port='6789'/> | <host name='192.168.0.40' port='6789'/> | </source> | <target dev='vdc' bus='virtio' /> | </disk> | <disk type='network' device='disk'> | <driver name='qemu'/> | <source protocol='rbd' name='libvirt-pool/arch_test-storage2'> | <host name='192.168.0.35' port='6789'/> | <host name='192.168.0.2' port='6789'/> | <host name='192.168.0.40' port='6789'/> | </source> | <target dev='vdd' bus='virtio' /> | </disk> | <disk type='network' device='disk'> | <driver name='qemu'/> | <source protocol='rbd' name='libvirt-pool/arch_test-storage3'> | <host name='192.168.0.35' port='6789'/> | <host name='192.168.0.2' port='6789'/> | <host name='192.168.0.40' port='6789'/> | </source> | <target dev='vde' bus='virtio' /> | </disk> | <disk type='network' device='disk'> | <driver name='qemu'/> | <source protocol='rbd' name='libvirt-pool/arch_test-storage4'> | <host name='192.168.0.35' port='6789'/> | <host name='192.168.0.2' port='6789'/> | <host name='192.168.0.40' port='6789'/> | </source> | <target dev='vdf' bus='virtio' /> | </disk> | <disk type='network' device='disk'> | <driver name='qemu'/> | <source protocol='rbd' name='libvirt-pool/arch_test-storage5'> | <host name='192.168.0.35' port='6789'/> | <host name='192.168.0.2' port='6789'/> | <host name='192.168.0.40' port='6789'/> | </source> | <target dev='vdg' bus='virtio' /> | </disk> | <interface type='bridge'> | <source bridge='ovsbr0'/> | <virtualport type='openvswitch'> | </virtualport> | <model type='virtio'/> | </interface> | | <controller type='usb' index='0'> | </controller> | <controller type='ide' index='0'> | </controller> | <controller type='virtio-serial' index='0'> | </controller> | <serial type='pty'> | <target port='0'/> | </serial> | <console type='pty'> | <target type='serial' port='0'/> | </console> | <input type='mouse' bus='ps2'/> | <graphics type='vnc' port='-1' autoport='yes'/> | <sound model='ich6'> | </sound> | | <video> | <model type='cirrus' vram='9216' heads='1'/> | </video> | | <memballoon model='virtio'> | </memballoon> | | </devices> | </domain> ##### ---------------------------------------------------------------------------------------------------------------- ##### | <domain type='kvm' id='169'> | <name>arch_test</name> | <uuid>7c3b44dc-ff91-413a-b1cf-dfbe2480d44e</uuid> | <memory unit='KiB'>4194304</memory> | <currentMemory unit='KiB'>4194304</currentMemory> | <vcpu placement='static'>2</vcpu> | <resource> | <partition>/machine</partition> | </resource> | <os> | <type arch='x86_64' machine='pc-i440fx-1.4'>hvm</type> | <boot dev='hd'/> | <bootmenu enable='no'/> | </os> | <features> | <acpi/> | <apic/> | <pae/> | </features> | <clock offset='utc'/> | <on_poweroff>destroy</on_poweroff> | <on_reboot>restart</on_reboot> | <on_crash>restart</on_crash> | <devices> | <emulator>/usr/bin/kvm</emulator> | <disk type='network' device='disk'> | <driver name='qemu'/> | <source protocol='rbd' name='libvirt-pool/arch_test-os'> | <host name='192.168.0.35' port='6789'/> | <host name='192.168.0.2' port='6789'/> | <host name='192.168.0.40' port='6789'/> | </source> | <target dev='vda' bus='virtio'/> | <alias name='virtio-disk0'/> | <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> | </disk> | <disk type='network' device='disk'> | <driver name='qemu'/> | <source protocol='rbd' name='libvirt-pool/arch_test-storage0'> | <host name='192.168.0.35' port='6789'/> | <host name='192.168.0.2' port='6789'/> | <host name='192.168.0.40' port='6789'/> | </source> | <target dev='vdb' bus='virtio'/> | <alias name='virtio-disk1'/> | <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> | </disk> | <disk type='network' device='disk'> | <driver name='qemu'/> | <source protocol='rbd' name='libvirt-pool/arch_test-storage1'> | <host name='192.168.0.35' port='6789'/> | <host name='192.168.0.2' port='6789'/> | <host name='192.168.0.40' port='6789'/> | </source> | <target dev='vdc' bus='virtio'/> | <alias name='virtio-disk2'/> | <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> | </disk> | <disk type='network' device='disk'> | <driver name='qemu'/> | <source protocol='rbd' name='libvirt-pool/arch_test-storage2'> | <host name='192.168.0.35' port='6789'/> | <host name='192.168.0.2' port='6789'/> | <host name='192.168.0.40' port='6789'/> | </source> | <target dev='vdd' bus='virtio'/> | <alias name='virtio-disk3'/> | <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> | </disk> | <disk type='network' device='disk'> | <driver name='qemu'/> | <source protocol='rbd' name='libvirt-pool/arch_test-storage3'> | <host name='192.168.0.35' port='6789'/> | <host name='192.168.0.2' port='6789'/> | <host name='192.168.0.40' port='6789'/> | </source> | <target dev='vde' bus='virtio'/> | <alias name='virtio-disk4'/> | <address type='pci' domain='0x0000' bus='0x00' slot='0x0a' function='0x0'/> | </disk> | <disk type='network' device='disk'> | <driver name='qemu'/> | <source protocol='rbd' name='libvirt-pool/arch_test-storage4'> | <host name='192.168.0.35' port='6789'/> | <host name='192.168.0.2' port='6789'/> | <host name='192.168.0.40' port='6789'/> | </source> | <target dev='vdf' bus='virtio'/> | <alias name='virtio-disk5'/> | <address type='pci' domain='0x0000' bus='0x00' slot='0x0b' function='0x0'/> | </disk> | <disk type='network' device='disk'> | <driver name='qemu'/> | <source protocol='rbd' name='libvirt-pool/arch_test-storage5'> | <host name='192.168.0.35' port='6789'/> | <host name='192.168.0.2' port='6789'/> | <host name='192.168.0.40' port='6789'/> | </source> | <target dev='vdg' bus='virtio'/> | <alias name='virtio-disk6'/> | <address type='pci' domain='0x0000' bus='0x00' slot='0x0c' function='0x0'/> | </disk> | <controller type='usb' index='0'> | <alias name='usb0'/> | <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> | </controller> | <controller type='ide' index='0'> | <alias name='ide0'/> | <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> | </controller> | <controller type='virtio-serial' index='0'> | <alias name='virtio-serial0'/> | <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> | </controller> | <controller type='pci' index='0' model='pci-root'> | <alias name='pci0'/> | </controller> | <interface type='bridge'> | <mac address='52:54:00:d0:da:73'/> | <source bridge='ovsbr0'/> | <virtualport type='openvswitch'> | <parameters interfaceid='f1c41c6e-8ca0-4c34-b1df-053c9a7976bb'/> | </virtualport> | <target dev='vnet2'/> | <model type='virtio'/> | <alias name='net0'/> | <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> | </interface> | <serial type='pty'> | <source path='/dev/pts/4'/> | <target port='0'/> | <alias name='serial0'/> | </serial> | <console type='pty' tty='/dev/pts/4'> | <source path='/dev/pts/4'/> | <target type='serial' port='0'/> | <alias name='serial0'/> | </console> | <input type='mouse' bus='ps2'/> | <graphics type='vnc' port='5902' autoport='yes' listen='127.0.0.1'> | <listen type='address' address='127.0.0.1'/> | </graphics> | <sound model='ich6'> | <alias name='sound0'/> | <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> | </sound> | <video> | <model type='cirrus' vram='9216' heads='1'/> | <alias name='video0'/> | <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> | </video> | <memballoon model='virtio'> | <alias name='balloon0'/> | <address type='pci' domain='0x0000' bus='0x00' slot='0x0d' function='0x0'/> | </memballoon> | </devices> | <seclabel type='dynamic' model='apparmor' relabel='yes'> | <label>libvirt-7c3b44dc-ff91-413a-b1cf-dfbe2480d44e</label> | <imagelabel>libvirt-7c3b44dc-ff91-413a-b1cf-dfbe2480d44e</imagelabel> | </seclabel> | </domain>

1 0

[libvirt-users] virsh detach typo
by Mauricio Tavares 03 Dec '13

03 Dec '13

[root@vmhost vms]# virsh detach-disk puppet vdb error: No found disk whose source path or target is vdb [root@vmhost vms]# virsh --version 0.10.2 [root@vmhost vms]# This probably was solved already but if not, "No found disk" probably sounds better if it was "No disk found"

2 1

[libvirt-users] Virsh snapshots
by Juraj Melo 03 Dec '13

03 Dec '13

Hello, I am working on my PhD thesis and it would be really helpfull if someone could advise me, whether can Virsh create snapshots of VMs using copy-on-write. Thanks for reply. Juraj

3 2

[libvirt-users] Does virsh support offline migration?
by me,apporc 03 Dec '13

03 Dec '13

I saw some docs referred one option "--offline" for "virsh migrate" on the internet, and there was one section called "Offline Migration" in libvirt.org, but i did find this option on my local machine. So, is it libvirt really support offline migration ? Is that because my libvirt is a little older? Is that option "--offline" right? -- Regards, apporc

2 1

[libvirt-users] FYI: Wiki account self-registration disabled
by Daniel P. Berrange 30 Nov '13

30 Nov '13

Unfortunately evil spammers have managed to defeat all the anti-spam measures we've tried with the wiki. So it is with regret that we have had to disable new wiki account self-registration. We do still welcome contributions from anyone interested in adding wiki content. We just ask that you send a mail to the main devel mailing list (libvir-list(a)redhat.com) to request an account be created for you by the wiki admin. Meanwhile we're hoping to migrate the wiki to new hosting service where we'll be able to deploy newer wiki software and thus hopefully better anti-spam measures. When this happens we'll look at re-enabling self-registration of accounts. Regards, Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|

1 0

[libvirt-users] Socket getting closed automatically after destroying vm.
by cool dharma06 29 Nov '13

29 Nov '13

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

2 2

[libvirt-users] Fw:Migration errors
by Tony Gong 27 Nov '13

27 Nov '13

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

1 0

[libvirt-users] Migration errors
by Tony Gong 27 Nov '13

27 Nov '13

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

1 0

[libvirt-users] Help required in simulating libvirt TLS server
by Arun Viswanath 26 Nov '13

26 Nov '13

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

3 2

[libvirt-users] Hypervisor load much greater than that of the guest
by Damion Parry 26 Nov '13

26 Nov '13

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.

1 0

[libvirt-users] Help with Vrbr0
by Sherin A 25 Nov '13

25 Nov '13

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

2 6

[libvirt-users] Scientific Linux as guest. Can't install with virt-manager because key "tab" in use
by E Gerlach 23 Nov '13

23 Nov '13

Please help, I can't install Scientific Linux 6.3 with virt-manager because the key tab switches between kvm windows. I urgently need tab to go on in install process. see screenshot: http://aiai.de/foren/scientificLinux_tab.png Even in fullscreen mode tab changes to kvm window and not to button "continue" for installation process. please help, I want to install scientific linux as kvm guest. I'm running debian wheezy as host. thx Eckard

2 3

[libvirt-users] Query:: Reg: Libvirt Networking
by Nehal J Wani 22 Nov '13

22 Nov '13

Currently, I have two networks configured via xml: virsh # net-dumpxml TestNetwork1 <network connections='2'> <name>TestNetwork1</name> <uuid>a76f665a-0196-4edb-81b4-340944a6869c</uuid> <forward dev='p1p1' mode='nat'> <nat> <port start='1024' end='65535'/> </nat> <interface dev='p1p1'/> </forward> <bridge name='virbr0' stp='on' delay='0'/> <mac address='52:54:00:0b:e9:35'/> <ip address='192.168.100.1' netmask='255.255.255.0'> <dhcp> <range start='192.168.100.128' end='192.168.100.254'/> </dhcp> </ip> </network> virsh # net-dumpxml default6 <network connections='1'> <name>default6</name> <uuid>6e57d831-f09e-4b33-950d-6d51c89f9786</uuid> <forward mode='nat'/> <bridge name='virbr3' stp='on' delay='0'/> <mac address='52:54:00:cb:c5:50'/> <ip family='ipv6' address='2001:db8:ca2:2::1' prefix='64'> <dhcp> <range start='2001:db8:ca2:2:1::10' end='2001:db8:ca2:2:1::ff'/> </dhcp> </ip> </network> # brctl show bridge name bridge id STP enabled interfaces virbr0 8000.5254000be935 yes virbr0-nic vnet0 vnet1 virbr3 8000.525400cbc550 yes virbr3-nic vnet2 My queries are: (i) For each interface that I attach to my guests, will a new vnetX (X=0,1,2,3,...) be created? (ii) Can two different active networks share the same bridge? Example, can the xml of two active networks have the same line <bridge name='virbr0' stp='on' delay='0'/> ? (iii) If the answer for (ii) is false, how can I obtain the interface name for a given bridge name in libvirt? -- Nehal J Wani

2 3

[libvirt-users] centos4.8 system container not working on fedora 19 machine
by Rahul Khengare 22 Nov '13

22 Nov '13

Hi All, I am trying to evaluate whether centos-4.8 system container work on Fedora-19 machine or not. Host machine : Fedora 19 Guest (LXC container) : CentOS4 .8 For creation of of container i followed following steps, 1. Installed libvirt packages on fedora19 2. For installation of rootfs using yum, I have created the LOCAL YUM REPO using CentOS-4.8 ISO files 3. Created rootfs using yum 4. Made changes in container xml file required for system container 5 .Define container using container xml file Whenever I start system container it get started successfully but when I am trying to access it using console then It show errors regarding /etc/fstab files and filesystem corruption. I am not able to access the container. Refer below for container xml file and error message, contents of xml file for Centos container, *Centos4_8.xml:* <domain type='lxc'> <name>BasicCentos</name> <memory unit='KiB'>102400</memory> <currentMemory unit='KiB'>102400</currentMemory> <os> <type>exe</type> <init>/sbin/init</init> </os> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/libexec/libvirt_lxc</emulator> <filesystem type='mount' accessmode='passthrough'> <source dir='/lxc/centos4.8'/> <target dir='/'/> </filesystem> <interface type='bridge'> <source bridge='br0'/> </interface> <console type='pty' port='0'></console> </devices> </domain> ------------- *ERROR LOG* When trying to access container using CONSOLE command, virsh # console BasicCentos Connected to domain BasicCentos Escape character is ^] INIT: version 2.85 booting /etc/rc.d/rc.sysinit: line 36: [: /sys/fs/selinux: binary operator expected Setting default font (): [ OK ] Welcome to CentOS release 4.8 (Final) Press 'I' to enter interactive startup. hwclock: KDGHWCLK ioctl failed, errno=25: Inappropriate ioctl for device. Cannot access the Hardware Clock via any known method. Use the --debug option to see the details of our search for an access method. Setting clock : Thu Nov 21 01:48:58 EST 2013 [ OK ] Starting udev: MAKEDEV: error making /dev/tty1: Operation not permitted [FAILED] Initializing hardware... storage network audio done [ OK ] raidautorun: unable to autocreate /dev/md0 mount: can't find /dev/pts in /etc/fstab or /etc/mtab Configuring kernel parameters: [ OK ] Setting hostname centos: [ OK ] Checking root filesystem fsck.ext2: Is a directory while trying to open / /: The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> [FAILED] *** An error occurred during the file system check. *** Dropping you to a shell; the system will reboot *** when you leave the shell. *** Warning -- SELinux is active *** Disabling security enforcement for system recovery. *** Run 'setenforce 1' to reenable. /etc/rc.d/rc.sysinit: line 52: $selinuxfs/enforce: ambiguous redirect Press enter for maintenance (or type Control-D to continue): (Repair filesystem) 1 # exit Unmounting file systems mount: can't find / in /etc/fstab or /etc/mtab Automatic reboot in progress. thanks in advance. Regards, Rahul Khengare, NTT OSS Center, Pune, India.

1 0