Could anyone please list out the steps required to run the command
$virsh qemu-agent-command
Steps that I followed:
1. Clone the latest source code of libvirt
2. Create a vm of f18 (source:liveCD)
3. Edit f18 domain xml and add this:
channel type='unix'
source mode='bind'
On Tue, Jun 4, 2013 at 9:29 AM, Roman Bogorodskiy bogorods...@gmail.comwrote:
Daniel P. Berrange wrote:
On Tue, Jun 04, 2013 at 09:33:15AM -0600, Eric Blake wrote:
On 06/04/2013 04:06 AM, Daniel P. Berrange wrote:
From: Daniel P. Berrange berra...@redhat.com
Historically
On 12/06/13 15:49, Michal Privoznik wrote:
On 11.06.2013 16:59, Franky Van Liedekerke wrote:
I just downloaded and compiled libvirtd on the same server as I did
1.0.4. Upon updating, libvirtd refuses to start, with this in the
logfile (obfuscated the hostname by xxx's):
2013-06-11
On 17/06/13 14:00, Nehal J. Wani wrote:
Could anyone please list out the steps required to run the command
$virsh qemu-agent-command
Steps that I followed:
1. Clone the latest source code of libvirt
2. Create a vm of f18 (source:liveCD)
3. Edit f18 domain xml and add this:
channel type='unix'
On 06/17/2013 09:05 AM, Osier Yang wrote:
On 12/06/13 15:49, Michal Privoznik wrote:
On 11.06.2013 16:59, Franky Van Liedekerke wrote:
So it seems two issues are present here:
1) it searches for /sys/class/fc_host//host0/max_npiv_vports for both
host1 and host2. Imho this path needs to be
The error:
# ./tools/virsh qemu-agent-command f18
'{execute:guest-network-get-interfaces}'
error: unknown procedure: 3
Comes when I clone from $git clone git://libvirt.org/libvirt.git
But when I download http://libvirt.org/sources/libvirt-1.0.6.tar.gz
and make, I get:
# ./tools/virsh
On 17/06/13 15:23, Ján Tomko wrote:
On 06/17/2013 09:05 AM, Osier Yang wrote:
On 12/06/13 15:49, Michal Privoznik wrote:
On 11.06.2013 16:59, Franky Van Liedekerke wrote:
So it seems two issues are present here:
1) it searches for /sys/class/fc_host//host0/max_npiv_vports for both
host1 and
On 06/10/2013 04:12 PM, Martin Kletzander wrote:
On 06/10/2013 02:10 PM, Ján Tomko wrote:
Split out option string generation to make adding new options easier
and simplify the code.
---
src/storage/storage_backend.c | 111
++
1 file changed, 59
On Fri, Jun 14, 2013 at 12:32:35 -0600, Don Dugger wrote:
On Fri, Jun 14, 2013 at 03:06:52PM +0200, Jiri Denemark wrote:
I was just trying to say that it doesn't provide anything more than
it's supported by the host CPU, which gives mostly no value in the
context of libvirt. Can you explain
Just to silence Coverity:
Event check_return:
Calling function virBufferTrim(virBufferPtr, char const *, int)
without checking return value (as is done elsewhere 5 out of 6 times).
---
src/node_device/node_device_udev.c | 5 ++---
src/rpc/virnetsshsession.c | 3 +--
2 files changed, 3
Hi,
I am compiling the libvirt from source and I am getting the following error:
Don't forget to
- include gnulib.mk from within gnulib/lib/Makefile.am,
- include gnulib.mk from within gnulib/tests/Makefile.am,
- mention -I gnulib/m4 in ACLOCAL_AMFLAGS in Makefile.am,
- mention
On 06/14/2013 02:34 PM, Viktor Mihajlovski wrote:
Implicit controllers may be dependent on device definitions altered
in a post-parse callback. E.g., if a console device is
defined without the target type, the type will be set in QEMU's
callback. In the case of s390, this is virtio, which
On 17.06.2013 09:21, Nehal J. Wani wrote:
The error:
# ./tools/virsh qemu-agent-command f18
'{execute:guest-network-get-interfaces}'
error: unknown procedure: 3
Comes when I clone from $git clone git://libvirt.org/libvirt.git
But when I download
Fixed virConnect destructor checking for attribute
existance before trying to use it.
Avoids:
Exception AttributeError: AttributeError(virConnect instance has no
attribute 'domainEventCallbacks',) in bound method virConnect.__del__
of libvirt.virConnect instance at 0x4280f38 ignored
However,
Bump!
Also:
31/05/13 16:23, Fred A. Kemp wrote:
For reference, my first attempt at a patch for this feature was:
1363682454-32012-1-git-send-email-ano...@lavabit.com
On second thought, an archive link might be a better reference for
people that doesn't keep old emails in the inbox for very
I was able to solve the error. It was a stupid mistake. There was a
mismatch between versions of virsh and the libvirt daemon.
On Mon, Jun 17, 2013 at 3:56 PM, Michal Privoznik mpriv...@redhat.comwrote:
On 17.06.2013 09:21, Nehal J. Wani wrote:
The error:
# ./tools/virsh qemu-agent-command
On 16.06.2013 23:45, Doug Goldstein wrote:
In the first if case, virGetUserEnt() isn't necessary so don't bother
calling it before determining we need it.
---
Found this trying to get libvirtd running happily on my Mac OS X machine
for qemu. Unfortunately it appears virGetUserEnt() is always
On 17.06.2013 10:34, Ján Tomko wrote:
Just to silence Coverity:
Event check_return:
Calling function virBufferTrim(virBufferPtr, char const *, int)
without checking return value (as is done elsewhere 5 out of 6 times).
---
src/node_device/node_device_udev.c | 5 ++---
On 06/17/2013 02:15 PM, Michal Privoznik wrote:
On 17.06.2013 10:34, Ján Tomko wrote:
Just to silence Coverity:
Event check_return:
Calling function virBufferTrim(virBufferPtr, char const *, int)
without checking return value (as is done elsewhere 5 out of 6 times).
---
On 17.06.2013 14:53, Ján Tomko wrote:
On 06/17/2013 02:15 PM, Michal Privoznik wrote:
On 17.06.2013 10:34, Ján Tomko wrote:
Just to silence Coverity:
Event check_return:
Calling function virBufferTrim(virBufferPtr, char const *, int)
without checking return value (as is done elsewhere 5 out
Implicit controllers may be dependent on device definitions altered
in a post-parse callback. Specifically, if a console device is
defined without the target type, the type will be set in QEMU's
callback. In the case of s390, this is virtio, which requires
an implicit virtio-serial controller.
For s390 the default console target type is virtio. This also requires
that an implicit virtio-serial controller is instantiated.
This testcase verifies that the target type of virtio is correctly set
in the generated XML if no target element was given and that the
corresponding virtio-serial
Implicit controllers may be dependent on device definitions altered
in a post-parse callback. E.g., if a console device is
defined without the target type, the type will be set in QEMU's
callback. In the case of s390, this is virtio, which requires
an implicit virtio-serial controller.
By moving
Hi all:
Work with virsh CLI, I can easy use the CLI virsh -c
qemu+tcp://127.0.0.1/system domdisplay instance-0001 successfully:
[root@webmintest ~]# virsh -c qemu+tcp://127.0.0.1/system domdisplay
instance-0001
Please enter your authentication name: fred
Please enter your
On 17.06.2013 17:19, mzawdx wrote:
Hi all:
Work with virsh CLI, I can easy use the CLI virsh -c
qemu+tcp://127.0.0.1/system domdisplay instance-0001 successfully:
[root@webmintest ~]# virsh -c qemu+tcp://127.0.0.1/system domdisplay
instance-0001
Please enter your
F20/rawhide has will support this.
From: Peter Robinson pbrobin...@gmail.com
---
libvirt.spec.in | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/libvirt.spec.in b/libvirt.spec.in
index 8d43e6d..e357a3d 100644
--- a/libvirt.spec.in
+++ b/libvirt.spec.in
@@ -54,7 +54,11 @@
Are there any comments on this iteration?
On Thu, 2013-05-23 at 18:12 +0100, james robson wrote:
This patch adds functionality to allow libvirt to configure the
'native-tagged' and 'native-untagged' modes on openvswitch networks.
v2 changes:
Fix problems reported by Eric Blake
v3
On 06/17/2013 01:56 PM, james robson wrote:
Are there any comments on this iteration?
Sorry, it somehow got lost in my unread list mail. I'll do my best to
review it before the end of the week.
On Thu, 2013-05-23 at 18:12 +0100, james robson wrote:
This patch adds functionality to allow
28 matches
Mail list logo
