September 2013 - Users - libvirt List Archives

[libvirt-users] creating snapshots for sheepdog with libvirt API
by Pavel Tokarev 24 Sep '13

24 Sep '13

Hello! I am trying to create snapshots for sheepdog disks using libvirt API or virsh. The disk is defined in domain as follows: <disk type='network' device='disk'> <driver name='qemu' cache='none'/> <source protocol='sheepdog' name='sheepvol1'/> <target dev='vdb' bus='virtio'/> </disk> I have tried both options "external" and "internal". If I try to create external snapshot with virsh command: snapshot-create-as vps vpssnap --disk-only --diskspec vda,snapshot=no --diskspec vdb,snapshot=external I get an error: source for disk 'vdb' is not a regular file; refusing to generate external snapshot name. If I try the same command but with "internal" mode: snapshot-create-as vps vpssnap --disk-only --diskspec vda,snapshot=no --diskspec vdb,snapshot=internal virsh creates a snapshot, but this snapshot is useless. If i try to revert to this snapshot i get an error: "qemu-img: Could not open 'sheepvol1': No such file or directory", plus if I list all VDIs with "collie vdi list" I do not see any snapshots there. So i guess virsh does not create an appropriate sheepdog snapshot at all. Can someone please tell me how to create snapshots for sheepdog disks? Thank you.

1 0

[libvirt-users] Using a shared LVM volume group for both virtual disks and host filesystems
by Edoardo Comar 24 Sep '13

24 Sep '13

Hi I have a test environment where a single LVM volume group is used both as a storage pool for virtual machines' disks AND for the LVs used for the HOST system filesystem. I never use libvirt commands to start/stop/activate the pool. Only to create/delete volumes. The test environment works fine. How suitable would be a shared VG for a production environment ? thanks, Edoardo Comar PS - This discussion seems to imply that separate VGs give more safety against data corruption in case of bugs ... did not point to real cases of failure. http://serverfault.com/questions/200728/lvm-volume-group-shared-between-kvm… 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] problem with sheepdog backend when creating a pool
by Giovanni Bellac 24 Sep '13

24 Sep '13

Hello all, I am getting a error, when creating a sheepdog pool via libvirt. libvirt is compiled as: ./configure --prefix=/opt/libvirt --without-xen --with-yajl --with-storage-sheepdog=/opt/sheepdog Sheepdog is functional, when creating manually a vdi via "qemu-img" and than using as disk in libvirt. The error looks like this: internal error missing backend for pool type 9 The peace of log: 2013-09-18 14:51:27.580+0000: 14522: debug : virEventPollMakePollFDs:391 : Prepare n=2 w=3, f=11 e=1 d=0 2013-09-18 14:51:27.580+0000: 14524: debug : virStoragePoolCreateXML:13588 : conn=0x7f1877937800, xmlDesc= <pool type="sheepdog"> <name>mysheeppool</name> <source> <name>mysheeppool</name> <host name='localhost' port='7000'/> </source> </pool> , flags=0 2013-09-18 14:51:27.580+0000: 14522: debug : virEventPollMakePollFDs:391 : Prepare n=3 w=4, f=12 e=1 d=0 2013-09-18 14:51:27.580+0000: 14522: debug : virEventPollMakePollFDs:391 : Prepare n=4 w=5, f=6 e=1 d=0 2013-09-18 14:51:27.580+0000: 14522: debug : virEventPollMakePollFDs:391 : Prepare n=5 w=6, f=14 e=1 d=0 2013-09-18 14:51:27.580+0000: 14522: debug : virEventPollMakePollFDs:391 : Prepare n=6 w=7, f=13 e=0 d=0 2013-09-18 14:51:27.580+0000: 14522: debug : virEventPollMakePollFDs:391 : Prepare n=7 w=8, f=13 e=1 d=0 2013-09-18 14:51:27.580+0000: 14522: debug : virEventPollMakePollFDs:391 : Prepare n=8 w=10, f=16 e=1 d=0 2013-09-18 14:51:27.580+0000: 14522: debug : virEventPollMakePollFDs:391 : Prepare n=9 w=12, f=17 e=1 d=0 2013-09-18 14:51:27.580+0000: 14522: debug : virEventPollCalculateTimeout:332 : Calculate expiry of 2 timers 2013-09-18 14:51:27.580+0000: 14522: debug : virEventPollCalculateTimeout:340 : Got a timeout scheduled for 1379515892580 2013-09-18 14:51:27.580+0000: 14522: debug : virEventPollCalculateTimeout:353 : Schedule timeout then=1379515892580 now=1379515887580 2013-09-18 14:51:27.580+0000: 14522: debug : virEventPollCalculateTimeout:361 : Timeout at 1379515892580 due in 5000 ms 2013-09-18 14:51:27.580+0000: 14522: debug : virEventPollRunOnce:627 : EVENT_POLL_RUN: nhandles=9 timeout=5000 2013-09-18 14:51:27.580+0000: 14524: debug : virFileClose:90 : Closed fd 18 2013-09-18 14:51:27.580+0000: 14524: debug : virObjectRef:293 : OBJECT_REF: obj=0x7f1877925550 2013-09-18 14:51:27.580+0000: 14524: debug : virAccessManagerCheckStoragePool:321 : manager=0x7f1877925550(name=stack) driver=QEMU pool=0x7f1864001340 perm=5 2013-09-18 14:51:27.580+0000: 14524: debug : virAccessManagerCheckStoragePool:321 : manager=0x7f1877929180(name=none) driver=QEMU pool=0x7f1864001340 perm=5 2013-09-18 14:51:27.580+0000: 14524: debug : virAccessManagerCheckStoragePool:321 : manager=0x7f1877925550(name=stack) driver=QEMU pool=0x7f1864001340 perm=2 2013-09-18 14:51:27.580+0000: 14524: debug : virAccessManagerCheckStoragePool:321 : manager=0x7f1877929180(name=none) driver=QEMU pool=0x7f1864001340 perm=2 2013-09-18 14:51:27.580+0000: 14524: debug : virObjectUnref:256 : OBJECT_UNREF: obj=0x7f1877925550 2013-09-18 14:51:27.580+0000: 14524: error : virStorageBackendForType:1114 : internal error missing backend for pool type 9 The pool XML: <pool type="sheepdog"> <name>mysheeppool</name> <source> <name>mysheeppool</name> <host name='localhost' port='7000'/> </source> </pool> Kind regards Giovanni

2 1

[libvirt-users] Expanding an LVM Storage Pool
by McEvoy, James 24 Sep '13

24 Sep '13

I looked around but could not find any info on how to expand a libvirt managed LVM storage pool. I do not see any virsh command to do it but I was successful using the vgexpand command to add some more storage once I destroyed the pools and then restarted it. I'd like to verify that this is the proper way to grow the storage in a libvirt LVM storage pool. And this brings up a second question, I did this without any VM running so I'd like to know what the impact of destroying a running pool is on running VMs. Does taking the pool off-line cause any issues with running VMs or is the only affect that the pool is unavailable for management by libvirt? These are the commands that I ran to create my pool and expand it after a kickstart of the server: pvcreate -ff -y /dev/mapper/mpath? virsh pool-define-as --name GuestVols --type logical --source-dev /dev/mapper/mpatha --target /dev/GuestVols virsh pool-build GuestVols virsh pool-start GuestVols virsh pool-autostart GuestVols virsh pool-destroy --pool GuestVols vgextend GuestVols /dev/mapper/mpath{b..d} vgdisplay GuestVols virsh pool-start --pool GuestVols virsh pool-info --pool GuestVols Is this the best way to create a managed pool across 4 LUNs? And to potentially expand the storage group in the future if more storage is needed? --jim

2 2

[libvirt-users] Specify mount option for Storage-Pool
by Jorge Fábregas 24 Sep '13

24 Sep '13

Hi, I've changed the "default" storage-pool from "directory-based" to a "pre-formatted block-device" since my /var/lib/libvirt/images is on a partition of its own. I would like to use the "discard" option as well as other (noatime etc) on this filesystem. Is there a way to specify mount options in the storage-pool XML definition? Thanks, Jorge p.d. the reason for the change is that I don't want the partition to be mounted all the time (just when I start libvirtd).

2 1

[libvirt-users] Libvirt ESX: Image file not getting copied to ESX server
by varun bhatnagar 23 Sep '13

23 Sep '13

Hi, I am trying to start a node using libvirt on ESX hypervisor. Before starting I am performing the following steps: 1) vol-create datastore1 /local/new_volume.xml (Creating a volume in pool) 2) define /local/esxdomain.xml (Defining a node) 3) start MyNode (Starting a node) I tried to get the status of my node and it is showing *running *but I am not able to ping my node (as it is in network). I later got the console of my node and found out that my node is not even getting started. It says "Operating System Not Found". I guess this is because my vmdk image file is not getting copied and the first command is just placing two files .vmdk and *-flat.vmdk (these are dummy files I guess). But it is not placing my original .vmdk files. How to place the original vmdk file in datastore. If I place it using scp command then libvirt pops out a message saying "Could not start domain: GenericVmConfigFault". How to resolve this error. I am pasting my xml files below. Any help is appreciated... :) *new_volume.xml:* *<volume> <name>test/MyNode.vmdk</name> <allocation>0</allocation> <capacity unit='G'>3</capacity> <target> <path>/local/vmdk/MyNode.vmdk</path> <format type='vmdk'/> </target> </volume>* *esxdomain.xml: * *<domain type='vmware'> <name>test</name> <memory>1048576</memory> <currentMemory>1048576</currentMemory> <vcpu>1</vcpu> <console>/dev/console</console> <os> <type arch='x86_64'>hvm</type> </os> <devices> <disk type='file' device='disk'> <source file='[datastore1] test/MyNode.vmdk'/> <target dev='sda' bus='scsi'/> <address type='drive' controller='0' bus='0' unit='0'/> </disk> <controller type='scsi' index='0' model='lsilogic'/>  <interface type='bridge'> <mac address='00:50:56:0f:01:01'/> <source bridge='VM Network'/> </interface> <interface type='bridge'> <mac address='00:50:56:0f:01:02'/> <source bridge='dummyPortGroup1'/> </interface> <interface type='bridge'> <mac address='00:50:56:0f:01:03'/> <source bridge='dummyPortGroup2'/> </interface> </devices> </domain>* Regards, Varun

1 0

[libvirt-users] Incremental Backups
by Thomas Stein 23 Sep '13

23 Sep '13

Hello. Is someone performing incremental backups via libvirt for qemu/kvm machines? I'm still having a hard time to find a nice procedure. I mean is it possible to make a full backup of an image on monday a do the next days of the week incremental backups? Another way could be mount the image and rsync its contents. Does that makes sense? Also i read in qemu changelog: --- Support for a new block device background job. Started by drive-backup, it will backup a disk's content to a new file. Unlike drive-mirror, the new file will include the source disk's content at the time the backup job was started. Atomic backup of multiple disks is supported using the "transaction" QMP command. --- Is this supported by libvirt? thanks and best regards thomas

4 11

[libvirt-users] Trouble using virStream with callbacks
by Jonathan Lebon 20 Sep '13

20 Sep '13

I am trying to write a simple app which connects a channel obtained from virDomainOpenChannel() to stdin/stdout (based in part on the snippet at [1]). However, it seems like the data received back from the stream is delayed by one iteration. It would be hard to explain this by simply showing the output, so here's a timeline instead: 1. start the program on the host 2. write "msg from host<Enter>" 3. socat on the guest sees this right away 4. from the guest's socat, write "msg from guest<Enter>" 5. the reply does not show up on the host until AFTER you press <Enter> (which of course also sends a newline to the guest) 6. this 'one line delay' occurs throughout the conversation, receiving guest replies to things sent two <Enter>s ago Doing socat on both sides work as expected. Also, using a blocked stream and a thread for sending and another for receiving works as well. It would be nice however if I could get rid of the threads in favour of callbacks. Not sure if I'm missing something obvious. Thanks, Jonathan [1] https://www.redhat.com/archives/libvir-list/2012-December/msg01084.html --- #include <ctype.h> #include <err.h> #include <errno.h> #include <stdlib.h> #include <stdio.h> #include <string.h> #include <libvirt/libvirt.h> #include <fcntl.h> #define CONNECT_URI "qemu:///system" #define DOMAIN "TestVM" #define CHANNEL "channel.0" #define BUF_SIZE 80 int stream_active = 1; void stdin_to_stream(int watch, int fd, int events, void *opaque) { virStreamPtr stream = *((virStreamPtr*)(opaque)); if (events & VIR_EVENT_HANDLE_READABLE) { char buf[1024]; int bytes_read = read(fd, buf, sizeof(buf)); if (bytes_read > 0) virStreamSend(stream, buf, bytes_read); } if (events & (VIR_EVENT_HANDLE_ERROR|VIR_EVENT_HANDLE_HANGUP)) { stream_active = 0; } return; } void stream_to_stdout(virStreamPtr stream, int events, void *opaque) { if (events & VIR_EVENT_HANDLE_READABLE) { char buf[1024]; int bytes_read = virStreamRecv(stream, buf, sizeof(buf)); if (bytes_read > 0) { fwrite(buf, bytes_read, 1, stdout); fflush(stdout); } } if (events & (VIR_EVENT_HANDLE_ERROR|VIR_EVENT_HANDLE_HANGUP)) { stream_active = 0; } return; } int main(int argc, char *argv[]) { virConnectPtr conn; virDomainPtr dom; virStreamPtr st; int bytes_read; char buf[BUF_SIZE]; if ((conn = virConnectOpen(CONNECT_URI)) == NULL) errx(1, "virConnectOpen"); if ((dom = virDomainLookupByName(conn, DOMAIN)) == NULL) errx(1, "virDomainLookupByName"); if ((st = virStreamNew(conn, VIR_STREAM_NONBLOCK)) == NULL) errx(1, "virStreamNew"); if (virDomainOpenChannel(dom, CHANNEL, st, 0) == -1) errx(1, "virDomainOpenChannel"); if (virEventRegisterDefaultImpl() != 0) errx(1, "virEventRegisterDefaultImpl"); if (virStreamEventAddCallback(st, 1|4|8, stream_to_stdout, NULL, NULL) != 0) errx(1, "virStreamEventAddCallback"); int flags = fcntl(fileno(stdin), F_GETFL) | O_NONBLOCK; fcntl(fileno(stdin), F_SETFL, flags); if (virEventAddHandle(fileno(stdin), 1|4|8, stdin_to_stream, &st, NULL) < 0) errx(1, "virEventAddHandle"); while (stream_active) { if (virEventRunDefaultImpl() != 0) { errx(1, "virEventRunDefaultImpl"); break; } } if (virStreamFinish(st) < 0) errx(1, "virStreamFinish"); if (virStreamFree(st) < 0) errx(1, "virStreamFree"); return 0; }

2 6

[libvirt-users] Libvirt not able to attach console to VM on ESX hypervisor
by varun bhatnagar 19 Sep '13

19 Sep '13

Hi, I have started a virtual machine on my ESXi server. I was trying to attach a console to it but when I executed the command I got a message saying that *"Attaching a console is not supported in the current hypervisor." *Is there any way (patch or something) through which I can attach a console to my VM. The ESX version is 5.1 and I am using latest version of libvirt. Regards, Varun

1 0

[libvirt-users] Specifying a USB Device to use USB2 Controller
by Cameron Curle 19 Sep '13

19 Sep '13

Hi all, Can anyone please advise the correct process for defining a USB device to point to a USB 2 Controller? Specifically, how do you define a USB device to use the EHCI controller in a guest xml file? To summarize my problem: I have 1 x USB1 device and 1 x USB2 device that I would like to use from within a Windows XP Guest. If I add the USB2 device (Avid M-box) to the guest machine via Virt-Manager it will not detect in the guest, when I check the libvirt logs for the VM it shows a "Device speed mismatch" error. Which leads me to think that its attaching itself to the default UHCI controller, as the USB1 device functions correctly. I've followed a similar post on the list here which seems to detail what I am trying to achieve: https://www.redhat.com/archives/libvirt-users/2012-June/msg00139.html I have tried using the controller type and model as below, however, when I try and define the "port" option, it disappears from the configuration file and won't attach to the EHCI controller. <controller type='usb' index='0' model='ich9-ehci' / I've done some searching but can't find any information on how to specifically assign a USB device to a certain controller. Any information or guides you could provide would be much appreciated. I'm using RHEL 6.4 with latest updates available. qemu-kvm-0.12.1.2-2.355.el6.4.7 libvirt-0.10.2-18.el6 4.9 I'm currently defining the USB2 device like this: <hostdev mode='subsystem' type='usb' managed='yes' <source> <vendor id='0x0763' /> <product id='0x202a' /> <address bus='1' device='3' /> </source> </hostdev> Thank you in advance for your assistance. Kind Regards, Cameron

1 1

[libvirt-users] Doc v2: How to use NPIV in libvirt
by Osier Yang 18 Sep '13

18 Sep '13

