- Users - libvirt List Archives

[libvirt-users] luks ecrypted storage poll - lvm - possible?
by lejeczek 21 Dec '18

21 Dec '18

hi everyone, do we get to encrypt lvm pools in/with libvirt? I'm on Centos 7.x but see mention of it, not even on the net. Or in other words - can guests(lxc I'm thinking of) run off ecrypted lvm where at least the part when dev gets luksOpened is taken care of by libvirt? many thanks, L.

3 3

[libvirt-users] Shutdown problem from virsh
by Thomas Munfort 20 Dec '18

20 Dec '18

Hi everyone, On a server running Debian 9, I have multiple KVM guests automatically started at boot by libvirtd.service and running in the background. When I shutdown this server, libvirtd.service automatically and gracefully shut them all down first. So, every thing is fine so far. Recently, I've added an additional KVM guest and this one does not respond to a shutdown command from virsh and therefore messes up the shutdown of the whole Debian 9 server. The things is, this additional KVM guest is not a regular Linux guest. It is DiskStation Manager (DSM) 6.2 from Synology (with XPEnology as the boot loader). I know this setup isn't supported by libvirt nor Synology. Nonetheless, I wonder if anyone would have idea on that matter ? Even some suggestions might help me find what needs fixing. Thank you, Best regards, Thomas M.

1 2

[libvirt-users] CfP for VHPC ‘19: HPC Virtualization Paper Registration due January 25, 2019 - 14th Virtualization in High-Performance Cloud Computing Workshop@ISC
by VHPC 19 20 Dec '18

20 Dec '18

