similar to: qemu:///session and network-mounted home directories

Displaying 20 results from an estimated 20000 matches similar to: "qemu:///session and network-mounted home directories"

2015 Oct 10
1
Re: qemu:///session and network-mounted home directories
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
2015 Oct 10
0
Re: qemu:///session and network-mounted home directories
On 10/10/2015 10:53 AM, Spencer Baugh wrote: > > 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
2010 Aug 27
1
Unable to autostart storage pool.
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>
2018 Dec 14
2
Re: "virsh list --all" is intermittently causing a shutdown client to boot?
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,
2011 May 18
1
[Qemu-devel] Qcow2
On Wed, May 18, 2011 at 5:18 PM, <arun.sasi1 at wipro.com> wrote: > Hello Stefan, > > > > Thank you very much for considering my issue... > > > > Here is My problem... > > > > 1) I have 4 VM`s Running on Base server. > > 2) Base server is having 15GB RAM. > > 3) I can start all VM`s apart from my file server. > > 4) File server is
2010 Jan 17
2
error: failed to serialize S-Expr
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
2006 Aug 07
2
Autostarting and job keys...
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
2010 Mar 17
1
Pool, iSCSI and guest start
-----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
2015 Dec 07
2
Re: Destroy autostarted network on shutdown
> 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
2011 Jul 05
2
Problems Syncing Home Directories
Hello All, I administrate public Internet computers for a number of libraries. I have a user ''public'' and I am trying to keep all the home''s for this user the same across multiple computers. When I try to do this with puppet, I get errors for some directories. It only happens on hidden directories, but I''m not sure if it is all of them, or just some of them.
2017 Jan 17
1
gluster store and autostart - but fails
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
2009 Dec 15
1
Libvirt problem - centos 5.4 / xen 3.4.2 all x86_64
Hi, Anyone have that problem xen installation? [root at xen64-dev ~]# virsh autostart appl error: Failed to mark domain appl as autostarted error: internal error sexpr2string failed root at xen64-dev opt]# rpm -qa |grep libvirt libvirt-client-0.7.0-6.el5 libvirt-python-0.7.0-6.el5 libvirt-0.7.0-6.el5 [root at xen64-dev opt]# rpm -qa |grep xen xen-libs-3.4.2-2.el5
2011 Aug 11
2
virInitialize dumps core intermittently.
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.
2015 Dec 21
2
CentOS 7.2 libvirtd 1.2.17 bug
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,
2013 Nov 13
4
How to tell libvirt not to use qemu "accel=kvm" for a FreeBSD guest
Hi there, I have used qemu to install FreeBSD 9.2 release, and i can boot it fine with: $ qemu-system-x86_64 -hda images/FreeBSD-9.2-RELEASE-amd64.img I then made virsh aware of my brand new VM (see attached XML), but when i run it via virsh, It hangs after the bootloader whith this message: Booting... CPU doesn't support long mode From the log, here is the generated qemu command:
2016 Oct 17
3
Libvirt newer than 2.1.0 doesnt start up
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
2015 Jun 22
2
Access to virtualization on a multi-user system
Hi libvirt-users, I find myself wanting to do something that seems like it must have some obvious solution: I have multiple users (let's just assume local Unix accounts) on a Linux system, and I want them all to have access to KVM-accelerated virtualization. But, I don't want them to be able to meddle with each other's virtual machines. Is there a solution to this problem? Methods of
2013 Jun 02
2
Pools are not persistent
Hi all! I'm trying virt-manager on Debian Wheezy and I noticed that it has already defined a "default" pool. But if I run: # /etc/init.d/libvirt-bin restart I lose the definition of the pools. Actually, there are the definitions of the pools; but these are not read after restarting libvirt. ss01:/etc/libvirt/storage# ls -l total 8 drwxr-xr-x 2 root root 4096 jun 1 09:36
2015 Dec 06
2
Destroy autostarted network on shutdown
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
2005 Feb 15
3
Autostart Asterisk on Slackware?
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?