Thanks for John Ferlan's lots of internal feedbacks, I believe it's more readable, and better orgnized now. Should we create a page for it under http://libvirt.org/deployment.html or add it in WIKI? ========================================== NPIV in libvirt NPIV (N_Port ID Virtualization) is a Fibre Channel technology to share a single physical Fibre Channel HBA with multiple virtual ports. Henceforth known as a "virtual port" or "virtual Host Bus Adapter" (vHBA), each virtual port is identified by its own WWPN (Word Wide Port Name) and WWNN (Word Wide Node Name). In the virtualization world the vHBA controls the LUNs for virtual machines. The libvirt implementation provides flexibility to configure the LUN's either directly to the virtual machine or as part of a storage pool which then can be configured for use on a virtual machine. NPIV support in libvirt was first added to libvirt 0.6.5; however, the following sections will primarily describe NPIV functionality as of the current libvirt release, 1.1.2. There will be a troubleshooting and prior version considerations section to describe some historical differences. 1) Discovery Discovery of HBA(s) capable of NPIV is provided through the virsh command 'virsh nodedev-list --cap vports'. If no HBA is returned, then the host configuration should be checked. The XML output from the command "virsh nodedev-dumpxml" will list fields <name>, <wwnn>, and <wwpn> to be used in order to create a vHBA. Take care to also note the <max_vports> value as this lets you know if the HBA is going to exceed the maximum vHBA supported. The following output indicates a host that has two HBAs to support vHBA and the layout of a HBA's XML: # virsh nodedev-list --cap vports scsi_host4 scsi_host5 # virsh nodedev-dumpxml scsi_host5 <device> <name>scsi_host5</name> <parent>pci_0000_04_00_1</parent> <capability type='scsi_host'> <host>5</host> <capability type='fc_host'> <wwnn>2001001b32a9da4e</wwnn> <wwpn>2101001b32a9da4e</wwpn> <fabric_wwn>2001000dec9877c1</fabric_wwn> </capability> <capability type='vport_ops'> <max_vports>164</max_vports> <vports>5</vports> </capability> </capability> </device> The "max_vports" value indicates there are a possible of 164 vports available for use in the HBA configuration. The "vports" value indicates the number of vports currently being used. Support for detection of HBA's capable of NPIV support prior to libvirt 1.0.4 is described in the "Troubleshooting" section. 2) Creation of a vHBA using the node device driver In order to create a vHBA using the node device driver, select an HBA with available "vport" space, use the HBA "<name>" field as the "<parent>" field in the following XML: <device> <parent>scsi_host5</parent> <capability type='scsi_host'> <capability type='fc_host'> </capability> </capability> </device> Then create the vHBA with the command "virsh nodedev-create" (assuming above XML file is named "vhba.xml"): # virsh nodedev-create vhba.xml Node device scsi_host6 created from vhba.xml NOTE: If you specify "name" for the vHBA, then it will be ignored. The kernel will automatically pick the next SCSI host name in sequence not already used. The "wwpn" and "wwnn" values will be automatically generated by libvirt. In order to see the generated vHBA XML, use the command "virsh nodedev-dumpxml" as follows: # virsh nodedev-dumpxml scsi_host6 <device> <name>scsi_host6</name> <parent>scsi_host5</parent> <capability type='scsi_host'> <capability type='fc_host'> <wwnn>2001001b32a9da5e</wwnn> <wwpn>2101001b32a9da5e</wwpn> </capability> </capability> </device> This vHBA will only be defined as long the host is not rebooted. In order to create a persistent vHBA, one must use a libvirt storage pool (see next section). 3) Creation of vHBA by the storage pool By design, vHBAs managed by the node device driver are transient across host reboots. It is recommended to define a libvirt storage pool based on the vHBA in order to preserve the vHBA configuration. Using a storage pool has two primary advantage, first the libvirt code will find the LUN's path via simple virsh command output and second migration of virtual machine's requires only defining and starting a storage pool with the same vHBA name on the target machine if you use the LUN with libvirt storage pool and volume name in virtual machine config (see section 5). In order to create a persistent vHBA configuration create a libvirt 'scsi' storage pool using the XML as follows: <pool type='scsi'> <name>poolvhba0</name> <source> <adapter type='fc_host' wwnn='20000000c9831b4b' wwpn='10000000c9831b4b'/> </source> <target> <path>/dev/disk/by-path</path> <permissions> <mode>0700</mode> <owner>0</owner> <group>0</group> </permissions> </target> </pool> You must use the "type='scsi'" for the pool; The source adapter type must be "fc_host". Attributes "wwnn" and "wwpn" are provided as the unique identifier for the vHBA to be created. There is an optional attribute "parent" for source the adapter. It indicates the name of the HBA which you want to use to create the vHBA. Its value should be consistent with what node device driver dumps (e.g. scsi_host5). If it's not specified, libvirt will pick the first HBA capable of NPIV that has not exceeded the maximum vports it supports. NOTE: You can also create a scsi pool with source adapter type "fc_host" for a HBA, and in that case the attribute "parent" is not necessary. If you prefer to choose which parent HBA to use for your vHBA, then you must provide the parent, wwnn, and wwpn in the source adapter XML as follows: <source> <adapter type='fc_host' parent='scsi_host5' wwnn='20000000c9831b4b' wwpn='10000000c9831b4b'/> </source> To define the persistent pool (assuming above XML is named as poolvhba0.xml): # virsh pool-define poolvhba0.xml NOTE: One must use pool-define to define the pool as persistent, since a pool created by pool-create is transient and it will disappear after a system reboot or a libvirtd restart. To start the pool: # virsh pool-start poolvhba0 To destroy the pool: # virsh pool-destroy poolvhba0 When starting the pool, libvirt will check if the vHBA with same "wwpn:wwpn" already exists. If it does not exist, a new vHBA with the provided "wwpn:wwnn" will be created. Correspondingly，when destroying the pool the vHBA is destroyed too. Finally, in order to ensure that subsequent reboots of your host will automatically define vHBA's for use in virtual machines, one must set the storage pool autostart feature as follows (assuming the name of the created pool was "poolvhba0"): # virsh pool-autostart poolvhba0 4) Finding LUNs on your vHBA 4.1) Utilizing LUN's from a vHBA created by the storage pool Assuming that a storage pool was created for a vHBA, use the command "virsh vol-list" command in order to generate a list of available LUN's on the vHBA, as follows: # virsh vol-list poolvhba0 --details Name Path --------------------------------------------------------------------- unit:0:2:0 /dev/disk/by-path/pci-0000:04:00.1-fc-0x203500a0b85ad1d7-lun-0 block The list of LUN names displayed will be available for use as disk volumes in virtual machine configurations. 4.2) Utilizing LUN's from a vHBA created using the node device driver Finding an available LUN from a vHBA created using the node device driver can be achieved either via use of the "virsh nodedev-list" command or through manual searching of the hosts system file system. Use the "virsh nodedev-list --tree | more" and find the parent HBA to which the vHBA was configured. The following example lists the pertinent part of the tree for the example HBA "scsi_host5": +- scsi_host5 | +- scsi_host7 +- scsi_target5_0_0 | | | +- scsi_5_0_0_0 | +- scsi_target5_0_1 | | | +- scsi_5_0_1_0 | +- scsi_target5_0_2 | | | +- scsi_5_0_2_0 | | | +- block_sdb_3600a0b80005adb0b0000ab2d4cae9254 | +- scsi_target5_0_3 | +- scsi_5_0_3_0 The "block_" indicates it's a block device, the "sdb_" is a convention to signify the the short device path of "/dev/sdb", and the short device path or the number can be used to search the "/dev/disk/by-{id,path,uuid,label}/" name space for the specific LUN by name, for example: # ls /dev/disk/by-id/ | grep 3600a0b80005adb0b0000ab2d4cae9254 scsi-3600a0b80005adb0b0000ab2d4cae9254 # ls /dev/disk/by-path/ -l | grep sdb lrwxrwxrwx. 1 root root 9 Sep 16 05:58 pci-0000:04:00.1-fc-0x203500a0b85ad1d7-lun-0 -> ../../sdb As an option to using "virsh nodedev-list", it is possible to manually iterate through the "/sys/bus/scsi/device" and "/dev/disk/by-path" directory trees in order to find a LUN using the following steps: 1. Iterate over all the directories beginning with the SCSI host number of the vHBA under the "/sys/bus/scsi/devices" tree. For example, if the SCSI host number is 6, the command would be: # ls /sys/bus/scsi/devices/6:* -d /sys/bus/scsi/devices/6:0:0:0 /sys/bus/scsi/devices/6:0:1:0 /sys/bus/scsi/devices/6:0:2:0 /sys/bus/scsi/devices/6:0:3:0 2. List the "block" names of all the entries belongs to the SCSI host as follows: # ls /sys/bus/scsi/devices/6:*/block/ /sys/bus/scsi/devices/6:0:2:0/block/: sdc /sys/bus/scsi/devices/6:0:3:0/block/: sdd This indicates that "scsi_host6" has two LUNs, one is attached to "6:0:2:0", with the short device name "sdc", and the other is attached to "6:0:3:0", with the short device name "sdd". 3. Determine the stable path to the LUN. Unfortunately a device name such as "sdc" is not stable enough for use by libvirt. In order to get the stable path, use the "ls -l /dev/disk/by-path" and look for the "sdc" path: # ls -l /dev/disk/by-path/ | grep sdc lrwxrwxrwx. 1 root root 9 Sep 10 22:28 pci-0000:08:00.1-fc-0x205800a4085a3127-lun-0 -> ../../sdc Thus "/dev/disk/by-path/pci-0000:08:00.1-fc-0x205800a4085a3127-lun-0" is the stable path of the LUN attached to address "6:0:2:0" and will be used in virtual machine configurations. 5) Virtual machine configuration change to use vHBA LUN Adding the vHBA LUN to the virtual machine configuration is done via an XML modification to the virtual machine. 5.1) Using a LUN from a vHBA created by the storage pool Adding the vHBA LUN to the virtual machine is handled via XML to create a disk volume on the virtual machine with the following example XML: <disk type='volume' device='disk'> <driver name='qemu' type='raw'/> <source pool='poolvhba0' volume='unit:0:2:0'/> <target dev='hda' bus='ide'/> </disk> In particular note the usage of the "<source>" directive with the "pool" and "volume" attributes listing the storage pool and the short volume name. 5.2) Using a LUN from a vHBA created using the node device driver Configuring a vHBA on the virtual machine can be done with its stable path (path of {by-id|by-path|by-uuid|by-label}). The following is an XML example of a direct LUN path: <disk type='volume' device='disk'> <driver name='qemu' type='raw'/> <source dev='/dev/disk/by-path/pci-0000\:04\:00.1-fc-0x203400a0b85ad1d7-lun-0'/> <target dev='sda' bus='scsi'/> </disk> NOTE: The use of "device='disk'" and the long "<source>" device name. The example uses the "by-path" option. The backslashes prior to the colons are required, since colons can be considered as delimiters. 5.3) To configure the LUN as a pass-through device, use the following XML examples. For a vHBA created using the node device driver: <disk type='volume' device='lun'> <driver name='qemu' type='raw'/> <source dev='/dev/disk/by-path/pci-0000\:04\:00.1-fc-0x203400a0b85ad1d7-lun-0'/> <target dev='sda' bus='scsi'/> </disk> NOTE: The use of "device='lun'" and again the long "<source>" device name. Again, the backslashes prior to the colons are required. For a vHBA created by a storage pool: <disk type='volume' device='disk'> <driver name='qemu' type='raw'/> <source pool='poolvhba0' volume='unit:0:2:0'/> <target dev='hda' bus='ide'/> </disk> Although it is possible to use the LUN's path as the disk source for a vHBA created by the storage pool, it is recommended to use libvirt storage pool and storage volume instead. 6) Destroying a vHBA A vHBA created by the storage pool can be destroyed by the virsh command "pool-destroy", for example: # virsh pool-destroy poolvhba0 NOTE: If the storage pool is persistent, the vHBA will also be removed by libvirt when it destroys the storage pool. A vHBA created using the node device driver can be destroyed by the command "virsh nodedev-destroy", for example (assuming that scsi_host6 was created as shown earlier): # virsh nodedev-destroy scsi_host6 Destroying a vHBA removes it just as a reboot would do since the node device driver does not support persistent configurations. 7) Troubleshooting 7.1) Discovery of HBA capable of NPIV prior to 1.0.4 Prior to libvirt 1.0.4, discovery of HBAs capable of NPIV requires checking each of the HBAs on the host for the capability flag "vport_ops", as follows: First you need to find out all the HBA by capability flag "scsi_host": # virsh nodedev-list --cap scsi_host scsi_host0 scsi_host1 scsi_host2 scsi_host3 scsi_host4 scsi_host5 Now check each HBA to find one with the "vport_ops" capability, either one at a time as follows: # virsh nodedev-dumpxml scsi_host3 <device> <name>scsi_host3</name> <parent>pci_0000_00_08_0</parent> <capability type='scsi_host'> <host>3</host> </capability> </device> That says "scsi_host3" doesn't support vHBA # virsh nodedev-dumpxml scsi_host5 <device> <name>scsi_host5</name> <parent>pci_0000_04_00_1</parent> <capability type='scsi_host'> <host>5</host> <capability type='fc_host'> <wwnn>2001001b32a9da4e</wwnn> <wwpn>2101001b32a9da4e</wwpn> <fabric_wwn>2001000dec9877c1</fabric_wwn> </capability> <capability type='vport_ops' /> </capability> </device> But "scsi_host5" supports it. NOTE: In addition to libvirt 1.0.4 automating the lookup of HBA's capable of supporting a vHBA configuration, the XML tags "max_vports" and "vports" will describe the maximum vports allowed and the current vports in use. As an alternative and smarter way, you can avoid above cumbersome steps by simple script like: for i in $(virsh nodedev-list --cap scsi_host); do if virsh nodedev-dumpxml $i | grep vport_ops > /dev/null; then echo $i; fi done NOTE: It is possible that node device is named "pci_10df_fe00_scsi_host_0". This is because libvirt supports two backends for the node device driver ("udev" and "HAL"), but they lead to completely different naming styles. The udev backend is preferred over the HAL backend since HAL support is in maintenance mode. The udev backend is more common; however, if your destribution packager built the libvirt binaries without the udev backend, then the more complicated names such as "pci_10df_fe00_scsi_host_0" must be used. 7.2) Creation of a vHBA using the node device driver prior to 0.9.10 For libvirt prior to 0.9.10, you will need to specify the "wwnn" and "wwpn" manually when creating a vHBA, example XML as follows: <device> <name>scsi_host6</name> <parent>scsi_host5</parent> <capability type='scsi_host'> <capability type='fc_host'> <wwnn>2001001b32a9da5e</wwnn> <wwpn>2101001b32a9da5e</wwpn> </capability> </capability> </device> 7.3) Creation of storage pool based on vHBA prior to 1.0.5 Prior to libvirt 1.0.5, one can define a "scsi" type pool based on a vHBA by it's SCSI host name (e.g. "host5" in XML below), using an example XML as follows: <pool type='scsi'> <name>poolhba0</name> <uuid>e9392370-2917-565e-692b-d057f46512d6</uuid> <capacity unit='bytes'>0</capacity> <allocation unit='bytes'>0</allocation> <available unit='bytes'>0</available> <source> <adapter name='host0'/> </source> <target> <path>/dev/disk/by-path</path> <permissions> <mode>0700</mode> <owner>0</owner> <group>0</group> </permissions> </target> </pool> There are two disadvantage of using the SCSI host name as the source adapter. First the SCSI host number is not stable, thus it may cause trouble for your storage pool after a system reboot. Second, the adapter name (e.g. "host5") is not consistent with node device name (e.g. "scsi_host5"). Moreover, using the SCSI host name as the source adapter doesn't allow you to create a vHBA. NOTE: Since 1.0.5, the source adapter name was changed to be consistent with node device name, thus the second disadvantage is destroyed. Regards, Osier

1 1

[libvirt-users] libvirt report error "error: End of file while reading data: Input/output error" when start domain
by Bing Bu Cao 18 Sep '13

18 Sep '13