Please accept our apologies if you receive multiple copies of this Call for Papers ==================================================================== CALL FOR PAPERS 14th Workshop on Virtualization in High-Performance Cloud Computing (VHPC '19) held in conjunction with the International Supercomputing Conference - High Performance, June 16-20, 2019, Frankfurt, Germany. (Springer LNCS Proceedings) ==================================================================== Date: June 20, 2019 Workshop URL: http://vhpc.org Abstract Submission Deadline: January 25, 2019 Springer LNCS, rolling abstract submission Abstract/Paper Submission Link: https://edas.info/newPaper.php?c=25685 Call for Papers Containers and virtualization technologies constitute key enabling factors 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-containerization 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; lastly, unikernels provide for many virtualization benefits with a minimized OS/library surface. I/O Virtualization in turn 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 the underlying physical topology is furthermore enabling virtualization of HPC infrastructures. Publication Accepted papers will be published in a Springer LNCS proceedings volume. 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, containers-virtualization and the cloud. Major Topics: - HPC on Containers and VMs - Containerized applications with OS-level virtualization - Lightweight applications with Unikernels - HP-as-a-Service each major topic encompassing design/architecture, management, performance management, modeling and configuration/tooling: Design / Architecture: - Containers and OS-level virtualization (LXC, Docker, rkt, Singularity, Shifter, i.a.) - Hypervisor support for heterogeneous resources (GPUs, co-processors, FPGAs, etc.) - Hypervisor extensions to mitigate side-channel attacks ([micro-]architectural timing attacks, privilege escalation) - VM & Container trust and security models - Multi-environment coupling, system software supporting in-situ analysis with HPC simulation - Cloud reliability, fault-tolerance and high-availability - Energy-efficient and power-aware virtualization - Containers inside VMs with hypervisor isolation - Virtualization support for emerging memory technologies - Lightweight/specialized operating systems in conjunction with virtual machines - Hypervisor support for heterogeneous resources (GPUs, co-processors, FPGAs, etc.) - Novel unikernels and use cases for virtualized HPC environments - ARM-based hypervisors, ARM virtualization extensions Management: - Container and VM management for HPC and cloud environments - HPC services integration, services to support HPC - Service and on-demand scheduling & resource management - Dedicated workload management with VMs or containers - Workflow coupling with VMs and containers - Unikernel, lightweight VM application management - Environments and tools for operating containerized environments (batch, orchestration) - Novel models for non-HPC workload provisioning on HPC resources Performance Measurements and Modeling: - Performance improvements for or driven by unikernels - Optimizations of virtual machine monitor platforms and hypervisors - Scalability analysis of VMs and/or containers at large scale - Performance measurement, modeling and monitoring of virtualized/cloud workloads - Virtualization in supercomputing environments, HPC clusters, HPC in the cloud Configuration / Tooling: - Tool support for unikernels: configuration/build environments, debuggers, profilers - Job scheduling/control/policy and container placement in virtualized environments - Operating MPI in containers/VMs and Unikernels - Software defined networks and network virtualization - GPU virtualization operationalization 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 January 25, 2019 - Abstract Registration deadline Apr 19th, 2019 - Paper submission deadline (Springer LNCS) May 3, 2019 - Acceptance notification June 20th, 2019 - Workshop Day July 10th, 2019 - Camera-ready version due Chair Michael Alexander (chair), University of Vienna, Austria Anastassios Nanos (co-chair), SunLight.io, UK Andrew Younge (co-chair), Sandia National Laboratories Program committee Stergios Anastasiadis, University of Ioannina, Greece Jakob Blomer, CERN, Europe Eduardo César, Universidad Autonoma de Barcelona, Spain Stephen Crago, USC ISI, USA Tommaso Cucinotta, St. Anna School of Advanced Studies, Italy Christoffer Dall, Columbia University, USA Patrick Dreher, MIT, USA Kyle Hale, Northwestern University, USA Brian Kocoloski, Washington University, USA John Lange, University of Pittsburgh, USA Giuseppe Lettieri, University of Pisa, Italy Qing Liu, Oak Ridge National Laboratory, USA Nikos Parlavantzas, IRISA, France Kevin Pedretti, Sandia National Laboratories, USA Amer Qouneh, Western New England University, USA Carlos Reaño, Queen’s University Belfast, UK Borja Sotomayor, University of Chicago, USA Joe Stubbs, Texas Advanced Computing Center, USA Anata Tiwari, San Diego Supercomputer Center, USA Kurt Tutschku, Blekinge Institute of Technology, Sweden Yasuhiro Watashiba, Osaka University, Japan Chao-Tung Yang, Tunghai University, Taiwan Na Zhang, VMware, USA 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, keywords, 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. Accepted papers will be published in a Springer LNCS volume. 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.springernature.com/cs-proceeding/llncs/llncs2e.zip Abstract, Paper Submission Link: https://edas.info/newPaper.php?c=25685 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) 2019, June 16-20, Frankfurt, Germany.

1 0

[libvirt-users] win10 network speed issue
by Michael Taboada 20 Dec '18

20 Dec '18

Hi there, I'm running a windows 10 vm on an arch linux host, linux 4.19.9.arch1-1, qemu 3.1.0-1, libvirt (from git) 4.10.0.45.g34eca98522-1, and recently have been having issues with network speeds on the windows vm. It started out getting 300-400 mb down, now it's down to about 10-30. Can anyone think of anything that might have caused this? I tried switching the network type to virtio, but that didn't make much of a difference. Afaik I don't think I've changed anything config-wise in the windows vm. Also the network type is nat. -Michael.

1 0

[libvirt-users] vms doesn't coomunicate via network
by daggs 19 Dec '18

19 Dec '18

Greetings, I have two vms, one is a router and the other one is a client, for some reason, the client vm is unable get ip via dhcp from the router vm. here are outputs: vm1.xml: <interface type='bridge'> <mac address='52:54:00:54:78:be'/> <source bridge='virbr0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> router.xml: <interface type='bridge'> <mac address='52:54:00:f9:bd:fb'/> <source bridge='virbr0'/> <target dev='vnet1'/> <model type='virtio'/> <alias name='net1'/> <address type='pci' domain='0x0000' bus='0x0a' slot='0x00' function='0x0'/> </interface> ifconfig: $ busybox ifconfig -a dummy0 Link encap:Ethernet HWaddr CE:2E:DD:15:8A:0C BROADCAST NOARP MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:21428 errors:0 dropped:0 overruns:0 frame:0 TX packets:21428 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1039176 (1014.8 KiB) TX bytes:1039176 (1014.8 KiB) virbr0 Link encap:Ethernet HWaddr 52:54:00:7E:27:AF inet6 addr: fe80::5054:ff:fe7e:27af/64 Scope:Link inet6 addr: fdab:9802:eb52:0:5054:ff:fe7e:27af/64 Scope:Global UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:530861 errors:0 dropped:0 overruns:0 frame:0 TX packets:85 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:591914339 (564.4 MiB) TX bytes:4042 (3.9 KiB) virbr0-dummy Link encap:Ethernet HWaddr 52:54:00:7E:27:AF UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:141357 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:32288355 (30.7 MiB) vnet0 Link encap:Ethernet HWaddr FE:54:00:8B:66:C1 inet addr:10.0.0.3 Bcast:10.0.0.255 Mask:255.255.255.0 inet6 addr: fdab:9802:eb52:0:fc54:ff:fe8b:66c1/64 Scope:Global inet6 addr: fe80::fc54:ff:fe8b:66c1/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:261801 errors:0 dropped:0 overruns:0 frame:0 TX packets:438289 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:42370344 (40.4 MiB) TX bytes:895415306 (853.9 MiB) vnet1 Link encap:Ethernet HWaddr FE:54:00:F9:BD:FB inet6 addr: fe80::fc54:ff:fef9:bdfb/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:531064 errors:0 dropped:0 overruns:0 frame:0 TX packets:262 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:599366518 (571.5 MiB) TX bytes:27088 (26.4 KiB) /etc/network/interface: $ cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback # The primary network interface #allow-hotplug enx503eaa4f9dcd #iface enx503eaa4f9dcd inet dhcp #allow-hotplug enp0s31f6 #iface enp0s31f6 inet dhcp allow-hotplug vnet0 iface vnet0 inet dhcp auto virbr0-dummy iface virbr0-dummy inet manual pre-up /sbin/ip link add virbr0-dummy type dummy up /sbin/ip link set virbr0-dummy address 52:54:00:7e:27:af auto virbr0 iface virbr0 inet manual hwaddress ether 19:7c:3b:92:ec:ee bridge_ports virbr0-dummy any ideas what cen be the issue? Thanks, Dagg.

2 2

[libvirt-users] "virsh list --all" is intermittently causing a shutdown client to boot?
by Peter Kukla 14 Dec '18

14 Dec '18

Hello, I have a CentOS 7 client running on a CentOS 7 server. "virsh --version" reports that 3.9.0 is being used. I'm issuing a "virsh shutdown" command to shutdown the client. I then confirm that the client has actually shutdown using "virsh list --all". Lately I've been seeing instances where I shutdown the client, turn away to work on something else, and then turn back to find that the client has booted again. Initially I thought I was mistaken, and that I somehow hadn't properly shutdown the client, but further experimentation shows that's definitely not the case. I've been able to reproduce this repeatedly using the following steps. 1. Run "virsh shutdown CLIENT"2. Wait ~30-60 seconds3. Run "virsh list --all; virsh console CLIENT" If I run "virsh console CLIENT" on its own when the client is in a shutdown state, I get the expected "error: The domain is not running" message. If I omit step #2 and run step #3 immediately after shutting down the client, virsh also complains that the client's not started and refuses to open a console. However, if I add a pause -- step 2, above -- between the shutdown and the "list --all" commands, then "list --all" shows that the client is running, and a console is opened to the VM. I have confirmed that the client boot is definitely being started by the "list --all" command (and not being started by something else while I'm not looking) by combining the "list --all" and "console" commands in step 3. This is ensuring that the console is started as soon as the "list --all" is complete, and the resulting screen output shows the BIOS boot options quickly followed by the kernel boot messages being dumped to the console. I can watch the entire boot process from start to finish. That pause between the shutdown and the "list --all" is critical. I've shutdown the client and then immediately followed it up with the command: watch virsh list --all ...which will run the "list --all" command every 2 seconds. This will run indefinitely without triggering the boot, which eliminates the possibility of the boot occurring due to the amount of time since the shutdown. It may be that other virsh commands are also causing the client to boot, but thus far I've only reproduced it using the list --all command. Can anyone tell me why this is happening? A bug? Something in my config? Something else? Thanks in advance, -peter .

4 6

[libvirt-users] Libvirt api for esx
by ROHIT SINGH 13 Dec '18

13 Dec '18

Hi, I am doing poc for using libvirt api for implementation of esx in python. I tried researching through module but did not find a way how it works for esx. Any help on how to proceed specifically for esx would be of great help. Please let me know as soon as possible, lagging on deliverables. Thanks for help!! Regards Rohit Singh

2 11

[libvirt-users] Usable and non-usable CPU models in nested virtualization
by Milan Zamazal 12 Dec '18

12 Dec '18

Hi, some custom CPU models are reported from virConnectGetDomainCapabilities as usable='yes' on a physical machine while as usable='no' inside a VM running on the same machine. That's not completely surprising. But what surprises me is that those models are still reported from virConnectCompareCPU as supported (VIR_CPU_COMPARE_SUPERSET) in the nested environment and VMs can be started happily with them. For instance, virConnectGetDomainCapabilities reports <model usable='no'>Skylake-Client</model> but when I try to use that model anyway, the VM starts fine with it: <cpu mode='custom' match='exact' check='full'> <model fallback='forbid'>Skylake-Client</model> <topology sockets='16' cores='1' threads='1'/> <feature policy='require' name='hypervisor'/> <feature policy='disable' name='invpcid'/> <numa> <cell id='0' cpus='0' memory='524288' unit='KiB'/> </numa> </cpu> That's actually good news, but unexpected. Do I miss something? Thanks, Milan

2 4

Re: [libvirt-users] Power on and power off code using LIBVIRT
by Daniel P. Berrangé 11 Dec '18

11 Dec '18

Re-adding libvirt-users - please don't remove mailing list addresses when replying. On Mon, Dec 10, 2018 at 09:42:29PM +0530, Chaithra Sn wrote: > Thanks Daniel for the reply. > > I want code in python langange. The 'create' method on the Domain object will start an existing defined guest. The 'destroy' method will stop a running guest. > On Mon, 10 Dec 2018 at 7:10 PM, Daniel P. Berrangé <berrange(a)redhat.com> > wrote: > > > On Mon, Dec 10, 2018 at 02:55:12PM +0530, Chaithra Sn wrote: > > > Dear Team, > > > > > > Please provide the code for power on and power off the VM using Libvirt. > > > > Thre's many ways to access / interact with libvirt, so you'll need to > > specify what language or tool you're trying to use libvirt with. > > > > Regards, > > Daniel > > -- > > |: https://berrange.com -o- > > https://www.flickr.com/photos/dberrange :| > > |: https://libvirt.org -o- > > https://fstop138.berrange.com :| > > |: https://entangle-photo.org -o- > > https://www.instagram.com/dberrange :| > > Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|

2 1

[libvirt-users] unable to add pci network to existing vm
by daggs 11 Dec '18

11 Dec '18

Greetings, I'm trying to add a virtual nic to an existing and active vm and I'm getting this error: error: internal error: No more available PCI slots the cmd I'm trying to run is: virsh -c qemu:///system attach-interface --domain router --type bridge --source virbr0 --model virtio --config --live the lspci output within the vm is this: # lspci 00:00.0 Host bridge: Intel Corporation 82G33/G31/P35/P31 Express DRAM Controller 00:01.0 PCI bridge: Intel Corporation 7500/5520/5500/X58 I/O Hub PCI Express Root Port 0 (rev 02) 00:01.1 PCI bridge: Intel Corporation 7500/5520/5500/X58 I/O Hub PCI Express Root Port 0 (rev 02) 00:01.2 PCI bridge: Intel Corporation 7500/5520/5500/X58 I/O Hub PCI Express Root Port 0 (rev 02) 00:01.3 PCI bridge: Intel Corporation 7500/5520/5500/X58 I/O Hub PCI Express Root Port 0 (rev 02) 00:01.4 PCI bridge: Intel Corporation 7500/5520/5500/X58 I/O Hub PCI Express Root Port 0 (rev 02) 00:01.5 PCI bridge: Intel Corporation 7500/5520/5500/X58 I/O Hub PCI Express Root Port 0 (rev 02) 00:01.6 PCI bridge: Intel Corporation 7500/5520/5500/X58 I/O Hub PCI Express Root Port 0 (rev 02) 00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03) 00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03) 00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03) 00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 92) 00:1f.0 ISA bridge: Intel Corporation 82801IB (ICH9) LPC Interface Controller (rev 02) 00:1f.2 SATA controller: Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA Controller [AHCI mode] (rev 02) 00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 02) 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-V (rev 31) 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06) 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06) 03:00.0 SCSI storage controller: Red Hat, Inc. Virtio block device (rev 01) 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06) 05:00.0 Unclassified device [00ff]: Red Hat, Inc. Virtio memory balloon (rev 01) 06:00.0 Ethernet controller: Red Hat, Inc. Virtio network device (rev 01) 07:00.0 Unclassified device [0002]: Red Hat, Inc. Virtio filesystem (rev 01) 08:00.0 PCI bridge: Red Hat, Inc. QEMU PCI-PCI bridge how can I add additional pci entry? I don't mind if I need to edit the xml file and restart the vm, I just don't want to cause the vm not to start due to bad xml or something. Thanks, Dagg.

2 2