- Users - libvirt List Archives

[libvirt-users] Qemu-1.4.0-2 and Qemu-1.4.0-1 is broken on virt-preview and rawhide
by Skardal, Harald 04 Mar '13

04 Mar '13

All, Our testing seems to indicate that Qemu-1.4.0-2 and Qemu-1.4.0-1 is broken on virt-preview and rawhide. I'm getting undefined symbol: usbredirparser_send_start_bulk_receiving when running qemu-system-x86_64 -version.. Do others see this issue? Is there a known solution? Harald Failing cases: ------------------------------------------------------------------------ -------------------------------------- Failed on Qemu-1.4.0-2 ---------------------- [root@node1 ~]# rpm -q --file /usr/bin/qemu-system-x86_64 qemu-system-x86-1.4.0-2.fc18.x86_64 [root@node1 ~]# /usr/bin/qemu-system-x86_64 --version /usr/bin/qemu-system-x86_64: symbol lookup error: /usr/bin/qemu-system-x86_64: undefined symbol: usbredirparser_send_start_bulk_receiving Failed on Qemu-1.4.0-1 ---------------------- [root@localhost ~]# rpm -q --file /usr/bin/qemu-system-x86_64 qemu-system-x86-1.4.0-1.fc18.x86_64 [root@localhost ~]# /usr/bin/qemu-system-x86_64 --version /usr/bin/qemu-system-x86_64: symbol lookup error: /usr/bin/qemu-system-x86_64: undefined symbol: usbredirparser_send_start_bulk_receiving ------------------------------------------------------------------------ -------------------------------------- Passed on Qemu-1.3.0-9 ---------------------- [root@node0 ~]# rpm -q --file /usr/bin/qemu-system-x86_64 qemu-system-x86-1.3.0-9.fc18.x86_64 [root@node0 ~]# /usr/bin/qemu-system-x86_64 --version QEMU emulator version 1.3.0, Copyright (c) 2003-2008 Fabrice Bellard

2 1

[libvirt-users] Secure communication from host to guest
by Shea Levy 02 Mar '13

02 Mar '13

Hi, On boot, I'd like to pass a public key to the VM to use for root ssh logins, and obviously only the user that started the VM on the host should be able to send the key. What's the best way to pass this kind of information into the VM? I thought about using a serial port connected to a fifo on the host, but I'd rather not deal with serial programming if I can avoid it... Thanks, Shea

2 1

[libvirt-users] VM can not start
by Qinghua Cheng 01 Mar '13

01 Mar '13

Hi Experts, I have libvirt 1.0.2 downloaded and build on my RH. And I also downloaded qemu 1.4.0 and build on this machine. When I tried to start my VM ubuntu12, get error messages: error: Failed to start domain ubuntu12 error: internal error Process exited while reading console log output: I have no idea what does this message mean. Could you please help point out what I should do next? Thanks, Conny

2 2

[libvirt-users] Libvirt not creating .vmdk file and .nvram files on vmware esx host
by Nithin Mp 28 Feb '13

28 Feb '13

Hi, I am currently using libvirt API(java api) for creating VMs in esxi host. I am passing commands as follows:(trying from terminal) virsh -c esx://192.168.0.144?no_verify=1 define /home/bm/eee.xml Domain eee defined from /home/bm/eee.xml I have attached the eee.xml file and the eee.vmx from the esxi datastore with this mail. the versions i am using is : virsh # version Compiled against library: libvirt 1.0.0 Using library: libvirt 1.0.0 Using API: ESX 1.0.0 Running hypervisor: ESX 5.0.0 The system i am using is Ubuntu 12.04 LTS 64 bit Please reply me.Waiting for your response. -- *Thanks & Regards* NITHIN.M.P

1 0

[libvirt-users] With no luck with virDomainGetInfo and virDomainMemoryStats for memory usage of a running vm
by 张章 28 Feb '13

28 Feb '13