Hi, When I want to start a VM by virsh, report error: virsh start vm1 2013-09-18 05:52:06.809+0000: 12324: info : libvirt version: 1.1.1, package: 1.mcp8_0.1 (Koji, 2013-08-09-07:55:01, lnxmcp1) 2013-09-18 05:52:06.809+0000: 12324: debug : virLogParseOutputs:1334 : outputs=1:file:/var/log/virsh.log error: Failed to start domain vm1 error: End of file while reading data: Input/output error error: One or more references were leaked after disconnect from the hypervisor error: Reconnected to the hypervisor I check the libvirtd.log and found the 'default' network is not active. If start the 'default' at first, virsh start will run sucessfully. But I was wondering why the virsh report different error against libvirtd. And why the virsh did not report "network 'default' is not active" error instead of "error: End of file while reading data: Input/output error" ? From the virsh log I found libvirt tried to read message from the socket and failed, but no idea why this happened when no 'default' network? Here is the virsh log: info : libvirt version: 1.1.1, package: 1.mcp8_0.1 (Koji, 2013-08-09-07:55:01, lnxmcp1) debug : virGlobalInit:436 : register drivers debug : virRegisterDriver:762 : driver=0x3fffd164b78 name=Test debug : virRegisterDriver:774 : registering Test as driver 0 debug : virRegisterNetworkDriver:609 : registering Test as network driver 0 debug : virRegisterInterfaceDriver:636 : registering Test as interface driver 0 debug : virRegisterStorageDriver:663 : registering Test as storage driver 0 debug : virRegisterNodeDeviceDriver:690 : registering Test as device driver 0 debug : virRegisterSecretDriver:717 : registering Test as secret driver 0 debug : virRegisterNWFilterDriver:744 : registering Test as network filter driver 0 debug : virRegisterDriver:762 : driver=0x3fffd165dd8 name=ESX debug : virRegisterDriver:774 : registering ESX as driver 1 debug : virRegisterInterfaceDriver:636 : registering ESX as interface driver 1 debug : virRegisterNetworkDriver:609 : registering ESX as network driver 1 debug : virRegisterStorageDriver:663 : registering ESX as storage driver 1 debug : virRegisterNodeDeviceDriver:690 : registering ESX as device driver 1 debug : virRegisterSecretDriver:717 : registering ESX as secret driver 1 debug : virRegisterNWFilterDriver:744 : registering ESX as network filter driver 1 debug : virRegisterDriver:762 : driver=0x3fffd165588 name=remote debug : virRegisterDriver:774 : registering remote as driver 2 debug : virRegisterNetworkDriver:609 : registering remote as network driver 2 debug : virRegisterInterfaceDriver:636 : registering remote as interface driver 2 debug : virRegisterStorageDriver:663 : registering remote as storage driver 2 debug : virRegisterNodeDeviceDriver:690 : registering remote as device driver 2 debug : virRegisterSecretDriver:717 : registering remote as secret driver 2 debug : virRegisterNWFilterDriver:744 : registering remote as network filter driver 2 debug : virEventRegisterDefaultImpl:230 : registering default event implementation debug : virEventPollAddHandle:111 : Used 0 handle slots, adding at least 10 more debug : virEventPollInterruptLocked:710 : Skip interrupt, 0 0 debug : virEventPollAddHandle:136 : EVENT_POLL_ADD_HANDLE: watch=1 fd=5 events=1 cb=0x3fffceb67a8 opaque=(nil) ff=(nil) debug : virEventRegisterImpl:203 : addHandle=0x3fffceb7060 updateHandle=0x3fffceb7450 removeHandle=0x3fffceb6814 addTimeout=0x3fffceb69c8 updateTimeout=0x3fffceb6c24 removeTimeout=0x3fffceb6e2c debug : virEventRunDefaultImpl:270 : running default event implementation debug : virEventPollCleanupTimeouts:514 : Cleanup 0 debug : virEventPollCleanupTimeouts:550 : Found 0 out of 0 timeout slots used, releasing 0 debug : virEventPollCleanupHandles:562 : Cleanup 1 debug : virEventPollMakePollFDs:391 : Prepare n=0 w=1, f=5 e=1 d=0 debug : virEventPollCalculateTimeout:332 : Calculate expiry of 0 timers debug : virEventPollCalculateTimeout:361 : Timeout at 0 due in -1 ms debug : virEventPollRunOnce:627 : EVENT_POLL_RUN: nhandles=1 timeout=-1 debug : virConnectOpenAuth:1457 : name=(null), auth=0x3fffd164728, flags=0 debug : virObjectNew:199 : OBJECT_NEW: obj=0x2aad62a1e10 classname=virConnect debug : virObjectNew:199 : OBJECT_NEW: obj=0x2aad62a1f40 classname=virConnectCloseCallbackData debug : virConnectGetConfigFile:998 : Loading config file '/etc/libvirt/libvirt.conf' debug : virConfReadFile:745 : filename=/etc/libvirt/libvirt.conf debug : virFileClose:90 : Closed fd 7 debug : do_open:1173 : no name, allowing driver auto-select debug : do_open:1215 : trying driver 0 (Test) ... debug : do_open:1222 : driver 0 Test returned DECLINED debug : do_open:1215 : trying driver 1 (ESX) ... debug : do_open:1222 : driver 1 ESX returned DECLINED debug : do_open:1215 : trying driver 2 (remote) ... debug : remoteConnectOpen:998 : Auto-probe remote URI debug : doRemoteOpen:599 : proceeding with name = debug : doRemoteOpen:608 : Connecting with transport 1 debug : doRemoteOpen:699 : Proceeding with sockname /var/run/libvirt/libvirt-sock debug : virNetSocketNew:155 : localAddr=0x3ffff825180 remoteAddr=0x3ffff825208 fd=7 errfd=-1 pid=0 debug : virObjectNew:199 : OBJECT_NEW: obj=0x2aad62a2520 classname=virNetSocket debug : virNetSocketNew:205 : RPC_SOCKET_NEW: sock=0x2aad62a2520 fd=7 errfd=-1 pid=0 localAddr=127.0.0.1;0, remoteAddr=127.0.0.1;0 debug : virObjectNew:199 : OBJECT_NEW: obj=0x2aad62a2920 classname=virNetClient debug : virNetClientNew:326 : RPC_CLIENT_NEW: client=0x2aad62a2920 sock=0x2aad62a2520 debug : virObjectRef:293 : OBJECT_REF: obj=0x2aad62a2920 debug : virObjectRef:293 : OBJECT_REF: obj=0x2aad62a2520 debug : virEventPollInterruptLocked:714 : Interrupting debug : virEventPollAddHandle:136 : EVENT_POLL_ADD_HANDLE: watch=2 fd=7 events=1 cb=0x3fffcff79e4 opaque=0x2aad62a2520 ff=0x3fffcff7948 debug : virKeepAliveNew:196 : client=0x2aad62a2920, interval=-1, count=0 debug : virObjectNew:199 : OBJECT_NEW: obj=0x2aad62a2c20 classname=virKeepAlive debug : virKeepAliveNew:215 : RPC_KEEPALIVE_NEW: ka=0x2aad62a2c20 client=0x2aad62a2920 debug : virObjectRef:293 : OBJECT_REF: obj=0x2aad62a2920 debug : virObjectRef:293 : OBJECT_REF: obj=0x2aad62a1f40 debug : virObjectNew:199 : OBJECT_NEW: obj=0x2aad62a2eb0 classname=virNetClientProgram debug : virObjectNew:199 : OBJECT_NEW: obj=0x2aad62a2850 classname=virNetClientProgram debug : virObjectNew:199 : OBJECT_NEW: obj=0x2aad62a3040 classname=virNetClientProgram debug : virObjectRef:293 : OBJECT_REF: obj=0x2aad62a2eb0 debug : virObjectRef:293 : OBJECT_REF: obj=0x2aad62a2850 debug : virObjectRef:293 : OBJECT_REF: obj=0x2aad62a3040 debug : doRemoteOpen:816 : Trying authentication debug : virNetMessageNew:44 : msg=0x2aad62a2ce0 tracked=0 debug : virNetMessageEncodePayload:373 : Encode length as 28 debug : virNetClientSendInternal:1952 : RPC_CLIENT_MSG_TX_QUEUE: client=0x2aad62a2920 len=28 prog=536903814 vers=1 proc=66 type=0 status=0 serial=0 debug : virNetClientCallNew:1905 : New call 0x2aad62a31c0: msg=0x2aad62a2ce0, expectReply=1, nonBlock=0 debug : virNetClientIO:1714 : Outgoing message prog=536903814 version=1 serial=0 proc=66 type=0 length=28 dispatch=(nil) debug : virNetClientIO:1773 : We have the buck head=0x2aad62a31c0 call=0x2aad62a31c0 debug : virEventPollUpdateHandle:147 : EVENT_POLL_UPDATE_HANDLE: watch=2 events=0 debug : virEventPollInterruptLocked:714 : Interrupting debug : virEventPollRunOnce:638 : Poll got 1 event(s) debug : virEventPollDispatchTimeouts:423 : Dispatch 0 debug : virEventPollDispatchHandles:468 : Dispatch 1 debug : virEventPollDispatchHandles:482 : i=0 w=1 debug : virEventPollDispatchHandles:496 : EVENT_POLL_DISPATCH_HANDLE: watch=1 events=1 debug : virEventPollCleanupTimeouts:514 : Cleanup 0 debug : virEventPollCleanupTimeouts:550 : Found 0 out of 0 timeout slots used, releasing 0 debug : virEventPollCleanupHandles:562 : Cleanup 2 debug : virEventRunDefaultImpl:270 : running default event implementation debug : virEventPollCleanupTimeouts:514 : Cleanup 0 debug : virEventPollCleanupTimeouts:550 : Found 0 out of 0 timeout slots used, releasing 0 debug : virEventPollCleanupHandles:562 : Cleanup 2 debug : virEventPollMakePollFDs:391 : Prepare n=0 w=1, f=5 e=1 d=0 debug : virEventPollMakePollFDs:391 : Prepare n=1 w=2, f=7 e=0 d=0 debug : virEventPollCalculateTimeout:332 : Calculate expiry of 0 timers debug : virEventPollCalculateTimeout:361 : Timeout at 0 due in -1 ms debug : virEventPollRunOnce:627 : EVENT_POLL_RUN: nhandles=1 timeout=-1 debug : virEventPollRunOnce:638 : Poll got 1 event(s) debug : virEventPollDispatchTimeouts:423 : Dispatch 0 debug : virEventPollDispatchHandles:468 : Dispatch 1 debug : virEventPollDispatchHandles:482 : i=0 w=1 debug : virEventPollDispatchHandles:496 : EVENT_POLL_DISPATCH_HANDLE: watch=1 events=1 debug : virEventPollCleanupTimeouts:514 : Cleanup 0 debug : virEventPollCleanupTimeouts:550 : Found 0 out of 0 timeout slots used, releasing 0 debug : virEventPollCleanupHandles:562 : Cleanup 2 debug : virEventRunDefaultImpl:270 : running default event implementation debug : virEventPollCleanupTimeouts:514 : Cleanup 0 debug : virEventPollCleanupTimeouts:550 : Found 0 out of 0 timeout slots used, releasing 0 debug : virEventPollCleanupHandles:562 : Cleanup 2 debug : virEventPollMakePollFDs:391 : Prepare n=0 w=1, f=5 e=1 d=0 debug : virEventPollMakePollFDs:391 : Prepare n=1 w=2, f=7 e=0 d=0 debug : virEventPollCalculateTimeout:332 : Calculate expiry of 0 timers debug : virEventPollCalculateTimeout:361 : Timeout at 0 due in -1 ms debug : virEventPollRunOnce:627 : EVENT_POLL_RUN: nhandles=1 timeout=-1 debug : virNetMessageDecodeLength:149 : Got length, now need 36 total (32 more) debug : virNetClientCallDispatch:1123 : RPC_CLIENT_MSG_RX: client=0x2aad62a2920 len=36 prog=536903814 vers=1 proc=66 type=1 status=0 serial=0 debug : virKeepAliveCheckMessage:374 : ka=0x2aad62a2c20, client=0x2aad62a2920, msg=0x2aad62a2988 debug : virNetMessageClear:55 : msg=0x2aad62a2988 nfds=0 debug : virNetClientIOEventLoopPassTheBuck:1420 : Giving up the buck 0x2aad62a31c0 debug : virNetClientIOEventLoopPassTheBuck:1434 : No thread to pass the buck to debug : virEventPollUpdateHandle:147 : EVENT_POLL_UPDATE_HANDLE: watch=2 events=1 debug : virEventPollInterruptLocked:714 : Interrupting debug : virNetClientIO:1803 : All done with our call head=(nil) call=0x2aad62a31c0 rv=0 debug : virNetMessageFree:72 : msg=0x2aad62a2ce0 nfds=0 cb=(nil) debug : virNetMessageNew:44 : msg=0x2aad62a2ce0 tracked=0 debug : virNetMessageEncodePayload:373 : Encode length as 32 debug : virNetClientSendInternal:1952 : RPC_CLIENT_MSG_TX_QUEUE: client=0x2aad62a2920 len=32 prog=536903814 vers=1 proc=60 type=0 status=0 serial=1 debug : virNetClientCallNew:1905 : New call 0x2aad62a20f0: msg=0x2aad62a2ce0, expectReply=1, nonBlock=0 debug : virNetClientIO:1714 : Outgoing message prog=536903814 version=1 serial=1 proc=60 type=0 length=32 dispatch=(nil) debug : virNetClientIO:1773 : We have the buck head=0x2aad62a20f0 call=0x2aad62a20f0 debug : virEventPollUpdateHandle:147 : EVENT_POLL_UPDATE_HANDLE: watch=2 events=0 debug : virEventPollInterruptLocked:714 : Interrupting debug : virEventPollRunOnce:638 : Poll got 1 event(s) debug : virEventPollDispatchTimeouts:423 : Dispatch 0 debug : virEventPollDispatchHandles:468 : Dispatch 1 debug : virEventPollDispatchHandles:482 : i=0 w=1 debug : virEventPollDispatchHandles:496 : EVENT_POLL_DISPATCH_HANDLE: watch=1 events=1 debug : virEventPollCleanupTimeouts:514 : Cleanup 0 debug : virEventPollCleanupTimeouts:550 : Found 0 out of 0 timeout slots used, releasing 0 debug : virEventPollCleanupHandles:562 : Cleanup 2 debug : virEventRunDefaultImpl:270 : running default event implementation debug : virEventPollCleanupTimeouts:514 : Cleanup 0 debug : virEventPollCleanupTimeouts:550 : Found 0 out of 0 timeout slots used, releasing 0 debug : virEventPollCleanupHandles:562 : Cleanup 2 debug : virEventPollMakePollFDs:391 : Prepare n=0 w=1, f=5 e=1 d=0 debug : virEventPollMakePollFDs:391 : Prepare n=1 w=2, f=7 e=0 d=0 debug : virEventPollCalculateTimeout:332 : Calculate expiry of 0 timers debug : virEventPollCalculateTimeout:361 : Timeout at 0 due in -1 ms debug : virEventPollRunOnce:627 : EVENT_POLL_RUN: nhandles=1 timeout=-1 debug : virEventPollRunOnce:638 : Poll got 1 event(s) debug : virEventPollDispatchTimeouts:423 : Dispatch 0 debug : virEventPollDispatchHandles:468 : Dispatch 1 debug : virEventPollDispatchHandles:482 : i=0 w=1 debug : virEventPollDispatchHandles:496 : EVENT_POLL_DISPATCH_HANDLE: watch=1 events=1 debug : virEventPollCleanupTimeouts:514 : Cleanup 0 debug : virEventPollCleanupTimeouts:550 : Found 0 out of 0 timeout slots used, releasing 0 debug : virEventPollCleanupHandles:562 : Cleanup 2 debug : virEventRunDefaultImpl:270 : running default event implementation debug : virEventPollCleanupTimeouts:514 : Cleanup 0 debug : virEventPollCleanupTimeouts:550 : Found 0 out of 0 timeout slots used, releasing 0 debug : virEventPollCleanupHandles:562 : Cleanup 2 debug : virEventPollMakePollFDs:391 : Prepare n=0 w=1, f=5 e=1 d=0 debug : virEventPollMakePollFDs:391 : Prepare n=1 w=2, f=7 e=0 d=0 debug : virEventPollCalculateTimeout:332 : Calculate expiry of 0 timers debug : virEventPollCalculateTimeout:361 : Timeout at 0 due in -1 ms debug : virEventPollRunOnce:627 : EVENT_POLL_RUN: nhandles=1 timeout=-1 debug : virNetMessageDecodeLength:149 : Got length, now need 32 total (28 more) debug : virNetClientCallDispatch:1123 : RPC_CLIENT_MSG_RX: client=0x2aad62a2920 len=32 prog=536903814 vers=1 proc=60 type=1 status=0 serial=1 debug : virKeepAliveCheckMessage:374 : ka=0x2aad62a2c20, client=0x2aad62a2920, msg=0x2aad62a2988 debug : virNetMessageClear:55 : msg=0x2aad62a2988 nfds=0 debug : virNetClientIOEventLoopPassTheBuck:1420 : Giving up the buck 0x2aad62a20f0 debug : virNetClientIOEventLoopPassTheBuck:1434 : No thread to pass the buck to debug : virEventPollUpdateHandle:147 : EVENT_POLL_UPDATE_HANDLE: watch=2 events=1 debug : virEventPollInterruptLocked:714 : Interrupting debug : virNetClientIO:1803 : All done with our call head=(nil) call=0x2aad62a20f0 rv=0 debug : virNetMessageFree:72 : msg=0x2aad62a2ce0 nfds=0 cb=(nil) debug : doRemoteOpen:842 : Trying to open URI debug : virNetMessageNew:44 : msg=0x2aad62a2ce0 tracked=0 debug : virNetMessageEncodePayload:373 : Encode length as 40 debug : virNetClientSendInternal:1952 : RPC_CLIENT_MSG_TX_QUEUE: client=0x2aad62a2920 len=40 prog=536903814 vers=1 proc=1 type=0 status=0 serial=2 debug : virNetClientCallNew:1905 : New call 0x2aad62a20f0: msg=0x2aad62a2ce0, expectReply=1, nonBlock=0 debug : virNetClientIO:1714 : Outgoing message prog=536903814 version=1 serial=2 proc=1 type=0 length=40 dispatch=(nil) debug : virNetClientIO:1773 : We have the buck head=0x2aad62a20f0 call=0x2aad62a20f0 debug : virEventPollUpdateHandle:147 : EVENT_POLL_UPDATE_HANDLE: watch=2 events=0 debug : virEventPollInterruptLocked:714 : Interrupting debug : virEventPollRunOnce:638 : Poll got 1 event(s) debug : virEventPollDispatchTimeouts:423 : Dispatch 0 debug : virEventPollDispatchHandles:468 : Dispatch 1 debug : virEventPollDispatchHandles:482 : i=0 w=1 debug : virEventPollDispatchHandles:496 : EVENT_POLL_DISPATCH_HANDLE: watch=1 events=1 debug : virEventPollCleanupTimeouts:514 : Cleanup 0 debug : virEventPollCleanupTimeouts:550 : Found 0 out of 0 timeout slots used, releasing 0 debug : virEventPollCleanupHandles:562 : Cleanup 2 debug : virEventRunDefaultImpl:270 : running default event implementation debug : virEventPollCleanupTimeouts:514 : Cleanup 0 debug : virEventPollCleanupTimeouts:550 : Found 0 out of 0 timeout slots used, releasing 0 debug : virEventPollCleanupHandles:562 : Cleanup 2 debug : virEventPollMakePollFDs:391 : Prepare n=0 w=1, f=5 e=1 d=0 debug : virEventPollMakePollFDs:391 : Prepare n=1 w=2, f=7 e=0 d=0 debug : virEventPollCalculateTimeout:332 : Calculate expiry of 0 timers debug : virEventPollCalculateTimeout:361 : Timeout at 0 due in -1 ms debug : virEventPollRunOnce:627 : EVENT_POLL_RUN: nhandles=1 timeout=-1 debug : virEventPollRunOnce:638 : Poll got 1 event(s) debug : virEventPollDispatchTimeouts:423 : Dispatch 0 debug : virEventPollDispatchHandles:468 : Dispatch 1 debug : virEventPollDispatchHandles:482 : i=0 w=1 debug : virEventPollDispatchHandles:496 : EVENT_POLL_DISPATCH_HANDLE: watch=1 events=1 debug : virEventPollCleanupTimeouts:514 : Cleanup 0 debug : virEventPollCleanupTimeouts:550 : Found 0 out of 0 timeout slots used, releasing 0 debug : virEventPollCleanupHandles:562 : Cleanup 2 debug : virEventRunDefaultImpl:270 : running default event implementation debug : virEventPollCleanupTimeouts:514 : Cleanup 0 debug : virEventPollCleanupTimeouts:550 : Found 0 out of 0 timeout slots used, releasing 0 debug : virEventPollCleanupHandles:562 : Cleanup 2 debug : virEventPollMakePollFDs:391 : Prepare n=0 w=1, f=5 e=1 d=0 debug : virEventPollMakePollFDs:391 : Prepare n=1 w=2, f=7 e=0 d=0 debug : virEventPollCalculateTimeout:332 : Calculate expiry of 0 timers debug : virEventPollCalculateTimeout:361 : Timeout at 0 due in -1 ms debug : virEventPollRunOnce:627 : EVENT_POLL_RUN: nhandles=1 timeout=-1 debug : virNetMessageDecodeLength:149 : Got length, now need 28 total (24 more) debug : virNetClientCallDispatch:1123 : RPC_CLIENT_MSG_RX: client=0x2aad62a2920 len=28 prog=536903814 vers=1 proc=1 type=1 status=0 serial=2 debug : virKeepAliveCheckMessage:374 : ka=0x2aad62a2c20, client=0x2aad62a2920, msg=0x2aad62a2988 debug : virNetMessageClear:55 : msg=0x2aad62a2988 nfds=0 debug : virNetClientIOEventLoopPassTheBuck:1420 : Giving up the buck 0x2aad62a20f0 debug : virNetClientIOEventLoopPassTheBuck:1434 : No thread to pass the buck to debug : virEventPollUpdateHandle:147 : EVENT_POLL_UPDATE_HANDLE: watch=2 events=1 debug : virEventPollInterruptLocked:714 : Interrupting debug : virNetClientIO:1803 : All done with our call head=(nil) call=0x2aad62a20f0 rv=0 debug : virNetMessageFree:72 : msg=0x2aad62a2ce0 nfds=0 cb=(nil) debug : doRemoteOpen:853 : Trying to query remote URI debug : virNetMessageNew:44 : msg=0x2aad62a2ce0 tracked=0 debug : virNetMessageEncodePayload:373 : Encode length as 28 debug : virNetClientSendInternal:1952 : RPC_CLIENT_MSG_TX_QUEUE: client=0x2aad62a2920 len=28 prog=536903814 vers=1 proc=110 type=0 status=0 serial=3 debug : virNetClientCallNew:1905 : New call 0x2aad62a20f0: msg=0x2aad62a2ce0, expectReply=1, nonBlock=0 debug : virNetClientIO:1714 : Outgoing message prog=536903814 version=1 serial=3 proc=110 type=0 length=28 dispatch=(nil) debug : virNetClientIO:1773 : We have the buck head=0x2aad62a20f0 call=0x2aad62a20f0 debug : virEventPollUpdateHandle:147 : EVENT_POLL_UPDATE_HANDLE: watch=2 events=0 debug : virEventPollInterruptLocked:714 : Interrupting debug : virEventPollRunOnce:638 : Poll got 1 event(s) debug : virEventPollDispatchTimeouts:423 : Dispatch 0 debug : virEventPollDispatchHandles:468 : Dispatch 1 debug : virEventPollDispatchHandles:482 : i=0 w=1 debug : virEventPollDispatchHandles:496 : EVENT_POLL_DISPATCH_HANDLE: watch=1 events=1 debug : virEventPollCleanupTimeouts:514 : Cleanup 0 debug : virEventPollCleanupTimeouts:550 : Found 0 out of 0 timeout slots used, releasing 0 debug : virEventPollCleanupHandles:562 : Cleanup 2 debug : virEventRunDefaultImpl:270 : running default event implementation debug : virEventPollCleanupTimeouts:514 : Cleanup 0 debug : virEventPollCleanupTimeouts:550 : Found 0 out of 0 timeout slots used, releasing 0 debug : virEventPollCleanupHandles:562 : Cleanup 2 debug : virEventPollMakePollFDs:391 : Prepare n=0 w=1, f=5 e=1 d=0 debug : virEventPollMakePollFDs:391 : Prepare n=1 w=2, f=7 e=0 d=0 debug : virEventPollCalculateTimeout:332 : Calculate expiry of 0 timers debug : virEventPollCalculateTimeout:361 : Timeout at 0 due in -1 ms debug : virEventPollRunOnce:627 : EVENT_POLL_RUN: nhandles=1 timeout=-1 debug : virEventPollRunOnce:638 : Poll got 1 event(s) debug : virEventPollDispatchTimeouts:423 : Dispatch 0 debug : virEventPollDispatchHandles:468 : Dispatch 1 debug : virEventPollDispatchHandles:482 : i=0 w=1 debug : virEventPollDispatchHandles:496 : EVENT_POLL_DISPATCH_HANDLE: watch=1 events=1 debug : virEventPollCleanupTimeouts:514 : Cleanup 0 debug : virEventPollCleanupTimeouts:550 : Found 0 out of 0 timeout slots used, releasing 0 debug : virEventPollCleanupHandles:562 : Cleanup 2 debug : virEventRunDefaultImpl:270 : running default event implementation debug : virEventPollCleanupTimeouts:514 : Cleanup 0 debug : virEventPollCleanupTimeouts:550 : Found 0 out of 0 timeout slots used, releasing 0 debug : virEventPollCleanupHandles:562 : Cleanup 2 debug : virEventPollMakePollFDs:391 : Prepare n=0 w=1, f=5 e=1 d=0 debug : virEventPollMakePollFDs:391 : Prepare n=1 w=2, f=7 e=0 d=0 debug : virEventPollCalculateTimeout:332 : Calculate expiry of 0 timers debug : virEventPollCalculateTimeout:361 : Timeout at 0 due in -1 ms debug : virEventPollRunOnce:627 : EVENT_POLL_RUN: nhandles=1 timeout=-1 debug : virNetMessageDecodeLength:149 : Got length, now need 48 total (44 more) debug : virNetClientCallDispatch:1123 : RPC_CLIENT_MSG_RX: client=0x2aad62a2920 len=48 prog=536903814 vers=1 proc=110 type=1 status=0 serial=3 debug : virKeepAliveCheckMessage:374 : ka=0x2aad62a2c20, client=0x2aad62a2920, msg=0x2aad62a2988 debug : virNetMessageClear:55 : msg=0x2aad62a2988 nfds=0 debug : virNetClientIOEventLoopPassTheBuck:1420 : Giving up the buck 0x2aad62a20f0 debug : virNetClientIOEventLoopPassTheBuck:1434 : No thread to pass the buck to debug : virEventPollUpdateHandle:147 : EVENT_POLL_UPDATE_HANDLE: watch=2 events=1 debug : virEventPollInterruptLocked:714 : Interrupting debug : virNetClientIO:1803 : All done with our call head=(nil) call=0x2aad62a20f0 rv=0 debug : virNetMessageFree:72 : msg=0x2aad62a2ce0 nfds=0 cb=(nil) debug : doRemoteOpen:861 : Auto-probed URI is qemu:///system debug : do_open:1222 : driver 2 remote returned SUCCESS debug : do_open:1248 : network driver 0 Test returned DECLINED debug : do_open:1248 : network driver 1 ESX returned DECLINED debug : do_open:1248 : network driver 2 remote returned SUCCESS debug : do_open:1264 : interface driver 0 Test returned DECLINED debug : do_open:1264 : interface driver 1 ESX returned DECLINED debug : do_open:1264 : interface driver 2 remote returned SUCCESS debug : do_open:1281 : storage driver 0 Test returned DECLINED debug : do_open:1281 : storage driver 1 ESX returned DECLINED debug : do_open:1281 : storage driver 2 remote returned SUCCESS debug : do_open:1298 : node driver 0 Test returned DECLINED debug : do_open:1298 : node driver 1 ESX returned DECLINED debug : do_open:1298 : node driver 2 remote returned SUCCESS debug : do_open:1315 : secret driver 0 Test returned DECLINED debug : do_open:1315 : secret driver 1 ESX returned DECLINED debug : do_open:1315 : secret driver 2 remote returned SUCCESS debug : do_open:1332 : nwfilter driver 0 Test returned DECLINED debug : do_open:1332 : nwfilter driver 1 ESX returned DECLINED debug : do_open:1332 : nwfilter driver 2 remote returned SUCCESS debug : virConnectRegisterCloseCallback:21344 : conn=0x2aad62a1e10 debug : virObjectRef:293 : OBJECT_REF: obj=0x2aad62a1e10 debug : virConnectIsAlive:21292 : conn=0x2aad62a1e10 debug : virDomainLookupByName:2242 : conn=0x2aad62a1e10, name=vm1 debug : virNetMessageNew:44 : msg=0x2aad62a2ce0 tracked=0 debug : virNetMessageEncodePayload:373 : Encode length as 36 debug : virNetClientSendInternal:1952 : RPC_CLIENT_MSG_TX_QUEUE: client=0x2aad62a2920 len=36 prog=536903814 vers=1 proc=23 type=0 status=0 serial=4 debug : virNetClientCallNew:1905 : New call 0x2aad62a2e40: msg=0x2aad62a2ce0, expectReply=1, nonBlock=0 debug : virNetClientIO:1714 : Outgoing message prog=536903814 version=1 serial=4 proc=23 type=0 length=36 dispatch=(nil) debug : virNetClientIO:1773 : We have the buck head=0x2aad62a2e40 call=0x2aad62a2e40 debug : virEventPollUpdateHandle:147 : EVENT_POLL_UPDATE_HANDLE: watch=2 events=0 debug : virEventPollInterruptLocked:714 : Interrupting debug : virEventPollRunOnce:638 : Poll got 1 event(s) debug : virEventPollDispatchTimeouts:423 : Dispatch 0 debug : virEventPollDispatchHandles:468 : Dispatch 1 debug : virEventPollDispatchHandles:482 : i=0 w=1 debug : virEventPollDispatchHandles:496 : EVENT_POLL_DISPATCH_HANDLE: watch=1 events=1 debug : virEventPollCleanupTimeouts:514 : Cleanup 0 debug : virEventPollCleanupTimeouts:550 : Found 0 out of 0 timeout slots used, releasing 0 debug : virEventPollCleanupHandles:562 : Cleanup 2 debug : virEventRunDefaultImpl:270 : running default event implementation debug : virEventPollCleanupTimeouts:514 : Cleanup 0 debug : virEventPollCleanupTimeouts:550 : Found 0 out of 0 timeout slots used, releasing 0 debug : virEventPollCleanupHandles:562 : Cleanup 2 debug : virEventPollMakePollFDs:391 : Prepare n=0 w=1, f=5 e=1 d=0 debug : virEventPollMakePollFDs:391 : Prepare n=1 w=2, f=7 e=0 d=0 debug : virEventPollCalculateTimeout:332 : Calculate expiry of 0 timers debug : virEventPollCalculateTimeout:361 : Timeout at 0 due in -1 ms debug : virEventPollRunOnce:627 : EVENT_POLL_RUN: nhandles=1 timeout=-1 debug : virEventPollRunOnce:638 : Poll got 1 event(s) debug : virEventPollDispatchTimeouts:423 : Dispatch 0 debug : virEventPollDispatchHandles:468 : Dispatch 1 debug : virEventPollDispatchHandles:482 : i=0 w=1 debug : virEventPollDispatchHandles:496 : EVENT_POLL_DISPATCH_HANDLE: watch=1 events=1 debug : virEventPollCleanupTimeouts:514 : Cleanup 0 debug : virEventPollCleanupTimeouts:550 : Found 0 out of 0 timeout slots used, releasing 0 debug : virEventPollCleanupHandles:562 : Cleanup 2 debug : virEventRunDefaultImpl:270 : running default event implementation debug : virEventPollCleanupTimeouts:514 : Cleanup 0 debug : virEventPollCleanupTimeouts:550 : Found 0 out of 0 timeout slots used, releasing 0 debug : virEventPollCleanupHandles:562 : Cleanup 2 debug : virEventPollMakePollFDs:391 : Prepare n=0 w=1, f=5 e=1 d=0 debug : virEventPollMakePollFDs:391 : Prepare n=1 w=2, f=7 e=0 d=0 debug : virEventPollCalculateTimeout:332 : Calculate expiry of 0 timers debug : virEventPollCalculateTimeout:361 : Timeout at 0 due in -1 ms debug : virEventPollRunOnce:627 : EVENT_POLL_RUN: nhandles=1 timeout=-1 debug : virNetMessageDecodeLength:149 : Got length, now need 56 total (52 more) debug : virNetClientCallDispatch:1123 : RPC_CLIENT_MSG_RX: client=0x2aad62a2920 len=56 prog=536903814 vers=1 proc=23 type=1 status=0 serial=4 debug : virKeepAliveCheckMessage:374 : ka=0x2aad62a2c20, client=0x2aad62a2920, msg=0x2aad62a2988 debug : virNetMessageClear:55 : msg=0x2aad62a2988 nfds=0 debug : virNetClientIOEventLoopPassTheBuck:1420 : Giving up the buck 0x2aad62a2e40 debug : virNetClientIOEventLoopPassTheBuck:1434 : No thread to pass the buck to debug : virEventPollUpdateHandle:147 : EVENT_POLL_UPDATE_HANDLE: watch=2 events=1 debug : virEventPollInterruptLocked:714 : Interrupting debug : virNetClientIO:1803 : All done with our call head=(nil) call=0x2aad62a2e40 rv=0 debug : virNetMessageFree:72 : msg=0x2aad62a2ce0 nfds=0 cb=(nil) debug : virObjectNew:199 : OBJECT_NEW: obj=0x2aad62a2bb0 classname=virDomain debug : virObjectRef:293 : OBJECT_REF: obj=0x2aad62a1e10 debug : virDomainGetID:3598 : dom=0x2aad62a2bb0, (VM: name=vm1, uuid=22d16da9-e05d-4e0f-bab4-bbacdfb82c92) debug : virDomainCreate:9415 : dom=0x2aad62a2bb0, (VM: name=vm1, uuid=22d16da9-e05d-4e0f-bab4-bbacdfb82c92) debug : virNetMessageNew:44 : msg=0x2aad62a2ce0 tracked=0 debug : virNetMessageEncodePayload:373 : Encode length as 56 debug : virNetClientSendInternal:1952 : RPC_CLIENT_MSG_TX_QUEUE: client=0x2aad62a2920 len=56 prog=536903814 vers=1 proc=9 type=0 status=0 serial=5 debug : virNetClientCallNew:1905 : New call 0x2aad62a2ad0: msg=0x2aad62a2ce0, expectReply=1, nonBlock=0 debug : virNetClientIO:1714 : Outgoing message prog=536903814 version=1 serial=5 proc=9 type=0 length=56 dispatch=(nil) debug : virNetClientIO:1773 : We have the buck head=0x2aad62a2ad0 call=0x2aad62a2ad0 debug : virEventPollUpdateHandle:147 : EVENT_POLL_UPDATE_HANDLE: watch=2 events=0 debug : virEventPollInterruptLocked:714 : Interrupting debug : virEventPollRunOnce:638 : Poll got 1 event(s) debug : virEventPollDispatchTimeouts:423 : Dispatch 0 debug : virEventPollDispatchHandles:468 : Dispatch 1 debug : virEventPollDispatchHandles:482 : i=0 w=1 debug : virEventPollDispatchHandles:496 : EVENT_POLL_DISPATCH_HANDLE: watch=1 events=1 debug : virEventPollCleanupTimeouts:514 : Cleanup 0 debug : virEventPollCleanupTimeouts:550 : Found 0 out of 0 timeout slots used, releasing 0 debug : virEventPollCleanupHandles:562 : Cleanup 2 debug : virEventRunDefaultImpl:270 : running default event implementation debug : virEventPollCleanupTimeouts:514 : Cleanup 0 debug : virEventPollCleanupTimeouts:550 : Found 0 out of 0 timeout slots used, releasing 0 debug : virEventPollCleanupHandles:562 : Cleanup 2 debug : virEventPollMakePollFDs:391 : Prepare n=0 w=1, f=5 e=1 d=0 debug : virEventPollMakePollFDs:391 : Prepare n=1 w=2, f=7 e=0 d=0 debug : virEventPollCalculateTimeout:332 : Calculate expiry of 0 timers debug : virEventPollCalculateTimeout:361 : Timeout at 0 due in -1 ms debug : virEventPollRunOnce:627 : EVENT_POLL_RUN: nhandles=1 timeout=-1 debug : virEventPollRunOnce:638 : Poll got 1 event(s) debug : virEventPollDispatchTimeouts:423 : Dispatch 0 debug : virEventPollDispatchHandles:468 : Dispatch 1 debug : virEventPollDispatchHandles:482 : i=0 w=1 debug : virEventPollDispatchHandles:496 : EVENT_POLL_DISPATCH_HANDLE: watch=1 events=1 debug : virEventPollCleanupTimeouts:514 : Cleanup 0 debug : virEventPollCleanupTimeouts:550 : Found 0 out of 0 timeout slots used, releasing 0 debug : virEventPollCleanupHandles:562 : Cleanup 2 debug : virEventRunDefaultImpl:270 : running default event implementation debug : virEventPollCleanupTimeouts:514 : Cleanup 0 debug : virEventPollCleanupTimeouts:550 : Found 0 out of 0 timeout slots used, releasing 0 debug : virEventPollCleanupHandles:562 : Cleanup 2 debug : virEventPollMakePollFDs:391 : Prepare n=0 w=1, f=5 e=1 d=0 debug : virEventPollMakePollFDs:391 : Prepare n=1 w=2, f=7 e=0 d=0 debug : virEventPollCalculateTimeout:332 : Calculate expiry of 0 timers debug : virEventPollCalculateTimeout:361 : Timeout at 0 due in -1 ms debug : virEventPollRunOnce:627 : EVENT_POLL_RUN: nhandles=1 timeout=-1 error : virNetSocketReadWire:1377 : End of file while reading data: Input/output error debug : virNetClientMarkClose:633 : client=0x2aad62a2920, reason=0 debug : virEventPollRemoveHandle:180 : EVENT_POLL_REMOVE_HANDLE: watch=2 debug : virEventPollRemoveHandle:193 : mark delete 1 7 debug : virEventPollInterruptLocked:714 : Interrupting debug : virNetClientIOEventLoopPassTheBuck:1420 : Giving up the buck 0x2aad62a2ad0 debug : virNetClientIOEventLoopPassTheBuck:1434 : No thread to pass the buck to debug : virNetClientCloseLocked:646 : client=0x2aad62a2920, sock=0x2aad62a2520, reason=0 debug : virObjectUnref:256 : OBJECT_UNREF: obj=0x2aad62a2520 debug : virObjectRef:293 : OBJECT_REF: obj=0x2aad62a2920 debug : virKeepAliveStop:307 : RPC_KEEPALIVE_STOP: ka=0x2aad62a2c20 client=0x2aad62a2920 debug : virObjectUnref:256 : OBJECT_UNREF: obj=0x2aad62a2c20 debug : virObjectUnref:258 : OBJECT_DISPOSE: obj=0x2aad62a2c20 debug : virKeepAliveDispose:227 : RPC_KEEPALIVE_DISPOSE: ka=0x2aad62a2c20 debug : virObjectUnref:256 : OBJECT_UNREF: obj=0x2aad62a2920 debug : remoteClientCloseFunc:361 : Triggering connection close callback 0x2aad61b6efc reason=0, opaque=(nil) debug : virObjectUnref:256 : OBJECT_UNREF: obj=0x2aad62a2920 debug : virNetClientIO:1803 : All done with our call head=(nil) call=0x2aad62a2ad0 rv=-1 debug : virNetMessageFree:72 : msg=0x2aad62a2ce0 nfds=0 cb=(nil) debug : virDomainGetName:3510 : domain=0x2aad62a2bb0 debug : virDomainFree:2406 : dom=0x2aad62a2bb0, (VM: name=vm1, uuid=22d16da9-e05d-4e0f-bab4-bbacdfb82c92) debug : virObjectUnref:256 : OBJECT_UNREF: obj=0x2aad62a2bb0 debug : virObjectUnref:258 : OBJECT_DISPOSE: obj=0x2aad62a2bb0 debug : virDomainDispose:262 : release domain 0x2aad62a2bb0 vm1 22d16da9-e05d-4e0f-bab4-bbacdfb82c92 debug : virObjectUnref:256 : OBJECT_UNREF: obj=0x2aad62a1e10 debug : virConnectUnregisterCloseCallback:21400 : conn=0x2aad62a1e10 error : virConnectUnregisterCloseCallback:21417 : Requested operation is not valid: A different callback was requested debug : virConnectClose:1501 : conn=0x2aad62a1e10 debug : virObjectUnref:256 : OBJECT_UNREF: obj=0x2aad62a1e10 debug : virConnectOpenAuth:1457 : name=(null), auth=0x3fffd164728, flags=0 debug : virObjectNew:199 : OBJECT_NEW: obj=0x2aad62a2ef0 classname=virConnect debug : virObjectNew:199 : OBJECT_NEW: obj=0x2aad62a31d0 classname=virConnectCloseCallbackData debug : virConnectGetConfigFile:998 : Loading config file '/etc/libvirt/libvirt.conf' debug : virConfReadFile:745 : filename=/etc/libvirt/libvirt.conf debug : virFileClose:90 : Closed fd 10 debug : do_open:1173 : no name, allowing driver auto-select debug : do_open:1215 : trying driver 0 (Test) ... debug : do_open:1222 : driver 0 Test returned DECLINED debug : do_open:1215 : trying driver 1 (ESX) ... debug : do_open:1222 : driver 1 ESX returned DECLINED debug : do_open:1215 : trying driver 2 (remote) ... debug : remoteConnectOpen:998 : Auto-probe remote URI debug : doRemoteOpen:599 : proceeding with name = debug : doRemoteOpen:608 : Connecting with transport 1 debug : doRemoteOpen:699 : Proceeding with sockname /var/run/libvirt/libvirt-sock debug : virNetSocketNew:155 : localAddr=0x3ffff825180 remoteAddr=0x3ffff825208 fd=10 errfd=-1 pid=0 debug : virObjectNew:199 : OBJECT_NEW: obj=0x2aad62a35c0 classname=virNetSocket debug : virNetSocketNew:205 : RPC_SOCKET_NEW: sock=0x2aad62a35c0 fd=10 errfd=-1 pid=0 localAddr=127.0.0.1;0, remoteAddr=127.0.0.1;0 debug : virObjectNew:199 : OBJECT_NEW: obj=0x2aad62a3900 classname=virNetClient debug : virNetClientNew:326 : RPC_CLIENT_NEW: client=0x2aad62a3900 sock=0x2aad62a35c0 debug : virObjectRef:293 : OBJECT_REF: obj=0x2aad62a3900 debug : virObjectRef:293 : OBJECT_REF: obj=0x2aad62a35c0 debug : virEventPollInterruptLocked:714 : Interrupting debug : virEventPollAddHandle:136 : EVENT_POLL_ADD_HANDLE: watch=3 fd=10 events=1 cb=0x3fffcff79e4 opaque=0x2aad62a35c0 ff=0x3fffcff7948 debug : virKeepAliveNew:196 : client=0x2aad62a3900, interval=-1, count=0 debug : virObjectNew:199 : OBJECT_NEW: obj=0x2aad62a3ab0 classname=virKeepAlive debug : virKeepAliveNew:215 : RPC_KEEPALIVE_NEW: ka=0x2aad62a3ab0 client=0x2aad62a3900 debug : virObjectRef:293 : OBJECT_REF: obj=0x2aad62a3900 debug : virObjectRef:293 : OBJECT_REF: obj=0x2aad62a31d0 debug : virObjectNew:199 : OBJECT_NEW: obj=0x2aad62a37f0 classname=virNetClientProgram debug : virObjectNew:199 : OBJECT_NEW: obj=0x2aad62a2050 classname=virNetClientProgram debug : virObjectNew:199 : OBJECT_NEW: obj=0x2aad62a3bb0 classname=virNetClientProgram debug : virObjectRef:293 : OBJECT_REF: obj=0x2aad62a37f0 debug : virObjectRef:293 : OBJECT_REF: obj=0x2aad62a2050 debug : virObjectRef:293 : OBJECT_REF: obj=0x2aad62a3bb0 debug : doRemoteOpen:816 : Trying authentication debug : virNetMessageNew:44 : msg=0x2aad62a3db0 tracked=0 debug : virNetMessageEncodePayload:373 : Encode length as 28 debug : virNetClientSendInternal:1952 : RPC_CLIENT_MSG_TX_QUEUE: client=0x2aad62a3900 len=28 prog=536903814 vers=1 proc=66 type=0 status=0 serial=0 debug : virNetClientCallNew:1905 : New call 0x2aad62b3ec0: msg=0x2aad62a3db0, expectReply=1, nonBlock=0 debug : virNetClientIO:1714 : Outgoing message prog=536903814 version=1 serial=0 proc=66 type=0 length=28 dispatch=(nil) debug : virNetClientIO:1773 : We have the buck head=0x2aad62b3ec0 call=0x2aad62b3ec0 debug : virEventPollUpdateHandle:147 : EVENT_POLL_UPDATE_HANDLE: watch=3 events=0 debug : virEventPollInterruptLocked:714 : Interrupting debug : virEventPollRunOnce:638 : Poll got 1 event(s) debug : virEventPollDispatchTimeouts:423 : Dispatch 0 debug : virEventPollDispatchHandles:468 : Dispatch 1 debug : virEventPollDispatchHandles:482 : i=0 w=1 debug : virEventPollDispatchHandles:496 : EVENT_POLL_DISPATCH_HANDLE: watch=1 events=1 debug : virEventPollCleanupTimeouts:514 : Cleanup 0 debug : virEventPollCleanupTimeouts:550 : Found 0 out of 0 timeout slots used, releasing 0 debug : virEventPollCleanupHandles:562 : Cleanup 3 debug : virEventPollCleanupHandles:575 : EVENT_POLL_PURGE_HANDLE: watch=2 debug : virObjectUnref:256 : OBJECT_UNREF: obj=0x2aad62a2920 debug : virObjectUnref:256 : OBJECT_UNREF: obj=0x2aad62a2520 debug : virObjectUnref:258 : OBJECT_DISPOSE: obj=0x2aad62a2520 debug : virNetSocketDispose:1002 : RPC_SOCKET_DISPOSE: sock=0x2aad62a2520 debug : virEventPollRemoveHandle:180 : EVENT_POLL_REMOVE_HANDLE: watch=2 debug : virFileClose:90 : Closed fd 7 debug : virEventRunDefaultImpl:270 : running default event implementation debug : virEventPollCleanupTimeouts:514 : Cleanup 0 debug : virEventPollCleanupTimeouts:550 : Found 0 out of 0 timeout slots used, releasing 0 debug : virEventPollCleanupHandles:562 : Cleanup 2 debug : virEventPollMakePollFDs:391 : Prepare n=0 w=1, f=5 e=1 d=0 debug : virEventPollMakePollFDs:391 : Prepare n=1 w=3, f=10 e=0 d=0 debug : virEventPollCalculateTimeout:332 : Calculate expiry of 0 timers debug : virEventPollCalculateTimeout:361 : Timeout at 0 due in -1 ms debug : virEventPollRunOnce:627 : EVENT_POLL_RUN: nhandles=1 timeout=-1 debug : virEventPollRunOnce:638 : Poll got 1 event(s) debug : virEventPollDispatchTimeouts:423 : Dispatch 0 debug : virEventPollDispatchHandles:468 : Dispatch 1 debug : virEventPollDispatchHandles:482 : i=0 w=1 debug : virEventPollDispatchHandles:496 : EVENT_POLL_DISPATCH_HANDLE: watch=1 events=1 debug : virEventPollCleanupTimeouts:514 : Cleanup 0 debug : virEventPollCleanupTimeouts:550 : Found 0 out of 0 timeout slots used, releasing 0 debug : virEventPollCleanupHandles:562 : Cleanup 2 debug : virEventRunDefaultImpl:270 : running default event implementation debug : virEventPollCleanupTimeouts:514 : Cleanup 0 debug : virEventPollCleanupTimeouts:550 : Found 0 out of 0 timeout slots used, releasing 0 debug : virEventPollCleanupHandles:562 : Cleanup 2 debug : virEventPollMakePollFDs:391 : Prepare n=0 w=1, f=5 e=1 d=0 debug : virEventPollMakePollFDs:391 : Prepare n=1 w=3, f=10 e=0 d=0 debug : virEventPollCalculateTimeout:332 : Calculate expiry of 0 timers debug : virEventPollCalculateTimeout:361 : Timeout at 0 due in -1 ms debug : virEventPollRunOnce:627 : EVENT_POLL_RUN: nhandles=1 timeout=-1 debug : virEventPollRunOnce:638 : Poll got 1 event(s) debug : virEventPollDispatchTimeouts:423 : Dispatch 0 debug : virEventPollDispatchHandles:468 : Dispatch 1 debug : virEventPollDispatchHandles:482 : i=0 w=1 debug : virEventPollDispatchHandles:496 : EVENT_POLL_DISPATCH_HANDLE: watch=1 events=1 debug : virEventPollCleanupTimeouts:514 : Cleanup 0 debug : virEventPollCleanupTimeouts:550 : Found 0 out of 0 timeout slots used, releasing 0 debug : virEventPollCleanupHandles:562 : Cleanup 2 debug : virEventRunDefaultImpl:270 : running default event implementation debug : virEventPollCleanupTimeouts:514 : Cleanup 0 debug : virEventPollCleanupTimeouts:550 : Found 0 out of 0 timeout slots used, releasing 0 debug : virEventPollCleanupHandles:562 : Cleanup 2 debug : virEventPollMakePollFDs:391 : Prepare n=0 w=1, f=5 e=1 d=0 debug : virEventPollMakePollFDs:391 : Prepare n=1 w=3, f=10 e=0 d=0 debug : virEventPollCalculateTimeout:332 : Calculate expiry of 0 timers debug : virEventPollCalculateTimeout:361 : Timeout at 0 due in -1 ms debug : virEventPollRunOnce:627 : EVENT_POLL_RUN: nhandles=1 timeout=-1 debug : virNetMessageDecodeLength:149 : Got length, now need 36 total (32 more) debug : virNetClientCallDispatch:1123 : RPC_CLIENT_MSG_RX: client=0x2aad62a3900 len=36 prog=536903814 vers=1 proc=66 type=1 status=0 serial=0 debug : virKeepAliveCheckMessage:374 : ka=0x2aad62a3ab0, client=0x2aad62a3900, msg=0x2aad62a3968 debug : virNetMessageClear:55 : msg=0x2aad62a3968 nfds=0 debug : virNetClientIOEventLoopPassTheBuck:1420 : Giving up the buck 0x2aad62b3ec0 debug : virNetClientIOEventLoopPassTheBuck:1434 : No thread to pass the buck to debug : virEventPollUpdateHandle:147 : EVENT_POLL_UPDATE_HANDLE: watch=3 events=1 debug : virEventPollInterruptLocked:714 : Interrupting debug : virNetClientIO:1803 : All done with our call head=(nil) call=0x2aad62b3ec0 rv=0 debug : virNetMessageFree:72 : msg=0x2aad62a3db0 nfds=0 cb=(nil) debug : virNetMessageNew:44 : msg=0x2aad62a3db0 tracked=0 debug : virNetMessageEncodePayload:373 : Encode length as 32 debug : virNetClientSendInternal:1952 : RPC_CLIENT_MSG_TX_QUEUE: client=0x2aad62a3900 len=32 prog=536903814 vers=1 proc=60 type=0 status=0 serial=1 debug : virNetClientCallNew:1905 : New call 0x2aad62a2660: msg=0x2aad62a3db0, expectReply=1, nonBlock=0 debug : virNetClientIO:1714 : Outgoing message prog=536903814 version=1 serial=1 proc=60 type=0 length=32 dispatch=(nil) debug : virNetClientIO:1773 : We have the buck head=0x2aad62a2660 call=0x2aad62a2660 debug : virEventPollUpdateHandle:147 : EVENT_POLL_UPDATE_HANDLE: watch=3 events=0 debug : virEventPollInterruptLocked:714 : Interrupting debug : virEventPollRunOnce:638 : Poll got 1 event(s) debug : virEventPollDispatchTimeouts:423 : Dispatch 0 debug : virEventPollDispatchHandles:468 : Dispatch 1 debug : virEventPollDispatchHandles:482 : i=0 w=1 debug : virEventPollDispatchHandles:496 : EVENT_POLL_DISPATCH_HANDLE: watch=1 events=1 debug : virEventPollCleanupTimeouts:514 : Cleanup 0 debug : virEventPollCleanupTimeouts:550 : Found 0 out of 0 timeout slots used, releasing 0 debug : virEventPollCleanupHandles:562 : Cleanup 2 debug : virEventRunDefaultImpl:270 : running default event implementation debug : virEventPollCleanupTimeouts:514 : Cleanup 0 debug : virEventPollCleanupTimeouts:550 : Found 0 out of 0 timeout slots used, releasing 0 debug : virEventPollCleanupHandles:562 : Cleanup 2 debug : virEventPollMakePollFDs:391 : Prepare n=0 w=1, f=5 e=1 d=0 debug : virEventPollMakePollFDs:391 : Prepare n=1 w=3, f=10 e=0 d=0 debug : virEventPollCalculateTimeout:332 : Calculate expiry of 0 timers debug : virEventPollCalculateTimeout:361 : Timeout at 0 due in -1 ms debug : virEventPollRunOnce:627 : EVENT_POLL_RUN: nhandles=1 timeout=-1 debug : virEventPollRunOnce:638 : Poll got 1 event(s) debug : virEventPollDispatchTimeouts:423 : Dispatch 0 debug : virEventPollDispatchHandles:468 : Dispatch 1 debug : virEventPollDispatchHandles:482 : i=0 w=1 debug : virEventPollDispatchHandles:496 : EVENT_POLL_DISPATCH_HANDLE: watch=1 events=1 debug : virEventPollCleanupTimeouts:514 : Cleanup 0 debug : virEventPollCleanupTimeouts:550 : Found 0 out of 0 timeout slots used, releasing 0 debug : virEventPollCleanupHandles:562 : Cleanup 2 debug : virEventRunDefaultImpl:270 : running default event implementation debug : virEventPollCleanupTimeouts:514 : Cleanup 0 debug : virEventPollCleanupTimeouts:550 : Found 0 out of 0 timeout slots used, releasing 0 debug : virEventPollCleanupHandles:562 : Cleanup 2 debug : virEventPollMakePollFDs:391 : Prepare n=0 w=1, f=5 e=1 d=0 debug : virEventPollMakePollFDs:391 : Prepare n=1 w=3, f=10 e=0 d=0 debug : virEventPollCalculateTimeout:332 : Calculate expiry of 0 timers debug : virEventPollCalculateTimeout:361 : Timeout at 0 due in -1 ms debug : virEventPollRunOnce:627 : EVENT_POLL_RUN: nhandles=1 timeout=-1 debug : virNetMessageDecodeLength:149 : Got length, now need 32 total (28 more) debug : virNetClientCallDispatch:1123 : RPC_CLIENT_MSG_RX: client=0x2aad62a3900 len=32 prog=536903814 vers=1 proc=60 type=1 status=0 serial=1 debug : virKeepAliveCheckMessage:374 : ka=0x2aad62a3ab0, client=0x2aad62a3900, msg=0x2aad62a3968 debug : virNetMessageClear:55 : msg=0x2aad62a3968 nfds=0 debug : virNetClientIOEventLoopPassTheBuck:1420 : Giving up the buck 0x2aad62a2660 debug : virNetClientIOEventLoopPassTheBuck:1434 : No thread to pass the buck to debug : virEventPollUpdateHandle:147 : EVENT_POLL_UPDATE_HANDLE: watch=3 events=1 debug : virEventPollInterruptLocked:714 : Interrupting debug : virNetClientIO:1803 : All done with our call head=(nil) call=0x2aad62a2660 rv=0 debug : virNetMessageFree:72 : msg=0x2aad62a3db0 nfds=0 cb=(nil) debug : doRemoteOpen:842 : Trying to open URI debug : virNetMessageNew:44 : msg=0x2aad62a3db0 tracked=0 debug : virNetMessageEncodePayload:373 : Encode length as 40 debug : virNetClientSendInternal:1952 : RPC_CLIENT_MSG_TX_QUEUE: client=0x2aad62a3900 len=40 prog=536903814 vers=1 proc=1 type=0 status=0 serial=2 debug : virNetClientCallNew:1905 : New call 0x2aad62a25a0: msg=0x2aad62a3db0, expectReply=1, nonBlock=0 debug : virNetClientIO:1714 : Outgoing message prog=536903814 version=1 serial=2 proc=1 type=0 length=40 dispatch=(nil) debug : virNetClientIO:1773 : We have the buck head=0x2aad62a25a0 call=0x2aad62a25a0 debug : virEventPollUpdateHandle:147 : EVENT_POLL_UPDATE_HANDLE: watch=3 events=0 debug : virEventPollInterruptLocked:714 : Interrupting debug : virEventPollRunOnce:638 : Poll got 1 event(s) debug : virEventPollDispatchTimeouts:423 : Dispatch 0 debug : virEventPollDispatchHandles:468 : Dispatch 1 debug : virEventPollDispatchHandles:482 : i=0 w=1 debug : virEventPollDispatchHandles:496 : EVENT_POLL_DISPATCH_HANDLE: watch=1 events=1 debug : virEventPollCleanupTimeouts:514 : Cleanup 0 debug : virEventPollCleanupTimeouts:550 : Found 0 out of 0 timeout slots used, releasing 0 debug : virEventPollCleanupHandles:562 : Cleanup 2 debug : virEventRunDefaultImpl:270 : running default event implementation debug : virEventPollCleanupTimeouts:514 : Cleanup 0 debug : virEventPollCleanupTimeouts:550 : Found 0 out of 0 timeout slots used, releasing 0 debug : virEventPollCleanupHandles:562 : Cleanup 2 debug : virEventPollMakePollFDs:391 : Prepare n=0 w=1, f=5 e=1 d=0 debug : virEventPollMakePollFDs:391 : Prepare n=1 w=3, f=10 e=0 d=0 debug : virEventPollCalculateTimeout:332 : Calculate expiry of 0 timers debug : virEventPollCalculateTimeout:361 : Timeout at 0 due in -1 ms debug : virEventPollRunOnce:627 : EVENT_POLL_RUN: nhandles=1 timeout=-1 debug : virEventPollRunOnce:638 : Poll got 1 event(s) debug : virEventPollDispatchTimeouts:423 : Dispatch 0 debug : virEventPollDispatchHandles:468 : Dispatch 1 debug : virEventPollDispatchHandles:482 : i=0 w=1 debug : virEventPollDispatchHandles:496 : EVENT_POLL_DISPATCH_HANDLE: watch=1 events=1 debug : virEventPollCleanupTimeouts:514 : Cleanup 0 debug : virEventPollCleanupTimeouts:550 : Found 0 out of 0 timeout slots used, releasing 0 debug : virEventPollCleanupHandles:562 : Cleanup 2 debug : virEventRunDefaultImpl:270 : running default event implementation debug : virEventPollCleanupTimeouts:514 : Cleanup 0 debug : virEventPollCleanupTimeouts:550 : Found 0 out of 0 timeout slots used, releasing 0 debug : virEventPollCleanupHandles:562 : Cleanup 2 debug : virEventPollMakePollFDs:391 : Prepare n=0 w=1, f=5 e=1 d=0 debug : virEventPollMakePollFDs:391 : Prepare n=1 w=3, f=10 e=0 d=0 debug : virEventPollCalculateTimeout:332 : Calculate expiry of 0 timers debug : virEventPollCalculateTimeout:361 : Timeout at 0 due in -1 ms debug : virEventPollRunOnce:627 : EVENT_POLL_RUN: nhandles=1 timeout=-1 debug : virNetMessageDecodeLength:149 : Got length, now need 28 total (24 more) debug : virNetClientCallDispatch:1123 : RPC_CLIENT_MSG_RX: client=0x2aad62a3900 len=28 prog=536903814 vers=1 proc=1 type=1 status=0 serial=2 debug : virKeepAliveCheckMessage:374 : ka=0x2aad62a3ab0, client=0x2aad62a3900, msg=0x2aad62a3968 debug : virNetMessageClear:55 : msg=0x2aad62a3968 nfds=0 debug : virNetClientIOEventLoopPassTheBuck:1420 : Giving up the buck 0x2aad62a25a0 debug : virNetClientIOEventLoopPassTheBuck:1434 : No thread to pass the buck to debug : virEventPollUpdateHandle:147 : EVENT_POLL_UPDATE_HANDLE: watch=3 events=1 debug : virEventPollInterruptLocked:714 : Interrupting debug : virNetClientIO:1803 : All done with our call head=(nil) call=0x2aad62a25a0 rv=0 debug : virNetMessageFree:72 : msg=0x2aad62a3db0 nfds=0 cb=(nil) debug : doRemoteOpen:853 : Trying to query remote URI debug : virNetMessageNew:44 : msg=0x2aad62a3db0 tracked=0 debug : virNetMessageEncodePayload:373 : Encode length as 28 debug : virNetClientSendInternal:1952 : RPC_CLIENT_MSG_TX_QUEUE: client=0x2aad62a3900 len=28 prog=536903814 vers=1 proc=110 type=0 status=0 serial=3 debug : virNetClientCallNew:1905 : New call 0x2aad62a2670: msg=0x2aad62a3db0, expectReply=1, nonBlock=0 debug : virNetClientIO:1714 : Outgoing message prog=536903814 version=1 serial=3 proc=110 type=0 length=28 dispatch=(nil) debug : virNetClientIO:1773 : We have the buck head=0x2aad62a2670 call=0x2aad62a2670 debug : virEventPollUpdateHandle:147 : EVENT_POLL_UPDATE_HANDLE: watch=3 events=0 debug : virEventPollInterruptLocked:714 : Interrupting debug : virEventPollRunOnce:638 : Poll got 1 event(s) debug : virEventPollDispatchTimeouts:423 : Dispatch 0 debug : virEventPollDispatchHandles:468 : Dispatch 1 debug : virEventPollDispatchHandles:482 : i=0 w=1 debug : virEventPollDispatchHandles:496 : EVENT_POLL_DISPATCH_HANDLE: watch=1 events=1 debug : virEventPollCleanupTimeouts:514 : Cleanup 0 debug : virEventPollCleanupTimeouts:550 : Found 0 out of 0 timeout slots used, releasing 0 debug : virEventPollCleanupHandles:562 : Cleanup 2 debug : virEventRunDefaultImpl:270 : running default event implementation debug : virEventPollCleanupTimeouts:514 : Cleanup 0 debug : virEventPollCleanupTimeouts:550 : Found 0 out of 0 timeout slots used, releasing 0 debug : virEventPollCleanupHandles:562 : Cleanup 2 debug : virEventPollMakePollFDs:391 : Prepare n=0 w=1, f=5 e=1 d=0 debug : virEventPollMakePollFDs:391 : Prepare n=1 w=3, f=10 e=0 d=0 debug : virEventPollCalculateTimeout:332 : Calculate expiry of 0 timers debug : virEventPollCalculateTimeout:361 : Timeout at 0 due in -1 ms debug : virEventPollRunOnce:627 : EVENT_POLL_RUN: nhandles=1 timeout=-1 debug : virEventPollRunOnce:638 : Poll got 1 event(s) debug : virEventPollDispatchTimeouts:423 : Dispatch 0 debug : virEventPollDispatchHandles:468 : Dispatch 1 debug : virEventPollDispatchHandles:482 : i=0 w=1 debug : virEventPollDispatchHandles:496 : EVENT_POLL_DISPATCH_HANDLE: watch=1 events=1 debug : virEventPollCleanupTimeouts:514 : Cleanup 0 debug : virEventPollCleanupTimeouts:550 : Found 0 out of 0 timeout slots used, releasing 0 debug : virEventPollCleanupHandles:562 : Cleanup 2 debug : virEventRunDefaultImpl:270 : running default event implementation debug : virEventPollCleanupTimeouts:514 : Cleanup 0 debug : virEventPollCleanupTimeouts:550 : Found 0 out of 0 timeout slots used, releasing 0 debug : virEventPollCleanupHandles:562 : Cleanup 2 debug : virEventPollMakePollFDs:391 : Prepare n=0 w=1, f=5 e=1 d=0 debug : virEventPollMakePollFDs:391 : Prepare n=1 w=3, f=10 e=0 d=0 debug : virEventPollCalculateTimeout:332 : Calculate expiry of 0 timers debug : virEventPollCalculateTimeout:361 : Timeout at 0 due in -1 ms debug : virEventPollRunOnce:627 : EVENT_POLL_RUN: nhandles=1 timeout=-1 debug : virNetMessageDecodeLength:149 : Got length, now need 48 total (44 more) debug : virNetClientCallDispatch:1123 : RPC_CLIENT_MSG_RX: client=0x2aad62a3900 len=48 prog=536903814 vers=1 proc=110 type=1 status=0 serial=3 debug : virKeepAliveCheckMessage:374 : ka=0x2aad62a3ab0, client=0x2aad62a3900, msg=0x2aad62a3968 debug : virNetMessageClear:55 : msg=0x2aad62a3968 nfds=0 debug : virNetClientIOEventLoopPassTheBuck:1420 : Giving up the buck 0x2aad62a2670 debug : virNetClientIOEventLoopPassTheBuck:1434 : No thread to pass the buck to debug : virEventPollUpdateHandle:147 : EVENT_POLL_UPDATE_HANDLE: watch=3 events=1 debug : virEventPollInterruptLocked:714 : Interrupting debug : virNetClientIO:1803 : All done with our call head=(nil) call=0x2aad62a2670 rv=0 debug : virNetMessageFree:72 : msg=0x2aad62a3db0 nfds=0 cb=(nil) debug : doRemoteOpen:861 : Auto-probed URI is qemu:///system debug : do_open:1222 : driver 2 remote returned SUCCESS debug : do_open:1248 : network driver 0 Test returned DECLINED debug : do_open:1248 : network driver 1 ESX returned DECLINED debug : do_open:1248 : network driver 2 remote returned SUCCESS debug : do_open:1264 : interface driver 0 Test returned DECLINED debug : do_open:1264 : interface driver 1 ESX returned DECLINED debug : do_open:1264 : interface driver 2 remote returned SUCCESS debug : do_open:1281 : storage driver 0 Test returned DECLINED debug : do_open:1281 : storage driver 1 ESX returned DECLINED debug : do_open:1281 : storage driver 2 remote returned SUCCESS debug : do_open:1298 : node driver 0 Test returned DECLINED debug : do_open:1298 : node driver 1 ESX returned DECLINED debug : do_open:1298 : node driver 2 remote returned SUCCESS debug : do_open:1315 : secret driver 0 Test returned DECLINED debug : do_open:1315 : secret driver 1 ESX returned DECLINED debug : do_open:1315 : secret driver 2 remote returned SUCCESS debug : do_open:1332 : nwfilter driver 0 Test returned DECLINED debug : do_open:1332 : nwfilter driver 1 ESX returned DECLINED debug : do_open:1332 : nwfilter driver 2 remote returned SUCCESS debug : virConnectRegisterCloseCallback:21344 : conn=0x2aad62a2ef0 debug : virObjectRef:293 : OBJECT_REF: obj=0x2aad62a2ef0 debug : virEventPollRunOnce:638 : Poll got 1 event(s) debug : virEventPollDispatchTimeouts:423 : Dispatch 0 debug : virEventPollDispatchHandles:468 : Dispatch 1 debug : virEventPollDispatchHandles:482 : i=0 w=1 debug : virEventPollDispatchHandles:496 : EVENT_POLL_DISPATCH_HANDLE: watch=1 events=1 debug : virEventPollCleanupTimeouts:514 : Cleanup 0 debug : virEventPollCleanupTimeouts:550 : Found 0 out of 0 timeout slots used, releasing 0 debug : virEventPollCleanupHandles:562 : Cleanup 2 debug : virEventRunDefaultImpl:270 : running default event implementation debug : virEventPollCleanupTimeouts:514 : Cleanup 0 debug : virEventPollCleanupTimeouts:550 : Found 0 out of 0 timeout slots used, releasing 0 debug : virEventPollCleanupHandles:562 : Cleanup 2 debug : virEventPollMakePollFDs:391 : Prepare n=0 w=1, f=5 e=1 d=0 debug : virEventPollMakePollFDs:391 : Prepare n=1 w=3, f=10 e=1 d=0 debug : virEventPollCalculateTimeout:332 : Calculate expiry of 0 timers debug : virEventPollCalculateTimeout:361 : Timeout at 0 due in -1 ms debug : virEventPollRunOnce:627 : EVENT_POLL_RUN: nhandles=2 timeout=-1 debug : virConnectUnregisterCloseCallback:21400 : conn=0x2aad62a2ef0 debug : virObjectUnref:256 : OBJECT_UNREF: obj=0x2aad62a2ef0 debug : virConnectClose:1501 : conn=0x2aad62a2ef0 debug : virObjectUnref:256 : OBJECT_UNREF: obj=0x2aad62a2ef0 debug : virObjectUnref:258 : OBJECT_DISPOSE: obj=0x2aad62a2ef0 debug : virNetMessageNew:44 : msg=0x2aad62a2ac0 tracked=0 debug : virNetMessageEncodePayload:373 : Encode length as 28 debug : virNetClientSendInternal:1952 : RPC_CLIENT_MSG_TX_QUEUE: client=0x2aad62a3900 len=28 prog=536903814 vers=1 proc=2 type=0 status=0 serial=4 debug : virNetClientCallNew:1905 : New call 0x2aad62a3240: msg=0x2aad62a2ac0, expectReply=1, nonBlock=0 debug : virNetClientIO:1714 : Outgoing message prog=536903814 version=1 serial=4 proc=2 type=0 length=28 dispatch=(nil) debug : virNetClientIO:1773 : We have the buck head=0x2aad62a3240 call=0x2aad62a3240 debug : virEventPollUpdateHandle:147 : EVENT_POLL_UPDATE_HANDLE: watch=3 events=0 debug : virEventPollInterruptLocked:714 : Interrupting debug : virEventPollRunOnce:638 : Poll got 1 event(s) debug : virEventPollDispatchTimeouts:423 : Dispatch 0 debug : virEventPollDispatchHandles:468 : Dispatch 2 debug : virEventPollDispatchHandles:482 : i=0 w=1 debug : virEventPollDispatchHandles:496 : EVENT_POLL_DISPATCH_HANDLE: watch=1 events=1 debug : virEventPollCleanupTimeouts:514 : Cleanup 0 debug : virEventPollCleanupTimeouts:550 : Found 0 out of 0 timeout slots used, releasing 0 debug : virEventPollCleanupHandles:562 : Cleanup 2 debug : virEventRunDefaultImpl:270 : running default event implementation debug : virEventPollCleanupTimeouts:514 : Cleanup 0 debug : virEventPollCleanupTimeouts:550 : Found 0 out of 0 timeout slots used, releasing 0 debug : virEventPollCleanupHandles:562 : Cleanup 2 debug : virEventPollMakePollFDs:391 : Prepare n=0 w=1, f=5 e=1 d=0 debug : virEventPollMakePollFDs:391 : Prepare n=1 w=3, f=10 e=0 d=0 debug : virEventPollCalculateTimeout:332 : Calculate expiry of 0 timers debug : virEventPollCalculateTimeout:361 : Timeout at 0 due in -1 ms debug : virEventPollRunOnce:627 : EVENT_POLL_RUN: nhandles=1 timeout=-1 debug : virNetMessageDecodeLength:149 : Got length, now need 28 total (24 more) debug : virNetClientCallDispatch:1123 : RPC_CLIENT_MSG_RX: client=0x2aad62a3900 len=28 prog=536903814 vers=1 proc=2 type=1 status=0 serial=4 debug : virKeepAliveCheckMessage:374 : ka=0x2aad62a3ab0, client=0x2aad62a3900, msg=0x2aad62a3968 debug : virNetMessageClear:55 : msg=0x2aad62a3968 nfds=0 debug : virNetClientIOEventLoopPassTheBuck:1420 : Giving up the buck 0x2aad62a3240 debug : virNetClientIOEventLoopPassTheBuck:1434 : No thread to pass the buck to debug : virEventPollUpdateHandle:147 : EVENT_POLL_UPDATE_HANDLE: watch=3 events=1 debug : virEventPollInterruptLocked:714 : Interrupting debug : virNetClientIO:1803 : All done with our call head=(nil) call=0x2aad62a3240 rv=0 debug : virNetMessageFree:72 : msg=0x2aad62a2ac0 nfds=0 cb=(nil) debug : virNetClientCloseInternal:687 : client=0x2aad62a3900 wantclose=0 debug : virNetClientMarkClose:633 : client=0x2aad62a3900, reason=3 debug : virEventPollRemoveHandle:180 : EVENT_POLL_REMOVE_HANDLE: watch=3 debug : virEventPollRemoveHandle:193 : mark delete 1 10 debug : virEventPollInterruptLocked:714 : Interrupting debug : virNetClientIOEventLoopPassTheBuck:1420 : Giving up the buck (nil) debug : virNetClientIOEventLoopPassTheBuck:1434 : No thread to pass the buck to debug : virNetClientCloseLocked:646 : client=0x2aad62a3900, sock=0x2aad62a35c0, reason=3 debug : virObjectUnref:256 : OBJECT_UNREF: obj=0x2aad62a35c0 debug : virObjectRef:293 : OBJECT_REF: obj=0x2aad62a3900 debug : virKeepAliveStop:307 : RPC_KEEPALIVE_STOP: ka=0x2aad62a3ab0 client=0x2aad62a3900 debug : virObjectUnref:256 : OBJECT_UNREF: obj=0x2aad62a3ab0 debug : virObjectUnref:258 : OBJECT_DISPOSE: obj=0x2aad62a3ab0 debug : virKeepAliveDispose:227 : RPC_KEEPALIVE_DISPOSE: ka=0x2aad62a3ab0 debug : virObjectUnref:256 : OBJECT_UNREF: obj=0x2aad62a3900 debug : virObjectUnref:256 : OBJECT_UNREF: obj=0x2aad62a3900 debug : virObjectUnref:256 : OBJECT_UNREF: obj=0x2aad62a3900 debug : virObjectUnref:256 : OBJECT_UNREF: obj=0x2aad62a37f0 debug : virObjectUnref:256 : OBJECT_UNREF: obj=0x2aad62a2050 debug : virObjectUnref:256 : OBJECT_UNREF: obj=0x2aad62a3bb0 debug : virObjectUnref:256 : OBJECT_UNREF: obj=0x2aad62a31d0 debug : virEventPollAddTimeout:225 : Used 0 timeout slots, adding at least 10 more debug : virEventPollInterruptLocked:714 : Interrupting debug : virEventPollAddTimeout:248 : EVENT_POLL_ADD_TIMEOUT: timer=1 frequency=0 cb=0x2aad61b6f9c opaque=(nil) ff=(nil) debug : virEventPollRunOnce:638 : Poll got 1 event(s) debug : virEventPollDispatchTimeouts:423 : Dispatch 1 debug : virEventPollDispatchTimeouts:446 : EVENT_POLL_DISPATCH_TIMEOUT: timer=1 debug : virEventPollDispatchHandles:468 : Dispatch 1 debug : virEventPollDispatchHandles:482 : i=0 w=1 debug : virEventPollDispatchHandles:496 : EVENT_POLL_DISPATCH_HANDLE: watch=1 events=1 debug : virEventPollCleanupTimeouts:514 : Cleanup 1 debug : virEventPollCleanupHandles:562 : Cleanup 2 debug : virEventPollCleanupHandles:575 : EVENT_POLL_PURGE_HANDLE: watch=3 debug : virObjectUnref:256 : OBJECT_UNREF: obj=0x2aad62a3900 debug : virObjectUnref:258 : OBJECT_DISPOSE: obj=0x2aad62a3900 debug : virNetClientDispose:599 : RPC_CLIENT_DISPOSE: client=0x2aad62a3900 debug : virObjectUnref:256 : OBJECT_UNREF: obj=0x2aad62a31d0 debug : virObjectUnref:258 : OBJECT_DISPOSE: obj=0x2aad62a31d0 debug : virObjectUnref:256 : OBJECT_UNREF: obj=0x2aad62a37f0 debug : virObjectUnref:258 : OBJECT_DISPOSE: obj=0x2aad62a37f0 debug : virObjectUnref:256 : OBJECT_UNREF: obj=0x2aad62a2050 debug : virObjectUnref:258 : OBJECT_DISPOSE: obj=0x2aad62a2050 debug : virObjectUnref:256 : OBJECT_UNREF: obj=0x2aad62a3bb0 debug : virObjectUnref:258 : OBJECT_DISPOSE: obj=0x2aad62a3bb0 debug : virFileClose:90 : Closed fd 12 debug : virFileClose:90 : Closed fd 11 debug : virNetMessageClear:55 : msg=0x2aad62a3968 nfds=0 debug : virObjectUnref:256 : OBJECT_UNREF: obj=0x2aad62a35c0 debug : virObjectUnref:258 : OBJECT_DISPOSE: obj=0x2aad62a35c0 debug : virNetSocketDispose:1002 : RPC_SOCKET_DISPOSE: sock=0x2aad62a35c0 debug : virEventPollRemoveHandle:180 : EVENT_POLL_REMOVE_HANDLE: watch=3 debug : virFileClose:90 : Closed fd 10 debug : virEventPollRemoveTimeout:300 : EVENT_POLL_REMOVE_TIMEOUT: timer=1 debug : virEventPollInterruptLocked:710 : Skip interrupt, 0 4397868808464 -- Best Regards, Mars-+

