- Users - libvirt List Archives

Re: [libvirt-users] VM crash and lock manager
by Eric Blake 31 Mar '16

31 Mar '16

[moderator note: .pngs were stripped to avoid overwhelming the mail server and list recipients with 1M of data] -------- Forwarded Message -------- Date: Wed, 30 Mar 2016 11:25:09 +0200 Message-ID: <20160330112509.Horde.0Oad-ZfkzdZnouXf-VkEmw1(a)webmailperso.univ-brest.fr> From: villeneu(a)kassis.univ-brest.fr To: Franky Van Liedekerke <liedekef(a)telenet.be> Cc: libvirt-users(a)redhat.com Subject: Re: [libvirt-users] VM crash and lock manager References: <20160329192740.Horde.BZXrmDPzMBshASPvOs_x4Q6(a)webmailperso.univ-brest.fr> <20160329231311.1ae867a1(a)telenet.be> In-Reply-To: <20160329231311.1ae867a1(a)telenet.be> --- Franky Van Liedekerke <liedekef(a)telenet.be> a écrit : > On Tue, 29 Mar 2016 19:27:40 +0200 > villeneu(a)kassis.univ-brest.fr wrote: > >> Hello >> >> I changed my hypervisors ( 8) from centos 6.0 to fedora 23 and I >> added locks to prevent starting VM on multiple nodes, and it's work >> well. >> >> Since I changed the OS some old VMs ( centos 5.x and 6.x ) with very >> old kernel seem very instable and crash very often ( after one or two >> days ). Before they never have these problems. >> >> I saw, perhaps the reason is the dev is too slow ??? see screenshot >> joined >> >> A major problem with these crashs is that the VMs couldn't be >> destroyed by the virsh command, the qemu process is notified as >> defunct by the ps command. >> >> with virsh destroy VM >> I often get >> >> Failed to terminate process xxx with SIGTERM: Device or resource busy >> and the VM is still in the list >> >> If I try to remove all the file associated with the VM in /var/run or >> /var/lib....channel .. It doesn't give results The >> VM is still running as defunct and after a libvirt restart , libvirt >> and virsh command are pending. >> >> With sanlock it's a problem because the is never release and it's >> impossible to restart the VM. I can't remove the VM in the sanlock >> list. I tried kill commands, rm ... but without a real success. >> >> I tried many command with sanlock perhaps I misunderstood some >> commands but I never succeed in removing lock on the VMs. >> >> sanlock client rem_lockspace -r >> __LIBVIRT__DISKS__:b90b9c61e2d6413077205907ffb3281a:/var/lib/libvirt/images/POOL_ADMIN/sanlock/b90b9c61e2d6413077205907ffb3281a:0:4 >> -p 9383 >> >> So I'm trying to use lock_manager to replace the sanlock but >> lock_manager doesn't have tools to retrieve the lock / VM name in >> case of failure or crash. >> >> My questions are, is there a way to release or to force to release a >> lock with sanlock even if the qemu process is defunc and a way to >> restart libvirt in normal usage ? >> >> Perhaps by the API it`s possible to forece the release the lock ? >> >> Is there tools to retreive or calculate SHA256 lock for a VM with the >> lock_manager lock. I saw it's the lock is a SHA256 hash of the path >> and the VM name but I nerver get the good hash when I try by the hand. >> >> Is there tools to retreive or calculate SHA256 the lock for a VM with >> the lock_manager lock. I saw that the lock is a SHA256 hash of the >> path and the VM name but I never get the good hash when I try by the >> hand. >> >> Thanks. >> Sorry for my poor english ... I 'am french >> Michel > > It seems the lock held by sanlock isn't being released, so the vm can't > be shut down properly. Maybe some selinux issue? > I've been using virtlockd without troubles for more than a year already > (without selinux). For the locks, see if the lslocks command helps you. > > Franky > > _______________________________________________ > libvirt-users mailing list > libvirt-users@redhat.comhttps://www.redhat.com/mailman/listinfo/libvirt-users I do not use selinux too, I preffered sanlock at the beginning because sanlock comes with tools to remove locks. But when VMs crash abnormaly or freeze ( see the sreenshot I missed to attach it yesterday ) there is no way to unlease or remove the locks, they are presents even if I kill the process qemu and I can't restart the VM because the lock is still here. So I try now lock-manager, but do you know exactly how the lock is calculate . In case of problem I want to be able to retrieve the lock coupled with the VM. I have seen that it is a hash SHA256 of the path and the name, but if a try to do by the hand a sha256 of the complete path of the VM I don't have the correct value ( the same value as lock_manager ). Any Ideas ? Thanks crash1.png crash2.png

1 0

[libvirt-users] Hello and a question about QEMU log
by zhukaijie 31 Mar '16

31 Mar '16

Hello, Each running VM has it's command line logged in /var/log/libvirt/qemu/${vmname}. And now I'd like to disable this log function, that is to say, not to record the QEMU command line of VM. Could you please tell me will can I configure it? Best wishes.

2 1

[libvirt-users] VM crash and lock manager
by villeneu＠kassis.univ-brest.fr 30 Mar '16

30 Mar '16

Hello I changed my hypervisors ( 8) from centos 6.0 to fedora 23 and I added locks to prevent starting VM on multiple nodes, and it's work well. Since I changed the OS some old VMs ( centos 5.x and 6.x ) with very old kernel seem very instable and crash very often ( after one or two days ). Before they never have these problems. I saw, perhaps the reason is the dev is too slow ??? see screenshot joined A major problem with these crashs is that the VMs couldn't be destroyed by the virsh command, the qemu process is notified as defunct by the ps command. with virsh destroy VM I often get Failed to terminate process xxx with SIGTERM: Device or resource busy and the VM is still in the list If I try to remove all the file associated with the VM in /var/run or /var/lib....channel .. It doesn't give results The VM is still running as defunct and after a libvirt restart , libvirt and virsh command are pending. With sanlock it's a problem because the is never release and it's impossible to restart the VM. I can't remove the VM in the sanlock list. I tried kill commands, rm ... but without a real success. I tried many command with sanlock perhaps I misunderstood some commands but I never succeed in removing lock on the VMs. sanlock client rem_lockspace -r __LIBVIRT__DISKS__:b90b9c61e2d6413077205907ffb3281a:/var/lib/libvirt/images/POOL_ADMIN/sanlock/b90b9c61e2d6413077205907ffb3281a:0:4 -p 9383 So I'm trying to use lock_manager to replace the sanlock but lock_manager doesn't have tools to retrieve the lock / VM name in case of failure or crash. My questions are, is there a way to release or to force to release a lock with sanlock even if the qemu process is defunc and a way to restart libvirt in normal usage ? Perhaps by the API it`s possible to forece the release the lock ? Is there tools to retreive or calculate SHA256 lock for a VM with the lock_manager lock. I saw it's the lock is a SHA256 hash of the path and the VM name but I nerver get the good hash when I try by the hand. Is there tools to retreive or calculate SHA256 the lock for a VM with the lock_manager lock. I saw that the lock is a SHA256 hash of the path and the VM name but I never get the good hash when I try by the hand. Thanks. Sorry for my poor english ... I 'am french Michel

