- Users - libvirt List Archives

[libvirt-users] what is the practical limit on snapshot generations?
by W Kern 16 Feb '18

16 Feb '18

I've googled around on this and haven't found much so I'll ask here. I have a client who routinely does live snapshots on snapshot on snapshot ( just keep going recursively) I've told him to roll them up once in a while, but he feels its unnecessary and only plans a rollup during a major maintenance period, where he can take the whole site down and then watch it grind during the commit. Note these are Qcow2 (1.1) images and they are external snaps. Most of the write activity is logging and medium database writes for an ecommerce store. It is certainly NOT heavy write i/o. Isn't there a cost (speed, resources) etc to all those generations. Any safety issues? Is there an optimium # of generations where if you exceed that you get diminishing returns. At one point are you shooting yourself in the foot, or is this really no big deal aside from two hours of downtime while the 'actual' commit occurs. -wk

1 0

[libvirt-users] Ask question
by 李杰 15 Feb '18

15 Feb '18

Dear Recently,I am interested in libvirt,but I found the libvirt does't support revert and delete the external snapshot which the raw disk based guest.My libvirt and qemu release are both 3.2.0.So I have a question,the community how to solve it,if have any plans about it.Can you tell me more about it?Thank you very much. Best Regards Rambo

3 4

[libvirt-users] kvm/libvirt on CentOS7 w/Windows 10 Pro guest
by Benjammin2068 14 Feb '18

14 Feb '18

Hey all, New to list, so I apologize if this has been asked a bunch already... Is there something I'm missing with Windows 10 as a guest that keeps Windows Updates from nuking the boot process? I just did an orderly shutdown and windows updated itself <I forgot to disable in time> only to reboot to the diagnostics screen which couldn't repair. going to command prompt and doing the usual "bootrec /fixmbr, /fixboot and /RebuildBcd" didn't help. This has happened a few times. I can't believe how fragile Win10pro is while running in a VM. (and it's happened on a couple machines I've been experimenting with -- both running same OS, but different hardware.) I just saw the FAQ about the libvirt repo for the virtio drivers for windows.... I need to go read more on it... but in the meantime, is there any other smoking gun I'm not aware of? (after lots of google searching) Thanks, -Ben

4 10

[libvirt-users] Nested KVM: L0 guest produces kernel BUG on wakeup from managed save (while a nested VM is running)
by Florian Haas 12 Feb '18

12 Feb '18