1 0

Re: [libvirt-users] libvirt-users Digest, Vol 45, Issue 28
by Matthias Babisch 17 Sep '13

17 Sep '13

Test libvirt-users-request(a)redhat.com schrieb: >Send libvirt-users mailing list submissions to > libvirt-users(a)redhat.com > >To subscribe or unsubscribe via the World Wide Web, visit > https://www.redhat.com/mailman/listinfo/libvirt-users >or, via email, send a message with subject or body 'help' to > libvirt-users-request(a)redhat.com > >You can reach the person managing the list at > libvirt-users-owner(a)redhat.com > >When replying, please edit your Subject line so it is more specific >than "Re: Contents of libvirt-users digest..." > > >Today's Topics: > > 1. Finding out CPU topology. (Peeyush Gupta) > 2. Re: Finding out CPU topology. (Daniel P. Berrange) > 3. Re: Finding out CPU topology. (Peeyush Gupta) > > >---------------------------------------------------------------------- > >Message: 1 >Date: Tue, 17 Sep 2013 17:41:12 +0800 (SGT) >From: Peeyush Gupta <gpeeyush(a)ymail.com> >To: "libvirt-users(a)redhat.com" <libvirt-users(a)redhat.com> >Subject: [libvirt-users] Finding out CPU topology. >Message-ID: > <1379410872.26498.YahooMailNeo(a)web194604.mail.sg3.yahoo.com> >Content-Type: text/plain; charset="iso-8859-1" > >Hi all, > >I have been trying to find out cpu topology using libvirt. When >I do 'virsh capabilites', I find this inside <topology> tag: > > ><topology> >? ? ? <cells num='1'> >? ? ? ? <cell id='0'> >? ? ? ? ? <memory unit='KiB'>3908488</memory> >? ? ? ? ? <cpus num='4'> >? ? ? ? ? ? <cpu id='0' socket_id='0' core_id='0' siblings='0'/> >? ? ? ? ? ? <cpu id='1' socket_id='0' core_id='0' siblings='1'/> >? ? ? ? ? ? <cpu id='2' socket_id='0' core_id='1' siblings='2'/> >? ? ? ? ? ? <cpu id='3' socket_id='0' core_id='1' siblings='3'/> >? ? ? ? ? </cpus> >? ? ? ? </cell> >? ? ? </cells> ></topology> > >But when I use the 'getCapbilities()' function of the python binding, >the result is: ><topology> ? ? >? <cells num='1'> ?? >? ? ?<cell id='0'> ? ? ? ?? >? ? ?<cpus num='4'> ?? >? ? ? ?<cpu id='0'/> >? ? ? ?<cpu id='1'/> >? ? ? ?<cpu id='2'/> >? ? ? ?<cpu id='3'/> ? ? ? ?? >? ? ?</cpus> ? ? ? ? >? ?</cell> ? ? ? >?</cells> ? ></topology>\n > >As you can see this doesnt give any information about >socket/core/thread etc. >What I an interested to know is that is it a limitation of python >binding or libvirt >C API itself? How can I get the whole topology without just parsing the >output >of virsh capabilities? > >Thanks. >~Peeyush Gupta >-------------- next part -------------- >An HTML attachment was scrubbed... >URL: ><https://www.redhat.com/archives/libvirt-users/attachments/20130917/ff834444…> > >------------------------------ > >Message: 2 >Date: Tue, 17 Sep 2013 10:49:29 +0100 >From: "Daniel P. Berrange" <berrange(a)redhat.com> >To: Peeyush Gupta <gpeeyush(a)ymail.com> >Cc: "libvirt-users(a)redhat.com" <libvirt-users(a)redhat.com> >Subject: Re: [libvirt-users] Finding out CPU topology. >Message-ID: <20130917094929.GD28204(a)redhat.com> >Content-Type: text/plain; charset=utf-8 > >On Tue, Sep 17, 2013 at 05:41:12PM +0800, Peeyush Gupta wrote: >> Hi all, >> >> I have been trying to find out cpu topology using libvirt. When >> I do 'virsh capabilites', I find this inside <topology> tag: >> >> >> <topology> >> ? ? ? <cells num='1'> >> ? ? ? ? <cell id='0'> >> ? ? ? ? ? <memory unit='KiB'>3908488</memory> >> ? ? ? ? ? <cpus num='4'> >> ? ? ? ? ? ? <cpu id='0' socket_id='0' core_id='0' siblings='0'/> >> ? ? ? ? ? ? <cpu id='1' socket_id='0' core_id='0' siblings='1'/> >> ? ? ? ? ? ? <cpu id='2' socket_id='0' core_id='1' siblings='2'/> >> ? ? ? ? ? ? <cpu id='3' socket_id='0' core_id='1' siblings='3'/> >> ? ? ? ? ? </cpus> >> ? ? ? ? </cell> >> ? ? ? </cells> >> </topology> >> >> But when I use the 'getCapbilities()' function of the python binding, >> the result is: >> <topology> ? ? >> ? <cells num='1'> ?? >> ? ? ?<cell id='0'> ? ? ? ?? >> ? ? ?<cpus num='4'> ?? >> ? ? ? ?<cpu id='0'/> >> ? ? ? ?<cpu id='1'/> >> ? ? ? ?<cpu id='2'/> >> ? ? ? ?<cpu id='3'/> ? ? ? ?? >> ? ? ?</cpus> ? ? ? ? >> ? ?</cell> ? ? ? >> ?</cells> ? >> </topology>\n >> >> As you can see this doesnt give any information about >socket/core/thread etc. >> What I an interested to know is that is it a limitation of python >binding or libvirt >> C API itself? How can I get the whole topology without just parsing >the output >> of virsh capabilities? > >Did you really run these two examples on the same machine, with the >same >libvirt URI ? Both virsh and the python binding call the same libvirt >API >'virConnectGetCapabilities' so will return the same data if run against >the same libvirt. The socket_id, core_id and siblings data is a >relatively >new feature we added, so older libvirt won't show it. > >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 :| > > > >------------------------------ > >Message: 3 >Date: Tue, 17 Sep 2013 17:54:40 +0800 (SGT) >From: Peeyush Gupta <gpeeyush(a)ymail.com> >To: "Daniel P. Berrange" <berrange(a)redhat.com> >Cc: "libvirt-users(a)redhat.com" <libvirt-users(a)redhat.com> >Subject: Re: [libvirt-users] Finding out CPU topology. >Message-ID: > <1379411680.85399.YahooMailNeo(a)web194601.mail.sg3.yahoo.com> >Content-Type: text/plain; charset="iso-8859-1" > >Yes, I have run both of them on same machine. And?I? >am running libvirt 1.1.0. So, I guess it's not ?a?problem? >of older version. >? >Thanks >~Peeyush Gupta > > >________________________________ > From: Daniel P. Berrange <berrange(a)redhat.com> >To: Peeyush Gupta <gpeeyush(a)ymail.com> >Cc: "libvirt-users(a)redhat.com" <libvirt-users(a)redhat.com> >Sent: Tuesday, 17 September 2013 3:19 PM >Subject: Re: [libvirt-users] Finding out CPU topology. > > >On Tue, Sep 17, 2013 at 05:41:12PM +0800, Peeyush Gupta wrote: >> Hi all, >> >> I have been trying to find out cpu topology using libvirt. When >> I do 'virsh capabilites', I find this inside <topology> tag: >> >> >> <topology> >> ? ? ? <cells num='1'> >> ? ? ? ? <cell id='0'> >> ? ? ? ? ? <memory unit='KiB'>3908488</memory> >> ? ? ? ? ? <cpus num='4'> >> ? ? ? ? ? ? <cpu id='0' socket_id='0' core_id='0' siblings='0'/> >> ? ? ? ? ? ? <cpu id='1' socket_id='0' core_id='0' siblings='1'/> >> ? ? ? ? ? ? <cpu id='2' socket_id='0' core_id='1' siblings='2'/> >> ? ? ? ? ? ? <cpu id='3' socket_id='0' core_id='1' siblings='3'/> >> ? ? ? ? ? </cpus> >> ? ? ? ? </cell> >> ? ? ? </cells> >> </topology> >> >> But when I use the 'getCapbilities()' function of the python binding, >> the result is: >> <topology> ? ? >> ? <cells num='1'> ?? >> ? ? ?<cell id='0'> ? ? ? ?? >> ? ? ?<cpus num='4'> ?? >> ? ? ? ?<cpu id='0'/> >> ? ? ? ?<cpu id='1'/> >> ? ? ? ?<cpu id='2'/> >> ? ? ? ?<cpu id='3'/> ? ? ? ?? >> ? ? ?</cpus> ? ? ? ? >> ? ?</cell> ? ? ? >> ?</cells> ? >> </topology>\n >> >> As you can see this doesnt give any information about >socket/core/thread etc. >> What I an interested to know is that is it a limitation of python >binding or libvirt >> C API itself? How can I get the whole topology without just parsing >the output >> of virsh capabilities? > >Did you really run these two examples on the same machine, with the >same >libvirt URI ? Both virsh and the python binding call the same libvirt >API >'virConnectGetCapabilities' so will return the same data if run against >the same libvirt. The socket_id, core_id and siblings data is a >relatively >new feature we added, so older libvirt won't show it. > >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 :| >-------------- next part -------------- >An HTML attachment was scrubbed... >URL: ><https://www.redhat.com/archives/libvirt-users/attachments/20130917/df8c7fbf…> > >------------------------------ > >_______________________________________________ >libvirt-users mailing list >libvirt-users(a)redhat.com >https://www.redhat.com/mailman/listinfo/libvirt-users > >End of libvirt-users Digest, Vol 45, Issue 28 >********************************************* -- Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.

