- Users - libvirt List Archives

[libvirt-users] VHPC at ISC extension - Papers due May 2
by VHPC 17 18 Apr '17

18 Apr '17

==================================================================== CALL FOR PAPERS 12th Workshop on Virtualization in High-Performance Cloud Computing (VHPC '17) held in conjunction with the International Supercomputing Conference - High Performance, June 18-22, 2017, Frankfurt, Germany. (Springer LNCS Proceedings) ==================================================================== Date: June 22, 2017 Workshop URL: http://vhpc.org Paper Submission Deadline: May 2, 2017 (extended), Springer LNCS, rolling abstract submission Abstract/Paper Submission Link: https://edas.info/newPaper.php?c=23179 Keynotes: Satoshi Matsuoka, Professor of Computer Science, Tokyo Institute of Technology and John Goodacre, Professor in Computer Architectures University of Manchester, Director of Technology and Systems ARM Ltd. Research Group and Chief Scientific Officer Kaleao Ltd. 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. 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 and the cloud. Major Topics - Virtualization in supercomputing environments, HPC clusters, HPC in the cloud and grids - OS-level virtualization and containers (Docker, rkt, Singularity, Shifter, i.a.) - Lightweight/specialized operating systems, unikernels - Optimizations of virtual machine monitor platforms and hypervisors - Hypervisor support for heterogenous 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 - Performance measurement, modelling and monitoring of virtualized/cloud workloads - Virtualization in data intensive computing and Big Data processing - HPC convergence - Adaptation of HPC technologies in the cloud (high performance networks, RDMA, etc.) - ARM-based hypervisors, ARM virtualization extensions - I/O virtualization and cloud based storage systems - GPU, 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 - Large-scale virtualization in domains such as finance and government - Energy-efficient and power-aware virtualization - Container security - Configuration management tools for containers (including CFEngine, Puppet, i.a.) - Emerging topics including multi-kernel approaches and,NUMA in hypervisors 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 Rolling Abstract Submission May 2, 2017 - Paper submission deadline (extended) May 30, 2017 - Acceptance notification June 22, 2017 - Workshop Day July 18, 2017 - Camera-ready version due Chair Michael Alexander (chair), scaledinfra technologies, 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 Jakob Blomer, CERN, Europe Ron Brightwell, Sandia National Laboratories, USA Eduardo César, Universidad Autonoma de Barcelona, Spain Julian Chesterfield, OnApp, UK Stephen Crago, USC ISI, USA Christoffer Dall, Columbia University, USA Patrick Dreher, MIT, USA Robert Futrick, Cycle Computing, USA Maria Girone, CERN, Europe Kyle Hale, Northwestern University, USA Romeo Kinzler, IBM, Switzerland Brian Kocoloski, University of Pittsburgh, USA Nectarios Koziris, National Technical University of Athens, Greece John Lange, University of Pittsburgh, USA Che-Rung Lee, National Tsing Hua University, Taiwan 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, University of Florida, USA Carlos Reaño, Technical University of Valencia, Spain Thomas Ryd, CFEngine, Norway Na Zhang, VMWare, USA Borja Sotomayor, University of Chicago, USA Craig Stewart, Indiana University, USA Anata Tiwari, San Diego Supercomputer Center, USA Kurt Tutschku, Blekinge Institute of Technology, Sweden Yasuhiro Watashiba, Osaka University, Japan Nicholas Wright, Lawrence Berkeley National Laboratory, USA Chao-Tung Yang, Tunghai University, Taiwan 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. 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.springer.de/pub/tex/latex/llncs/latex2e/llncs2e.zip Abstract, Paper Submission Link: https://edas.info/newPaper.php?c=23179 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) 2017, June 18-22, Frankfurt, Germany.

1 0

[libvirt-users] Libvirt and libssh2 with openauth
by spiperac 16 Apr '17

16 Apr '17

Hi all, i have same question as this one https://www.redhat.com/archives/libvirt-users/2014-March/msg00158.html. ( Only im using python) Is there any new follow-up on this? Thanks

2 1

[libvirt-users] Windows Guest Server 2016, bad performance of whole virtualisation system
by Marko Weber | 8000 13 Apr '17

13 Apr '17

hello , i did a kvm guest with virt-manager and installed windows server 2016. performance settings for the disk: hypervisor default for cache & io mode i added a 2nd disk to the guest , also with hypervisor default settings on cache & io mode Under disk settings in windows server 2016 i set "format whole disk NTFS" i did not choose the "quick format" option. when windows is formatting this 1TB drive the performance on the virtualisation host goes down loging via ssh take ages, top take 2 mins to start up. the physical disks are connected to a raid controller LSI and FS on virtualisation server where the qcow2 files are is XFS. DO i have to set another options for "performance options" as "hypervisor default" to keep the system performant on formatting the disk? thanks for any hints. marko -- zbfmail - Mittendrin statt nur Datei!

1 0

[libvirt-users] Windows Guest Server 2016, bad performance of whole virtualisation system
by Marko Weber | 8000 12 Apr '17

12 Apr '17

hello list, i did a kvm guest with virt-manager and installed windows server 2016. performance settings for the disk: hypervisor default for cache & io mode i added a 2nd disk to the guest , also with hypervisor default settings on cache & io mode Under disk settings in windows server 2016 i set "format whole disk NTFS" i did not choose the "quick format" option. when windows is formatting this 1TB drive the performance on the virtualisation host goes down loging via ssh take ages, top take 2 mins to start up. the physical disks are connected to a raid controller LSI and FS on virtualisation server where the qcow2 files are is XFS. DO i have to set another options for "performance options" as "hypervisor default" to keep the system performant on formatting the disk? thanks for any hints. marko -- zbfmail - Mittendrin statt nur Datei!

1 0

[libvirt-users] Cannot save domain
by Tony Arnold 06 Apr '17

06 Apr '17

I have a domain running a Windows 10 system on an Ubuntu 16.10 host system. The domain has 4096MiB of memory. When I try to save the domain, or managedsave the domain, I get an error when it's about 96% complete. The terminal session looks like this: virsh # save Windows10 windows10-20170402.save --bypass-cache --verbose Save: [ 95 %]error: Failed to save domain Windows10 to windows10- 0170402.save error: operation failed: domain is not running It seems the domain closes before the save has completed. libvirt is at version 2.1.0 Should I submit this as a bug, or is there something I can change to fix this? Regards, Tony. -- Tony Arnold MBCS, CITP | Senior IT Security Analyst | Directorate of IT Services | G64, Kilburn Building | The University of Manchester | Manchester M13 9PL | T: +44 161 275 6093 | M: +44 773 330 0039

2 1

[libvirt-users] creating a lxc image to be used with libvirt-lxc
by Spike 05 Apr '17

05 Apr '17

Dear all, I'm moving my first baby steps with libvirt-lxc trying to convert over from an LXD installation and one of the hurdles is putting together an image. All the examples I found about libvirt-lxc refer to running /bin/sh in a container, almost as if it was docker, as opposed to run a "full system" like I've been doing with lxd. Also virt-install, often referred in libvirt docs, seems to be specific/only for kvm. Can anybody point me to any documentation to achieve the same as you'd do with lxd? would it even just work to use those images ( https://cloud-images.ubuntu.com/) with libvirt? Last but not least, is there any way to "publish" a modified image so that I could make changes to any of the above and then reuse the modified one as a base for other containers? thank you, spike

2 4

[libvirt-users] libvirt-lxc: good for production?
by Spike 03 Apr '17

03 Apr '17

Dear all, I'm a happy lxc (lxd) user with a need to add a bunch of KVM images to the mix. More importantly I need to have some simple frontend to give users the ability to quickly run some VMs for testing. Researching the topic brought me to virt-manager and from there libvirt. I've had however a hard time to answer a few questions that I hope this list can help me with: 1) is the libvirt-lxc driver actively developed? there's been a lot of upgrades to lxc and there seems to be relatively little activity on the lxc driver 2) is libvirt-lxc to be used in production to begin with? every single guide I found about libvirt pretty much points to KVM usage, with simple /bin/sh examples with lxc. Furthermore stuff like virt-install seems to be exclusively catered to full os/KVM images creation, with no obvious way to create a container image. thanks for any input, even just docs I missed that explain the avove would be most helpful. Spike

