- Users - libvirt List Archives

[libvirt-users] Where does "cmd" initailize in qemu_command.c?
by He Xin 17 Aug '12

17 Aug '12

Hi, Excuse me, I have a question when I reading the libvirt source codes. I have known the process of how libvirt start/manage qemu, since I need to write a driver based on libvirt. But one thing also confused, please give me some tips. 1. In qemu_command.c, there is a function call "cmd = virCommandNewArgList(emulator, "-S", NULL);", which initializes pointer "cmd". However, I don't find the initial value of "cmd->args", which represents the input of virFindFileInPath in Util.c. Through virFindFileInPath, one could find a requested executable file in the PATH env to start specified hypervisors. So could you please tell me what the value of args[0] is? Or where does cmd->args initialize? 2. In qemu_driver.c, there is a function call "vm = virDomainFindByUUID(&driver->domains, dom->uuid);", whose returned value "vm" is important in the next functions. Then we could get the "vm"'s value in hash.c which is the end part to lookup domains saved in hashtable. May I know where does HashTable initialize? I mean where can I set the hashtable's values in detail, if I want to modify some values? 3. This might be the same as question 1. In command.c, "execve(cmd->args[0], cmd->args, cmd->env)" is a way to exec command. About qemu_driver, what is the value of those three inputs? Thanks a lot! Regard, Corey

2 2

[libvirt-users] Fwd: vm pxe fail
by Alex Jia 17 Aug '12

17 Aug '12

