- Users - libvirt List Archives

[libvirt-users] virsh define function question
by zhanggp 19 Jul '12

19 Jul '12

Hi, How do I view the libvirt virsh domxml-to-native function implementation? I think this function contains some error. Because we use libvirt to manage some host and vms on vmware hypervisor. We use openenbula generate a template for libvirt ,such as my attachment windows2008.xml. but when i use domxml-to-native to convert xml file to vmware config file vmx as below. This may not be accurate. For example: 1. guestOs type : could I config this parameter in xml file ,so after domxml-to-native to vmware.vmx , guestOS in my vmx file is "windows7srv-64 ". And also my pciBridge disappeared ! So could someone help me and tell us about 'virsh-c the esx :/ /@host?no_verify=1 define windows2008.xml' function realization。 Thanks all! virsh # domxml-to-native vmware-vmx windows2008.xml .encoding = "UTF-8" config.version = "8" virtualHW.version = "7" guestOS = "other-64" uuid.bios = "42 11 25 27 fd b6 7b 6d-72 3f 75 c6 25 fe ef 3e" displayName = "windows2008" memsize = "2048" numvcpus = "2" sched.cpu.shares = "normal" ide0:0.present = "true" ide0:0.deviceType = "ata-hardDisk" ide0:0.fileName = "/vmfs/volumes/349969f9-070dee8d/./windows2008.vmdk" floppy0.present = "false" floppy1.present = "false" ethernet0.present = "true" ethernet0.virtualDev = "e1000" ethernet0.networkName = "VM Network" ethernet0.connectionType = "bridged" ethernet0.addressType = "vpx" ethernet0.generatedAddress = "00:50:56:91:00:07" svga.vramSize = "8388608" zhanggp --------------------------------------------------------------------------------------------------- Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s) is intended only for the use of the intended recipient and may be confidential and/or privileged of Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is not the intended recipient, unauthorized use, forwarding, printing, storing, disclosure or copying is strictly prohibited, and may be unlawful.If you have received this communication in error,please immediately notify the sender by return e-mail, and delete the original message and all copies from your system. Thank you. ---------------------------------------------------------------------------------------------------

2 1

[libvirt-users] Questions related to the snapshot
by lin tan 19 Jul '12

19 Jul '12

Hi, I faced two problems with the snapshot: First issue, I can use the snapshot functions via the virsh correctly such as snapshot-list. And when I removed the snapshot XML files from /var/lib/libvirt/qemu/snapshot/**/, I don't see the snapshot of the Virtual Machine any more. That's correct. But after I copying the XML files back, I can't see the the snapshot as well. Only if I restart my laptop can I see them. However, restarting is what I want to avoid. Because I wish I could utilize the functions in a server in the future. Does anyone have ideas about this, Did I do something wrong or it's a limitation. So far, I am using the qemu-img command to check the snapshot and do the revert without restarting my laptop. Because the snapshots are already embedded in the img file. Second issue, I find if I create the XML file of snapshot by using getXMLDesc and output to a new file in python, there is a slightly different. But, the new XML file can't be recognized even if I restart my laptop. The new XML file miss the attribute <active> as far as I can see, is it so important? Here is one example: The original XML in the default folder: <domainsnapshot> <name>Ex</name> <description>Snapshot of OS updates</description> <state>running</state> <parent> <name>1342427860</name> </parent> <creationTime>1342428835</creationTime> <domain> <uuid>2c853de2-6bba-ad26-bf05-0045e5f1beb9</uuid> </domain> <active>0</active> </domainsnapshot> The new XML file I created: <domainsnapshot> <name>Ex</name> <description>Snapshot of OS updates</description> <state>running</state> <parent> <name>1342427860</name> </parent> <creationTime>1342428835</creationTime> <domain> <uuid>2c853de2-6bba-ad26-bf05-0045e5f1beb9</uuid> </domain> </domainsnapshot> Thank you so much. Best Regards Tan

2 1

[libvirt-users] save / restore RAM state - Problem
by Evaggelos Balaskas 19 Jul '12

19 Jul '12