Hi everyone, I hope this is the correct list to discuss this issue; please feel free to redirect me otherwise. I have a nested virtualization setup that looks as follows: - Host: Ubuntu 16.04, kernel 4.4.0 (an OpenStack Nova compute node) - L0 guest: openSUSE Leap 42.3, kernel 4.4.104-39-default - Nested guest: SLES 12, kernel 3.12.28-4-default The nested guest is configured with "<type arch='x86_64' machine='pc-i440fx-1.4'>hvm</type>". This is working just beautifully, except when the L0 guest wakes up from managed save (openstack server resume in OpenStack parlance). Then, in the L0 guest we immediately see this: [Tue Feb 6 07:00:37 2018] ------------[ cut here ]------------ [Tue Feb 6 07:00:37 2018] kernel BUG at ../arch/x86/kvm/x86.c:328! [Tue Feb 6 07:00:37 2018] invalid opcode: 0000 [#1] SMP [Tue Feb 6 07:00:37 2018] Modules linked in: fuse vhost_net vhost macvtap macvlan xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp tun br_netfilter bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables vboxpci(O) vboxnetadp(O) vboxnetflt(O) af_packet iscsi_ibft iscsi_boot_sysfs vboxdrv(O) kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel hid_generic usbhid jitterentropy_rng drbg ansi_cprng ppdev parport_pc floppy parport joydev aesni_intel processor button aes_x86_64 virtio_balloon virtio_net lrw gf128mul glue_helper pcspkr serio_raw ablk_helper cryptd i2c_piix4 ext4 crc16 jbd2 mbcache ata_generic [Tue Feb 6 07:00:37 2018] virtio_blk ata_piix ahci libahci cirrus(O) drm_kms_helper(O) syscopyarea sysfillrect sysimgblt fb_sys_fops ttm(O) drm(O) virtio_pci virtio_ring virtio uhci_hcd ehci_hcd usbcore usb_common libata sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua scsi_mod autofs4 [Tue Feb 6 07:00:37 2018] CPU: 2 PID: 2041 Comm: CPU 0/KVM Tainted: G W O 4.4.104-39-default #1 [Tue Feb 6 07:00:37 2018] Hardware name: OpenStack Foundation OpenStack Nova, BIOS 1.10.1-1ubuntu1~cloud0 04/01/2014 [Tue Feb 6 07:00:37 2018] task: ffff880037108d80 ti: ffff88042e964000 task.ti: ffff88042e964000 [Tue Feb 6 07:00:37 2018] RIP: 0010:[<ffffffffa04f20e5>] [<ffffffffa04f20e5>] kvm_spurious_fault+0x5/0x10 [kvm] [Tue Feb 6 07:00:37 2018] RSP: 0018:ffff88042e967d70 EFLAGS: 00010246 [Tue Feb 6 07:00:37 2018] RAX: 0000000000000000 RBX: ffff88042c4f0040 RCX: 0000000000000000 [Tue Feb 6 07:00:37 2018] RDX: 0000000000006820 RSI: 0000000000000282 RDI: ffff88042c4f0040 [Tue Feb 6 07:00:37 2018] RBP: ffff88042c4f00d8 R08: ffff88042e964000 R09: 0000000000000002 [Tue Feb 6 07:00:37 2018] R10: 0000000000000004 R11: 0000000000000000 R12: 0000000000000001 [Tue Feb 6 07:00:37 2018] R13: 0000021d34fbb21d R14: 0000000000000001 R15: 000055d2157cf840 [Tue Feb 6 07:00:37 2018] FS: 00007f7c52b96700(0000) GS:ffff88043fd00000(0000) knlGS:0000000000000000 [Tue Feb 6 07:00:37 2018] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [Tue Feb 6 07:00:37 2018] CR2: 00007f823b15f000 CR3: 0000000429334000 CR4: 0000000000362670 [Tue Feb 6 07:00:37 2018] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [Tue Feb 6 07:00:37 2018] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [Tue Feb 6 07:00:37 2018] Stack: [Tue Feb 6 07:00:37 2018] ffffffffa07939b1 ffffffffa0787875 ffffffffa0503a60 ffff88042c4f0040 [Tue Feb 6 07:00:37 2018] ffffffffa04e5ede ffff88042c4f0040 ffffffffa04e6f0f ffff880037108d80 [Tue Feb 6 07:00:37 2018] ffff88042c4f00e0 ffff88042c4f00e0 ffff88042c4f0040 ffff88042e968000 [Tue Feb 6 07:00:37 2018] Call Trace: [Tue Feb 6 07:00:37 2018] [<ffffffffa07939b1>] intel_pmu_set_msr+0xfc1/0x2341 [kvm_intel] [Tue Feb 6 07:00:37 2018] DWARF2 unwinder stuck at intel_pmu_set_msr+0xfc1/0x2341 [kvm_intel] [Tue Feb 6 07:00:37 2018] Leftover inexact backtrace: [Tue Feb 6 07:00:37 2018] [<ffffffffa0787875>] ? vmx_interrupt_allowed+0x15/0x30 [kvm_intel] [Tue Feb 6 07:00:37 2018] [<ffffffffa0503a60>] ? kvm_arch_vcpu_runnable+0xa0/0xd0 [kvm] [Tue Feb 6 07:00:37 2018] [<ffffffffa04e5ede>] ? kvm_vcpu_check_block+0xe/0x60 [kvm] [Tue Feb 6 07:00:37 2018] [<ffffffffa04e6f0f>] ? kvm_vcpu_block+0x8f/0x310 [kvm] [Tue Feb 6 07:00:37 2018] [<ffffffffa0503c17>] ? kvm_arch_vcpu_ioctl_run+0x187/0x400 [kvm] [Tue Feb 6 07:00:37 2018] [<ffffffffa04ea6d9>] ? kvm_vcpu_ioctl+0x359/0x680 [kvm] [Tue Feb 6 07:00:37 2018] [<ffffffff81016689>] ? __switch_to+0x1c9/0x460 [Tue Feb 6 07:00:37 2018] [<ffffffff81224f02>] ? do_vfs_ioctl+0x322/0x5d0 [Tue Feb 6 07:00:37 2018] [<ffffffff811362ef>] ? __audit_syscall_entry+0xaf/0x100 [Tue Feb 6 07:00:37 2018] [<ffffffff8100383b>] ? syscall_trace_enter_phase1+0x15b/0x170 [Tue Feb 6 07:00:37 2018] [<ffffffff81225224>] ? SyS_ioctl+0x74/0x80 [Tue Feb 6 07:00:37 2018] [<ffffffff81634a02>] ? entry_SYSCALL_64_fastpath+0x16/0xae [Tue Feb 6 07:00:37 2018] Code: d7 fe ff ff 8b 2d 04 6e 06 00 e9 c2 fe ff ff 48 89 f2 e9 65 ff ff ff 0f 1f 44 00 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 <0f> 0b 66 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 89 ff 48 89 [Tue Feb 6 07:00:37 2018] RIP [<ffffffffa04f20e5>] kvm_spurious_fault+0x5/0x10 [kvm] [Tue Feb 6 07:00:37 2018] RSP <ffff88042e967d70> [Tue Feb 6 07:00:37 2018] ---[ end trace e15c567f77920049 ]--- We only hit this kernel bug if we have a nested VM running. The exact same setup, sent into managed save after shutting down the nested VM, wakes up just fine. Now I am aware of https://bugzilla.redhat.com/show_bug.cgi?id=1076294, which talks about live migration — but I think the same considerations apply. I am also aware of https://fedoraproject.org/wiki/How_to_enable_nested_virtualization_in_KVM, which strongly suggests to use host-passthrough or host-model. I have tried both, to no avail. The stack trace persists. I have also tried running a 4.15 kernel in the L0 guest, from https://kernel.opensuse.org/packages/stable, but again, the stack trace persists. What does fix things, of course, is to switch from the nested guest from KVM to Qemu — but that also makes things significantly slower. So I'm wondering: is there someone reading this who does run nested KVM and has managed to successfully live-migrate or managed-save? If so, would you be able to share a working host kernel / L0 guest kernel / nested guest kernel combination, or any other hints for tuning the L0 guest to support managed save and live migration? I'd be extraordinarily grateful for any suggestions. Thanks! Cheers, Florian

4 21

[libvirt-users] Method for connecting to CDROM/DVD
by CJ Mills 11 Feb '18

11 Feb '18

Hi everyone, I have a question on connecting to hardware devices. With virt- manager I am attempting to use a hardware cdrom/dvd drive from an Ubuntu 16.04 VM however, i keep getting "'host_cdrom' is not whitelisted" errors when starting the VM. After some searching I checked my processor and realized it does not support VT-d. Is this 1) a requirement for sharing the device with the VM, and 2) the only way of sharing the device?