2 2

[libvirt-users] (Live) Migration safe vs. unsafe
by Michael Hierweck 03 Apr '17

03 Apr '17

Hi all, virsh checks whether a (live) migration is safe or unsafe. When a migration is considered to be unsafe it is rejected unless the --unsafe option is prodivided. As a part of those checks virsh considers the cache settings for the underlying storage resources. In this context only cache="none" is considered to be safe. I wonder why cache="directsync" might be harmfull as it bypasses the host page cache completely. Regards, Michael

2 1

[libvirt-users] migrated RHEL7/CentsOS7 VMs fail to boot
by Daniel Pocock 03 Apr '17

03 Apr '17

I migrated a CentOS7 VM (the fedrtc.org site) from an XCP environment to a libvirt/KVM environment. This involved using qemu-img to convert the image from VHD to qcow2 and then using virt-install --import to define the VM in libvirt. Three problems occurred during boot: a) on the first boot, the BIOS screen and grub screen don't appear at all, the screen is blank for a couple of seconds and then the message about loading a kernel appears. Hard reset and on the second and subsequent attempts I see the grub screen and have the opportunity to interact with it. This actually happened with many of my VMs, not just the CentOS7 VM. b) with console=hvc0 in the grub config, the kernel refused to boot, no error appeared on the screen. I was able to remove that easily enough by pressing "e" in grub. Rather than halting, should the kernel fall back to VGA perhaps when the console= argument is not valid? Or could KVM emulate the Xen console device to make migrations easier? c) after that, the boot proceeds up to about the point where I see systemd messages about starting basic system. Then it sits there for a few minutes and then these messages appear: warning: dracut-initqueue timeout - starting timeout scripts and after that I see "A start job is running for dev-mapp...oot.device (X min Ys/ no limit) Rebooting and choosing the "rescue" image from the bottom of the grub menu got me past that, I was able to log in and then I ran: dracut --kver 3.10.0-514.10.2.el7.x86_64 --force and on the next attempt it was able to boot successfully. The block device for the root FS is an LVM volume (so the name should have been constant) and the block device for the /boot filesystem listed in /etc/fstab was mounted by UUID (the block device name itself changed from xvda1 (XCP) to vda1 (KVM)). All my Debian VMs were able to cope with this device name changing. The CentOS7 system was originally installed using default settings for just about everything. Why does dracut need to be re-run in this situation? Should a bug report be filed about this?