Hi all, i am trying (test) to save / restore a state of a winxp virtual machine. Perhaps i am missing that i can not restore save image to LVM partition. "error: Failed to read file '/root/winxp.save': Value too large for defined data type" Below are my settings libvirt 0.9.13 qemu-kvm 1.1.1 # virsh Welcome to virsh, the virtualization interactive terminal. Type: 'help' for help with commands 'quit' to quit virsh # list Id Name State ---------------------------------------------------- 3 winxp running virsh # save winxp /root/winxp.save Domain winxp saved to /root/winxp.save virsh # list Id Name State ---------------------------------------------------- virsh # list --all Id Name State ---------------------------------------------------- - winxp shut off virsh # restore winxp /root/winxp.save error: Failed to read file '/root/winxp.save': Value too large for defined data type # du -h /root/winxp.save 278M /root/winxp.save # virsh dumpxml winxp | more <domain type='kvm'> <name>winxp</name> <uuid>b528a71f-aca1-5024-c460-892100b97ef2</uuid> <memory unit='KiB'>1597440</memory> <currentMemory unit='KiB'>1048576</currentMemory> <vcpu placement='static'>1</vcpu> <os> <type arch='x86_64' machine='pc-1.1'>hvm</type> <boot dev='hd'/> </os> --- Logical volume --- LV Path /dev/vg01/winxp LV Name winxp VG Name vg01 LV UUID hrXdl6-oRMC-dl7l-mkad-SSDl-y1hf-1Q1MPp LV Write Access read/write LV Creation host, time mywork, 2012-03-16 10:54:08 +0200 LV Status available # open 0 LV Size 5.00 GiB Current LE 1280 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 254:4 -- Evaggelos Balaskas - Unix System Engineer http://gr.linkedin.com/in/evaggelosbalaskas

1 1

[libvirt-users] I can't virt-clone into an existing LVM now (ERROR: clone onto existing storage volume is not supported:) - i could in previous lbvirt versions? (deployment scripts no longer work...)
by Morgan Cox 18 Jul '12

18 Jul '12

Hi To deploy KVM vms I use a KVM template + script - which is cloned, then cloned again and resized - using virt-resize. i.e ---------------------------------------------------- virt-clone --original debian6template-DONTSTART --name NAME.test -f /dev/vgpool/NAME.test virsh vol-create-as vgpool NAME 8G virt-clone --original NAME.test --name NAME -f /dev/vgpool/NAME virt-resize --expand /dev/sda1 /dev/vgpool/NAME.test /dev/vgpool/NAME ---------------------------------------------------- The reason I clone twice is because I know that virt-clone does things to prep it for a new install, also the whole point was to be able to specify a size to be clone into (hence the use of virt-resize) This worked fine on our Ubuntu 11.10 server, however in Ubuntu 12.04 when I try to do the same I get the error 'ERROR Clone onto existing storage volume is not supported: '/dev/vgpool/test' If I can't virt-clone into an existing LVM I know I can clone once - then resize with LVM, then virt-resize into the partition (then virt-sysprep) - however the issue with that is that it is far more fiddly to mange... Previously could just make a 20GB partition and use virt-resize to expand into - using the above method I would have to increase the LVM to the value I want minus the size of the template.. i.e I have to specify - the amount to increase by, rather than the final size I want.... The templates also change size (when I update them, etc) which would mean re-writting the script after every update. Is there a way I can re-enable being able to virt-clone to an existing LVM partition ? As mentioned it works 100% fine in Ubuntu 10.04 Regards

3 4

[libvirt-users] virDomainMemoryStats call
by Parakkal, Navin S 18 Jul '12

18 Jul '12

Hi, I'm using the API virDomainMemoryStats to fetch memory stats for a domain/guest on Fedora 16/RHEL 6.3 . I don't get these counters filled up VIR_DOMAIN_MEMORY_STAT_UNUSED, VIR_DOMAIN_MEMORY_STAT_ACTUAL_BALLOON,VIR_DOMAIN_MEMORY_STAT_AVAILABLE , VIR_DOMAIN_MEMORY_STAT_MAJOR_FAULT and VIR_DOMAIN_MEMORY_STAT_MINOR_FAULT. The version of libvirt 0.9.11 on Fedora 16 . How to get all the counters filled up ? Should I take a specific version of qemu or should I do some config settings so that these values are filled up ? P.S. Please copy me in reply Regards, Navin Parakkal HP Software

3 3

[libvirt-users] Attaching usb devices
by Mauricio Tavares 18 Jul '12

18 Jul '12

Is the only way to attach a usb device to a vm first specifying the device, <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x3080'/> <product id='0x1234'/> </source> </hostdev> and then booting the vm while the device is attached? Can't I attach/detach a USB device to the vm later? I did try the method suggested in http://david.wragg.org/blog/2009/03/usb-pass-through-with-libvirt-and-kvm.h… but did not have much luck. Also, can anyone explain me what happened in this log excerpt: husb: open device 1.18 husb: grabbed usb device 1.18 husb: config #1 need 1 husb: 1 interfaces claimed for configuration 1 husb: device 1.18 disconnected

2 1

[libvirt-users] Set IP for LXC-container through libvirt XML
by Timothy Klim 17 Jul '12

17 Jul '12