----- Forwarded Message ----- From: "Andrew Holway" <a.holway(a)syseleven.de> To: "Alex Jia" <ajia(a)redhat.com> Cc: kvm(a)vger.kernel.org Sent: Friday, August 17, 2012 4:24:33 PM Subject: Re: [libvirt-users] vm pxe fail Hello, On Aug 17, 2012, at 4:34 AM, Alex Jia wrote: > Hi Andrew, > I can't confirm a root reason based on your information, perhaps you may > try to find a reason by yourself via the following docs: > > http://wiki.libvirt.org/page/PXE_boot_%28or_dhcp%29_on_guest_failed (Troubleshooting) > http://docs.fedoraproject.org/en-US/Fedora/13/html/Virtualization_Guide/sec… (User Guide) Everything seems quite normal. > > If can't, please provide your version of kvm, libvirt, tftp, etc, and run 'virsh net-dumpxml br0' to dump your > network bridge XML configuration, and run 'cat pxelinux.cfg' to show your pxelinux configuration, thanks. default is my pxelinux configuration but I'm not sure is this is what your after. dhcp is a protocol decode of the DHCP traffic. You see that the VM is sending each request twice which is a bit odd. [root@node002 ~]# yum list | grep qemu gpxe-roms-qemu.noarch 0.9.7-6.9.el6 @base qemu-img.x86_64 2:0.12.1.2-2.295.el6_3.1 @updates qemu-kvm.x86_64 2:0.12.1.2-2.295.el6_3.1 @updates qemu-guest-agent.x86_64 2:0.12.1.2-2.295.el6_3.1 updates qemu-kvm-tools.x86_64 2:0.12.1.2-2.295.el6_3.1 updates br0 is created by brctl. There is not XML config as far as I am aware. [root@node002 ~]# ifconfig br0 br0 Link encap:Ethernet HWaddr 00:9C:02:24:1A:E0 inet addr:10.141.80.2 Bcast:10.141.255.255 Mask:255.255.0.0 inet6 addr: fe80::29c:2ff:fe24:1ae0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:185129 errors:0 dropped:0 overruns:0 frame:0 TX packets:2094 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:8820359 (8.4 MiB) TX bytes:123842 (120.9 KiB) [root@node002 ~]# ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:02:C9:36:21:A1 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) [root@node002 ~]# brctl show bridge name bridge id STP enabled interfaces br0 8000.009c02241ae0 no eth1 vnet0 virbr0 8000.525400a6d5aa yes virbr0-nic > > -- > Regards, > Alex > > > ----- Original Message ----- > From: "Andrew Holway" <a.holway(a)syseleven.de> > To: kvm(a)vger.kernel.org > Sent: Thursday, August 16, 2012 8:25:35 PM > Subject: [libvirt-users] vm pxe fail > > Hallo > > I have a kvm vm that I am attempting to boot from pxe. The dhcp works perfectly and I can see the VM in the pxe server arp. but the tftp just times out. I don't see any tftp traffic on either the physical host or on the pie server. I am using a bridged interface. I have tried using several virtual nic drivers, several different mac addresses and several different ips. on the physical host I can get the pxelinux.0 file from the pxe server via tftp and can clearly see that traffic with tcpdump. > > Ive tried using various virtual interfaces. > > I can pxe boot my physical hosts with no problems. > > I can tftp fine from the physical host and see the traffic with ethdump > > Here is the terminal output from the VM: https://dl.dropbox.com/u/98200887/Screen%20Shot%202012-08-15%20at%206.41.12… > > Thanks, > > Andrew > > [root@node002 ~]# yum list | grep qemu > gpxe-roms-qemu.noarch 0.9.7-6.9.el6 @base > qemu-img.x86_64 2:0.12.1.2-2.295.el6_3.1 @updates > qemu-kvm.x86_64 2:0.12.1.2-2.295.el6_3.1 @updates > qemu-guest-agent.x86_64 2:0.12.1.2-2.295.el6_3.1 updates > qemu-kvm-tools.x86_64 2:0.12.1.2-2.295.el6_3.1 updates > > [root@node002 ~]# ethtool eth0 > Settings for eth0: > Supported ports: [ TP ] > Supported link modes: 10000baseT/Full > Supports auto-negotiation: No > Advertised link modes: 10000baseT/Full > Advertised pause frame use: No > Advertised auto-negotiation: No > Speed: Unknown! > Duplex: Unknown! (255) > Port: Twisted Pair > PHYAD: 0 > Transceiver: internal > Auto-negotiation: off > MDI-X: Unknown > Supports Wake-on: g > Wake-on: g > Current message level: 0x00000014 (20) > Link detected: no > > [root@node002 ~]# brctl show > bridge name bridge id STP enabled interfaces > br0 8000.009c02241ae0 no eth1 > vnet0 > virbr0 8000.525400a6d5aa yes virbr0-nic > > [root@node002 ~]# ethtool vnet0 > Settings for vnet0: > Supported ports: [ ] > Supported link modes: > Supports auto-negotiation: No > Advertised link modes: Not reported > Advertised pause frame use: No > Advertised auto-negotiation: No > Speed: 10Mb/s > Duplex: Full > Port: Twisted Pair > PHYAD: 0 > Transceiver: internal > Auto-negotiation: off > MDI-X: Unknown > Current message level: 0xffffffa1 (-95) > Link detected: yes > > <domain type='kvm'> > <name>vm004</name> > <uuid>4f03b09b-e834-bbf3-a6c2-1689f3156ef2</uuid> > <memory unit='KiB'>2097152</memory> > <currentMemory unit='KiB'>2097152</currentMemory> > <vcpu placement='static'>2</vcpu> > <os> > <type arch='x86_64' machine='rhel6.3.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/libexec/qemu-kvm</emulator> > <disk type='file' device='disk'> > <driver name='qemu' type='raw' cache='none'/> > <source file='/cm/shared/vm/vm004.img'/> > <target dev='hda' bus='ide'/> > <address type='drive' controller='0' bus='0' target='0' unit='0'/> > </disk> > <disk type='block' device='cdrom'> > <driver name='qemu' type='raw'/> > <target dev='hdc' bus='ide'/> > <readonly/> > <address type='drive' controller='0' bus='1' target='0' unit='0'/> > </disk> > <controller type='usb' index='0'> > <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> > </controller> > <controller type='ide' index='0'> > <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> > </controller> > <interface type='bridge'> > <mac address='00:00:00:00:00:0d'/> > <source bridge='br0'/> > <model type='rtl8139'/> > <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='0x04' function='0x0'/> > </memballoon> > </devices> > </domain> > > > > _______________________________________________ > libvirt-users mailing list > libvirt-users(a)redhat.com > https://www.redhat.com/mailman/listinfo/libvirt-users

1 0

[libvirt-users] vm pxe fail
by Andrew Holway 16 Aug '12

16 Aug '12