1 0

[libvirt-users] Finding out CPU topology.
by Peeyush Gupta 17 Sep '13

17 Sep '13

Hi all, I have been trying to find out cpu topology using libvirt. When I do 'virsh capabilites', I find this inside <topology> tag: <topology> <cells num='1'> <cell id='0'> <memory unit='KiB'>3908488</memory> <cpus num='4'> <cpu id='0' socket_id='0' core_id='0' siblings='0'/> <cpu id='1' socket_id='0' core_id='0' siblings='1'/> <cpu id='2' socket_id='0' core_id='1' siblings='2'/> <cpu id='3' socket_id='0' core_id='1' siblings='3'/> </cpus> </cell> </cells> </topology> But when I use the 'getCapbilities()' function of the python binding, the result is: <topology> <cells num='1'> <cell id='0'> <cpus num='4'> <cpu id='0'/> <cpu id='1'/> <cpu id='2'/> <cpu id='3'/> </cpus> </cell> </cells> </topology>\n As you can see this doesnt give any information about socket/core/thread etc. What I an interested to know is that is it a limitation of python binding or libvirt C API itself? How can I get the whole topology without just parsing the output of virsh capabilities? Thanks. ~Peeyush Gupta

2 2

[libvirt-users] Regarding libvirt usage
by Manzoor Ahamed 16 Sep '13