Hi! How I can set IP to container without using dhcp? From http://libvirt.org/formatnetwork.html I have: <network> <mac address='00:16:3E:5D:C7:9E'/> <ip address="192.168.122.1" netmask="255.255.255.0"> <dhcp> <range start="192.168.122.100" end="192.168.122.254" /> <host mac="00:16:3e:77:e2:ed" name="foo.example.com" ip="192.168.122.10" /> <host mac="00:16:3e:3e:a9:1a" name="bar.example.com" ip="192.168.122.11" /> </dhcp> </ip> <ip family="ipv6" address="2001:db8:ca2:2::1" prefix="64" /> </network> Can I just set IP for domain(lxc-container)? Thank you.

1 0

[libvirt-users] Is there a version with libvirt supporting domain Autostart?
by xuanmao_001 16 Jul '12

16 Jul '12

I want to know if libvirt supporting qemu domain Autostart? my libvirt version is 0.9.8. xuanmao_001

2 1

[libvirt-users] qemu-ga : windows 2008 64bit not working.
by desi babu 16 Jul '12

16 Jul '12

Qemu Guest Agent on Windows 2008 is not able to connect to virtio-serial socket. Windows Version : 2008 64 Bit Version : qemu-ga -V QEMU Guest Agent 1.1.0 VIRT-IO Serial Driver installed in windows. Driver Provider : Redhat Inc. Driver Date : 61.63.103.2200 Libvirt Settings. <channel type='unix'> <source mode='bind' path='/tmp/qemu-ga.w2008.0.sock'/> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> qemu-ga.exe critical : error opening path critical : error opening channel critical : failed to create guest agent channel critical : failed to initialize guest agent channel. Any recommendations or debugging methods to verify vertio-serial ? Thanks in advance. /Suresh

1 0

[libvirt-users] ubuntu 12.04 x64 virt-manager 0.9.1
by Kobi Biton 15 Jul '12

15 Jul '12

dear experts, I have a clean kvm installation on ubuntu 12.04 x64 , when trying to create my first guest I get the following error: Unable to complete install: 'internal error cannot load AppArmor profile 'libvirt-ac760227-6849-b81e-15f6-a7eae418225f'' Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 45, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/create.py", line 1909, in do_install guest.start_install(False, meter=meter) File "/usr/lib/python2.7/dist-packages/virtinst/Guest.py", line 1236, in start_install noboot) File "/usr/lib/python2.7/dist-packages/virtinst/Guest.py", line 1304, in _create_guest dom = self.conn.createLinux(start_xml or final_xml, 0) File "/usr/lib/python2.7/dist-packages/libvirt.py", line 2166, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self) libvirtError: internal error cannot load AppArmor profile 'libvirt-ac760227-6849-b81e-15f6-a7eae418225f' some details: - the user used on the virt-manager connection is a memeber of the libvirtd group - using ssh key auth from the virt-manager Any Ideas? Thanks!

1 0

[libvirt-users] PCI passthrough troubles
by mike allison 14 Jul '12

14 Jul '12

