similar to: Libvirt problem - centos 5.4 / xen 3.4.2 all x86_64

Hi, It's exist any repo where I find a newer libvirt-0.7.4 for Centos 5.4_x86_64? For at ll

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>

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

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

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

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

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

I have an issue setting a persistent kernel option on a libvirt net device since that device does not exist early enough during the boot of the KVM host. I am using the 127.0.0.0 local net for cluster communication between the KVM host and its guests as well as between KVM guests. In order to use addresses on the 127.0.0.0/8 network, which is reserved for local communication, two configuration

-----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 did post to ovirt-devel but I am not a registered user, so a moderator need to review my posting before it becomes available. I will register, but right now I only have a few seconds to spare. I try to add use "Add Virtual Machine" but the "Storage" is empty. My iSCSI and NFS storage says "State: pending_setup". What am I doing wrong? Sincerely, /bs66

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,

Devs, compiz listmates: Why can't I turn off compiz autostart on openSuSE 10.3 i386? Compiz just decided to start automatically with KDE login ever since I upgraded to the first 0.7.4.x release from the openSuSE build service. I have tried to disable it by creating the file "disable-compiz" in ~/.config/compiz but compiz still starts at login. Even if I switch to kwin before

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

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

Good morning, I need to use pciback.hide to hide a pci card because I want to pci passthrough that card to a domU. My hardware neither supports Intel-Vt-d nor AMD's IOMMU. Unfortunately this doesn't seem to work in Centos 54 anymore. I guess it doesn't work because it is not compiled into the kernel, but as a module. I got the following error in dmesg and the pci device is still

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

Hi everyone Ok this is really strange. I''ve been messing around with Xen for the past few weeks on a 32bit test machine and CentOS 5.4 and it''s been working fine. At the weekend I went into the office to install Xen on our server but I had a major problem. The server is a home-build with a Tyan s5211 motherboard with an Intel i3210w chipset CentOS 5.4 64bit installed and

I''m new to rspec. I just installed these: rspec (0.7.4) RSpec-0.7.4 (r1201) (rspec gem) rspec_on_rails .3 plugin (on vendor/plugin) I''ve set up a simple spec - spec/library/test_spec.rb: require File.dirname(__FILE__) + ''/../spec_helper'' context "test context" do setup do #nothing end specify "nothing to specify" do

I''ve migrated my Dom0 host to Xen 4.2.0 + xl toolstack. With ''xm'' toolstack, configs in /etc/xen/auto are autostarted, assuming xend/xendomains services are started. IIUC, when using xl toolstack, those services are not to be started; and, afaict, the installation process for 4.2 has them disabled by default. Now, the configs in /etc/xen/auto are simply ignored. I

Dear all, First, sorry for all that noise. I know you guys *just don't care*TM, but this requires some clarification. I won't say more than what's in this email. The VMKit paper dates from early 2008. It compares VMKit with pnet 0.7.4 and not the latest release (0.8.0) because we were not able to get any information to build it correctly at the time; the website that hosted