search for: autostarts

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>

Hello all, I'm running a newly installed CentOS 5.4 KVM host and am running into problems setting guests up to autostart. Has anyone seen and/or overcome this issue? [root at virt04 ~]# virsh autostart guest02 error: Failed to mark domain guest02 as autostarted error: internal error cannot set autostart for transient domain Just for kicks I tried symlinking /etc/libvirt/guest02.xml and

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:

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

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

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

Hello there, CentOS6.7 64-bit up-to-date running on my laptop.. This night I had to restart (did it properly). Since then, my ~/.config/autostart/ contains some new broken .desktop files and /var/log/messages complains: gnome-session[7280]: WARNING: Could not parse desktop file /home/wwp/.config/autostart/gnome-keyring-daemon.desktop: Key file does not have key 'Name'

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 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

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

-----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

I have a feeling my no autostart problem is related to the following tests in compiz-manager. Is there a way I can "step" through the script on openSuSE 10.3 while it is running to find out where the script dies? Or do I basically have to insert error returns throughout the script to capture that info? ---- # if we run under Xgl, we can skip some tests here if ! check_xgl; then # if

...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 t...

> 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

Hi, Does backgroundrb 0.2.1 support autostart? I''ve tried to set up autostart by adding something like the following in backgroundrb.yml: autostart: 1: class: bar_worker args: '''' However, that does not seem to work. I also tried the scheduling mechanism like this in backgroundrb_schedules.yml: bar: :class: :bar_worker :job_key: :bar1

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

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

-----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

Maybe trivial question, but I cannot find an answer: How to autostart Asterisk (daemon) on Slackware 10? I know that I should put something in /etc/rc.d, but what?

All, Is there a preferred method for creating a domain today; in other words, virt-install, xm create, etc.? I have one machine that the domains were created by another admin using xm create, and I /do/ like the config options for autostarting, etc. For some reason, I used virt-install on the current machine, and ended up with domains named and placed in