Hello, I have been struggling as of late to successfully configure a pci passthrough using libvirt with kvm. Hoping someone can shed some light on the problem. Overall my experience with virtualization limited is so please forgive. The guest runs fine till passthrough is configured. I am using virt-manager. This has been tried on both a Fedora17 x86_64 and Arch Linux x86_64 build with pretty much identical errors. I have carefully reviewed my hardware and purchased vt-d enabled parts where needed. vt-d is enabled for my chipset, cpu and in it's enabled in the bios. on both systems I complied a custom kernel to enable DMA Remapping, PCI-stub and set CONFIG_INTEL_IOMMU_DEFAULT_ON=y using kernel boot param: intel_iommu=on (not sure if overkill) have kvm module option allow_unsafe_assigned_interrupts=1 selinux set to permissive mode in fedora. not used in arch when launching I 1) modprobe pci_stub, 2) virsh nodedev-dettach pci device, 3) load guest using virtmanager... it get the following the log outputs * libvirt error window* > Error starting domain: Unable to read from monitor: Connection reset by > peer > > Traceback (most recent call last): > File "/usr/share/virt-manager/virtManager/asyncjob.py", line 45, in > cb_wrapper > callback(asyncjob, *args, **kwargs) > File "/usr/share/virt-manager/virtManager/asyncjob.py", line 66, in tmpcb > callback(*args, **kwargs) > File "/usr/share/virt-manager/virtManager/domain.py", line 1114, in > startup > self._backend.create() > File "/usr/lib/python2.7/site-packages/libvirt.py", line 620, in create > if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self) > libvirtError: Unable to read from monitor: Connection reset by peer > */var/log/libvirt/qemu/AED-VM.log* > char device redirected to /dev/pts/3 > Failed to assign irq for "hostdev0": Input/output error > Perhaps you are assigning a device that shares an IRQ with another device? > */var/log/libvirt/libvirtd.log* > 2012-07-08 22:45:11.403+0000: 3773: warning : ebiptablesDriverInit:4157 : > Could not find 'ebtables' executable > 2012-07-08 22:45:11.442+0000: 3773: error : virSysinfoRead:767 : internal > error Failed to find path for dmidecode binary > 2012-07-08 22:45:17.710+0000: 3764: error : > virConnectNumOfInterfaces:10466 : this function is not supported by the > connection driver: virConnectNumOfInterfaces > 2012-07-08 22:46:13.494+0000: 3764: warning : qemuDomainObjTaint:1371 : > Domain id=1 name='AED-VM' uuid=8f2892d8-df3c-6e75-0fe5-42c1ecd7835d is > tainted: high-privileges > 2012-07-08 22:46:13.725+0000: 3762: error : qemuMonitorIORead:526 : Unable > to read from monitor: Connection reset by peer > 2012-07-08 22:46:13.725+0000: 3762: error : qemuMonitorIO:582 : internal > error event from unexpected fd -1!=21 / watch 9!=9 > 2012-07-08 22:48:51.281+0000: 4097: info : libvirt version: 0.9.13 > * dmesg* > [ 158.017387] virbr0: port 1(vnet0) entered forwarding state > [ 158.017395] virbr0: port 1(vnet0) entered forwarding state > [ 158.017615] ADDRCONF(NETDEV_CHANGE): virbr0: link becomes ready > [ 158.476879] assign device 0:3:2.0 > [ 158.477080] deassign device 0:3:2.0 > [ 158.719521] virbr0: port 1(vnet0) entered disabled state > [ 158.719673] device vnet0 left promiscuous mode > any help would be greatly appreciated. mike allison

1 0

Re: [libvirt-users] [ovs-discuss] OpenVswitch with KVM virtual machines
by Neha Jatav 12 Jul '12

12 Jul '12