Hallo I have a kvm vm that I am attempting to boot from pxe. The dhcp works perfectly and I can see the VM in the pxe server arp. but the tftp just times out. I don't see any tftp traffic on either the physical host or on the pie server. I am using a bridged interface. I have tried using several virtual nic drivers, several different mac addresses and several different ips. on the physical host I can get the pxelinux.0 file from the pxe server via tftp and can clearly see that traffic with tcpdump. Ive tried using various virtual interfaces. I can pxe boot my physical hosts with no problems. I can tftp fine from the physical host and see the traffic with ethdump Here is the terminal output from the VM: https://dl.dropbox.com/u/98200887/Screen%20Shot%202012-08-15%20at%206.41.12… Thanks, Andrew [root@node002 ~]# yum list | grep qemu gpxe-roms-qemu.noarch 0.9.7-6.9.el6 @base qemu-img.x86_64 2:0.12.1.2-2.295.el6_3.1 @updates qemu-kvm.x86_64 2:0.12.1.2-2.295.el6_3.1 @updates qemu-guest-agent.x86_64 2:0.12.1.2-2.295.el6_3.1 updates qemu-kvm-tools.x86_64 2:0.12.1.2-2.295.el6_3.1 updates [root@node002 ~]# ethtool eth0 Settings for eth0: Supported ports: [ TP ] Supported link modes: 10000baseT/Full Supports auto-negotiation: No Advertised link modes: 10000baseT/Full Advertised pause frame use: No Advertised auto-negotiation: No Speed: Unknown! Duplex: Unknown! (255) Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: off MDI-X: Unknown Supports Wake-on: g Wake-on: g Current message level: 0x00000014 (20) Link detected: no [root@node002 ~]# brctl show bridge name bridge id STP enabled interfaces br0 8000.009c02241ae0 no eth1 vnet0 virbr0 8000.525400a6d5aa yes virbr0-nic [root@node002 ~]# ethtool vnet0 Settings for vnet0: Supported ports: [ ] Supported link modes: Supports auto-negotiation: No Advertised link modes: Not reported Advertised pause frame use: No Advertised auto-negotiation: No Speed: 10Mb/s Duplex: Full Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: off MDI-X: Unknown Current message level: 0xffffffa1 (-95) Link detected: yes <domain type='kvm'> <name>vm004</name> <uuid>4f03b09b-e834-bbf3-a6c2-1689f3156ef2</uuid> <memory unit='KiB'>2097152</memory> <currentMemory unit='KiB'>2097152</currentMemory> <vcpu placement='static'>2</vcpu> <os> <type arch='x86_64' machine='rhel6.3.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/libexec/qemu-kvm</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='none'/> <source file='/cm/shared/vm/vm004.img'/> <target dev='hda' bus='ide'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='block' device='cdrom'> <driver name='qemu' type='raw'/> <target dev='hdc' bus='ide'/> <readonly/> <address type='drive' controller='0' bus='1' target='0' unit='0'/> </disk> <controller type='usb' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='ide' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <interface type='bridge'> <mac address='00:00:00:00:00:0d'/> <source bridge='br0'/> <model type='rtl8139'/> <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='0x04' function='0x0'/> </memballoon> </devices> </domain>

1 0

[libvirt-users] error: virsh not could create bridge interface
by Gao Yongwei 16 Aug '12

16 Aug '12