2 2

[libvirt-users] different bios file per guest
by Anton Gorlov 31 Mar '17

31 Mar '17

Can I set different bios file per guest? For some guest need UEFI. By default using bios-256k.bin

2 1

[libvirt-users] libvirt + lxc + cgroups mounting
by Pyles, Andy 22 Mar '17

22 Mar '17

All, Within: https://libvirt.org/drvlxc.html#cgroups it mentions that : “/sys/fs/cgroup/NNNN the host cgroups controllers bind-mounted to only expose the sub-tree associated with the container” In my environment, the host contains: $ls –l /sys/fs/cgroup/ cpu -> cpu,acct cpu,cpuacct cpuacct -> cpu,cpuacct cpuset debug devices freezer memory net_cls systemd - but on my LXC container, I have only: $ls –l /sys/fs/cgroup memory -- How do I add additional host cgroup controllers to the set which is bind-mounted within the container? Thanks, Andy Pyles

1 0

[libvirt-users] libvirtd firewalld support
by Leon Goldberg 22 Mar '17

22 Mar '17

Hey, I've been wondering about the extent libvirt makes use of firewalld. I'm looking to use firewalld exclusively and wonder about the ports libvirt takes care of for me via firewalld (e.g. will console/vnc ports, qemu migration ports, etc, will be handled for me?) I have only done a little bit of testing, but it seems like I can't connect to a vm via vnc without explicitly opening ports beforehand. Thanks, Leon

3 2

[libvirt-users] Memory statistics for a domain
by Szczerbik, PrzemyslawX 22 Mar '17

22 Mar '17