I am running NOX controller with a python script that prints out the destination mac and the source mac for each packet arriving at the now controller and then floods it out. So here's what happening: With em1 connected, all the packets that arrive at em1 are coming to the controller and printing out the details. However, without em1 connected to the OVS, when I have the following setup: ____ ____ / VM1\______br0_______/ VM3\ \____/ | \____/ | _|_ /VM2\ \___/ VM1 & VM2 are of the same subnet. They can ping each other. The ping packets aren't seen at the controller probably because they are in the same subnet and they don't need a flow table entry. VM3 is in a different subnet. So, when I ping from VM1 to VM3 or viceversa, they aren't reachable to each other. However, the packets do not arrive at the controller at all. Could you suggest me what might possibly be wrong. This is how the bridge looks: $sudo ovs-vsctl br0 show Bridge "br0" Port "vnet1" Interface "vnet1" Port "br0" Interface "br0" type: internal Port "vnet0" Interface "vnet0" Port "vnet2" Interface "vnet2" ovs_version: "1.4.0" Thanks and Regards, Neha On 7/9/12 11:48 PM, "Neha Jatav" <jneha(a)yahoo-inc.com> wrote: > > >On 7/9/12 10:25 PM, "Ben Pfaff" <blp(a)nicira.com> wrote: > >>On Tue, Jul 10, 2012 at 01:46:07AM +0900, Neha Jatav wrote: >>> I have KVM installed on my Fedora 17 box. I added the network >>>interfaces of the virtual machines to the openvswitch bridge as follows: >>> >>> ____ ____ >>> / VM1\______br0_______/ em1\ >>> \____/ | \____/ >>> | >>> _|_ >>> /VM2\ >>> \____/ >>> >>> virbr0 is the virtual network switch >>> VM1 and VM2 are on the same subnet having tap interfaces vnet0 and >>>vnet1 respectively. >>> em1 is the default network interface. >>> >>> $sudo ovs-vsctl add-br br0 >>> $sudo ovs-vsctl add-port br0 em1 >>> $sudo ifconfig br0 <ip address of em1> >>> $sudo ip route del default dev em1 >>> $sudo ip route add default dev br0 >>> (Using the above commands, I was able to connect to the internet) >>> >>> $sudo brctl delif virbr0 vnet0 >>> $sudo ovs-vsctl add-port br0 vnet0 >>> $sudo brctl delif virbr0 vnet1 >>> $sudo ovs-vsctl add-port br0 vnet1 >>> >>> $brctl show >>> bridge name bridge id STP enabled interfaces >>> virbr0 8000.52540094e45e yes virbr0-nic >>> vnet0 >>> vnet2 >>> >>> $sudo ovs-vsctl show >>> Bridge "br0" >>> Port "vnet1" >>> Interface "vnet1" >>> Port "br0" >>> Interface "br0" >>> type: internal >>> Port "vnet0" >>> Interface "vnet0" >>> Port "em1" >>> Interface "em1" >>> ovs_version: "1.4.0" >>> >>> $ifconfig em1 >>> em1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 >>> inet 10.66.97.253 netmask 255.255.254.0 broadcast >>>10.66.97.255 >>> inet6 fe80::226:55ff:fe3e:971c prefixlen 64 scopeid >>>0x20<link> >>> ether 00:26:55:3e:97:1c txqueuelen 1000 (Ethernet) >>> RX packets 194955 bytes 81216930 (77.4 MiB) >>> RX errors 0 dropped 0 overruns 0 frame 0 >>> TX packets 53004 bytes 9477482 (9.0 MiB) >>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >>> device interrupt 19 memory 0xf0200000-f0220000 >>> >>> $ifconfig br0 >>> br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 >>> inet 10.66.97.253 netmask 255.0.0.0 broadcast 10.255.255.255 >>> inet6 fe80::226:55ff:fe3e:971c prefixlen 64 scopeid >>>0x20<link> >>> ether 00:26:55:3e:97:1c txqueuelen 0 (Ethernet) >>> RX packets 84745 bytes 60302978 (57.5 MiB) >>> RX errors 0 dropped 0 overruns 0 frame 0 >>> TX packets 44528 bytes 7732040 (7.3 MiB) >>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >>> >>> By default, the OVS should act as a MAC-layer learning switch. However, >>>the VMs which are in the same subnet can ping each other but the VMs >>>can't ping the host machine (10.66.97.253) & viceversa. >>> Can you tell me where am I wrong in my approach? >> >>You appear to have both OVS bridges and Linux bridges. Why? And at >>least interface vnet0 is configured to be on both the Linux bridge and >>the OVS bridge. That can't work. > >$sudo brctl delif virbr0 vnet0 >I deleted this interface from virbr0 using the above command and only then >I connected it to br0. So, vnet0 is only configured on the OVS bridge. >Same is true with the vnet1. > > > >> >>Also you appear to have the same IP address 10.66.97.253 configured on >>both em1 and br0 (with different netmasks). That won't work properly >>either. > >I did the following: >$sudo ifconfig br0 10.66.97.253 netmask 255.255.254.0 >It resulted in losing connection to the internet. > >> >>Did you read the FAQ? http://openvswitch.org/faq/ >

2 1

[libvirt-users] Different SAS controller IDs
by Anton Nikiforov 12 Jul '12

12 Jul '12

Dear All, I have problem with setting up migration on Intel Multi-Flex server. The problem is that SAS controller IDs (and volume ids in /dev/disk/by-path directory) are different between nodes. For example on node0 i have: lrwxrwxrwx 1 root root 9 Jun 29 07:20 pci-0000:04:00.0-sas-0x500015500002040a-lun-0 -> ../../sda lrwxrwxrwx 1 root root 10 May 27 09:17 pci-0000:04:00.0-sas-0x500015500002040a-lun-0-part1 -> ../../sda1 ....... On node1 i have: lrwxrwxrwx 1 root root 9 Jul 12 21:19 /dev/disk/by-path/pci-0000:04:00.0-sas-0x5000155000020409-lun-0 -> ../../sda lrwxrwxrwx 1 root root 10 Jul 12 21:19 /dev/disk/by-path/pci-0000:04:00.0-sas-0x5000155000020409-lun-0-part1 -> ../../sda1 ........ Difference is in 0x500015500002040a and 0x5000155000020409 But this is the matter of migration falure because migration script cannot find needed volume. Is there any chance to fix it somehow? Best regards, Anton Nikiforov

2 2

[libvirt-users] Starting a program inside VM through libvirt
by Jørgen Nordmoen 12 Jul '12

12 Jul '12

Hi again. I was just wondering if there are any support for running programs inside a VM through libvirt. From what I can see in the API the only solution I found was connecting to the VM with openConsole and running the program I want. This however seems a bit tricky through Python and I was just wondering if there are any simpler solutions. Best regards. Jørgen

2 2

[libvirt-users] PCI-Passthrough suddenly stopped working
by Rouven Sacha 12 Jul '12

12 Jul '12