hello, virsh iface-bridge to build bridge interface does not work for me,i've searched in google but got nothing ,please give some help,thanks. # VIRSH_DEBUG=0 VIRSH_LOG_FILE=bridge.log virsh iface-bridge eth0 br0 iface-bridge: found option <interface>: eth0 iface-bridge: <interface> trying as interface NAME libvir: Interface error : Interface not found: couldn't find interface named 'br0' libvir: Interface error : internal error could not get interface XML description: XSLT transformation failed - runtime error: file /usr/share/netcf/xml/initscripts-get.xsl line 196 element node error: Failed to define new bridge interface br0 error: internal error could not get interface XML description: XSLT transformation failed - runtime error: file /usr/share/netcf/xml/initscripts-get.xsl line 196 element node # virsh version Compiled against library: libvir 0.9.10 Using library: libvir 0.9.10 Using API: QEMU 0.9.10 Running hypervisor: QEMU 0.12.1 # cat bridge.log [2012.08.16 16:16:50 virsh 10895] INFO iface-bridge: found option <interface>: eth0 [2012.08.16 16:16:50 virsh 10895] DEBUG iface-bridge: <interface> trying as interface NAME [2012.08.16 16:16:50 virsh 10895] ERROR Failed to define new bridge interface br0 [2012.08.16 16:16:50 virsh 10895] ERROR internal error could not get interface XML description: XSLT transformation failed - runtime error: file /usr/share/netcf/xml/initscripts-get.xsl line 196 element node this is some debug log from /var/log/libvirt/libvirtd.log: 2012-08-16 08:54:25.724+0000: 11526: debug : virInterfaceDefineXML:10794 : conn=0x7f963c0009c0, xml=<?xml version="1.0"?> <interface type="bridge" name="br0"> <start mode="onboot"/> <protocol family="ipv4"> <ip address="118.123.12.65" prefix="25"/> <route gateway="118.123.12.1"/> </protocol> <bridge stp="on" delay="0"><interface type="ethernet" name="eth0"><mac address="00:30:48:D9:F7:EE"/></interface></bridge></interface> , flags=0 2012-08-16 08:54:25.724+0000: 11523: debug : virEventPollCleanupTimeouts:506 : Cleanup 3 2012-08-16 08:54:25.724+0000: 11523: debug : virEventPollCleanupHandles:554 : Cleanup 8 2012-08-16 08:54:25.724+0000: 11523: debug : virEventPollMakePollFDs:383 : Prepare n=0 w=1, f=7 e=1 d=0 2012-08-16 08:54:25.724+0000: 11523: debug : virEventPollMakePollFDs:383 : Prepare n=1 w=2, f=9 e=1 d=0 2012-08-16 08:54:25.724+0000: 11523: debug : virEventPollMakePollFDs:383 : Prepare n=2 w=3, f=12 e=1 d=0 2012-08-16 08:54:25.724+0000: 11523: debug : virEventPollMakePollFDs:383 : Prepare n=3 w=4, f=13 e=1 d=0 2012-08-16 08:54:25.724+0000: 11523: debug : virEventPollMakePollFDs:383 : Prepare n=4 w=5, f=6 e=1 d=0 2012-08-16 08:54:25.724+0000: 11523: debug : virEventPollMakePollFDs:383 : Prepare n=5 w=6, f=16 e=1 d=0 2012-08-16 08:54:25.724+0000: 11523: debug : virEventPollMakePollFDs:383 : Prepare n=6 w=7, f=15 e=1 d=0 2012-08-16 08:54:25.724+0000: 11523: debug : virEventPollMakePollFDs:383 : Prepare n=7 w=8, f=17 e=1 d=0 2012-08-16 08:54:25.724+0000: 11523: debug : virEventPollCalculateTimeout:325 : Calculate expiry of 3 timers 2012-08-16 08:54:25.724+0000: 11523: debug : virEventPollCalculateTimeout:351 : Timeout at 0 due in -1 ms 2012-08-16 08:54:25.724+0000: 11523: debug : virEventPollRunOnce:619 : EVENT_POLL_RUN: nhandles=8 imeout=-1 2012-08-16 08:54:25.730+0000: 11526: error : interfaceDefineXML:425 : internal error could not get interface XML description: XSLT transformation failed - runtime error: file /usr/share/netcf/xml/initscripts-get.xsl line 196 element node thanks.

1 0

[libvirt-users] What can cause "libvirtd dead but pid file exists."
by xuanmao_001 16 Aug '12

16 Aug '12

Hi, # service libvirtd status libvirtd dead but pid file exists. I operated VMs(like create, edit, delte) normally for a second, but the libvirtd on host was dead. I checked the libvirtd.log but didn't find any useful information. so I want to know what can cause the problem? another question: I found the message in /var/log/message like "libvirtd: Could not find keytab file: /etc/libvirt/krb5.tab: Permission denied." what is going wrong? my libvirt version: 0.9.8. xuanmao_001

1 0

[libvirt-users] Source of Qcow2 Image Corruption
by Andrew Martin 14 Aug '12

14 Aug '12

