similar to: libvirt 0.10 and cephx

Hi all, I'd like to get a few storage statistics from a running vm. I'd like to know read and write data about QCOW2 devices and about RBD volumes. I did try to execute a command similar to this: virsh qemu-monitor-command vm-vnc '{ "execute": "query-block"}' as described here:

The problem desribed here: https://bugzilla.redhat.com/show_bug.cgi?id=593266 Please update http://www.libvirt.org/formatdomain.html and describe NEW xml tags, like <serial>xxxx</serial> for hard drive and all cpu tags, other if any. -- Segmentation fault

I was playing with SASL authentication a bit today and I wasn't able to get libvirt to authenticate against PAM (or anything else except the sasldb, although I didn't try Kerberos). Does anybody know off the top of their head what mechanisms/password check options work? I'm trying to figure out if I'm attempting the impossible. Dave

Hi guys, I am new to QEMU-KVM, libvmi and libvirt stuff. Libvmi uses libvirt. I am trying to to run process-list example of libvmi and getting error as below. It seems that this error may be due to libvirt as it is not able to find domain. I seek your kind help on below error: spanhal1@seclab2:~/KVMModule/libvmi-0.10.1$ sudo ./examples/process-list ubuntu libvir: QEMU error : Domain not found:

I tried running qemu-system-x86_64 -help" command manually. But it seems that it work normally. Here is the output. Kindly guide me. spanhal1@seclab2:/usr/bin$ qemu-system-x86_64 -help QEMU emulator version 1.2.0 (qemu-kvm-1.2.0), Copyright (c) 2003-2008 Fabrice Bellard usage: qemu-system-x86_64 [options] [disk_image] 'disk_image' is a raw hard disk image for IDE hard disk 0

On Fri, Jul 18, 2014 at 11:58 PM, Andrey Korolyov <andrey@xdel.ru> wrote: > Hello, > > 2.0 model works fine > > 2.1 crashes with following: > > /tmp/buildd/qemu-2.0.92+rev1/hw/i386/smbios.c:825: smbios_get_tables: > Assertion `smbios_smp_sockets >= 1' failed > > Not sure if bisect will help much, but the commit which introduced > this platform works

Hello everybody, I am a new user discovering libvirt with KVM software. During my first VM creation, I saw an issue with virsh that I can't understand. I wanted to emulate another CPU than the classical qemu32 using virsh. So I used the virsh capabilites command to detect how is detected my CPU host which is an Intel Xeon E5410 and my problem is that this CPU is detected only with the

I know I would still have to provide the Mon addresses and Cephx user to go with the secret UUID, that's fine. The primary goal is so I can just see if I can open a RADOS connection to the cluster before I try a virsh attach-device. On Tue, Feb 11, 2014 at 9:37 AM, Scott Sullivan < scottgregorysullivan@gmail.com> wrote: > As the subject suggests, I am wondering if its possible to

As the subject suggests, I am wondering if its possible to verify if the currently defined libvirt secret provides valid authentication via Cephx to a Ceph cluster? I ask because ideally I would like to verify that the given cephx credentials in my libvirt secret are valid before I even attempt the virsh attach-device on the domain. I tried searching for a solution to this, but I can't seem

Hi All, I am setting the value for "read_bytes_sec" using the following API code virDomainSetBlockIoTune(dom, "/mnt/tmpsdb/FileVM1", parainfoPtr, nparams, 2); I am succesfully able to set this value and i can read it back using the API virDomainGetBlockIoTune(dom,"/mnt/tmpsdb/FileVM1",parainfoPtr,&nparams,2); But after setting this value when i shutdown

Hi all, I try to understand why the interface bandwidth limits are not applied to my Ubuntu 12.04 VM (qemu-kvm driver) and I would need some insights. I spawn my VM with OpenStack and when I issue a dumpxml on my domain, I can see that bandwidth limits are set: <interface type='ethernet'> <mac address='02:68:b5:c6:fa:a5'/> <bandwidth> <inbound

Hi, After following advice from you good folks, I gave mongrel a try in a cluster design based on the example on the Mongrel website - and it worked right out of the box which is great - and it''s very fast :) I have got a bit stuck though. I have two MS Word files in /public/files/. I can pull back these files no problem but it isn''t sending a mimetype. I think I have two

HI, me and firewalld won't have a good start, but I hope we'll be good friends. One of my hosts must rerote traffic from one to another host. It isn't a big problem. I've a host witch must do: 1) forwarding port 25 tcp to a second host Here I've a special mail-relay. My external.xml look like this one: <?xml version="1.0" encoding="utf-8"?>

HI, here I have an eMail with connected to a DMZ 10.0.0.0/24 network. This server holds 10.0.0.87 There are two firewall-hosts one with CentOS 6 10.0.0.10 and one with CentOS 7 10.0.0.17 The CentOS 6 has the following iptables-rule (extract): ----------------------8<----------------------8<----------------------8< *nat -A POSTROUTING -o eth1 -j MASQUERADE -A PREROUTING -i eth1 -d

Hello List, I am having problem in getting iptables recent module working for me, so I was looking into /proc to get some clues. I see following line in the /proc for my iptables recent rule: # cat /proc/net/ipt_recent/badguy src=10.0.0.17 ttl: 63 last_seen: 3301974512 oldest_pkt: 2 3301973507, 3301974512 What does ttl mean? Is it time-to-live or what? What does it signify? -- CS

I?m trying out the the doveadm http api for the first time. When I do: $ curl -H "Authorization: Basic <base64 doveadm:doveadm_password>" http://localhost:8888 curl: (52) Empty reply from server In the logs, I see the following error: May 09 11:58:05 doveadm(10.0.0.17): Error: doveadm client not compatible with this server (mixed old and new binaries?) I am running Dovecot

Hello list. I'm trying to rebuild the 2.6.9.67.0.20.EL kernel, but it fails even without modifications. How did I try it? Created a (non-root) build environment (not a mock ) Installed the kernel.scr.rpm and did a rpmbuild -ba --target=`uname -m` kernel-2.6.spec 2> prep-err.log | tee prep-out.log The build failed at the end: Processing files: kernel-xenU-devel-2.6.9-67.0.20.EL Checking