Hi everybody! On a Centos 5.8 with libvirt qemu-0.10.5-1.el5.2, libvirt-0.8.2-22.el5 and 2.6.18-308.11.1.el5 I have a Windows machine that used to have pci-passthrough for a device enabled and working. After an update (kernel, libvirt afaik) and a reboot, pci-passthrough stopped working. Intel IOMMU is enabled (can see that from the dmesg output). All i get on the console when i try to start the vm is the following: Fehler: internal error process exited while connecting to monitor: char device redirected to /dev/pts/3 Failed to assign device "14:00.2" : Invalid argument Failed to deassign device "14:00.2" : Invalid argument Failed to initialize assigned device host=14:00.2 SELinux ist disabled. Does anyone have any hint what could have possibly gone wrong? As an additional info: "virsh nodeddev-list" also doesn't work. I don't know if I mix that up, but i seem to remember that that used to work on that machine. root@kvm ~]# virsh nodedev-list --tree Fehler: Failed to count node devices Fehler: this function is not supported by the connection driver: virNodeNumOfDevices Any hints are greatly appreciated! Thanks & Cheers, Rouven -- Blinkenlichten Open Source Solutions Maass Sacha GbR | Weigandufer 45 | 12059 Berlin tel: +493013896247 | fax: +493013896249 | mob: +491744220127 Web: http://www.blinkenlichten.de/ G+: http://gplus.to/blinkenlichten Blinkenlichten Zarafa Hosted Tweets: http://twitter.com/zarafamail/

2 2

[libvirt-users] compiling docs from git
by Arindam Choudhury 12 Jul '12

12 Jul '12

Hi, I am unable to compile documents obtained from the git source. I am getting this error: Brand 'libvirt' had no content to copy. at /usr/bin/publican line 763 Thanks

2 1

[libvirt-users] storage volume's size change
by Shantanu Pavgi 11 Jul '12

11 Jul '12

I have a question regarding storage volumes. I have uploaded a sparsed raw disk file to a storage volume, where virtual/max. size of the raw disk file is larger than size of the initial libvirt volume. Following is an example of commands: # Create storage volume of capacity 9G $ virsh-sys vol-create-as --pool pool-01 --name saturn.img --capacity 9G # Display volume info $ virsh-sys vol-info saturn.img --pool pool-01 Name: saturn.img Type: file Capacity: 9.00 GB Allocation: 36.11 MB # Upload raw disk file to the volume $ virsh-sys vol-upload --vol saturn.img --file /lustre/scratch/shantanup/saturn-disk.img --pool pool-01 # qemu-img info on disk file which was uploaded $ qemu-img info /lustre/scratch/shantanup/saturn-disk.img file format: raw virtual size: 20G (21474836480 bytes) disk size: 5.7G # vol-info after uploading the raw disk image $ virsh-sys vol-info saturn.img --pool pool-01 Name: saturn.img Type: file Capacity: 20.00 GB Allocation: 20.00 GB The vol-info command indicates that volume size has changed after uploading the raw disk image to it. So has the volume size really changed to 20G or will the system experience any problem after actual disk size (currently 5.7G) hits 9G limit? I can't directly poke into the storage pool mount to run ls or qemu-img commands on underlying volumes, so I don't have that information. Any help? -- Thanks, Shantanu

1 0

[libvirt-users] live migration
by hcyy 11 Jul '12

11 Jul '12

Hello, everybody. I use NFS to do live migration。After input virsh --connect=qemu:///system --quiet migrate --live vm12 qemu+tcp://pcmk-1/system (vm12 is vm name,/pcmk-1 is host name)it use almost 10s for preparation. During the 10s,the vm is still runing and can ping other vm. But if i input mkdir pcmk-6 in vm during the 10s,it say :mkdir: cannot create directory `pcmk-6': Read-only file system. Anybody can tell me this situation is due to my wrong configure or libvirt cannot mkdir during migration？thanks!

2 2

[libvirt-users] segfault on snapshot-list, 0.9.13
by Andrey Korolyov 10 Jul '12

10 Jul '12