Hello, I have two KVM virtual machine nodes in a high-availability cluster using Pacemaker + Heartbeat on Ubuntu 10.04 Server amd64. This cluster hosts a single Ubuntu 10.04 VM which uses a qcow2 image file, myvm.qcow2, with a backing file, backingfile.qcow2. This morning, the VM suddenly powered off. I attempted to start it again with virsh start domain, but it would only start briefly and then power off again. I checked the qcow2 disk image and found countless corruption errors: root@vmhost:/mnt/storage/vmstore/disks# qemu-img info myvm.qcow2 image: myvm.qcow2 file format: qcow2 virtual size: 9.8G (10485760000 bytes) disk size: 13G cluster_size: 65536 backing file: backingfile.qcow2 (actual path: backingfile.qcow2) Snapshot list: ID TAG VM SIZE DATE VM CLOCK 1.5G 2056-05-05 21:01:212795663:45:42.642 /archive/1006/20100627000/2il_root/save/archive/1002/20100204005/1 743M 1995-08-16 12:47:352289751:06:20.183 root@vmhost:/mnt/storage/vmstore/disks# qemu-img check myvm.qcow2 2>&1 | head ERROR OFLAG_COPIED: offset=80000002047d0000 refcount=0 ERROR OFLAG_COPIED: offset=8000000212e50000 refcount=0 ERROR OFLAG_COPIED: offset=80000001ffde0000 refcount=0 ERROR OFLAG_COPIED: offset=80000001ff710000 refcount=0 ERROR OFLAG_COPIED: offset=8000000216ec0000 refcount=0 ERROR OFLAG_COPIED: offset=8000000206db0000 refcount=0 ERROR OFLAG_COPIED: offset=80000001ff720000 refcount=0 ERROR OFLAG_COPIED: offset=80000001ffdf0000 refcount=0 ERROR OFLAG_COPIED: offset=8000000212e60000 refcount=0 ERROR OFLAG_COPIED: offset=8000000212e70000 refcount=0 root@vmhost:/mnt/storage/vmstore/disks# qemu-img info backingfile.qcow2 image: backingfile.qcow2 file format: qcow2 virtual size: 9.8G (10485760000 bytes) disk size: 4.8G cluster_size: 65536 root@vmhost:/mnt/storage/vmstore/disks# qemu-img check backingfile.qcow2 No errors were found on the image. If I use qemu-img to convert the image, the resulting image is "clean": # convert myvm.qcow2 -O qcow2 /tmp/test.qcow2 # qemu-img check /tmp/test.qcow2 No errors were found on the image. I had this corruption happen a month ago to a different VM on the same machine but a different physical drive, so I do not believe it to be a physical disk failure. I can find nothing in /var/log that gives any more information related to this corruption. What other debug information can I provide to diagnose why these images are getting corrupted and taking these running VMs offline? Thanks, Andrew Martin

1 1

[libvirt-users] Error: virNetSocketReadWire:904 : Cannot recv data: Input/output error
by Adarsh Guler 14 Aug '12

14 Aug '12

Hi, When am trying to send q job query using HTTP, am getting the error as indicated in the subject line. can some one help to resolve this error? Regards, Adarsh

1 0

[libvirt-users] How to use ext transport?
by Christian Schmidt 14 Aug '12

14 Aug '12

Hi, I would like to use the ext transport mode to migrate VMs between two hosts, but I didn't find any documentation about the ext interface. I have successfully migrate a vm with a programm that passes it's incomming messages through the network to libvirts socket on the target server. But the external program on the source side didn't get the connection URI or the server address or port. Is is possible to pass some arguments to the external programm or how can the external programm get the connection URI? My migration command looks like: virsh migrate --live --verbose myvm qemu+ext://targethost:7866/system?command=/root/dev/bin/trans At the moment I've written the target host and the port in the transport programm, but I think there have to be a better solution... -- Christian

1 0

[libvirt-users] Which functions call qemu_driver API?
by He Xin 14 Aug '12

14 Aug '12

Hi, Excuse me, I have watched qemu_driver.c where most of the libvirt API is overrided in order to connect qemu. But I am confused which functions then call those qemu_driver API? I mean where is the qemu_driver implementation? Libvirt.c? But how does the qemu_driver connect and control qemu? Thanks a lot! Regards, Corey

2 1

[libvirt-users] Does Libvirt-0.8.8(windows) support URI like qemu+ssh on windows?
by xuanmao_001 14 Aug '12

14 Aug '12

Hi, Eric: I have ssh2.exe and ssh-keygen2 tools on my windows which as parts of "SSH Secure Shell for Workstations Windows Client", and they work well. Now I want to know if libvirt support URI like qemu+ssh on windows? Give me some ideas. thanks xuanmao_001

2 1