Hi, I'm wondering whether there is any difference between VIR_DOMAIN_MEMORY_STAT_ACTUAL_BALLOON and 'memory' member from virDomainInfo structure. Based on the documentation those values should correspond to current balloon and memory used by the domain respectively. Is it always the case that those values will be equal? Is there a reason why maximum memory allowed ('maxMem' from virDomainInfo structure) cannot be retrieved from virDomainMemoryStats API? It seems that it's required to call 2 different APIs to get all memory metrics for a domain. Regards, Przemek -------------------------------------------------------------- Intel Research and Development Ireland Limited Registered in Ireland Registered Office: Collinstown Industrial Park, Leixlip, County Kildare Registered Number: 308263 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.

1 0

[libvirt-users] Running virConnectGetCapabilities / virsh capabilities without a daemon or KVM
by Richard W.M. Jones 22 Mar '17

22 Mar '17

For virt-p2v we want to get the host CPU model, topology etc, and the best way we found to do that was to pull it from libvirt capabilities[1]. Since libvirt is already parsing the host CPU information, and because /proc/cpuinfo is such a stupid format to parse, this is very convenient. Unfortunately it doesn't work unless libvirtd _and_ KVM are both installed. Without libvirtd installed: # virsh capabilities error: failed to connect to the hypervisor error: Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory With libvirt-daemon installed, but not QEMU: # virsh capabilities error: failed to connect to the hypervisor error: no connection driver available for <null> I feel I should be able to fiddle with the connection URI in some way to make this possible, at least in the second case. However there's not a concept of "no hypervisor", and I couldn't find any other way to make it work. Using "test:///default" seems tempting, but it substitutes some imaginary host (i686) so that's no good. Installing KVM isn't really an option for us since we are trying to build a minimal bootable ISO. Just installing qemu-system-x86_64 pulls in half the world. (Even installing libvirtd is difficult, and we'd prefer to avoid it). Any ideas? Rich. [1] https://github.com/libguestfs/libguestfs/commit/963d6c3be7cd91c0373f67cfdd9… -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com Fedora Windows cross-compiler. Compile Windows programs, test, and build Windows installers. Over 100 libraries supported. http://fedoraproject.org/wiki/MinGW

3 3

[libvirt-users] libvirt-guests and time sync on autostart vms
by ıuoʎ 21 Mar '17

21 Mar '17

I have a host running a few guests all configured to autostart. I'm also using libvirt-guests to suspend the guests when the host restarts or shuts down When the host comes back up I see a bunch of log messages - Resuming guest vm01 already active Resuming guest vm02 already active I guess this is because libvirt autostarts the guests when it starts and before libvirt-guests has a chance to start them. I didn't think this is an issue until I noticed the time on the guests is totally out of sync. SYNC_TIME=1 is enabled in the conf file but this doesn't seem to work I can see from the code at libvirt-guests.sh that the time sync function will only run if the guest is started by libvirt-guests ans will be skipped for guests that are already running So I'm not sure if this is a bug in libvirt-guests.sh or if I'm doing something wrong by using both libvirt-guests and autostart. I assume libvirt-guests will always resume guests on proper reboot but I'm think if there is any unexpected failure where guests weren't properly suspended before boot I still want them to come backup when the server boots Regards, Yoni

3 4

Re: [libvirt-users] CPU Pinning Help
by arrakis＠tsiom.com 21 Mar '17

21 Mar '17

1 0

[libvirt-users] [RFC] per-device metadata
by Francesco Romani 21 Mar '17

21 Mar '17

Hi, Currently libvirt supports metadata in the domain XML. This is very convenient for data related to the VM, but it is a little awkward for devices. Let's pretend I want to have extradata (say, a specific port for a virtual switch) related to a device (say, a NIC). Nowadays I can store that data in the metadata section, but I need some kind of mapping to correlate this piece of information to the specific device. I can use the device alias, but this is not available when the device is created. This is also more complex when doing hotplug/hotunplug, because I need to do update device and update metadata; if either fails, the entire operation must be considered failed. It would be nice to be able to attach metadata to the device, and this is what I'm asking for/proposing in this mail. Would it be possible in a future libvirt release? If this is not possible, what's the best way to do the aforementioned mapping? If it's alias (or device address), how can I be sure than I'm addressing (no pun intended) the right device when I don't have them? (e.g. hotplug new device, or just first time VM created)? Thanks, -- Francesco Romani Red Hat Engineering Virtualization R & D IRC: fromani