Hi, virsh crashes when doing snapshot-list: Program received signal SIGSEGV, Segmentation fault. 0x00007f4ba600dc51 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) bt #0 0x00007f4ba600dc51 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x00007f4ba60905b7 in xdr_string () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x00007f4ba8e92cfe in xdr_remote_nonnull_string (xdrs=<optimized out>, objp=<optimized out>) at /var/tmp/build/libvirt/libvirt-0.9.13/./src/remote/remote_protocol.c:31 #3 0x00007f4ba8e93111 in xdr_remote_nonnull_domain (xdrs=0x7fff39fc2db0, objp=0x7fff39fc3010) at /var/tmp/build/libvirt/libvirt-0.9.13/./src/remote/remote_protocol.c:58 #4 0x00007f4ba8e99691 in xdr_remote_domain_list_all_snapshots_args (xdrs=0x7fff39fc2db0, objp=0x7fff39fc3010) at /var/tmp/build/libvirt/libvirt-0.9.13/./src/remote/remote_protocol.c:4549 #5 0x00007f4ba8ea60f7 in virNetMessageEncodePayload (msg=0x1a306c0, filter=0x7f4ba8e99670 <xdr_remote_domain_list_all_snapshots_args>, data=0x7fff39fc3010) at /var/tmp/build/libvirt/libvirt-0.9.13/./src/rpc/virnetmessage.c:351 #6 0x00007f4ba8e9de3f in virNetClientProgramCall (prog=<optimized out>, client=0x1a30ab0, serial=7, proc=274, noutfds=<optimized out>, outfds=0x0, ninfds=0x0, infds=0x0, args_filter=0x7f4ba8e99670 <xdr_remote_domain_list_all_snapshots_args>, args=0x7fff39fc3010, ret_filter=0x7f4ba8e996e0 <xdr_remote_domain_list_all_snapshots_ret>, ret=0x7fff39fc2ff0) at /var/tmp/build/libvirt/libvirt-0.9.13/./src/rpc/virnetclientprogram.c:327 #7 0x00007f4ba8e7f550 in callWithFD (priv=0x1a30400, flags=<optimized out>, fd=<optimized out>, proc_nr=274, args_filter=<optimized out>, args=<optimized out>, ret_filter=0x7f4ba8e996e0 <xdr_remote_domain_list_all_snapshots_ret>, ret=0x7fff39fc2ff0 "", conn=<optimized out>) at /var/tmp/build/libvirt/libvirt-0.9.13/./src/remote/remote_driver.c:4799 #8 0x00007f4ba8e7f6a4 in call (priv=<optimized out>, flags=<optimized out>, proc_nr=<optimized out>, args_filter=<optimized out>, args=<optimized out>, ret_filter=<optimized out>, ret=0x7fff39fc2ff0 "", conn=<optimized out>) at /var/tmp/build/libvirt/libvirt-0.9.13/./src/remote/remote_driver.c:4820 #9 0x00007f4ba8e8edfd in remoteDomainListAllSnapshots (dom=0x1a300f0, snapshots=0x7fff39fc3218, flags=<optimized out>) at /var/tmp/build/libvirt/libvirt-0.9.13/./src/remote/remote_driver.c:4895 #10 0x00007f4ba8e6c36f in virDomainListAllSnapshots (domain=0x1a300f0, snaps=0x7fff39fc3218, flags=0) at /var/tmp/build/libvirt/libvirt-0.9.13/./src/libvirt.c:17262 #11 0x000000000042bca6 in vshSnapshotListCollect (tree=false, flags=0, from=0x0, dom=0x1a300f0, ctl=0x7fff39fc35e0) at /var/tmp/build/libvirt/libvirt-0.9.13/./tools/virsh.c:17198 #12 cmdSnapshotList (ctl=0x7fff39fc35e0, cmd=<optimized out>) at /var/tmp/build/libvirt/libvirt-0.9.13/./tools/virsh.c:17590 #13 0x000000000040ec92 in vshCommandRun (ctl=0x7fff39fc35e0, cmd=0x1a30f20) at /var/tmp/build/libvirt/libvirt-0.9.13/./tools/virsh.c:19461 #14 0x000000000040bdb0 in main (argc=<optimized out>, argv=<optimized out>) at /var/tmp/build/libvirt/libvirt-0.9.13/./tools/virsh.c:21094

2 1

[libvirt-users] What is the procedure of libvirt internal when you run a domain.
by xuanmao_001 10 Jul '12

10 Jul '12

Hi, all. I want to know when I press run button. start a domain. What is the procedure of libvirt internal. I know it will call virDomainCreate(),then qemuDomainStart() -> qemuDomainStartWithFlags(). what is the next? xuanmao_001

2 1

[libvirt-users] Adding a second lv as vm drive: how to set the pci part
by Mauricio Tavares 10 Jul '12

10 Jul '12

Let's say I have a vm, vm1, which has a lv as its hard drive: <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='none' io='native'/> <source file='/dev/mapper/kvmtest_vm1_rootvg'/> <target dev='vda' bus='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> I could add pickles as a second drive as follows: <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='none' io='native'/> <source file='/dev/mapper/kvmtest_pickles'/> <target dev='vdb' bus='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </disk> but I am trying to understand the pci address entry. Must drive be on a different slot?

2 1

[libvirt-users] Issue with getCPUStats and getMemoryStats
by Ananth 10 Jul '12

10 Jul '12