Hi, all I am trying to get used memory of a running vm using libvirt and then to calculate the memory usage, but with no luck. 1.The used memory returned by virDomainGetInfo is equal to max memory with no virtio balloon driver set. When using virtio balloon driver and setting currentMemory less than memory in the xml, the used memory returned by virDomainGetInfo is nearly equal to currentMemroy. Again, I can't get the memory used by vm. 2. When I turned to virDomainMemoryStats, I can only get two values : Current balloon value and Resident Set Size of the process running the domain. (for kvm 0.14.1 and libvirt 1.0.2) That's not what I want. I only need to know how much memory used by the running vm, so I can calculate the memory usage of this vm. (like the used memory return by cmd "free -m") Any hints? Many thanks! Z. ZhangNational Research Center for intelligent Computing Systems,ICT, Chinese Academy of Sciences

1 0

[libvirt-users] Deleting and coalescing live snapshots
by Skardal, Harald 28 Feb '13

28 Feb '13

All, I have a service that takes new live KVM snapshots Si regularly, keeps a fixed number N (Si ,..,Si-N+1), and therefore needs to delete Si-N in this cycle. Until libvirt includes support for this capability that is said to be available in qemu, what is a safe workflow to delete old live KVM snapshots w/o losing data. Do I need to pause/shut down the VM? The development environment is Fedora 18 with qemu, libvirtd and libvirt upgrades to the more recent stable versions. Harald Skardal, Stratus Technologies.

3 2

[libvirt-users] The accurate CPU usage of a domain?
by 张章 28 Feb '13

28 Feb '13

