March 2016 - Users - libvirt List Archives

[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 18 Mar '16

18 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 18 Mar '16

18 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 18 Mar '16

18 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 17 Mar '16

17 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 17 Mar '16

17 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 17 Mar '16

17 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 15 Mar '16

15 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

[libvirt-users] Where are libvirt's USB autroredirection settings stored?
by bancfc＠openmailbox.org 12 Mar '16

12 Mar '16

For security reasons Debian's libvirt maintainer has opted to disable the default behavior of autoredirecting any newly attached USB device to a running VM with SPICE USB redirection ports added. I tried looking for an obvious setting in virt-manager's menus to change this but can't see anything. What libvirt/virt-manager configuration file is this setting stored so I can change it on demand?

1 1

[libvirt-users] 100% CPU when using nested virtualization
by Digimer 11 Mar '16

11 Mar '16

Hi all, I got a new laptop recently and what worked before no longer works (Fedora 23 on the laptops in both cases)... I'm trying to get nested virtualization to work because I use the VMs on the laptop to simulate an HA cluster that itself hosts VMs. I don't care much at all about the performance of the nested VM, it's just there so that I can work on the cluster's code. When I try to provision a VM inside a VM (the host VM is CentOS/RHEL 6.7), the CPU load spikes to such a high degree that my ssh session times out after a while. The VM appears in libvirtd (as viewed by virt-manager on another machine), but the VM itself never starts. In one case, the VM host remained somewhat functional and killing kvm/qemu/libvirtd didn't reduce the CPU load. The main difference between the setups is that the older laptop had a Sandy bridge(? Thinkpad W530) and the new laptop is a Broadwell (Thinkpad P70). I've tried to loading vhost_net without much luck. I have, of course, enabled nesting on the actual hardware: cat /sys/module/kvm_intel/parameters/nested Y Any tips on how to debug? I'm in quite a pickle with this, so any and all help is much appreciated. -- Digimer Papers and Projects: https://alteeve.ca/w/ What if the cure for cancer is trapped in the mind of a person without access to education?

2 2

[libvirt-users] EPT Misconfiguration
by Andrei Perietanu 10 Mar '16

10 Mar '16

I am using libvirt 1.2.20. I noticed that when running some VMs (CentOS ) with 2G ram, 2CPUs each for some reason they go from 'state=running' to 'state=paused'; and they can't be restarted. They are un-usable. When this happens I get the following in dmesg output: [ 46.595265] EPT: Misconfiguration. [ 46.595271] EPT: GPA: 0xfee000b0 [ 46.595275] ept_misconfig_inspect_spte: spte 0x7e4968107 level 4 [ 46.595279] ept_misconfig_inspect_spte: spte 0x7e4961107 level 3 [ 46.595281] ept_misconfig_inspect_spte: spte 0x7e4960107 level 2 [ 46.595284] ept_misconfig_inspect_spte: spte 0x7e592ff77 level 1 I have seen discussions about this topic, but for older code versions. The problem happens often and I could not find a fix for it. Has anyone seen this?Is there a fix for it? Thanks, 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] Zombie processes being created when console buffer is full
by Peter Steele 10 Mar '16

10 Mar '16

We have been researching stuck zombie processes in our libvirt lxc containers. What we found was: 1) Each zombie’s parent was pid 1. init which symlinks to systemd. 2) In some cases, the zombies were launched by systemd, in others the zombie was inherited. 3) While the child is in the zombie state, the parent process (systemd) /proc/1/status shows no pending signals. 4) Attaching gdb to systemd, there was 1 thread and it was waiting in write() and the file being written was /dev/console. This write() to the console never returns. We operated under the assumption that systemd's SIGCHLD handler sets a bit and a foreground thread (the only thread) would see that child processes needed reaping. While the single thread is stuck in write(), the reaping never takes place. So why is write() blocking? The answer seems to be that there is nothing draining the console and eventually it blocks write() when its buffers become full. When we attached to the container's console, the buffer is cleared allowing systemd’s write() to return. The zombies are then reaped and everything goes back to normal. Our “solution” was more of a workaround. systemd was altered to log errors/warnings/etc to /dev/null instead of /dev/console. This prevented the problem, only in that the console buffer was unlikely to get filled up since systemd generally is the only then that writes to it. This is definitely a hack though. This may be a bug in the libvirt container library (you can't expect something to periodically connect to a container's console to empty it out). We suspect there may also be a configuration issue in our containers with regards to the console. Has anyone else observed this problem? Peter _______________________________________________ libvirt-users mailing list libvirt-users(a)redhat.com https://www.redhat.com/mailman/listinfo/libvirt-users

2 3

[libvirt-users] Buggy 1.3.2? Disconnected from qemu:///session due to I/O error
by Lars Kellogg-Stedman 10 Mar '16