1 0

[libvirt-users] Virtualization Management Platforms
by TomK 09 Feb '18

09 Feb '18

Hey All, Curious about the best, easy to use virtualization management platform for small labs of 30-40 physical servers. Looking for something that's relatively simple to operate, install and lightweight but with enough maturity to provide monitoring as well as holistic views of the entire physical space etc. Hearing of oVirt, Xen and Eucalyptus to name a few but wondering what other options do I have for a small physical space? -- Cheers, Tom K.

3 2

[libvirt-users] libvirt and NAT on a system that already has a DHCP server
by john＠bluemarble.net 08 Feb '18

08 Feb '18

I'm trying to use virt-manager and qemu/kvm on Arch Linux. The box I'm using is also the router for my house. It runs a kea DHCP server. When I try to start the default NAT network, it can't start dnsmasq because that port is already bound. Is there a way to have it not bind on this interface? I see there is an except-on statement in the dnsmasq.conf, but I can't add lines to that directly, and I didn't see any way to add special options using virsh net-edit default. Thanks.

4 6

[libvirt-users] Libvirt for virtual devices like virtual printers
by Deepti S 08 Feb '18

08 Feb '18

Hi, I have a couple of questions. - I am a new libvirt code user. I have just cloned the repo and I am looking for a suitable debugger/IDE which will help me debug the code. - I work in developing and creating virtual printers with display, with QEMU as the hypervisor (no KVM-only Qemu). Currently we have our own application to manage the virtual printers. Our plan is to migrate to libvirt, and enable our application to use the libvirt APIs. libvirt code currently looks to be specialized in pure OS-specific guests (like PCs), and I hit snags where there are manadatory devices added which a virtual printer does not need. Are there any users who are looking into customized virtual devices? I would like to knowledge share with them. The intention is to provide new libvirt APIs whenever there is such a snag and thus enable libvirt to be used for managing virtual printers. - One issue that we are seeing is with regard to USB Host Controller: We have a customized model of ehci USB Host Controller (named nr52_ehci_usb) in qemu (locally built). When I add the custom value (n552_ehci_usb) of the host controller as the "model" type in my dom xml, virsh define <xml> fails with invalid model type error. I remove the usb controller entry from the xml, and add "-usb" as a "qemucommandline" parameter, but then libvirt adds the device lsi (-device lsi,id=scsi0 -usb), and the virsh create command fails with: "-device lsi,id=scsi0 No PCI bus found for lsi53c895a". The board we have created in QEMU does not have PCI bus implemented. Is there any way I can get my usb host controller to be recognized by libvirt? Is there a way I can prevent lsi device from getting added when I make -usb a qemu command line parameter? Regards, Deepti