Hi, I am facing issue with the calls getCPUStats and getMemoryStats. Please find the error below. AttributeError: 'module' object has no attribute 'VIR_NODE_CPU_STATS_ALL_CPUS' >>> print con.getCPUStats(2, None, 0, 0) Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/lib64/python2.6/site-packages/libvirt.py", line 2173, in getCPUStats ret = libvirtmod.virNodeGetCPUStats(self._o, cpuNum, params, nparams, flags) *AttributeError: 'module' object has no attribute 'virNodeGetCPUStats'* >>> print con.getMemoryStats(2, None, 0, 0) Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/lib64/python2.6/site-packages/libvirt.py", line 2245, in getMemoryStats ret = libvirtmod.virNodeGetMemoryStats(self._o, cellNum, params, nparams, flags) *AttributeError: 'module' object has no attribute 'virNodeGetMemoryStats'* Kind let me know if this is a known issue. I came to know that this issue was fixed in 0.9.8 version of libvirt. I am executing these calls on libvirt-0.9.8 compiled (--with-netcf) on centos 6.2. Please let me know if any other option needs to be specified while compiling libvirt in order to get this working. -- Regards Ananth

2 1

Re: [libvirt-users] virsh iface-list () - function is not supported
by Osier Yang 10 Jul '12

10 Jul '12

On 2012年07月03日 00:42, Ananth wrote: > Thank you. Can you give pointers on how to compile libvirt code? and > documentation available for the same? Sorry for the late response, I'm in vacation. Yes, there is documentation. http://libvirt.org/compiling.html Regards, Osier

2 3

[libvirt-users] OpenVswitch with KVM virtual machines
by Neha Jatav 09 Jul '12

09 Jul '12

Hey, I have KVM installed on my Fedora 17 box. I added the network interfaces of the virtual machines to the openvswitch bridge as follows: ____ ____ / VM1\______br0_______/ em1\ \____/ | \____/ | _|_ /VM2\ \____/ virbr0 is the virtual network switch VM1 and VM2 are on the same subnet having tap interfaces vnet0 and vnet1 respectively. em1 is the default network interface. $sudo ovs-vsctl add-br br0 $sudo ovs-vsctl add-port br0 em1 $sudo ifconfig br0 <ip address of em1> $sudo ip route del default dev em1 $sudo ip route add default dev br0 (Using the above commands, I was able to connect to the internet) $sudo brctl delif virbr0 vnet0 $sudo ovs-vsctl add-port br0 vnet0 $sudo brctl delif virbr0 vnet1 $sudo ovs-vsctl add-port br0 vnet1 $brctl show bridge name bridge id STP enabled interfaces virbr0 8000.52540094e45e yes virbr0-nic vnet0 vnet2 $sudo ovs-vsctl show Bridge "br0" Port "vnet1" Interface "vnet1" Port "br0" Interface "br0" type: internal Port "vnet0" Interface "vnet0" Port "em1" Interface "em1" ovs_version: "1.4.0" $ifconfig em1 em1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 10.66.97.253 netmask 255.255.254.0 broadcast 10.66.97.255 inet6 fe80::226:55ff:fe3e:971c prefixlen 64 scopeid 0x20<link> ether 00:26:55:3e:97:1c txqueuelen 1000 (Ethernet) RX packets 194955 bytes 81216930 (77.4 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 53004 bytes 9477482 (9.0 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 19 memory 0xf0200000-f0220000 $ifconfig br0 br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 10.66.97.253 netmask 255.0.0.0 broadcast 10.255.255.255 inet6 fe80::226:55ff:fe3e:971c prefixlen 64 scopeid 0x20<link> ether 00:26:55:3e:97:1c txqueuelen 0 (Ethernet) RX packets 84745 bytes 60302978 (57.5 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 44528 bytes 7732040 (7.3 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 By default, the OVS should act as a MAC-layer learning switch. However, the VMs which are in the same subnet can ping each other but the VMs can't ping the host machine (10.66.97.253) & viceversa. Can you tell me where am I wrong in my approach? Thanks and regards, Neha.

2 1

[libvirt-users] guest VM waiting for a symbol at serial console
by Andrey Korolyov 09 Jul '12

09 Jul '12

Hi, Recently I`ve run into weird bug, which may be reproduced in following way: - start qemu virtual machine configured with direct boot and kernel args like 'console=tty0 console=ttyS0,38400n8', connect to serial console, disconnect and then shutdown vm - try to start vm again, machine hangs on booting kernel until I press any key into 'virsh console' session - after first power cycle, this bug remains until host system will be rebooted. This happens only when vm experiencing 'power cycle', rebooting inside same kvm process do fine. guest kernel 3.4.4/3.2.20, libvirt 0.9.12 and qemu-1.1.0

1 0