16 Sep '13

Hi Team, I am using libvirt module to retrieve configuration of the virtual machines, Can you please tell me how to retrieve the disk space of the Virtual machines. In my KVM hyper i am running two virtual machines. Regards Manzoor

3 4

[libvirt-users] Doc: How to use NPIV in libvirt
by Osier Yang 12 Sep '13

12 Sep '13

Before posting it to WIKI or somewhere, I want to see if there is any suggestions on it, or if I missed something. ============================================ How to use NPIV in libvirt I planned to wrote a document about how to use NPIV in libvirt after more features are supported, but it looks like I can't wait till then, got lots lots of questions from both the bugs and mails. So here we go. The document tries to summary up the things about NPIV that libvirt supports till now, and the TODO list. Feedback or suggestion is welcomed. 1) How to find out which HBA(s) support vHBA For libvirt newer than "1.0.4", you can find it out simply by: # virsh nodedev-list --cap vports "--cap vports" is to tell "nodedev-list" only outputs the devices which support "vports" capability, i.e. support vHBA. And also since version "1.0.4", you should be able to know the maximum vports the HBA supports and the current vports number from the HBA's XML, e.g. # virsh nodedev-dumpxml scsi_host5 <device> <name>scsi_host5</name> <parent>pci_0000_04_00_1</parent> <capability type='scsi_host'> <host>5</host> <capability type='fc_host'> <wwnn>2001001b32a9da4e</wwnn> <wwpn>2101001b32a9da4e</wwpn> <fabric_wwn>2001000dec9877c1</fabric_wwn> </capability> <capability type='vport_ops'> <max_vports>164</max_vports> <vports>5</vports> </capability> </capability> </device> For libvirt older than "1.0.4", it's a bit complicated than above: First you need to find out all the HBAs, e.g. # virsh nodedev-list --cap scsi_host scsi_host0 scsi_host1 scsi_host2 scsi_host3 scsi_host4 scsi_host5 And then, to see if the HBA supports vHBA, check if the dumped XML contains "vport_ops" capability. E.g. # virsh nodedev-dumpxml scsi_host3 <device> <name>scsi_host3</name> <parent>pci_0000_00_08_0</parent> <capability type='scsi_host'> <host>3</host> </capability> </device> That says "scsi_host3" doesn't support vHBA # virsh nodedev-dumpxml scsi_host5 <device> <name>scsi_host5</name> <parent>pci_0000_04_00_1</parent> <capability type='scsi_host'> <host>5</host> <capability type='fc_host'> <wwnn>2001001b32a9da4e</wwnn> <wwpn>2101001b32a9da4e</wwpn> <fabric_wwn>2001000dec9877c1</fabric_wwn> </capability> <capability type='vport_ops' /> </capability> </device> But "scsi_host5" supports it. One might be confused with the node device naming style (e.g. scsi_host5) in this document and RHEL6 Virtualization Guide [1] (pci_10df_fe00_scsi_host_0). It's because of libvirt has two backends for node device driver: udev and HAL. We prefer the udev backend more than HAL backend in internal implementation, I think there is good enough reason to do so (HAL is maintenance mode now). I believe udev backend is used more than HAL backend, but if your destribution packager build libvirt without udev backend, don't be surprised with the node device names like the ones in [1]. 2) How to create a vHBA Pick up one HBA which supports vHBA, use it's "node device name" as the "parent" of vHBA, and specify the "wwnn" and "wwpn" in the vHBA's XML. E.g. <device> <name>scsi_host6</name> <parent>scsi_host5</parent> <capability type='scsi_host'> <capability type='fc_host'> <wwnn>2001001b32a9da5e</wwnn> <wwpn>2101001b32a9da5e</wwpn> </capability> </capability> </device> Then create the vHBA with virsh command "nodedev-create" (assuming above XML file is named "vhba.xml"): # virsh nodedev-create vhba.xml Node device scsi_host6 created from vhba.xml Since "0.9.10", libvirt will generate "wwnn" and "wwpn" automatically if they are not specified. It means one can create the vHBA by a more simple XML like: <device> <parent>scsi_host5</parent> <capability type='scsi_host'> <capability type='fc_host'> </capability> </capability> </device> 3) How to destroy a vHBA As usual, destroying something is always simpler than creating it: # virsh nodedev-destroy scsi_host6 Destroyed node device 'scsi_host6' You might already realize that the vHBA is removed permanently, don't be surprised, it's the life, node device driver doesn't support persistent config. I won't say it's nightmare for users who screams when realizing the vHBA disappeared after a system rebooting, but it's relatively not good, (assuming that you got the wwnn:wwpn pair from the storage admin, but didn't record it). Fortunately, we support the persistent vHBA now, see next section for details. 4) How to create a persistent vHBA Let's go back to the history a bit firstly. Prior to libvirt "1.0.5", one can define a "scsi" type pool based on a (v)HBA by it's scsi host name (e.g. "host5" in XML below). E.g. <pool type='scsi'> <name>poolhba0</name> <uuid>e9392370-2917-565e-692b-d057f46512d6</uuid> <capacity unit='bytes'>0</capacity> <allocation unit='bytes'>0</allocation> <available unit='bytes'>0</available> <source> <adapter name='host0'/> </source> <target> <path>/dev/disk/by-path</path> <permissions> <mode>0700</mode> <owner>0</owner> <group>0</group> </permissions> </target> </pool> Quite nice? yeah, at least it looks so, but the problem is the scsi host number is *unstable* (it can be changed after system rebooting, or kernel module reloading, or a vHBA recreating etc), and thus the "scsi" type pool based on a (v)HBA becomes unstable too. Obviously it doesn't help on the "persistent vHBA" problem. To solve the problems, since libvirt "1.0.5", we introduced new XML schema to indicate the (v)HBA. An example of the XML: <pool type='scsi'> <name>poolvhba0</name> <uuid>e9392370-2917-565e-692b-d057f46512d6</uuid> <source> <adapter type='fc_host' parent='scsi_host5' wwnn='20000000c9831b4b' wwpn='10000000c9831b4b'/> </source> <target> <path>/dev/disk/by-path</path> <permissions> <mode>0700</mode> <owner>0</owner> <group>0</group> </permissions> </target> </pool> It allows to define a "scsi" type pool based on either a HBA or a vHBA. For HBA, "parent" attribute can be omitted. For vHBA, if "parent" is not specified, libvirt will pick up the first HBA which supports vHBA, and doesn't exceed the maximum vports it supports, automatically. For the pool based on a vHBA, When the pool is starting, libvirt will check if the specified vHBA (wwnn:wwpn) is existing on host or not, if it doesn't exist yet, libvirt will create it automatically. When the pool is being stopped, the vHBA is destroyed. But since storage driver supports the persistent config, one can easily gets the vHBA with same "wwnn:wwpn" in next starting (Don't scream if your pool is transient). It's not the end if you want to get the vHBA created automatically after system rebooting, you will need to set the pool as "autostart": # virsh pool-autostart poolvhba0 One might be curious about why not to support persistent config for node device driver, and support to create persistent vHBA there. One of the reason is that it will be duplicate with what storage pool does. And another reason (the important one) is we want to assiciate the libvirt storage pool/volume with domain (see section "Use LUN for guest" below). 5) How to find out the LUN's path If you have defined the "scsi" type pool based on the (v)HBA, it's simple to lookup what LUNs attached to the (v)HBA by virsh command "vol-list", e.g. # virsh vol-list poolvhba0 --details Name Path Type Capacity Allocation -------------------------------------------------------------------------------------------------------- unit:0:2:0 /dev/disk/by-path/pci-0000:04:00.1-fc-0x203500a0b85ad1d7-lun-0 block 20.01 GiB 20.01 GiB If you have not defined a "scsi" type pool based on the (v)HBA, you can find it out (v)HBA by either virsh command "nodedev-list --tree", or iterating sysfs manually. To find out the LUNs by virsh command "nodedev-list" (irrelevant ouputs are omitted): # virsh nodedev-list --tree +- pci_0000_00_0d_0 | | | +- pci_0000_04_00_0 | | | | | +- scsi_host4 | | | +- pci_0000_04_00_1 | | | +- scsi_host5 | | | +- scsi_host7 | +- scsi_target5_0_0 | | | | | +- scsi_5_0_0_0 | | | +- scsi_target5_0_1 | | | | | +- scsi_5_0_1_0 | | | +- scsi_target5_0_2 | | | | | +- scsi_5_0_2_0 | | | | | +- block_sdb_3600a0b80005adb0b0000ab2d4cae9254 | | | +- scsi_target5_0_3 | | | +- scsi_5_0_3_0 "scsi_host5" is an HBA on my host, it has a LUN named "block_sdb_3600a0b80005adb0b0000ab2d4cae9254", don't be confused with the naming, it's the naming style libvirt uses, meaningful only for libvirt. It indicates the LUN has a short device path "/dev/sdb", and a ID "3600a0b80005adb0b0000ab2d4cae9254": # ls /dev/disk/by-id/ | grep 3600a0b80005adb0b0000ab2d4cae9254 scsi-3600a0b80005adb0b0000ab2d4cae9254 To manually find the LUNs of a (v)HBA: First, you need to iterate over all the directores begins with the SCSI scsi host number of the v(HBA) under "/sys/bus/scsi/devices". E.g. I will look up the LUNs of the HBA with SCSI host number 5 on my host: # ls /sys/bus/scsi/devices/5:* -d /sys/bus/scsi/devices/5:0:0:0 /sys/bus/scsi/devices/5:0:1:0 /sys/bus/scsi/devices/5:0:2:0 /sys/bus/scsi/devices/5:0:3:0 # ls /sys/bus/scsi/devices/5\:0\:3\:0/block/sdc It means scsi_host5 has a LUN attached with device name "sdc" on address "5:0:3:0". # ls /sys/bus/scsi/devices/5\:0\:1\:0/ | grep block device_blocked scsi_host5 doesn't have a LUN attached on address "5:0:2:0" The device name like "sdc" is not stable, to find out the stable path, find out the symbol link which points to the device name. E.g. # ls -l /dev/disk/by-path/ lrwxrwxrwx. 1 root root 9 Sep 10 22:28 pci-0000:00:07.0-scsi-0:0:0:0 -> ../../sda lrwxrwxrwx. 1 root root 10 Sep 10 22:28 pci-0000:00:07.0-scsi-0:0:0:0-part1 -> ../../sda1 lrwxrwxrwx. 1 root root 9 Sep 10 22:28 pci-0000:04:00.1-fc-0x203400a0b85ad1d7-lun-0 -> ../../sdc Then "/dev/disk/by-path/pci-0000:04:00.1-fc-0x203400a0b85ad1d7-lun-0" is the stable path of the LUN attached to address "5:0:3:0". Of course, you can use the similiar method to get the "by-id | by-uuid | by-label" stable path. 6) Use the LUN to guest Since libvirt "1.0.5", we supported to use the storage volume as disk source by two new attributes ("pool" and "volume") for disk "<source"> element. E.g. <disk type='volume' device='disk'> <driver name='qemu' type='raw'/> <source pool='poolvhba0' volume='unit:0:2:0 '/> <target dev='hda' bus='ide'/> </disk> There are lots of advantage to do so. Since the mainly purpose of the document is about "how to use", I will only mention two here to persuade you using the it. First, you don't need to look up the LUN's path youself. Second, assuming that you want to migrate a domain which uses a LUN attached to a vHBA, do you want to create the vHBA manually on target host? With the pool, you can simply define/start a pool with same config on target host. So, if your libvirt is newer than "1.0.5", we recommend you to define the "scsi" type pool based on the (v)HBA, and use "pool/volume" names to use the LUN as disk source. You can either use the LUN as qemu emulated disk, or passthrough it to guest. To use it as qemu emulated disk, specifying the "device" attribute as "device='disk|cdrom|floppy'". E.g. <disk type='volume' device='disk'> <driver name='qemu' type='raw'/> <source pool='blk-pool0' volume='blk-pool0-vol0'/> <target dev='hda' bus='ide'/> </disk> Or (using the LUN's path directly) <disk type='volume' device='disk'> <driver name='qemu' type='raw'/> <source dev='/dev/disk/by-path/pci-0000\:04\:00.1-fc-0x203400a0b85ad1d7-lun-0'/> <target dev='sda' bus='scsi'/> </disk> To passthrough the LUN, specifying the "device" attribute as "device='lun'", e.g. <disk type='volume' device='lun'> <driver name='qemu' type='raw'/> <source dev='/dev/disk/by-path/pci-0000\:04\:00.1-fc-0x203400a0b85ad1d7-lun-0'/> <target dev='sda' bus='scsi'/> </disk> 6) Future work * NPIV based SCSI host passthrough That's what the users ask: How to passthrough a (v)HBA to guest? * Expose vendor information, LUN's path, state of (v)HBA in its XML * May be a virsh command to simplify vHBA creation with options [1] http://www.linuxtopia.org/online_books/rhel6/rhel_6_virtualization/rhel_6_v… Regards, Osier