2 1

[libvirt-users] failed to update cdrom device with rbd disk
by chao.zhou＠zstack.io 06 Feb '18

06 Feb '18

Hello, I'm trying to using virsh update-device to update the CDROM from type='file' to ceph rbd iso with type='network'. But I always get error: Failed to update device from disk error: internal error: unable to execute QEMU command 'change': error connecting: Operation not supported I'm using libvirt-libs-3.10.0-1.el7.x86_64 with centos7.4 my original cdrom xml: <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <target dev='hdc' bus='ide' tray='open'/> <readonly/> <alias name='ide0-1-0'/> <address type='drive' controller='0' bus='1' target='0' unit='0'/> </disk> my rbd cdrom xml: <disk device="cdrom" type="network"> <driver name='qemu' type='raw'/> <auth username="zstack"> <secret type="ceph" uuid="efd3eb93-014f-4a0f-ba1f-84d7e70c9a89"/> </auth> <source name="ssd/4922ebebd7b52f11bf13b3a482b6ab7e@4922ebebd7b52f11bf13b3a482b6ab7e" protocol="rbd"> <host name="192.168.250.35" port="6789"/> </source> <target bus="ide" dev="hdc"/> <readonly/> </disk> >From the libvirtd.log, I got Send command '{"execute":"change","arguments":{"device":"drive-ide0-1-0","target":"rbd:ss d/4922ebebd7b52f11bf13b3a482b6ab7e@4922ebebd7b52f11bf13b3a482b6ab7e:auth_sup ported=none:mon_host=192.168.250.35\\:6789","arg":"raw"},"id":"libvirt-286"} ' which seems it pass the auth_support=none to the qemu, while I'm using an authentication ceph, it should use auth_support=cephx instead. I also tried to boot the VM with rbd iso and then update-device to another rbd iso, but got no luck with the same error. I have succeeded to update-device with libvirt-1.3.3, I noticed that it depends on the orig_disk->privData->secinfo, and in my environment it will be null which leads to the auth_support=none. So I'm wondering if this is a bug or I did something wrong with my configuration. Thanks in advance, Best Regards, Chao

2 1