3 9

[libvirt-users] Get PID of a domain's QEMU instance from its domain ID
by Thibaut SAUTEREAU 21 Mar '17

21 Mar '17

Hello, I cannot find a way to retrieve PIDs of QEMU instances from libvirt domains' IDs (I'm using libvirt C API). I recognize it sounds like a bad idea doing so (and I know PIDs are explicitly made not available, as I gathered from the source code and on your IRC channel) but I need that to use the perf_event_open syscall in order to gather statistics on my QEMU/KVM guests. I also know libvirt now supports some perf events but only a few and I need more. I could submit patches to add them and I will definitely consider that but in the meantime... What would be the best way to get those PIDs? I tried using the XML file but PID is hidden in there too. I took a look at QEMU Machine Protocol. Now I'm going to walk /proc and match on guests names but it is not that elegant. Any ideas? Thanks, Thibaut S.

3 3

[libvirt-users] CPU Pinning Help
by arrakis＠tsiom.com 21 Mar '17

21 Mar '17

2 1

[libvirt-users] VIR_ERR_OPERATION_INVALID from virDomainDestroyFlags call
by Milan Zamazal 17 Mar '17

17 Mar '17

Hi, we experienced a strange, non-reproducible error after a successful migration to another host. When we called virDomainDestroyFlags with VIR_DOMAIN_DESTROY_GRACEFUL flag after the migration on the source host, we got VIR_ERR_OPERATION_INVALID (code 55) error. The same with repeated virDomainDestroyFlags calls. Normally, we would expect either success or VIR_ERR_NO_DOMAIN error. `virsh list' didn't show the VM. Can anybody please explain to us when this can happen and what the error means in this context? When we have good reasons to believe that the VM is down (e.g. after a migration call successfully finishes) and we receive such an error from virDomainDestroyFlags, is it safe to assume the VM is basically gone and can we perform standard cleanup actions (like removing related files from the host file system)? Thank you, Milan

2 4

[libvirt-users] migrating from XenServer / XCP to libvirt/KVM
by Daniel Pocock 15 Mar '17

15 Mar '17

I've been using XenServer / XCP (with the "xe" toolset) for a number of years for hosting servers used for development and free software projects and I'm now looking at migrating all those environments to libvirt / KVM. I had a look at the wiki[1] already and didn't see XenServer mentioned there. Could anybody help comment on or explain a few things: - comparison between XenServer and libvirt: I notice many similar concepts, for example, XenServer has storage repositories and libvirt has storage pools. However, in many examples such as this[2] it appears that libvirt requires more manual effort. For example, when you create a storage repository in XenServer, the tool takes a physical block device as input and creates the necessary volume group, logical volume and a filesystem. In that libvirt example, it appears each of those steps must be done manually. The networking examples are similar: the XenServer tools do all the Open vSwitch stuff behind the scenes but in the libvirt examples it appears necessary to create the bridge manually before telling libvirt about it. Is this all correct or are the examples I've seen out of date? Do more recent (or future) releases of libvirt aim to automate/hide more of these things? - what is best practice for virtual disk images? Does libvirt always use files (like XenServer) or can/should block devices be used directly? If using files, is any special care needed to avoid block alignment problems? - are there any guides or tools recommended for migrating small XenServer environments (less than 50 domains on a single physical node) to libvirt + KVM? - is there a list of small things that need to change in a VM before running it under libvirt / KVM? I'm guessing this might include bootloader config, updating the kernel, changing block device names in /etc/fstab and changing network device names in scripts - are there any others? - can anybody comment on more tricky issues that may arise in such a migration, for example, will a Windows VM be likely to run without modification when migrated from XenServer to libvirt/KVM or will it need extra drivers added or anything else before the migration? Regards, Daniel 1. http://wiki.libvirt.org/page/Main_Page 2. https://keepingitclassless.net/2014/01/libvirt-intro-basic-configuration/

2 2

[libvirt-users] MIPS emulation broken - No PCI buses available
by Ian Pilcher 15 Mar '17

15 Mar '17

I am trying to create a QEMU MIPS guest, so that I can test some code for big-endian safety. Every attempt to create a MIPS guest is giving me an error: Unable to complete install: 'XML error: No PCI buses available' It seems like this is a known issue. https://www.redhat.com/archives/libvir-list/2016-May/msg00197.html However, I am still getting this on a fully updated Fedora 25 system with libvirt-2.2.0-2.fc25.x86_64. -- ======================================================================== Ian Pilcher arequipeno(a)gmail.com -------- "I grew up before Mark Zuckerberg invented friendship" -------- ========================================================================

3 4

[libvirt-users] trouble after upgrading from 3.0.0 to 3.1.0
by Michael Ströder 15 Mar '17

15 Mar '17

HI! After the last OS update (openSUSE Tumbleweed) with libvirt being updated from 3.0.0 to 3.1.0 starting the VMs (qemu-kvm) does not work anymore: error: internal error: child reported: Kernel does not provide mount namespace: Permission denied Kernel was updated before to 4.10.1 and worked just fine with libvirt 3.0.0 packages. Any clue how to work around that? Ciao, Michael.

2 4

Re: [libvirt-users] [libvirt] libvirt and dmesg
by Cedric Bosdonnat 15 Mar '17

15 Mar '17

Hello Pierre-Jacques, First note that you posted your message on the developer's mailing list. For such user questions, rather email: https://www.redhat.com/mailman/listinfo/libvirt-users According to https://linuxcontainers.org/lxc/manpages//man5/lxc.container.conf.5.html lxc.kmsg is only used to symlink /dev/kmsg to /dev/console. Thus setting this to 0 only results in the lack of that symlink. libvirt doesn't setup this link at all, may be it is coming from the lxc domain root file system. On Wed, 2017-03-15 at 08:49 +0100, Michel Pierre-Jacques wrote: > Hi all, il try to find the way to obtain the same use as in the > lxc config file lxc.kmsg=0 > > how to do that, with the xml of a lxc domain, i make lot of try without > success . > > is there another way to deny access to the dmesg for a libvirt lxc > domain ? >From what I see, dmesg doesn't necessarily requires /dev/kmsg (at least on opensuse). So blocking it may be more tricky. May be you should tell us more how you setup your container. -- Cedric

1 0

[libvirt-users] question about libvirt and suspending guests during live migration
by Chris Friesen 13 Mar '17

13 Mar '17

Hi, I hope someone can help me out. I'm running into an issue with libvirt 1.2.12 reporting "operation failed: domain is no longer running" for a migration when qemu thinks it was fine. The steps are: 1) create guest with stress test running in it to dirty memory at a high rate (fast enough that it would not normally complete live-migration) 2) trigger live migration with dom.migrateToURI2() 3) while migration is in progress, call dom.suspend() on the migrating domain. What I see at this point is the following: a) At time 50.465 the monitoring code sees a VIR_DOMAIN_EVENT_SUSPENDED event, as expected. b) An instrumented qemu logs the following: 51.143: done transferring state 51.143: done migration 51.144: qmp_query_migrate reporting state completed c) At time 51.468 the monitoring code sees a VIR_DOMAIN_EVENT_RESUMED event, with detail of VIR_DOMAIN_EVENT_RESUMED_UNPAUSED c) At time 51.469 the the monitoring code sees a VIR_DOMAIN_EVENT_RESUMED event, with detail of VIR_DOMAIN_EVENT_RESUMED_MIGRATED e) At time 51.471 the dom.migrateToURI2() call raises an exception (this is python). The corresponding libvirt log file shows: "error : virNetClientProgramDispatchError:177 : operation failed: domain is no longer running" For what it's worth, the problem seems to be fixed in libvirt 1.2.17. In that version and later I don't see the VIR_DOMAIN_EVENT_RESUMED event, the migration just completes. I'm looking at the libvirt history, but I figured I'd ask here too... Thanks, Chris

2 1