2 1

Re: [libvirt-users] "INTx fd" busy error on VM startup at boot, subsequent startup okay
by Pittman, Randall 30 Mar '16

30 Mar '16

Hey Mike, did you ever have any success figuring out this issue? I am having the same problem (on CentOS 7) with a custom data acquisition PCI card. It seems like the solution might have something to do with delaying the start of libvirtd in systemd until the PCI card (or vfio?) is ready, but I don’t know how to do that. Can anyone else offer assistance? My output: 2016-03-29T18:29:26.191010Z qemu-kvm: -device vfio-pci,host=05:00.0,id=hostdev0,bus=pci.0,addr=0x7: vfio: Error: Failed to setup INTx fd: Device or resource busy 2016-03-29T18:29:26.289154Z qemu-kvm: -device vfio-pci,host=05:00.0,id=hostdev0,bus=pci.0,addr=0x7: Device initialization failed. 2016-03-29T18:29:26.289195Z qemu-kvm: -device vfio-pci,host=05:00.0,id=hostdev0,bus=pci.0,addr=0x7: Device 'vfio-pci' could not be initialized 2016-03-29 18:29:26.337+0000: shutting down Thanks, Randy <--Original Message--> Hey all, I'm getting an error starting a libvirt managed qemu/kvm VM at physical host boot time, but manually starting it afterwards works fine. This is on a Ubuntu Wily i7-4790 box running Linux 4.2 and libvirt 1.2.16. There is a legacy (5V) PCI card being passed through to the VM, the error seems to relate to that. The error that always appears at boot in `/var/log/libvirt/qemu/test-vm.log` is: 2016-01-11T05:29:28.487935Z qemu-system-x86_64: -device vfio-pci,host=05:00.0,id=hostdev0,bus=pci.0,addr=0x4: vfio: Error: Failed to setup INTx fd: Device or resource busy 2016-01-11T05:29:28.488148Z qemu-system-x86_64: -device vfio-pci,host=05:00.0,id=hostdev0,bus=pci.0,addr=0x4: Device initialization failed 2016-01-11T05:29:28.488169Z qemu-system-x86_64: -device vfio-pci,host=05:00.0,id=hostdev0,bus=pci.0,addr=0x4: Device 'vfio-pci' could not be initialized After the physical machine has completed booting, starting the VM via virsh or virt-manager works fine. The card is an old Firewire card. I have blacklisted the firewire modules on the physical machine so they aren't loaded, but is it possible that the kernel, udev or some other process still has access to the device when systemd starts the libvirt-bin service? Any clues greatly appreciated. Thanks, //Mike -- ⊨ Michael Gratton, Percept Wrangler. ⚙ <http://mjog.vee.net/>

1 0

[libvirt-users] Using Openvswitch and qemu:///session
by Predrag Ivanovic 24 Mar '16

24 Mar '16