Hi,all I want to get a relatively accurate cpu usage of a domain. I have a few questions about virDomainGetInfo: struct virDomainInfo{ unsigned char state : //the running state, one of virDomainState unsigned long maxMem :// the maximum memory in KBytes allowed unsigned long memory :// the memory in KBytes used by the domain unsigned short nrVirtCpu :// the number of virtual CPUs for the domain unsigned long long cpuTime : //the CPU time used in nanoseconds } If a domain is assigned to 4 vcpus and my machine has 6 physical cores, then the cpuTime in virDomainInfo should be the sum of cpu time of the 4 vcpus. When I want to calculate the cpu usage, which of the following is more accurate? 1/4 * cpu time / total time or 4/6 * cpu time / total time or just cpu time / total time regardszhangzhang

2 1

[libvirt-users] error when call migrate function "error: invalid argument: qemuDomainMigratePrepare3: unsupported flags (0x200)"
by loic.cloatre＠orange.com 27 Feb '13

27 Feb '13

Hello, I try to migrate a VM and I get this error : loic@loic-VirtualBox:~/workspace/src/build/bin$ ./virsh --connect qemu:///system migrate --live vmUbuntuPartage2CacheWriteBack qemu+ssh://192.168.10x.2x/system --unsafe loic(a)192.168.10x.2x's password: error: invalid argument: qemuDomainMigratePrepare3: unsupported flags (0x200) Does somebody know this error? I am working on windows 7, I have: 1) Virtual box with two vms ubuntu desktop 12.04: "VM1" and "VM40" 2) One shared hard drive build with virtual box: "newDiskSharedFev.vdi" In my VM1: 1) I have build one "vmUbuntuPartage" ubuntu server 12.10 on shared disk with this command: sudo virt-install -n vmUbuntuPartage -r 1500 --disk path=/media/partage/newDiskSharedFev.vdi,bus=virtio,size=4,cache=writeback -c /home/loic/Downloads/ubuntu-12.04.1-server-i386.iso --network network=default,model=virtio --connect=qemu:///system --vnc -v 2) I have download and built libvirt-0.10.0 (I can give configure command if necessary) In my VM40: 1) I install libvirt with apt-get 2) I have mounted shared folder with "newDiskSharedFev.vdi" So, in my VM1 I try to migrate my "vmUbuntuPartage" from VM1 to VM40 and I get error above. Here my configuration file /etc/libvirt/qemu/ vmUbuntuPartage.xml --> I try to change <driver name='qemu' type='raw' cache='none or writeback or writetrough'/> ================  <domain type='qemu'> <name>vmUbuntuPartage</name> <uuid>5d38cf86-d9c5-b0f2-cc03-982a1f18bede</uuid> <memory>1536000</memory> <currentMemory>1536000</currentMemory> <vcpu>1</vcpu> <os> <type arch='i686' machine='pc-1.0'>hvm</type> <boot dev='hd'/> </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/qemu-system-x86_64</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='none'/> <source file='/media/partage/SharedDiskUbuntu.vdi'/> <target dev='vda' bus='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> <disk type='block' device='cdrom'> <driver name='qemu' type='raw'/> <target dev='hdc' bus='ide'/> <readonly/> <address type='drive' controller='0' bus='1' unit='0'/> </disk> <controller type='ide' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <interface type='network'> <mac address='52:54:00:8b:b1:80'/> <source network='default'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <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'/> <video> <model type='cirrus' vram='9216' heads='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </memballoon> </devices> </domain> ================== Loïc Cloâtre _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified. Thank you.

3 14

[libvirt-users] questions of libvirt's lxc
by Han Yuejuan-B42073 27 Feb '13

27 Feb '13

Hi all, I am trying to init lxc by libvirt instead of using lxc tools. I have several questions as following: software platform: integrating libvirt-0.10.1 to yocto based on sdk1.3 hardwatre platform: p4080ds steps: root@p4080ds:~# cat > container.xml <<EOF <domain type='lxc'> <name>container</name> <memory>500000</memory> <os> <type>exe</type> <init>/bin/sh</init> </os> <vcpu>1</vcpu> <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> <interface type='network'> <source network='default'/> </interface> <console type='pty' /> </devices> </domain> <EOF root@p4080ds:~# libvirtd -d root@p4080ds:~# virsh --connect lxc:/// define container.xml Domain container defined from container.xml root@p4080ds:~# virsh --connect lxc:/// start container error: Failed to start domain container error: internal error Network 'default' is not active. To resolve this issue I change the container.xml to as below: <domain type='lxc'> <name>container</name> <memory>500000</memory> <os> <type>exe</type> <init>/bin/sh</init> </os> <vcpu>1</vcpu> <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> <interface type='bridge'> <source network='br0'/> <mac address='00:11:22:34:34:34'/> (I am not sure it will make difference) </interface> <console type='pty' /> </devices> </domain> then error infos as below: root@p4080ds:~# virsh --connect lxc:/// define container.xml error: Failed to define domain from container.xml error: internal error No <source> 'bridge' attribute specified with <interface type='bridge'/> Q1: What an appropriate virtual network is supported by virsh for error mentioned above? Linux container support several types of network such as veth, vlan, macvlan, phys and how to edit different xml file for different network type? Q2: There are two kinds of containers , application container and system container. If using lxc tools, lxc-execute will establish an application container and lxc-create with lxc-start will establish a system container. So with libvirt how to set up these two kinds of containers? by different xml file or by different virsh cmds? Q3: If I want to define a rootfs (such as busybox) for container how I edit the relative xml file? anyone has related infos that can be shared? Q4:Cgroups manage and control resources using for lxc containers. If use libvirt how to realise the similar resource tuning for containers based on PowerPC? There are limited infos at: https://www.berrange.com/posts/2009/12/03/using-cgroups-with-libvirt-and-lx… Regards, Yuejuan

1 0

[libvirt-users] VMs XML difinitions can't be recognized after upgrading to libvirt 0.9.13
by Marwan Tanager 27 Feb '13

27 Feb '13

I used to run many VMs on my Ubuntu 10.04 box. However, after upgrading to Ubuntu 12.10 (and thus, libvirt 0.9.13), The VMs can't be recognized anymore. Nothing appears in the output of 'virsh list --all', nor in virt-manager. When I created a new VM based on a disk image of one of the not-recognized-any-more VMs, a new schema file has been auto-generated, and the new VM now is recognized. So, if this is caused by incompatibility with the old schemas, would the solution be to manually recreate all the VMs by importing their disk images to the newly created VMs, or is there a more intelligent approach? Thanks for your time. Marwan

2 2