December 2012 - Users - Libvirt List Archives

[libvirt-users] Incorrect currentMemory for qemu-1.2+

by Andrey Korolyov

Hi, Since this message(https://www.redhat.com/archives/libvirt-users/2012-October/msg000... qemu folks have released one minor version in the 1.2 branch and shiny new 1.3 some days ago and the problem still persists. At first I has blamed libvirt, but I was not correct at all - since I have released package ``slices'' for myself including both newer libvirth and qemu, I wasn`t able to corner this problem and my report may be counted as completely wrong. Right now, I have the following situation: - all libvirt versions running above qemu-1.1 always reports right balloon and currentMemory sizes - for qemu 1.2 it is quite more funny: as in message above, I receive wrong currentMemory always set to ``magic'' 5398528kB at the 8gb host node, but only if ``memory'' parameter has same or higher value, even <memory unit='KiB'>5348520</memory> works okay, providing righ balloon value for the libvirt. As you can see the ~2700MB offset between current and maximum(or entire host) memory present in both configurations. 8Gb node is a simple non-numa machine so this is not related to numa miscalculation. Previous test at the link above processed on the 64GB two-head node with symmetric numa topology, if it matters. And finally, $ virsh dumpxml vm010-000-000-092 | grep curr <currentMemory unit='KiB'>5398528</currentMemory> $ virsh qemu-monitor-command --hmp vm010-000-000-092 info balloon balloon: actual=1176 Until virtio_balloon initializes in the guest, libvirt reporting _right_ value for some seconds after VM start, so bug (which I unable to track by myself) almost for sure presented in parsing of received values from guest balloon.

11 years, 11 months

1
1
0 / 0

[libvirt-users] Libvirt migration compatible

by Timon Wang

Hi all, I am use libvirt and kvm for migrate a vm from a pc to a Dell pc server, and the cpu feature are not the same, I am wondering if there is any solution to make the migration works smoothly. The PC's cpu feature is less than Dell pc server, so how to make sure the migration work. Another question is I found a post in 2007, said that AMD has make the migration from amd server to intel server by AMD-V Extended Migration and Intel Flex Migration, can I use these tech in libvirt? -- Focus on: Server Vitualization, Network security,Scanner,NodeJS,JAVA,WWW Blog: http://www.nohouse.net

11 years, 11 months

1
0
0 / 0

[libvirt-users] Strange behavior of QoS

by Davide Guerri

Hi, I'm having some weird problem with the setup of the QoS on a bridged network. As the docs states, outbound/inbound average speed should be expressed in KBps (KBytes per second) but in order to get a maximum speed of 10Mbps (megabits per second) surprising enough I have to use 2560 on the guest (not 1280 as expected). Using 1280 units I get a speed og 5Mbps. I'm aware of peak and burst parameters but even with them I'm seeing the same (long-term) behavior. Here follows my configuration. Thank you in advance for any help you can provide. Domain definition (relevant part only) virsh # dumpxml mydomain <domain type='kvm' id='45'> [...] <devices> [...] <interface type='network'> <mac address='52:54:00:xx:xx:xx'/> <source network='br909'/> <target dev='vnet43'/> <model type='virtio'/> <bandwidth> <inbound average='2560'/> <outbound average='2560'/> </bandwidth> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> [...] </devices> </domain> The network definition: virsh # net-dumpxml br909 <network> <name>br909</name> <uuid>07319380-2025-cdcc-924a-149cd0370b56</uuid> <forward mode='bridge'/> <bridge name='br909' /> </network> And iperf result (client and server are on the same vlan and they are running on the same host) [ 5] local xx.xx.xx.xx port 5001 connected with xx.xx.xx.yy port 18396 [ 5] 0.0-30.1 sec 35.4 MBytes 9.87 Mbits/sec

11 years, 11 months

3
2
0 / 0

[libvirt-users] Error using virt-convert

by Chandana De Silva

All, I am trying to use virt-convert to convert a KVM/libvirt guest to VMWare ESX 4, and getting an error. Any help would be greatly appreciated. I have created a virt-image image file as shown at http://people.redhat.com/dlutter/virt-image/virt-image-xml.html. See below for the xml file. I am using the following command for the conversion, and am getting the error shown : /usr/bin/virt-convert -i virt-image -o vmx -D vmdk mon03.xml mon03 ERROR Couldn't import file "mon03.xml": Couldn't import file 'mon03.xml': Disk entry for 'mon03' not found The image file itself is readable by all: ls -la /var/lib/libvirt/imageshelf/mon03.img -rw-r--r-- 1 root m4u 8589934592 Dec 3 09:25 /var/lib/libvirt/imageshelf/mon03.img ls -la mon03.xml -rw-rw-r-- 1 chandana chandana 657 Dec 5 09:08 mon03.xml <image> <name>mon03</name> <domain> <boot type="hvm"> <guest> <arch>i686</arch> </guest> <os> <loader dev="cdrom"/> </os> <drive disk="mon03" target="hda"/> </boot> <devices> <vcpu>2</vcpu> <memory>262144</memory> <interface/> <graphics/> </devices> <storage> <disk id="mon03" file="/var/lib/libvirt/imageshelf/mon03.img" use="system" size="8388608" format="raw"/> </storage> </domain> </image>

11 years, 11 months

2
1
0 / 0

[libvirt-users] Clone disk image common ancestry/branching.

by Mestnik, Michael J - Eagan, MN - Contractor

Hello, I was wondering if it was possible to support or easily extent libvirt to perform steps like the following when cloning: # Any existing VMs must be paused or better. ln $currentimg backing-store.img qemu-img create -o backing-store.img $currentimg.tmp qemu-img create -o backing-store.img $newimg # Get any existing VM using $currentimg.tmp mv $currentimg.tmp $currentimg The idea being to create branches of an installs ancestry rather than simply duplicating the install. Cheers. Mike Mestnik, Michael J The ESM Tools Enterprise Systems Monitoring United States Postal Service O: (651) 406-2048 Michael.J.Mestnik(a)usps.gov ITEnterpriseSystemsMonitoring(a)usps.gov

11 years, 11 months

1
0
0 / 0

[libvirt-users] Strange QoS behavior

by Davide Guerri

Hi, I'm having some weird problem with the setup of the QoS on a bridged network. As the docs states, outbound/inbound average speed should be expressed in KBps (KBytes per second) but in order to get a maximum speed of 10Mbps (megabits per second) surprising enough I have to use 2560 on the guest (not 1280 as expected). Using 1280 units I get a speed og 5Mbps. I'm aware of peak and burst parameters but even with them I'm seeing the same (long-term) behavior. Here follows my configuration. Thank you in advance for any help you can provide. Domain definition (relevant part only) virsh # dumpxml mydomain <domain type='kvm' id='45'> [...] <devices> [...] <interface type='network'> <mac address='52:54:00:xx:xx:xx'/> <source network='br909'/> <target dev='vnet43'/> <model type='virtio'/> <bandwidth> <inbound average='2560'/> <outbound average='2560'/> </bandwidth> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> [...] </devices> </domain> The network definition: virsh # net-dumpxml br909 <network> <name>br909</name> <uuid>07319380-2025-cdcc-924a-149cd0370b56</uuid> <forward mode='bridge'/> <bridge name='br909' /> </network> And iperf result (client and server are on the same vlan and they are running on the same host) [ 5] local xx.xx.xx.xx port 5001 connected with xx.xx.xx.yy port 18396 [ 5] 0.0-30.1 sec 35.4 MBytes 9.87 Mbits/sec

11 years, 11 months

3
4
0 / 0

[libvirt-users] error: unsupported configuration: block I/O throttling not supported with this QEMU binary

by hzguanqiang

Hi, guys. I want to change block I/O throttle using 'virsh blkdeviotune' with vm not running, it reported an error: # virsh blkdeviotune instance-000000dc /dev/loop0 --total-bytes-sec 20000000 --total-iops-sec 20 --config error: Unable to change block I/O throttle error: unsupported configuration: block I/O throttling not supported with this QEMU binary I can do this when the vm is running. Is it a bug? How can I fix this problem. BTW,My libvirt version is 0.9.13: # virsh version Compiled against library: libvir 0.9.13 Using library: libvir 0.9.13 Using API: QEMU 0.9.13 Running hypervisor: QEMU 1.1.2 Thanks. 2012-11-28 hzguanqiang

11 years, 11 months

2
5
0 / 0

[libvirt-users] iSCSI storage pool autostart

by rh ev

Hello everyone, I have recently installed libvirt 1.0.0 and am having a problem with my iSCSI storage pool's autostarting. They are just going to an inactive state right after a reboot of the host. However once the startup is complete I can manually start the pool without problem. I am getting the following errors in the libvirtd.log file but they don't really give me much as to what could be causing this. I also looked in the messages log file but didn't find anything that looked useful. *2012-11-27 20:06:50.845+0000: 1358: error : virCommandWait:2287 : internal error Child process (/sbin/iscsiadm –mode session) unexpected exit status 21 * *2012-11-27 20:06:50.890+0000: 1358: error : virCommandWait:2287 : internal error Child process (/sbin/iscsiadm –mode session) unexpected exit status 21 * *2012-11-27 20:07:10.159+0000: 1358: error : virCommandWait:2287 : internal error Child process (/sbin/iscsiadm –mode discovery –type sendtargets –portal 192.168.220.50:3260,1) unexpected exit status 4* *2012-11-27 20:07:10.159+0000: 1358: error : storageDriverAutostart:101 : Failed to autostart storage pool ‘stoPool01′: internal error Child process (/sbin/iscsiadm –mode discovery –type sendtargets –portal 192.168.220.50:3260,1) unexpected exit status 4* If anyone has any ideas what is causing this it would be a great help. If you need more information let me know. Thanks, Darcy

11 years, 11 months

3
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Users December 2012