2 1

Re: [libvirt-users] Questions on how to reset ID numbers for virt Guests.
by Paolo Bonzini 11 Sep '13

11 Sep '13

Il 11/09/2013 00:27, James Sparenberg ha scritto: > I'm doing some experimenting in our Development lab and as a result > I'm kickstarting over and over Virtual guests. This is of course > causing the guest Id to increment by one with each test. I've > googled around and tried searching the list but have not found out > how (if at all) it would be possible to reset the ID number back to 1 > more than is in use. Also is there a limit where I run out of ID's? > (for example does it only go up to 99?) No, there is no limit. I don't know the answer to your other question, so I'm adding the libvirt-users mailing list. Paolo

4 3

[libvirt-users] libvirt-1.2.2-r1 (Gentoo) fails to start LXC containers
by Dennis Jenkins 11 Sep '13

11 Sep '13

I recently upgraded "libvirt" on Gentoo to 1.2.2-r1 (latest available). I have not used LXC containers for a few weeks, so I don't recall what version of libvirt I was using when my container last booted successfully. Unfortunately, Gentoo's portage tree does not offer any previous versions of libvirt that I could downgrade to. TL;DR: My container is configured to use "br0" for its networking. "br0" exists totally inside my linux server - it is NOT bound to any physical NIC. "br0" is used for most of my QEMU and LXC VMs. libvirt is reporting that it cannot find device "veth1". All of my Gentoo packages are up-to-date. Digging through my logs (/var/log/libvirt/libvirt.log), I see that I last successfully booted this LXC container on 2013-07-22, with libvirt reporting version "1.1.0". Thoughts? ostara lxc # equery l libvirt * Searching for libvirt ... [IP-] [ ] app-emulation/libvirt-1.1.2-r1:0 ostara lxc # uname -a Linux ostara 3.10.7-gentoo #2 SMP PREEMPT Sat Aug 24 16:03:57 CDT 2013 x86_64 Intel(R) Core(TM) i5 CPU 760 @ 2.80GHz GenuineIntel GNU/Linux ostara ~ # emerge -pvuND world These are the packages that would be merged, in order: Calculating dependencies... done! Total: 0 packages, Size of downloads: 0 kB ostara lxc # virsh -c lxc:/// start dwj-hfax-dev error: Failed to start domain dwj-hfax-dev error: internal error: guest failed to start: PATH=/bin:/sbin TERM=linux container=lxc-libvirt container_uuid=681410de-7b56-41bd-b38d-3c66ce97e7b3 LIBVIRT_LXC_UUID=681410de-7b56-41bd-b38d-3c66ce97e7b3 LIBVIRT_LXC_NAME=dwj-hfax-dev /sbin/init error receiving signal from container: Input/output error ostara ~ # tail /var/log/libvirt/lxc/dwj-hfax-dev.log 2013-09-10 13:56:22.767+0000: starting up PATH=/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin:/opt/bin:/usr/x86_64-pc-linux-gnu/gcc-bin/4.6.3:/usr/x86_64-pc-linux-gnu/i686-pc-mingw32/gcc-bin/4.7.3 LIBVIRT_DEBUG=3 LIBVIRT_LOG_OUTPUTS=3:file:/var/log/libvirt/libvirtd.log /usr/libexec/libvirt_lxc --name dwj-hfax-dev --console 20 --security=none --handshake 23 --background --veth veth1 PATH=/bin:/sbin TERM=linux container=lxc-libvirt container_uuid=681410de-7b56-41bd-b38d-3c66ce97e7b3 LIBVIRT_LXC_UUID=681410de-7b56-41bd-b38d-3c66ce97e7b3 LIBVIRT_LXC_NAME=dwj-hfax-dev /sbin/init error receiving signal from container: Input/output error ostara ~ # tail /var/log/libvirt/libvirtd.log 2013-09-10 13:56:22.998+0000: 12948: info : libvirt version: 1.1.2 2013-09-10 13:56:22.998+0000: 12948: error : virLXCControllerRun:2186 : error receiving signal from container: Input/output error 2013-09-10 13:56:23.053+0000: 12948: error : virCommandWait:2348 : internal error: Child process (ip link del veth1) unexpected exit status 1: Cannot find device "veth1" 2013-09-10 13:56:23.097+0000: 10451: error : virNetSocketReadWire:1369 : Cannot recv data: Connection reset by peer 2013-09-10 13:56:23.153+0000: 10453: error : virLXCProcessStart:1234 : internal error: guest failed to start: PATH=/bin:/sbin TERM=linux container=lxc-libvirt container_uuid=681410de-7b56-41bd-b38d-3c66ce97e7b3 LIBVIRT_LXC_UUID=681410de-7b56-41bd-b38d-3c66ce97e7b3 LIBVIRT_LXC_NAME=dwj-hfax-dev /sbin/init error receiving signal from container: Input/output error 2013-09-10 13:56:23.343+0000: 10453: error : virCommandWait:2348 : internal error: Child process (ip link del veth1) unexpected exit status 1: Cannot find device "veth1" (first occurrence of "veth1" in my libvirtd logs) ostara ~ # grep -a veth1 /var/log/libvirt/libvirtd.log | head -1 2013-09-10 13:51:55.333+0000: 9742: error : virCommandWait:2348 : internal error: Child process (ip link del veth1) unexpected exit status 1: Cannot find device "veth1" ostara ~ # which ip /bin/ip ostara ~ # equery b /bin/ip * Searching for /bin/ip ... sys-apps/iproute2-3.8.0 (/bin/ip) ostara ~ # ls -l /bin/ip -rwxr-xr-x 1 root root 282616 May 4 04:08 /bin/ip ostara ~ # ifconfig -a | grep "^[a-z]" br0: flags=4355<UP,BROADCAST,PROMISC,MULTICAST> mtu 1500 br1: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST> mtu 1500 enp4s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 enp5s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 enp6s2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 ostara ~ # virsh -c lxc:/// dumpxml dwj-hfax-dev <domain type='lxc'> <name>dwj-hfax-dev</name> <uuid>681410de-7b56-41bd-b38d-3c66ce97e7b3</uuid> <memory unit='KiB'>4194304</memory> <currentMemory unit='KiB'>4194304</currentMemory> <vcpu placement='static'>4</vcpu> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64'>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='/vm/lxc/dwj-hfax-dev'/> <target dir='/'/> </filesystem> <filesystem type='mount' accessmode='passthrough'> <source dir='/usr/portage'/> <target dir='/usr/portage'/> </filesystem> <filesystem type='mount' accessmode='passthrough'> <source dir='/usr/src'/> <target dir='/usr/src'/> </filesystem> <filesystem type='mount' accessmode='passthrough'> <source dir='/home'/> <target dir='/home'/> </filesystem> <interface type='bridge'> <mac address='82:00:00:00:01:01'/> <source bridge='br0'/> </interface> <console type='pty'> <target type='lxc' port='0'/> </console> </devices> </domain>