10 Mar '16

I think I've hit the same problem that Predrag reported in http://comments.gmane.org/gmane.comp.emulators.libvirt.user/8825. With libvirt-1.3.2-1.fc23.x86_64 on Fedora 23, when I try uploading an image with vol-upload to a user libvirtd (qemu:///session): virsh vol-upload --pool default volume.qcow /path/to/file.qcow2 I am getting: error: Disconnected from qemu:///session due to I/O error error: cannot send data to volume volume.qcow2 error: Cannot write data: Broken pipe error: One or more references were leaked after disconnect from the hypervisor If I downgrade to libvirt-1.2.18.2-2.fc23.x86_64 (which is what actually ships in F23), the image upload completes without a problem. -- Lars Kellogg-Stedman <lars(a)redhat.com> | larsks @ {freenode,twitter,github} Cloud Engineering / OpenStack | http://blog.oddbit.com/

2 1

[libvirt-users] removing virbr0
by Andrei Perietanu 10 Mar '16

10 Mar '16

I am building a custom Linux image which includes KVM and will be installed on multiple machines. By default when installing libvirt you get a 'default network' which adds a 'vrbr0'. I found several tutorials online about removing this 'virbr0' but I would like to not have it in the first place. I am compiling libvirt from source so I would think there is some compile time option or some configuration file I need to change for the default network not to be included. Thanks for your help! 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.

4 8

[libvirt-users] different uuids, but still "Attempt to migrate guest to same host" error
by Devin Reade 10 Mar '16

10 Mar '16

Background: ---------- I'm trying to debug a two-node pacemaker/corosync cluster where I want to be able to do live migration of KVM/qemu VMs. Storage is backed via dual-primary DRBD (yes, fencing is in place). When moving the VM between nodes via 'pcs resource move RES NODENAME', the live migration fails although pacemaker will shut down the VM and restart it on the other node. For the purpose of diagnosing things, on both nodes I've put SELinux into permissive mode and disabled firewalld. Interesting Bit: --------------- Debugging a bit further, I put the VM into an unmanaged state and then try with virsh, from the node currently running the VM: [root@node1 ~]# virsh migrate --live --verbose testvm qemu+ssh://node2/system error: internal error: Attempt to migrate guest to the same host node1.example.tld A quick google points toward uuid problems, however the two nodes are, afaict, working with different UUIDs. (Substantiating info shown toward the end.) I thought that since `hostname` only returns the node name and not the FQDN that perhaps there was internal qemu confusion about using the short node name vs FQDN. However fully qualifying it made no difference: [root@node1 ~]# virsh migrate --live --verbose testvm qemu+ssh://node2.example.tld/system error: internal error: Attempt to migrate guest to the same host node1.example.tld Running virsh with a debug level of 1 doesn't reveal anything interesting that I can see. Running libvirtd at that level shows that node2 is seeing node1.example.tld in the emitted XML in qemuMigrationPrepareDirect. I'm assuming that means the wrong node has been calculated somewhere prior to that. At this point I'm grasping at straws and looking for ideas. Does anyone have a clue-bat? Devin Config Info Follows: ------------------- CentOS Linux release 7.2.1511 (Core) libvirt on both nodes is 1.2.17-13 [root@node1 ~]# virsh sysinfo | grep uuid <entry name='uuid'>03DE0294-0480-05A4-B906-8E0700080009</entry> [root@node2 ~]# virsh sysinfo | grep uuid <entry name='uuid'>03DE0294-0480-05A4-B206-320700080009</entry> [root@node1 ~]# dmidecode -s system-uuid 03DE0294-0480-05A4-B906-8E0700080009 [root@node2 ~]# dmidecode -s system-uuid 03DE0294-0480-05A4-B206-320700080009 [root@node1 ~]# fgrep uuid /etc/libvirt/libvirtd.conf | grep -v '#' host_uuid = "875cb1a3-437c-4cb5-a3de-9789d0233e4b" [root@node2 ~]# fgrep uuid /etc/libvirt/libvirtd.conf | grep -v '#' host_uuid = "643c0ef4-bb46-4dc9-9f91-13dda8d9aa33" [root@node2 ~]# pcs config show ... Resource: testvm (class=ocf provider=heartbeat type=VirtualDomain) Attributes: hypervisor=qemu:///system config=/cluster/config/libvirt/qemu/testvm.xml migration_transport=ssh Meta Attrs: allow-migrate=true is-managed=false Operations: start interval=0s timeout=120 (testvm-start-interval-0s) stop interval=0s timeout=240 (testvm-stop-interval-0s) monitor interval=10 timeout=30 (testvm-monitor-interval-10) migrate_from interval=0 timeout=60s (testvm-migrate_from-interval-0) migrate_to interval=0 timeout=120s (testvm-migrate_to-interval-0) ... (The /cluster/config directory is a shared GlusterFS filesystem.) [root@node1 ~]# cat /etc/hosts | grep -v localhost 192.168.10.8 node1.example.tld node2 192.168.10.9 node2.example.tld node2 192.168.11.8 node1hb.example.tld node1hb 192.168.11.9 node2hb.example.tld node2hb (node1 and node2 are the "reachable" IPs and totem ring1. node1hb and node2hb form a direct connection via crossover cable for DRBD and totem ring0.)