[libvirt-users] CfP 13th Virtualization in High-Performance Cloud Computing Workshop (VHPC '18)
by VHPC 18 01 Feb '18

01 Feb '18

*====================================================================CALL FOR PAPERS 13th Workshop on Virtualization in High-Performance Cloud Computing (VHPC '18)held in conjunction with the International Supercomputing Conference - High Performance,June 24-28, 2018, Frankfurt, Germany.(Springer LNCS Proceedings) ====================================================================Date: June 28, 2018Workshop URL: http://vhpc.org <http://vhpc.org>Paper Submission Deadline: April 23, 2018, Springer LNCS, rolling abstract submissionAbstract/Paper Submission Link: https://edas.info/newPaper.php?c=24355 <https://edas.info/newPaper.php?c=24355>Special Track: GPU - Accelerator Virtualization Call for PapersVirtualization technologies constitute a key enabling factor for flexible resource managementin modern data centers, and particularly in cloud environments. Cloud providers need tomanage complex infrastructures in a seamless fashion to support the highly dynamic andheterogeneous workloads and hosted applications customers deploy. Similarly, HPCenvironments have been increasingly adopting techniques that enable flexible managementof vast computing and networking resources, close to marginal provisioning cost, which isunprecedented in the history of scientific and commercial computing.Various virtualization technologies contribute to the overall picture in different ways: machinevirtualization, with its capability to enable consolidation of multiple underutilized servers withheterogeneous software and operating systems (OSes), and its capability to live-migrate afully operating virtual machine (VM) with a very short downtime, enables novel and dynamicways to manage physical servers; OS-level virtualization (i.e., containerization), with itscapability to isolate multiple user-space environments and to allow for their coexistencewithin 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 network interfaces to take traffic from multiple VMs or containers; network virtualization, with its capability to create logical network overlays that are independent of theunderlying physical topology is furthermore enabling virtualization of HPC infrastructures. PublicationAccepted papers will be published in a Springer LNCS proceedings volume.Topics of InterestThe VHPC program committee solicits original, high-quality submissions related tovirtualization across the entire software stack with a special focus on the intersection of HPCand the cloud.Major Topics- Virtualization in supercomputing environments, HPC clusters, HPC in the cloud and grids- OS-level virtualization and containers (LXC, Docker, rkt, Singularity, Shifter, i.a.)- Lightweight/specialized operating systems in conjunction with virtual machines- Novel unikernels and use cases for virtualized HPC environments- Performance improvements for or driven by unikernels- Tool support for unikernels: configuration/build environments, debuggers, profilers- Hypervisor extensions to mitigate side-channel attacks ([micro-]architectural timing attacks, privilege escalation)- VM & Container trust and security- Containers inside VMs with hypervisor isolation- GPU virtualization operationalization- Approaches to GPGPU virtualization including API remoting and hypervisor abstraction- Optimizations of virtual machine monitor platforms and hypervisors- Hypervisor support for heterogeneous resources (GPUs, co-processors, FPGAs, etc.)- Virtualization support for emerging memory technologies- Virtualization in enterprise HPC and microvisors- Software defined networks and network virtualization- Management, deployment of virtualized environments and orchestration (Kubernetes i.a.)- Workflow-pipeline container-based composability - Checkpointing facilitation utilizing containers and VMs - Emerging topics including multi-kernel approaches and NUMA in hypervisors- Operating MPI in containers/VMs and Unikernels - Virtualization in data intensive computing (big data) - HPC convergence- Adaptation of HPC technologies in the cloud (high performance networks, RDMA, etc.)- Performance measurement, modelling and monitoring of virtualized/cloud workloads- Latency-and jitter sensitive workloads in virtualized/containerized environments- I/O virtualization (including applications, SR-IOV, i.a.) - Hybrid local facility + cloud compute and based storage systems, cloudbursting- FPGA and many-core accelerator virtualization- Job scheduling/control/policy and container placement in virtualized environments- Cloud reliability, fault-tolerance and high-availability- QoS and SLA in virtualized environments- IaaS platforms, cloud frameworks and APIs- Energy-efficient and power-aware virtualization- Configuration management tools for containers (including in OpenStack, Ansible, i.a.)- ARM-based hypervisors, ARM virtualization extensionsSpecial Track: GPU - Accelerator VirtualizationGPU virtualization technologies, performance and benchmarking, integration withworkflow scheduling systems, integration to cluster managers.GPUs are taking on many HPC workload areas, especially in deep learning withinmachine learning. In addition, a lot of workload is being pushed to elastic environments utilizing various virtualization technologies on different levels like hypervisors (e.g. VMWare, Xen, KVM), kernel (Docker, Kubernetes) or on the resource managerlevel (YARN, Mesos). In this track we invite submissions addressing these problems. Suggested Themes and Topics:Technology - What technologies and best practices exist for GPU - hardware accelerator virtualization and usage of hardware accelerators in virtual environments on the hypervisor, kernel or resource manager levelDevelopers - Real-life experience when addressing HPC/ML/DL problems with GPUs or hardware accelerators in virtual environmentsPerformance - Performance comparisons between different technologies / solutionsThe Workshop on Virtualization in High-Performance Cloud Computing (VHPC) aims tobring together researchers and industrial practitioners facing the challenges posed by virtualization in order to foster discussion, collaboration, mutual exchangeof knowledge and experience, enabling research to ultimately provide novelsolutions for virtualized computing systems of tomorrow.The workshop will be one day in length, composed of 20 min paper presentations, eachfollowed by 10 min discussion sections, plus lightning talks that are limited to 5 minutes.Presentations may be accompanied by interactive demonstrations.Important DatesFebruary 23, 2018 (AoE) - Abstract SubmissionApril 23, 2018 (AoE) - Paper submission deadline (Springer LNCS)May 30, 2018 - Acceptance notification June 28, 2018 - Workshop DayJuly 12, 2018 - Camera-ready version dueChairMichael Alexander (chair), Institute of Science and Technology, AustriaAnastassios Nanos (co-chair), OnApp, UKRomeo Kienzler (co-chair), IBM, SwitzerlandProgram committeeStergios Anastasiadis, University of Ioannina, Greece Jakob Blomer, CERN, Europe Eduardo César, Universidad Autonoma de Barcelona, SpainStephen Crago, USC ISI, USATommaso Cucinotta, St. Anna School of Advanced Studies, ItalyChristoffer Dall, Columbia University, USAFrançois Diakhaté, CEA, FrancePatrick Dreher, MIT, USA Kyle Hale, Northwestern University, USA Brian Kocoloski, University of Pittsburgh, USAUday Kurkure, VMware, USAJohn Lange, University of Pittsburgh, USAGiuseppe Lettieri, University of Pisa, ItalyQing Liu, Oak Ridge National Laboratory, USANikos Parlavantzas, IRISA, FranceKevin Pedretti, Sandia National Laboratories, USAAmer Qouneh, Western New England University, USA Carlos Reaño, Technical University of Valencia, SpainBorja Sotomayor, University of Chicago, USA Anata Tiwari, San Diego Supercomputer Center, USAKurt Tutschku, Blekinge Institute of Technology, Sweden Yasuhiro Watashiba, Osaka University, JapanChao-Tung Yang, Tunghai University, Taiwan Andrew Younge, Sandia National Laboratory, USANa Zhang, VMware, USAPaper Submission-PublicationPapers submitted to the workshop will be reviewed by at least twomembers of the program committee and external reviewers. Submissionsshould include abstract, keywords, the e-mail address of thecorresponding author, and must not exceed 10 pages, including tablesand figures at a main font size no smaller than 11 point. Submissionof a paper should be regarded as a commitment that, should the paperbe accepted, at least one of the authors will register and attend theconference to present the work. Accepted papers will be published in aSpringer LNCS volume. . The format must be according to the Springer LNCS Style. Initialsubmissions are in PDF; authors of accepted papers will be requestedto provide source files.Format Guidelines:ftp://ftp.springer.de/pub/tex/latex/llncs/latex2e/llncs2e.zip <ftp://ftp.springer.de/pub/tex/latex/llncs/latex2e/llncs2e.zip>Abstract, Paper Submission Link:https://edas.info/newPaper.php?c=24355 <https://edas.info/newPaper.php?c=24355>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 InformationThe workshop is one day in length and will be held in conjunction with the InternationalSupercomputing Conference - High Performance (ISC) 2018, June 18-22, Frankfurt, Germany.*

1 0