4 5

[libvirt-users] Help needed in simulating libvirt
by Arun Viswanath 11 Sep '13

11 Sep '13

Hi All, I'm need to simulate libvirt API's say to mock the libvirt API responses. (Actually I need to simulate qemu API's response). Because of my project needs I need to write this simulated libvirt server in Java. I believe the simulated libvirt can be written as java RPC which should capable to receive the client RPC request calls and by dispatcher we can dispatch to the simulated java functions. I searched for .x file to be used for generating server stubs but unfortunately .x files like "remote_protocol.x", "virnetprotocol.x", "qemu_protocol.x" and "lxc_monitor_protocol.x" are not containing any procedure for libvirt API's that exposed. Please let me know which files will have these exposed procedures and how can I use it in java, Also I'm not sure how to implement the ssl layer support for the libvirt server in java. I need to write a java server in such a way that python client should capable to create a connection with uri "qemu+tls://systemip:port?no_tty=1". Also with the created connection object it should able to call the libvirt API's like getCapabilities, etc. Any help and ideas on this will be really helpful. Thanks in Advance, Arun V

3 6

Re: [libvirt-users] libvirt-1.1.2-r1 (Gentoo) fails to start LXC containers (subject line minor edit, was libvirt-1.2.2-r1)
by Dennis Jenkins 10 Sep '13

10 Sep '13

On Tue, Sep 10, 2013 at 1:34 PM, Doug Goldstein <cardoe(a)gentoo.org> wrote: > On Tue, Sep 10, 2013 at 9:09 AM, Dennis Jenkins > <dennis.jenkins.75(a)gmail.com> wrote: > > Yeah our security people got a bit over zealous. That's being rectified. > > :) > > > > TL;DR: My container is configured to use "br0" for its networking. "br0" > > exists totally inside my linux server - it is NOT bound to any physical > NIC. > > "br0" is used for most of my QEMU and LXC VMs. libvirt is reporting > that it > > cannot find device "veth1". All of my Gentoo packages are up-to-date. > > > > Digging through my logs (/var/log/libvirt/libvirt.log), I see that I last > > successfully booted this LXC container on 2013-07-22, with libvirt > reporting > > version "1.1.0". > > > > Thoughts? > > You really need to look at /var/log/libvirt/lxc/dwj-hfax-dev.log > > I did. I thought that I posted the relevant bits. I'll check/repost. It just lots of this (one set from each test that I did): 2013-09-10 13:56:22.767+0000: starting up PATH=/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin:/opt/bin:/usr/x86_64-pc-linux-gnu/gcc-bin/4.6.3:/usr/x86_64-pc-linux-gnu/i686-pc-mingw32/gcc-bin/4.7.3 LIBVIRT_DEBUG=3 LIBVIRT_LOG_OUTPUTS=3:file:/var/log/libvirt/libvirtd.log /usr/libexec/libvirt_lxc --name dwj-hfax-dev --console 20 --security=none --handshake 23 --background --veth veth1 PATH=/bin:/sbin TERM=linux container=lxc-libvirt container_uuid=681410de-7b56-41bd-b38d-3c66ce97e7b3 LIBVIRT_LXC_UUID=681410de-7b56-41bd-b38d-3c66ce97e7b3 LIBVIRT_LXC_NAME=dwj-hfax-dev /sbin/init error receiving signal from container: Input/output error I see the "--veth veth1", which is the same of the NIC that cannot be found. But that NIC is not listed in my domain config XML. > A suggestion would be to make sure that you have all the necessary > kernel options enabled. You can check with: ebuild > /usr/portage/app-emulation/libvirt/libvirt-1.1.2-r1.ebuild setup clean > > No errors. ostara ~ # ebuild /usr/portage/app-emulation/libvirt/libvirt-1.1.2-r1.ebuild setup clean * libvirt-1.1.2.tar.gz SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ] * libvirt-1.1.2-e89bdf01.tar.xz SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * Determining the location of the kernel source code * Found kernel source directory: * /usr/src/linux * Found kernel object directory: * /lib/modules/3.10.7-gentoo/build * Found sources for kernel version: * 3.10.7-gentoo * Checking for suitable kernel configuration options... [ ok ] 16 days ago, I updated from kernel 3.8.13 to 3.10.7. I could take a brief outage and down-grade my kernel if you think that is a worthy test. I just realized that when I composed my original email/bug report, that I misquoted the version of libvirt that I am running. I am indeed running "1.1.2-r1", but posted as "1.2.2-r1". ostara ~ # virsh version --daemon Compiled against library: libvirt 1.1.2 Using library: libvirt 1.1.2 Using API: QEMU 1.1.2 Running hypervisor: QEMU 1.5.2 Running against daemon: 1.1.2

1 2

[libvirt-users] how to setup network filter
by Jiaan Zeng 10 Sep '13

10 Sep '13

Hi All, I am new to libvirt and encounter a strange problem to set up network filter in a NAT network. I launched VMs in a single host using NAT, i.e. interface type='network'. Now I want to control the outbound traffic from VM instance - only allow the VM to asses a set of ip addresses. My network filter xml is as follows. The problem is once I change the VM xml, shutdown and start VM, VM cannot get ip address. /var/log/libvirt/libvirt.log shows " error : virNetDevGetIndex:656 : Unable to get index for interface vnet2: No such device" error. But when I remove the drop rule in the filter xml, VM can get IP address. I even tried the clean-traffic filter shipped with libvirt. VM throws the same error above. Any idea why this happens? How can I implement outbound traffic control in libvirt? Thanks a lot. <filter name='filter-test'> <rule action='accept' direction='in' priority='500'> <tcp dstportstart='22'/> </rule> <rule action='accept' direction='out' priority='500'> <ip dstipaddr='IP1'/> </rule> <rule action='accept' direction='out' priority='500'> <ip dstipaddr='IP2'/> </rule> <rule action='drop' direction='out' priority='500'> <all/> </rule> </filter> The VM network section XML looks like this <interface type='network'> <mac address='52:54:00:0d:f1:ce'/> <source network='default'/> <filterref filter='filter-test'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> -- Regards, Jiaan

2 1

[libvirt-users] Problems with user namespaces
by Jaka Hudoklin 10 Sep '13

10 Sep '13

Hello! I'm testing user namespaces and I have quite some problem getting them to work. First of all, I have user namespaces support enabled in kernel: offlinehacker:~/ $ uname -r 3.10.10 offlinehacker:~/ $ ls /proc/self/ns/ ipc@ mnt@ net@ pid@ user@ uts@ I created simple ubuntu rootfs and when I start container without idmap, so without user namespace mappings, it works just fine: Libivrt config: <domain type='lxc'> <name>helloworld</name> <memory>102400</memory> <os> <type>exe</type> <init>/bin/dash</init> </os>  <devices> <console type='pty'/> <filesystem type='mount'> <source dir='/home/offlinehacker/rootfs'/> <target dir='/'/> </filesystem> </devices> </domain> This is how my rootfs looks like: offlinehacker:~/ $ ls -la rootfs drwxr-xr-x 23 offlinehacker users 4096 sep 5 19:06 ./ drwxr-xr-x 59 offlinehacker users 4096 sep 5 19:06 ../ drwxr-xr-x 2 offlinehacker users 4096 avg 27 14:11 bin/ drwxr-xr-x 3 offlinehacker users 4096 avg 27 14:11 boot/ drwxr-xr-x 4 offlinehacker users 4096 avg 27 14:11 dev/ drwxr-xr-x 86 offlinehacker users 4096 sep 5 18:20 etc/ drwxr-xr-x 3 offlinehacker users 4096 avg 27 14:11 home/ lrwxrwxrwx 1 offlinehacker users 33 avg 27 14:10 initrd.img -> /boot/initrd.img-3.2.0-52-virtual drwxr-xr-x 18 offlinehacker users 4096 avg 27 14:10 lib/ drwxr-xr-x 2 offlinehacker users 4096 avg 27 14:10 lib64/ drwx------ 2 offlinehacker users 4096 avg 27 14:11 lost+found/ drwxr-xr-x 2 offlinehacker users 4096 avg 27 14:09 media/ drwxr-xr-x 2 offlinehacker users 4096 apr 19 2012 mnt/ drwxr-xr-x 2 offlinehacker users 4096 avg 27 14:09 opt/ -rw-r--r-- 1 offlinehacker vboxusers 231671365 avg 27 14:12 precise-server-cloudimg-amd64-root.tar.gz drwxr-xr-x 2 offlinehacker users 4096 apr 19 2012 proc/ drwx------ 2 offlinehacker users 4096 sep 3 23:47 root/ drwxr-xr-x 2 offlinehacker users 4096 avg 27 14:11 run/ drwxr-xr-x 2 offlinehacker users 4096 avg 27 14:11 sbin/ drwxr-xr-x 2 offlinehacker users 4096 mar 5 2012 selinux/ drwxr-xr-x 2 offlinehacker users 4096 avg 27 14:09 srv/ drwxr-xr-x 2 offlinehacker users 4096 apr 14 2012 sys/ drwxrwxrwt 2 offlinehacker users 4096 sep 4 01:39 tmp/ drwxr-xr-x 10 offlinehacker users 4096 avg 27 14:09 usr/ drwxr-xr-x 12 offlinehacker users 4096 sep 5 18:10 var/ lrwxrwxrwx 1 offlinehacker users 29 avg 27 14:10 vmlinuz -> boot/vmlinuz-3.2.0-52-virtual And this is who I am: offlinehacker:~/ $ id uid=499(offlinehacker) gid=67(libvirtd) groups=100(users),1(wheel),57(networkmanager),67(libvirtd) When I create the container with idmap uncommented I get the following error: offlinehacker:~/ $ virsh -c lxc:/// create helloworld.xml error: Failed to create domain from helloworld.xml error: internal error: guest failed to start: 2013-09-05 19:08:57.781+0000: 19036: debug And these are the logs: sep 05 19:08:52 laptop libvirtd[1542]: server=0x7fc8a60ddd60 client=0x7fc8a60e68d0 msg=0x7fc8a60e9380 rerr=0x7fc89a32cd40 args=0x7fc88800b4a0 ret=0x7fc88800a1c0 sep 05 19:08:52 laptop libvirtd[1542]: priv=0x7fc8a60e91f0 conn=(nil) sep 05 19:08:52 laptop libvirtd[1542]: name=lxc:/// sep 05 19:08:57 laptop libvirtd[1542]: Cannot recv data: Connection reset by peer sep 05 19:08:58 laptop libvirtd[1542]: internal error: guest failed to start: 2013-09-05 19:08:57.781+0000: 19036: debug Looks like .oldroot, dev, proc and sys gets created with mapped permissions(499:100), but container fails to start. Any help or direction how to get this working would be appriciated, Thanks, Jaka Hudoklin!

2 7

[libvirt-users] LVM Thin Volumes & Storage Pools
by Jorge Fábregas 09 Sep '13

09 Sep '13

Hi, Is it possible to create a storage pool based on an LVM thin pool? I read a recent bugzilla but the problem there was that the storage-pool became unusable AFTER creating a thinpool which is a different case. Thanks, Jorge

2 5

[libvirt-users] How to insert vcpupin in guest xml file
by Peeyush Gupta 09 Sep '13

09 Sep '13

Hi all, I am trying to add vcpupin in the guest xml file. I am working with openstack and the code I have is python bound. I investigated through the code and found that the elemets in xml file are set in get_guest_config function. Now the thing is I am not able to set vcpupin element. I mean I tried guest.cputune_vcpupin but it's not working. Help me out, please! Thanks. ~Peeyush Gupta

3 2

[libvirt-users] Cannot create a volume
by Daniele 09 Sep '13

09 Sep '13

Hi all, I'm trying to create a new volume in a netfs pool. The pool works correctly and it is active. If I try to create the volume from the virt-manager GUI nothing happens. While if I use virsh this is the result. *virsh # pool-list * *Name State Autostart * *-----------------------------------------* *routers active yes * * * *virsh # vol-create-as routers namevol 2G* *error: Failed to create vol vr1* *error: cannot create path '/var/lib/libvirt/images/routers/namevol': Invalid argument* What am I missing? Thanks for your help! Daniele

2 2