similar to: CentOS 7 libvirt-1.3.0-1 coming to virt-xen buildlogs

On Fri, Dec 18, 2015 at 7:38 PM, Pulkit Gupta <pulgup at gmail.com> wrote: > Hi, > > There is a strange issue in the CentOS 7.2 libvirtd 1.2.17 service. > If there is a symlink in the "/etc/libvirt/qemu/autostart/" which is created > before the libvirtd service is started, libvirtd wont start. > Deleting the symlink from the autostart folder, then starting the

Hi, There is a strange issue in the CentOS 7.2 libvirtd 1.2.17 service. If there is a symlink in the "/etc/libvirt/qemu/autostart/" which is created before the libvirtd service is started, libvirtd wont start. Deleting the symlink from the autostart folder, then starting the libvirtd service works. Is this a know issue ? We have found this on 4-5 servers. Regards, Pulkit Gupta

Hi, There is a strange issue in the CentOS 7.2 libvirtd 1.2.17 service. If there is a symlink in the "/etc/libvirt/qemu/autostart/" which is created before the libvirtd service is started, libvirtd wont start. Deleting the symlink from the autostart folder, then starting the libvirtd service works. Is this a know issue ? We have found this on 4-5 servers. Regards,

Hello, I am managing several virtual machines (a predefined set) with virsh, and I would like to make sure that all VMs are booted when the host reboots. What is the recommended approach for this? Thanks, Daniel Gonzalez -------------- next part -------------- An HTML attachment was scrubbed... URL:

At long last, we have the packages and the infrastructure set up in what will be (hopefully) the final form for the CentOS 7 Virt SIG Xen packages. Please help us by testing the packages and the infrastructure. To install the Virt SIG Xen repositories, install the CentOS 7 centos-release-xen package directly from buildlogs: yum update

xen-4.4.3-9 and kernel-3.18.21-17 (unsigneg) are now on buildlogs.centos.org, and signed packages should be making their way through the mirror system in the near future. Updated package sources can be found in the virt sig area on CentOS: https://github.com/CentOS-virt7/xen https://github.com/CentOS-virt7/xen-kernel The packages contain updates for XSAs 155, 157, 164, 165, and 166 (released

Hi, I have a host with 6 VMs set to autostart. When this host reboots, it starts libvirtd, pegasus cimom and libvirt-cim. It also restarts the VMs. Intermittently we noticed a core during start up that points to the last call made by libvirt-cim to "virInitialize". I am thinking that it is a timing issue where virInitialize is called while libvirt is trying to autostart the VMs.

Hi! I am trying to run tap networking with libvirtd. My test system is Fedora18/ppc64, libvirt 1.0.4 (compiled from git and installed). On another system with Fedora17/ppc64 with the same settings, dnsmasq is running. All configs in /etc/libvirt/ are default and not changed, the only exception is /etc/libvirt/qemu/networks/default.xml which I copied from Fedora17/ppc64 setup. What does

Autostart is set to "enable" for this domain, but I wouldn't expect autostart to be invoked when a simple "read-only" command is run.  I'd expect the "list --all" command to only display details about the domain...not change the status of the domain by booting it.  Maybe I'm misunderstanding things... On Thursday, December 13, 2018, 11:20:30 AM EST,

Hi Folks, been searching around for a while on this and see similar issues reported going back a number of years without solution. The START_DELAY=(number) seems to be completely ignored in /etc/sysconfig/libvirt-guests which is unfortunate as it means everything starts at once without control. This is fine on NVMe based servers however on the older spinning disks the I/O is creating

On Wed, Nov 18, 2015 at 1:31 PM, Pasi K?rkk?inen <pasik at iki.fi> wrote: > On Wed, Nov 18, 2015 at 02:20:49PM +0200, Manuel Wolfshant wrote: >> On 11/18/2015 02:08 PM, Pasi K?rkk?inen wrote: >> >Hello, >> > >> >On Sun, Nov 15, 2015 at 06:42:18PM +0200, Pasi K?rkk?inen wrote: >> >>On Sun, Nov 15, 2015 at 02:04:58PM +0200, Pasi K?rkk?inen wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Former user of Xen and newbie in kvm/qemu/libvirt stuff, I give it a try on my network ;-) I need to run a VM with iSCSI target attached. I did it this way : 1) Creation of iscsi pool (equa.xml) : <pool type="iscsi"> <name>equalog</name> <source> <host name="10.10.0.1"/> <device

Hi all, I''ve used ruby and ferret for the past one month to index resumes. Now I need a web front-end to the application and the obvious choice turns out to be rails. But as I''m not interested in using a database and intend to just use the index, I''m not sure as to how to put it into the MVC framework as the model implicitly takes a database. Is there a way it can take

> autostarting (and autostopping) based on what event? Based on start/shutdown of the host or starting/stopping libvirtd. I just wrote a script to start with systemd but as there is that autostart functionality in libvirtd this might not be the best solution. Regards, Jan

I have observed 3 scenarios after I reboot the host with 2 guests (which are supposed to autostart after boot/reboot of the host): 1. Default network is created but I can not ping guests. Gests don't have assigned IP address or they both have IP address 192.168.122.100. 2. Default network is not created. 3. Default netork is properly created and everything works fine. In each case guests are

hello, I was having some problems in debugging C codes assocaited with R-packages. I don't have much experience with debugging tools used in C language. Is there any methods similar to R-debugging tools such as browser ,debug etc which can be used to debug such C files. I was using the foreign package and found a bug in reading dta files containing empty strings "" in the data. I

hi all I've a few guest which work/run perfectly fine, I believe, except for autostart. Configuration of system, gluster and libvirt is pretty regular and not complex. Errors I see: ... failed to initialize gluster connection (src=0x7f9424266350 priv=0x7f94242922b0): Transport endpoint is internal error: Failed to autostart VM 'rhel-work2': failed to initialize gluster connection

Hi all, I have some problems with libvirt >2.1.0 (so 2.2.0 and 2.3.0): I have a working environment using libvirt 2.1.0 with 1 domain (called "mail") and one network (called "default6"), both are autostarted. I have no problems with this environment using libvirt 2.1.0, everything works great. But after (testwise) updating to libvirt 2.2.0 or 2.3.0, libvirt doesn't

On Sun, Jun 04, 2017 at 06:42:39PM -0400, Michael C Cambria wrote: >I've upgraded from Fedora 20; probably missed a merge of rpmnew with >existing .conf; permission problem, some other mistake along the way to >Fedora 25. > Yeah, probably some 'rpm -qV' (or whatever the command to verify all packages is) could help as well. >Is there a "how to" similar to [1]

Martin, et al, Sorry for the lag in response. So I started playing with the various virsh commands. Awesome. Been doing some reading and I believe I have some things configured not so well. As I stated earlier in the thread, we have all of the VM image files on one RAID5. Very fast machine. When using top, the load average is a stable "5.xx". No I/O wait. GB's of free memory.