1 0

[libvirt-users] How to test if a console session is active?
by Peter Steele 10 Mar '16

10 Mar '16

I use libvirt to manage a container based environment. Is there an efficient method for testing if someone has a console session open for a given container? The approach I'm using at the moment is to use lsof and check if there is an entry for the container's console pts device. For example, I can determine a container's console device from its xml definition: # virsh dumpxml vm-00|grep -A 4 pty <console type='pty' tty='/dev/pts/3'> <source path='/dev/pts/3'/> <target type='lxc' port='0'/> <alias name='console0'/> </console> Once I have pts device, I can do something like # if lsof /dev/pts/3; then echo "Container vm-00 has an active console session"; fi This all works fine but we've found that lsof is very expensive. Is there a more efficient means to make this active console check? Peter

1 0

[libvirt-users] Problems creating a LXC rootfs to be used with virt-manager
by Markus Rhonheimer 09 Mar '16

09 Mar '16

Hello everyone, Laine Stump over at OFTC #virt was kind enough to point me to this email address. I am trying to run a LXC OS container with virt-manager and found out, that I need to create the rootfs with LXC/LXD and then point virt-manager to the rootfs location. ( I am running Ubuntu 16.04 inside a virtual machine [kvm] for testing) Both "lxc-create" and "lxc launch" worked to create the rootfs and run the VMs. When I tried to add them to virt-manager I always get error messages like this: https://postimg.org/image/lkqn1ery5/ the configuration looks like this: http://pastebin.com/fg1JFCRX I would appreciate any help. kind regards, Markus

1 0

[libvirt-users] unable to create preallocated image with gluster protocol
by SATHEESARAN 09 Mar '16

09 Mar '16

Hi All, When I tried to create preallocated image with gluster , I am unable to create one The image gets created but not preallocated. [root@ ]# qemu-img create -f qcow2 -o preallocation=full gluster://host1.lab.eng.blr.redhat.com/rep3vol/vm3.img 3G Formatting 'gluster://dhcp37-61.lab.eng.blr.redhat.com/rep3vol/newvm3.img', fmt=qcow2 size=3221225472 encryption=off cluster_size=65536 preallocation='full' Unknown option 'preallocation' Is it a known issue ? -- Satheesaran S

2 1

[libvirt-users] (no subject)
by nidhi d 08 Mar '16

08 Mar '16

How do i add a new rpc to the existing code ?

1 0

[libvirt-users] How to measure memory utilizatin of guest when dommemstat reports "RSS" is more than "ACTUAL"?
by suyog jadhav 08 Mar '16

08 Mar '16

How to measure memory utilizatin of guest when dommemstat reports "RSS" is more than "ACTUAL"? Following is the output on RHEL 6.6 # dommemstat 1 actual 16777216 rss 16890372 # dommemstat 2 actual 16777216 rss 16460516 I found following article on Redhat which suggests that this is normal/expected? https://access.redhat.com/solutions/2017943 Now we use following formula to calculate the memory utilization. mem_util = (rss/actual)*100 now this gives more that 100% as the result. We use the libvirt library to call the virDomainMemoryStats. (which is the same used by the "virsh dommemstat" command) If we can't use the RSS as the "used memory", what else should be used to calculate the same? What is the ideal approach to report memory utilization of guest from the KVM host?

2 1

[libvirt-users] Compiling qemu
by Dominique Ramaekers 08 Mar '16

08 Mar '16

Hi, I've installed qemu 2.5 through the package manager. There is a bug which blocks making an external snapshot for the second time. A fix is released: https://lists.gnu.org/archive/html/qemu-devel/2016-01/msg06163.html I thought, why not download the source, apply the patch, build + make and then copy qemu-system-x86_64 to the /usr/bin/ folder..... But if I do 'virsh start my_vm', I get these errors: fout: internal error: early end of file from monitor, possible problem: warning: host doesn't support requested feature: CPUID.80000001H:ECX.svm [bit 2] warning: host doesn't support requested feature: CPUID.80000001H:ECX.svm [bit 2] qemu: could not load PC BIOS 'bios-256k.bin' First: What can I do about the 'host doesn't support requested feature'? Second: I think the compiled binary doesn't look for the bios-256k.bin in the right place? Help wil be much apreciated... Greetings, Dominique.

2 1