similar to: Preferred DomU creation method

> 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

Hello everyone, I have recently installed libvirt 1.0.0 and am having a problem with my iSCSI storage pool's autostarting. They are just going to an inactive state right after a reboot of the host. However once the startup is complete I can manually start the pool without problem. I am getting the following errors in the libvirtd.log file but they don't really give me much as to what

Hi all, I just ran into problem properly stopping a network. I have defined a network and network hook script to accomplish some preparations and cleanup. Testing my configuration (virsh net-start and virsh net-destroy) was successfully. Now I wanted to automate the lifecycle. Unfortunately I realized that an autostarted network has to be persistent and thus will not be destroyed (even if the

-----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 there, as i stated before in my talk with Ben Johnson, I hacked a little bit and here it is - autostarting jobs. I think someone (eh... Ezra) should review it and check to see if i made any mistakes. Also i dont have the possibility to test it on other-than-Windows systems, but since the calling process works just the same, it should do well... Now the neccesary evil, the documentation... If

All, A few people have reported this problem over time: A machine that has been up for awhile, you execute the console for a DomU and you type a few characters and the system becomes unresponsive. Everything on the DomU is working, but you can''t use the console. The only way to fix this is to find the running process id for the xenconsoled and kill it and then restart the console.

If a DomU was compramised, could the Dom0 or other DomUs be compramised? I guess I''m trying to work out how much isolated Xen gives.. Thanks _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

I''ve now got 5 processes auto started. But I when I query the MiddleMan for their keys (in script/console), it doesn''t find them. Looking at the start script, it looks like it might be creating a new MiddleMan object for each autostart BackgrounDRb::MiddleMan.new.new_worker(:class => entry[''class''], Even changing it to

The continuing challenges of getting a workable server continue. The latest spins of VirtualBox seem to have solved the issues of DKMS auto compiles of the driver being aborted. The yum updates work as expected, provided one stops the running vms manually first. However, trying to get systemd to start the vms is proving to be a PITA. I have extensively googled and found that there are no

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello everyone, How do I make storage pool auto start? I have: virsh # pool-list Name State Autostart - ----------------------------------------- default active yes virtimages active no I don't see anything in pool's xml that could suit this purpose: virsh # pool-dumpxml virtimages

hi, i am getting this error below when i try to create a storage volume: ? ? libvirt.virStoragePool.CreateXML(storagepoolobject,xmldesc,0) AttributeError: class virStoragePool has no attribute 'CreateXML' my code is: xmldesc="xml description of storage volume which i got from sudo virsh vol-dumpxml" #get a storage pool object to use in creating a volume

Cole Robinson <crobinso@redhat.com> writes: > The proper way to make sure shared VMs aren't started across multiple machines > is libvirt's locking support: https://libvirt.org/locking.html > > It requires running a separate daemon though so isn't trivial, and I have no > idea if it can be made to work with qemu:///session. Hmm, but what do you mean by shared VMs

On 28/05/16 12:43, Anthony K wrote: > On 17/05/16 17:55, Rob Kampen wrote: >> No idea where to from here, so if there is anyone that has a working >> systemd autostart VirtualBox setup on a headless CentOS 7 server - >> please advise what you have done to get it working. > I'm running CentOS7 as my host and when I was using Virtualbox, I had > my VM's

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,

Following xml file was used to create storage pool using 'virsh pool-create <xml>' <pool type='dir'> <name>my-diskpool</name> <uuid>2fbc894e-7619-6cda-a33c-b27fae5fbe8b</uuid> <capacity>136024670208</capacity> <allocation>11416657920</allocation> <available>124608012288</available> <source>

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

Dear libvirt-users, Suppose my home directory is network mounted on to several different machines. And suppose I defined some VMs in qemu:///session. The configuration files and disk images for qemu:///session are stored in my home directory. Now suppose I log in to some machine and use virsh. The qemu:///session VMs that are marked autostart are started. Now if I log into another machine and

Last night I upgraded from b127 to b130 and now I can''t mark autostart domains: # virsh autostart lunar-1 error: Failed to mark domain lunar-1 as autostarted error: failed to serialize S-Expr: (domain (on_crash restart) (uuid 91c21040-2098-bc0d-b401-3908f3a21667) (bootloader_args) (vcpus 1) (name lunar-1) (on_poweroff destroy) (on_reboot restart) (cpus ( Searching the archives

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,

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.