Hi. I'd like to use Openvswitch while running libvirt as an unprivileged user (qemu:///session). As expected, system session works just fine with OVS. When I try to start the domain from user session, with the relevant network part of the domain xml edited to use openvswitch, like this --- <interface type='bridge'> <mac address='52:54:00:4a:ef:bb'/> <source bridge='ovs-br'/> <virtualport type='openvswitch'> <parameters interfaceid='33ec3d9d-a92a-468e-aa48-6c31f7882d6f'/> </virtualport> <target dev='veth0-ovs'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </interface> --- I get this error: --- start freebsd-10.3 error: Failed to start domain freebsd-10.3 error: internal error: /usr/lib/qemu/qemu-bridge-helper --use-vnet --br=ovs-br --fd=19: failed to communicate with bridge helper: Transport endpoint is not connected stderr=failed to add interface `tap0' to bridge `ovs-br': Operation not supported --- Now, if I understand correctly, this is Qemu, not libvirt error? Libvirt prepares the network, passes it to qemu-bridge-helper, which has no idea what to do with it, since it's not the regular bridge, and barfs? The reason I ask is because I saw calls to ovs-vsctl in the logs when I did the same thing using qemu:///system. My question (finally): if I reconfigure OVS to not run as root:root, but as ovs:ovs, and add the user to that group, will libvirt/virsh automagically figure out that the user has permissions to run ovs-whatever and write permission to /var/run/openvswitch/db.sock, so there is no need for qemu-bridge-helper, and just set up the network, just like when system sesion is used, or is using qemu-bridge-helper the only option available for non-root users ? If it is, due to some Linux constraints, I'll curse a bit and migrate the domains :) And, before I forget, I am using libvirt and qemu built from git master, and openvswitch-2.5.0 Pedja

2 2

[libvirt-users] virsh and bash_complete
by Mohsen Pahlevanzadeh 24 Mar '16

24 Mar '16

3 3

[libvirt-users] /run/user/<uid> persists after user account is deleted
by Lars Kellogg-Stedman 24 Mar '16

24 Mar '16

In the tripleo-quickstart project, we're making use of libvirt's unprivileged mode. When run as a non-root user using a qemu:///session uri, libvirt creates files and sockets in subdirectories of $XDG_RUNTIME_DIR (aka /run/user/<uid>). We are seeing situations in which: - A "stack" user is created - Some libvirt resources (a storage pool) are provisioned for that user - The "stack" user is deleted (we first kill off any processes owned by the stack user, then delete the user via ansible which ultimately calls "userdel -r stack"). - The corresponding /run/user/<uid> directory is *not* deleted - A new "stack" user is created, and the stale storage pool from the previous invocation exists in an indeterminate state such at attempts to undefine it fail with: storage pool the_pool exists but directory /home/stack/pool is missing I can work around the problem like this: virsh pool-dumpxml the_pool | virsh pool-define /dev/stdin This ensures that a subsequent pool-undefine operation can successfully delete the pool. I think there are two problems here. Once is clearly a system problem; the /run/user directory should be deleted when the user account is deleted, period. The other problem seems like a libvirt problem: faced with a storage pool in this state, libvirt should permit the pool to be undefined anyway. It's possible this is already fixed in later releases of libvirt, but this is on CentOS 7, so we're stuck with libvirt-1.2.17-13.el7_2.3.x86_64 for now. I'm curious if anyone has seen this behavior or knows whether or not it has been corrected in later releases. Thanks, -- Lars Kellogg-Stedman <lars(a)redhat.com> | larsks @ {freenode,twitter,github} Cloud Engineering / OpenStack | http://blog.oddbit.com/

1 0

[libvirt-users] libvirt 1.3.3 and Hyper-V 2012
by Schwab Michael 23 Mar '16

23 Mar '16

Hello I installed libvirt 1.3.3 for managing a Hyper-V 2012 R2 Server. On the hyper-v server I entered the two commands: winrm set winrm/config/service/auth @{Basic="true"} winrm set winrm/config/service @{AllowUnencrypted="true"} After connecting, I receive the following error: user@ubuntu-serv-kvm:~/libvirt-hyperv-r2-2012$ virsh -c hyperv://192.168.33.140/?transport=http Enter username for 192.168.33.140 [administrator]: Enter administrator's password for 192.168.33.140: error: failed to connect to the hypervisor error: internal error: SOAP fault during enumeration: code 's:Sender', subcode 'n:CannotProcessFilter', reason 'The data source could not process the filter. The filter might be missing or it might be invalid. Change the filter and try the request again. ', detail '500The specified class does not exist in the given namespace. HRESULT 0x8033801a0052150858778HRESULTThe specified class does not exist in the given namespace. ' I found a patch: https://github.com/vikhyath/libvirt-hyperv-r2-2012 How can I add this patch? exist another method? Thanks for your help Greatings Michael

1 0

[libvirt-users] Virtual Netwok manager and cmd
by Mohsen Pahlevanzadeh 23 Mar '16

23 Mar '16

Dear All, I'm reading the following pages: http://wiki.libvirt.org/page/TaskRoutedNetworkSetupVirtManager http://wiki.libvirt.org/page/TaskNATSetupVirtManager http://wiki.libvirt.org/page/TaskIsolatedNetworkSetupVirtManager routed mode, NAT mode and Isolated mode, But above pages explain with GUI, a sysadmin forgets GUI... Question is What's replacement of above command? ---Best Regards Mohsen

2 1

[libvirt-users] changing clock on host temporarily blocks guest OS operation
by Andrei Perietanu 22 Mar '16

22 Mar '16

I have the following running on my system: - one linux host running libvirt 1.2.20 - two Linux guestOS VMs running When I change the clock on the host, the VMs stop responding: The VNC connection stops working, the console connection to the VMs does not work, ping stops reponding, libvirt commands temporarily stop working (after issuing the command, the system just hangs). I get control back after 5 min or so, but I have to restart the VMs for everything to work again. Any ideas what's causing this? Is this a know bug? Is there a fix for it? Thanks in advance, Andrei -- The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you receive this in error please contact the sender and delete the material from any computer immediately. It is the policy of Klas Limited to disavow the sending of offensive material and should you consider that the material contained in the message is offensive you should contact the sender immediately and also your I.T. Manager. Klas Telecom Inc., a Virginia Corporation with offices at 1101 30th St. NW, Washington, DC 20007. Klas Limited (Company Number 163303) trading as Klas Telecom, an Irish Limited Liability Company, with its registered office at Fourth Floor, One Kilmainham Square, Inchicore Road, Kilmainham, Dublin 8, Ireland.

1 0

[libvirt-users] virtual machine won't autostart when using LVM with cache
by David Hlacik 21 Mar '16

21 Mar '16

Hello guys, Recently I have switched to use LVM cache feature on logical volume /dev/hdd/windata1 to improve it performace using 32GB partition from SSD disk. However, when my computer will start, my virtual machine won't autostart Mar 21 10:48:57 brutus-coreos libvirtd[956]: Cannot access storage file '/dev/hdd/windata1' (as uid:107, gid:107): No such file or directory Mar 21 10:48:57 brutus-coreos libvirtd[956]: Failed to autostart VM 'winos1': Cannot access storage file '/dev/hdd/windata1' (as uid:107, gid:107): No such file or directory Mar 21 10:48:57 brutus-coreos libvirtd[956]: Cannot access storage file '/dev/hdd/windata1' (as uid:107, gid:107): No such file or directory It seems that when using LVM cache, one have to wait till it will inicialize? When I will manually start virtual machine afterwards, everything works OK : [root@brutus-coreos ~]# virsh start winos1 Domain winos1 started I have tried to remove LVM cache from /dev/hdd/windata1 and afterward autostart works! So it must be LVM cache related. Can you please help me to solve this ? Thanks in advance David Hlacik +420-777-307-745 | david(a)hlacik.cz [image: View David Hlacik's profile on LinkedIn] <http://cz.linkedin.com/in/hlacik>

1 0

[libvirt-users] Libvirt bite sized tasks
by Michal Privoznik 21 Mar '16

21 Mar '16

Dear lists, I've just started new wiki page which aim is to summarize small and trivial tasks, that starting contributors can take, investigate and implement. The aim is to give them something easy to start with while not scaring them out about complexity of our code. The page can be found here: http://wiki.libvirt.org/page/BiteSizedTasks The name is copied from qemu wiki: http://wiki.qemu.org/BiteSizedTasks Please, feel free to extend the list. I plan to use it in the future when interviewing GSoC candidates. Michal

2 1

[libvirt-users] Incorrect memory usage returned from virsh
by Connor Osborn 19 Mar '16

19 Mar '16

When I run `virsh dominfo <domain>` I get the following: Id: 455 Name: instance-000047e0 UUID: 50722aa0-d5c6-4a68-b4ef-9b27beba48aa OS Type: hvm State: running CPU(s): 4 CPU time: 123160.4s Max memory: 33554432 KiB Used memory: 33554432 KiB Persistent: yes Autostart: disable Managed save: no Security model: apparmor Security DOI: 0 Security label: libvirt-50722aa0-d5c6-4a68-b4ef-9b27beba48aa (enforcing) The domain is not at 100% memory capacity. How can I diagnose this further?

3 3

[libvirt-users] Can I use 'virsh save' this command only get 'vm physical memory' ? If not , please tell me how can I get it .
by Leekitty 19 Mar '16

19 Mar '16

Can I use 'virsh save' this command only get 'vm physical memory' ? If not ,please tell me how can I get it . Thanks in advance. Lee Wen

2 1

[libvirt-users] CfP 11th Workshop on Virtualization in High-Performance Cloud Computing (VHPC '16)
by VHPC 16 19 Mar '16

19 Mar '16

==================================================================== CALL FOR PAPERS 11th Workshop on Virtualization in High-Performance Cloud Computing (VHPC '16) held in conjunction with the International Supercomputing Conference - High Performance, June 19-23, 2016, Frankfurt, Germany. ==================================================================== Date: June 23, 2016 Workshop URL: http://vhpc.org Paper Submission Deadline: April 25, 2016 Call for Papers Virtualization technologies constitute a key enabling factor for flexible resource management in modern data centers, and particularly in cloud environments. Cloud providers need to manage complex infrastructures in a seamless fashion to support the highly dynamic and heterogeneous workloads and hosted applications customers deploy. Similarly, HPC environments have been increasingly adopting techniques that enable flexible management of vast computing and networking resources, close to marginal provisioning cost, which is unprecedented in the history of scientific and commercial computing. Various virtualization technologies contribute to the overall picture in different ways: machine virtualization, with its capability to enable consolidation of multiple underutilized servers with heterogeneous software and operating systems (OSes), and its capability to live-migrate a fully operating virtual machine (VM) with a very short downtime, enables novel and dynamic ways to manage physical servers; OS-level virtualization (i.e., containerization), with its capability to isolate multiple user-space environments and to allow for their coexistence within the same OS kernel, promises to provide many of the advantages of machine virtualization with high levels of responsiveness and performance; I/O Virtualization allows physical NICs/HBAs to take traffic from multiple VMs or containers; network virtualization, with its capability to create logical network overlays that are independent of the underlying physical topology and IP addressing, provides the fundamental ground on top of which evolved network services can be realized with an unprecedented level of dynamicity and flexibility; the increasingly adopted paradigm of Software-Defined Networking (SDN) promises to extend this flexibility to the control and data planes of network paths. Topics of Interest The VHPC program committee solicits original, high-quality submissions related to virtualization across the entire software stack with a special focus on the intersection of HPC and the cloud. Topics include, but are not limited to: - Virtualization in supercomputing environments, HPC clusters, cloud HPC and grids - OS-level virtualization including container runtimes (Docker, rkt et al.) - Lightweight compute node operating systems/VMMs - Optimizations of virtual machine monitor platforms, hypervisors - QoS and SLA in hypervisors and network virtualization - Cloud based network and system management for SDN and NFV - Management, deployment and monitoring of virtualized environments - Virtual per job / on-demand clusters and cloud bursting - Performance measurement, modelling and monitoring of virtualized/cloud workloads - Programming models for virtualized environments - Virtualization in data intensive computing and Big Data processing - Cloud reliability, fault-tolerance, high-availability and security - Heterogeneous virtualized environments, virtualized accelerators, GPUs and co-processors - Optimized communication libraries/protocols in the cloud and for HPC in the cloud - Topology management and optimization for distributed virtualized applications - Adaptation of emerging HPC technologies (high performance networks, RDMA, etc..) - I/O and storage virtualization, virtualization aware file systems - Job scheduling/control/policy in virtualized environments - Checkpointing and migration of VM-based large compute jobs - Cloud frameworks and APIs - Energy-efficient / power-aware virtualization The Workshop on Virtualization in High-Performance Cloud Computing (VHPC) aims to bring together researchers and industrial practitioners facing the challenges posed by virtualization in order to foster discussion, collaboration, mutual exchange of knowledge and experience, enabling research to ultimately provide novel solutions for virtualized computing systems of tomorrow. The workshop will be one day in length, composed of 20 min paper presentations, each followed by 10 min discussion sections, plus lightning talks that are limited to 5 minutes. Presentations may be accompanied by interactive demonstrations. Important Dates April 25, 2016 - Paper submission deadline May 30, 2016 Acceptance notification June 23, 2016 - Workshop Day July 25, 2016 - Camera-ready version due Chair Michael Alexander (chair), TU Wien, Austria Anastassios Nanos (co-chair), NTUA, Greece Balazs Gerofi (co-chair), RIKEN Advanced Institute for Computational Science, Japan Program committee Stergios Anastasiadis, University of Ioannina, Greece Costas Bekas, IBM Research, Switzerland Jakob Blomer, CERN Ron Brightwell, Sandia National Laboratories, USA Roberto Canonico, University of Napoli Federico II, Italy Julian Chesterfield, OnApp, UK Stephen Crago, USC ISI, USA Christoffer Dall, Columbia University, USA Patrick Dreher, MIT, USA Robert Futrick, Cycle Computing, USA Robert Gardner, University of Chicago, USA William Gardner, University of Guelph, Canada Wolfgang Gentzsch, UberCloud, USA Kyle Hale, Northwestern University, USA Marcus Hardt, Karlsruhe Institute of Technology, Germany Krishna Kant, Templte University, USA Romeo Kinzler, IBM, Switzerland Brian Kocoloski, University of Pittsburgh, USA Kornilios Kourtis, IBM Research, Switzerland Nectarios Koziris, National Technical University of Athens, Greece John Lange, University of Pittsburgh, USA Nikos Parlavantzas, IRISA, France Kevin Pendretti, Sandia National Laboratories, USA Che-Rung Roger Lee, National Tsing Hua University, Taiwan Giuseppe Lettieri, University of Pisa, Italy Qing Liu, Oak Ridge National Laboratory, USA Paul Mundt, Adaptant, Germany Amer Qouneh, University of Florida, USA Carlos Reaño, Technical University of Valencia, Spain Seetharami Seelam, IBM Research, USA Josh Simons, VMWare, USA Borja Sotomayor, University of Chicago, USA Dieter Suess, TU Wien, Austria Craig Stewart, Indiana University, USA Anata Tiwari, San Diego Supercomputer Center, USA Kurt Tutschku, Blekinge Institute of Technology, Sweden Amit Vadudevan, Carnegie Mellon University, USA Yasuhiro Watashiba, Osaka University, Japan Nicholas Wright, Lawrence Berkeley National Laboratory, USA Chao-Tung Yang, Tunghai University, Taiwan Gianluigi Zanetti, CRS4, Italy Paper Submission-Publication Papers submitted to the workshop will be reviewed by at least two members of the program committee and external reviewers. Submissions should include abstract, key words, the e-mail address of the corresponding author, and must not exceed 10 pages, including tables and figures at a main font size no smaller than 11 point. Submission of a paper should be regarded as a commitment that, should the paper be accepted, at least one of the authors will register and attend the conference to present the work. The format must be according to the Springer LNCS Style. Initial submissions are in PDF; authors of accepted papers will be requested to provide source files. Format Guidelines: ftp://ftp.springer.de/pub/tex/latex/llncs/latex2e/llncs2e.zip Abstract, Paper Submission Link: https://edas.info/newPaper.php?c=21801 Lightning Talks Lightning Talks are non-paper track, synoptical in nature and are strictly limited to 5 minutes. They can be used to gain early feedback on ongoing research, for demonstrations, to present research results, early research ideas, perspectives and positions of interest to the community. Submit abstract via the main submission link. General Information The workshop is one day in length and will be held in conjunction with the International Supercomputing Conference - High Performance (ISC) 2016, June 19-23, Frankfurt, Germany.

1 0

[libvirt-users] save - restore problem
by Fırat KÜÇÜK 19 Mar '16

19 Mar '16

I was trying to live-migrate a VM. I have not succeeded for now. Instead live-migration Just tried simple save and restore action in same host. virsh save my-domain my-domain.saved virsh restore my-domain.saved Everything seems fine after restoring. But after 5 minutes VM halted. No network connectivity. No response to VNC keystrokes. Totally halted. Is there any suggestion?

1 1

[libvirt-users] Fwd: [Issue]: Regarding client socket getting closed from the server once the lxc container is started
by rammohan madhusudan 18 Mar '16

18 Mar '16

Hi Folks, Using libvirt python bindings we are creating an lxc container.Here is the problem that we see sometimes (say 20 % of the time) when we create a new container. 1.container gets created, and also starts.However the we are not able to enter the namepace of the container.It throws an error initPid not available.We see that the using netstat command , socket connection is closed. 2.To get around this problem we have to stop and start the container again.We see that socket under (/var/run/libvirt/*) connection is established and we are able to enter the namespace. Enabled the libvirtd debug logs to debug this issue. For *success* case we see that for new client connection gets created and is able to handle async incoming events, *2016-03-12 08:18:55.748+0000: 1247: info : virObjectNew:202 : OBJECT_NEW: obj=0x7fed54005460 classname=virLXCMonitor* *2016-03-12 08:18:55.748+0000: 1247: debug : virNetSocketNew:159 : localAddr=0x7fed7cd1d170 remoteAddr=0x7fed7cd1d200 fd=28 errfd=-1 pid=0* *2016-03-12 08:18:55.749+0000: 1247: info : virObjectNew:202 : OBJECT_NEW: obj=0x7fed54009040 classname=virNetSocket* *2016-03-12 08:18:55.749+0000: 1247: info : virNetSocketNew:209 : RPC_SOCKET_NEW: sock=0x7fed54009040 fd=28 errfd=-1 pid=0 localAddr=127.0.0.1;0, remoteAddr=127.0.0.1;0* *2016-03-12 08:18:55.749+0000: 1247: info : virObjectNew:202 : OBJECT_NEW: obj=0x7fed54009d10 classname=virNetClient* *2016-03-12 08:18:55.749+0000: 1247: info : virNetClientNew:327 : RPC_CLIENT_NEW: client=0x7fed54009d10 sock=0x7fed54009040* *2016-03-12 08:18:55.749+0000: 1247: info : virObjectRef:296 : OBJECT_REF: obj=0x7fed54009d10* *2016-03-12 08:18:55.749+0000: 1247: info : virObjectRef:296 : OBJECT_REF: obj=0x7fed54009040* *2016-03-12 08:18:55.750+0000: 1247: info : virObjectNew:202 : OBJECT_NEW: obj=0x7fed540009a0 classname=virNetClientProgram* *2016-03-12 08:18:55.750+0000: 1247: info : virObjectRef:296 : OBJECT_REF: obj=0x7fed540009a0* *2016-03-12 08:18:55.750+0000: 1247: info : virObjectRef:296 : OBJECT_REF: obj=0x7fed54005460* *2016-03-12 08:18:55.750+0000: 1247: info : virObjectUnref:259 : OBJECT_UNREF: obj=0x7fed5c168eb0* *2016-03-12 08:18:55.750+0000: 1247: debug : virLXCProcessCleanInterfaces:475 : Cleared net names: eth0 * *2016-03-12 08:18:55.750+0000: 1247: info : virObjectUnref:259 : OBJECT_UNREF: obj=0x7fed5c168eb0* *2016-03-12 08:18:55.750+0000: 1247: info : virObjectUnref:259 : OBJECT_UNREF: obj=0x7fed5c169600* *2016-03-12 08:18:55.755+0000: 1244: debug : virNetClientIncomingEvent:1808 : client=0x7fed54009d10 wantclose=0* *2016-03-12 08:18:55.755+0000: 1244: debug : virNetClientIncomingEvent:1816 : Event fired 0x7fed54009040 1* *2016-03-12 08:18:55.755+0000: 1244: debug : virNetMessageDecodeLength:151 : Got length, now need 36 total (32 more)* *2016-03-12 08:18:55.756+0000: 1244: info : virNetClientCallDispatch:1116 : RPC_CLIENT_MSG_RX: client=0x7fed54009d10 len=36 prog=305402420 vers=1 proc=2 type=2 status=0 serial=1* *2016-03-12 08:18:55.756+0000: 1244: debug : virKeepAliveCheckMessage:377 : ka=(nil), client=0x7fed81fc5ed4, msg=0x7fed54009d78* *2016-03-12 08:18:55.756+0000: 1244: debug : virNetClientProgramDispatch:220 : prog=305402420 ver=1 type=2 status=0 serial=1 proc=2* *2016-03-12 08:18:55.756+0000: 1244: debug : virLXCMonitorHandleEventInit:109 : Event init 1420 * For *failure* case ,we see that the client socket connection is initiated and gets closed immediately after receiving an incoming event.In this case, I don’t see an object for virNetClientProgram being created. Incoming event comes in and since the its unable to find client->prog it bails out and closes the connection. Snaphost of the code, static int virNetClientCallDispatchMessage(virNetClientPtr client) { size_t i; virNetClientProgramPtr prog = NULL; for (i = 0; i < client->nprograms; i++) { if (virNetClientProgramMatches(client->programs[i], &client->msg)) { prog = client->programs[i]; break; } } if (!prog) { * VIR_DEBUG("No program found for event with prog=%d vers=%d",* * client->msg.header.prog, client->msg.header.vers);* return -1; } *2016-03-12 08:19:15.935+0000: 1246: info : virObjectRef:296 : OBJECT_REF: obj=0x7fed5c168eb0* *2016-03-12 08:19:15.935+0000: 1246: info : virObjectRef:296 : OBJECT_REF: obj=0x7fed82bd7bc0* *2016-03-12 08:19:15.935+0000: 1246: info : virObjectNew:202 : OBJECT_NEW: obj=0x7fed82bd8120 classname=virLXCMonitor* *2016-03-12 08:19:15.935+0000: 1246: debug : virNetSocketNew:159 : localAddr=0x7fed7d51e170 remoteAddr=0x7fed7d51e200 fd=31 errfd=-1 pid=0* *2016-03-12 08:19:15.936+0000: 1246: info : virObjectNew:202 : OBJECT_NEW: obj=0x7fed82bd8660 classname=virNetSocket* *2016-03-12 08:19:15.936+0000: 1246: info : virNetSocketNew:209 : RPC_SOCKET_NEW: sock=0x7fed82bd8660 fd=31 errfd=-1 pid=0 localAddr=127.0.0.1;0, remoteAddr=127.0.0.1;0* *2016-03-12 08:19:15.936+0000: 1246: info : virObjectNew:202 : OBJECT_NEW: obj=0x7fed82bd8ca0 classname=virNetClient* *2016-03-12 08:19:15.936+0000: 1246: info : virNetClientNew:327 : RPC_CLIENT_NEW: client=0x7fed82bd8ca0 sock=0x7fed82bd8660* *2016-03-12 08:19:15.936+0000: 1246: info : virObjectRef:296 : OBJECT_REF: obj=0x7fed82bd8ca0* *2016-03-12 08:19:15.936+0000: 1246: info : virObjectRef:296 : OBJECT_REF: obj=0x7fed82bd8660* *2016-03-12 08:19:15.942+0000: 1244: debug : virNetClientIncomingEvent:1808 : client=0x7fed82bd8ca0 wantclose=0* *2016-03-12 08:19:15.942+0000: 1244: debug : virNetClientIncomingEvent:1816 : Event fired 0x7fed82bd8660 1* *2016-03-12 08:19:15.942+0000: 1244: debug : virNetMessageDecodeLength:151 : Got length, now need 36 total (32 more)* *2016-03-12 08:19:15.942+0000: 1244: info : virNetClientCallDispatch:1116 : RPC_CLIENT_MSG_RX: client=0x7fed82bd8ca0 len=36 prog=305402420 vers=1 proc=2 type=2 status=0 serial=1* *2016-03-12 08:19:15.942+0000: 1244: debug : virKeepAliveCheckMessage:377 : ka=(nil), client=0x7fed81fc5ed4, msg=0x7fed82bd8d08* *2016-03-12 08:19:15.942+0000: 1244: debug : virNetClientCallDispatchMessage:1008 : No program found for event with prog=305402420 vers=1* *2016-03-12 08:19:15.942+0000: 1244: debug : virNetMessageClear:57 : msg=0x7fed82bd8d08 nfds=0* *2016-03-12 08:19:15.942+0000: 1244: debug : virNetClientMarkClose:632 : client=0x7fed82bd8ca0, reason=0* *2016-03-12 08:19:15.942+0000: 1244: debug : virNetClientCloseLocked:648 : client=0x7fed82bd8ca0, sock=0x7fed82bd8660, reason=0* Here is the snapshot of code , virLXCMonitorPtr virLXCMonitorNew(virDomainObjPtr vm, const char *socketdir, virLXCMonitorCallbacksPtr cb) { virLXCMonitorPtr mon; char *sockpath = NULL; if (virLXCMonitorInitialize() < 0) return NULL; if (!(mon = virObjectLockableNew(virLXCMonitorClass))) return NULL; if (virAsprintf(&sockpath, "%s/%s.sock", socketdir, vm->def->name) < 0) goto error; if (!(mon->client = virNetClientNewUNIX(sockpath, false, NULL))) goto error; * if (virNetClientRegisterAsyncIO(mon->client) < 0)* * goto error;* * if (!(mon->program = virNetClientProgramNew(VIR_LXC_MONITOR_PROGRAM,* * VIR_LXC_MONITOR_PROGRAM_VERSION,* * virLXCMonitorEvents,* * ARRAY_CARDINALITY(virLXCMonitorEvents),* * mon)))* * goto error;* * if (virNetClientAddProgram(mon->client,* * mon->program) < 0)* * goto error;* * mon->vm = vm;* * memcpy(&mon->cb, cb, sizeof(mon->cb));* virObjectRef(mon); virNetClientSetCloseCallback(mon->client, virLXCMonitorEOFNotify, mon, virLXCMonitorCloseFreeCallback); Is the problem occurring due to invocation of “*virNetClientRegisterAsyncIO" api before the virNetClientAddProgram.Probably once we register for aysnc IO , immediately an event comes in and that thread takes priority and bails out since it does not find the client->prog?Also the client is not retrying to establish a new connection.* *Please let me any thoughts/comments.Is there any patch already available which has fixed this issue?We are using libvirt 1.2.15* *-Thanks,* *Rammohan*

1 0

[libvirt-users] Questions regarding hostdev scsi
by Martin Polednik 18 Mar '16

18 Mar '16

Hi! I'm oVirt developer responsible for most of 'hostdev' support. While working on SCSI passthrough (that is hostdev type='scsi'), I've encountered few issues I'm not sure how to solve somewhat effectively and nicely. Just a note - oVirt by default disables 'dynamic_ownership', meaning we have to handle endpoint ownership/labeling ourselves. This is not something I can change in a short term. Also, oVirt uses libvirt's python API, I'll do my best using the original C names. To report and construct the hostdev element, I am using virConnectListAllNodeDevices. To get information about the devices, virNodeDeviceGetXMLDesc is called on each device. For PCI and USB devices, XML of the device contains everything needed to a) construct the element, b) fix endpoint permissions. SCSI device becomes more difficult as the information is scattered between multiple devices. Devices I have encountered contain this subtree: <device> <name>scsi_host4</name> <path>/sys/devices/pci0000:00/0000:00:1f.2/ata5/host4</path> <parent>pci_0000_00_1f_2</parent> <capability type='scsi_host'> <host>4</host> <unique_id>5</unique_id> </capability> </device> <device> <name>scsi_target4_0_0</name> <path>/sys/devices/pci0000:00/0000:00:1f.2/ata5/host4/target4:0:0</path> <parent>scsi_host4</parent> <capability type='scsi_target'> <target>target4:0:0</target> </capability> </device> <device> <name>scsi_4_0_0_0</name> <path>/sys/devices/pci0000:00/0000:00:1f.2/ata5/host4/target4:0:0/4:0:0:0</path> <parent>scsi_target4_0_0</parent> <driver> <name>sd</name> </driver> <capability type='scsi'> <host>4</host> <bus>0</bus> <target>0</target> <lun>0</lun> <type>disk</type> </capability> </device> <device> <name>block_sdb_Samsung_SSD_850_PRO_256GB_S251NXAGB42213R</name> <path>/sys/devices/pci0000:00/0000:00:1f.2/ata5/host4/target4:0:0/4:0:0:0/block/sdb</path> <parent>scsi_4_0_0_0</parent> <capability type='storage'> <block>/dev/sdb</block> <bus>ata</bus> <drive_type>disk</drive_type> <model>Samsung SSD 850</model> <vendor>ATA</vendor> <serial>Samsung_SSD_850_PRO_256GB_S251NXAGB42213R</serial> <size>256060514304</size> <logical_block_size>512</logical_block_size> <num_blocks>500118192</num_blocks> </capability> </device> <device> <name>scsi_generic_sg1</name> <path>/sys/devices/pci0000:00/0000:00:1f.2/ata5/host4/target4:0:0/4:0:0:0/scsi_generic/sg1</path> <parent>scsi_4_0_0_0</parent> <capability type='scsi_generic'> <char>/dev/sg1</char> </capability> </device> To construct the element, information from device scsi_4_0_0_0 is needed for <address> element (minus the host element). Adapter element is one of the places that I am not sure which information I can rely on, currently 'host' element from scsi_4_0_0_0 is used to form string 'scsi_host{host}'. Is this correct? Reliable? Whole different issue is locating the endpoint (/dev/sg{int}) to set the permissions. From the subtree, it's apparent that it is included in device called scsi_generic_sg1, but there is no *direct* link between scsi_4_0_0_0 and scsi_generic_sg1. At this point, we present user with devices matching capability='scsi', therefore to get the information 2 additional parses of the tree would have to be done. Other way would be reporting 'scsi_generic' capability, where only 2 additional virNodeDeviceLookupByName calls would be required (to descend 2 levels). Is there anything *really* wrong with this approach? Are there any other options without dynamic ownershit? Seclabel doesn't seem to be available. I'm thankful for any hints. Regards, mpolednik

2 1

[libvirt-users] Backup with external snapshots
by Dominique Ramaekers 18 Mar '16

18 Mar '16

Hi everybody, Following this user mailing list over a period of time, I saw a few messages regarding not being able using the external snapshot feature. I refer to this procedure: http://wiki.libvirt.org/page/Live-disk-backup-with-active-blockcommit I would like to mention this hoping it will help those users: Using external snapshots works perfect again in qemu 2.5.0 together with this patch https://bugzilla.redhat.com/show_bug.cgi?id=1300209 Full version list on which I did my testing: Compiled against library: libvirt 1.3.1 Using library: libvirt 1.3.1 Gebruikte API: QEMU 1.3.1 Draaiende hypervisor: QEMU 2.5.0 Greetings, Dominique.

1 0

[libvirt-users] share nothing live migration causes read only filesystem
by Fırat KÜÇÜK 18 Mar '16

18 Mar '16

Hello, I started live migration job for a guest with the following command: virsh migrate --live --domain my-guest --verbose --persistent --copy-storage-all --desturi qemu+ssh://root@my-otherhost/system Guest system disk cache mode is none: <disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='none'/> <source file='/opt/datastore/bulutkare-1118.img'/> <backingStore/> <target dev='vda' bus='virtio'/> <alias name='virtio-disk0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> after live migration completed, filesystem blocked write operations. root@my-guest:~/tmp# touch hello touch: cannot touch ‘hello’: Read-only file system What can be the reason? What is the best of migrating a VM to a target machine? Additional info: Guest operating system is Ubuntu 14.04 x64 Source/Target Host operating system is Ubuntu 15.04 x64 Guest file system is ext4 + swap Source/Target Host file system is XFS Source/Target Qemu version 1.2.2 Source/Target libvirt 1.2.12 This is from target libvirt log. It can be important: /build/qemu-Bjjgxn/qemu-2.2+dfsg/nbd.c:nbd_co_receive_request():L1146: reading from socket failed

2 1

[libvirt-users] disabling disk cache
by Fırat KÜÇÜK 18 Mar '16

18 Mar '16

Hello, is it possible to disable disk (vda) cache without rebooting system? Thanks.

2 1

[libvirt-users] Re：Re: [help] How to modify the vgamem value ?
by hongzhen_luo＠sina.com 16 Mar '16

16 Mar '16

Dear Mr Holger and Mr Pavel Thanks for your help , I am going to try to modify the vgamem value . ^ ^Have a nice day ... Best regards >Hi Pavel, >I have to apologize. After your post I study the page again and I >found your descrption. >Best regards, >Am 14.03.2016 um 10:20 schrieb Pavel Hrdina: > On Mon, Mar 14, 2016 at 09:41:36AM +0100, Holger Schranz wrote: >> Hi Luo, >> >> the vgamem is limited inside. Myself, I use QEMU 2.5/Virgil3D to expand >> the vgamem. > > It's not limited and can be modified inside the xml, the only limitation is that > the value has to be a power of 2 and for QXL the value must be at least 1024. > There is an exception, qemu can and in some cases updates the value internally, > libvirt after the guest is started will get the actual value from qemu and > update live XML. > > Pavel >

1 0

[libvirt-users] Unsupported network type ethernet using LXC
by abhishek jain 16 Mar '16

16 Mar '16

Hi Team I'm trying to launch VM using LXC as a hypervisor with interace="ethernet" configuration and I'm getting below errors.. *virsh -c lxc: start instance-00000321error: Failed to start domain instance-00000321error: internal error: Unsupported network type ethernet* Below is the xml file which I'm using .... cat right.xml <domain type='lxc'> <name>instance-00000321</name> <uuid>13dd822c-a99d-4f28-9f4e-53dfb744efcc</uuid> <memory unit='KiB'>524288</memory> <currentMemory unit='KiB'>524288</currentMemory> <vcpu placement='static'>1</vcpu> <resource> <partition>/machine</partition> </resource> <os> <type arch='aarch64' machine='virt'>exe</type> <init>/bin/sh</init> <cmdline>root=/dev/ram0 rw console=ttyAMA0 rootwait earlyprintk</cmdline> </os> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/lib/libvirt/libvirt_lxc</emulator> <filesystem type='mount' accessmode='passthrough'> <source dir='/'/> <target dir='/'/> </filesystem> <interface type='ethernet'> <mac address='02:74:ff:9d:52:f5'/> <script path=''/> <target dev='tap74ff9d52-f5'/> </interface> <interface type='ethernet'> <mac address='02:9b:a6:1e:67:5b'/> <script path=''/> <target dev='tap9ba61e67-5b'/> </interface> <console type='pty'> <target type='lxc' port='0'/> </console> </devices> <seclabel type='none'/> </domain> However I'm able to launch the same above xml file using KVM as hypervisor on the same host. Please help me regarding this. --Thanks Abhishek Jain

1 1

[libvirt-users] TCP Tunnel Info
by bancfc＠openmailbox.org 14 Mar '16

14 Mar '16

libvirt-users(a)redhat.com TCP Tunnel Info I've been looking at the TCP Tunnel network feature as a potential replacement for the extra private internal networking configuration file. Usecase: This network is supposed to go from VM1 to VM2 without DHCP, DNS or any incoming/outgoing connections to the host or outside world possible. https://libvirt.org/formatdomain.html#elementsNICSTCP * To make sure I understand, adding the TCP Tunnel setting for both VMs 1 and 2 is enough to do what I need? (force them to exclusively communicate without the need for adding a new network as typically done). * If another set of VMs 3 and 4 are running and connected to each other but I want to make sure they cannot connect to VMs 1 and 2, what source addresses should be used to isolate these 2 networks? Do you follow CIDR rules? * For example if the chosen source address is 10.152.152.11 for VMs 1 and 2 what should the other network have? * Going more complicated. Can one VM participate in two separate TCP Tunnel networks while keeping them isolated? Topology: VM1(virtual NIC1) <-> VM2 | VM1(virtual NIC2) <-> VM3 VM2 and 3 can only talk to VM1 but not to each other in this example. * Offtopic: Do your answers similarly apply for using the other Multicast and UDP options too? I can explain better if I'm not making any sense.

2 1

[libvirt-users] [help] How to modify the vgamem value ?
by hongzhen_luo＠sina.com 14 Mar '16

14 Mar '16

Dear everyone Do you know how to modify vgamem value in the .xml file ? such as :<video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1'/> // from instance-0000015e.xml <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/</video> I plan to increase the volume of vgamem , but it seems that always keep the original value ‘16384’. Was it limited by QEMU? or others？ Please tell me how I can I modify it ? it's better that help me to make a example for modifing the vgamem..... Thank you very much Best Regards .

3 3