On Thu, Oct 18, 2012 at 09:34:17PM -0600, Eric Blake wrote:
On 10/18/2012 05:24 PM, Guido Günther wrote:
If we can't probe the architecture from QMP we parse the architecture
from the qemu binaries name. This results in the architecture being i386
instead of i686 which then results in
Currently consumers of libvirt's APIs must assume/attempt to define a
VM that uses spice, vnc, or sdl without knowing if the actual
hypervisor supports it. Obviously my discussion is very QEMU oriented
but it would be good to leave expansion for the future. I was thinking
that under the guest
On 19.10.2012 08:31, Doug Goldstein wrote:
Currently consumers of libvirt's APIs must assume/attempt to define a
VM that uses spice, vnc, or sdl without knowing if the actual
hypervisor supports it. Obviously my discussion is very QEMU oriented
but it would be good to leave expansion for the
As we switched to setting capabilities based on QMP communication,
qemu seamless-migration capability was not set. In the -help output
this knob is called seamless-migration=[on|off]. The equivalent in
QMP world is SPICE_MIGRATE_COMPLETED event (qemu upstream commit
2fdd16e2).
---
On 10/19/2012 05:45 AM, Osier Yang wrote:
On 2012年10月17日 23:38, Martin Kletzander wrote:
According to our recent changes (clarifications), we should be pinning
qemu's emulator processes using thevcpu 'cpuset' attribute in case
there is noemulatorpin specified. This however doesn't work
Relabeling tapfd right after the tap device is created.
qemuPhysIfaceConnect is common function called both for static
netdevs and for hotplug netdevs.
---
src/qemu/qemu_command.c | 18 ++
1 file changed, 14 insertions(+), 4 deletions(-)
diff --git a/src/qemu/qemu_command.c
On 10/19/2012 06:02 AM, Osier Yang wrote:
On 2012年10月18日 21:51, Martin Kletzander wrote:
Commit ba63d8f7d843461f77a8206c1ef9da38388713e5 introduced a bug that
makes machines, that don't have either cpuset invcpu or
emulatorpin specified, fail. Because the function that sets
affinity is
Am 18.10.2012 23:37, schrieb Corey Bryant:
On 10/18/2012 04:43 PM, Eric Blake wrote:
On 10/18/2012 01:19 PM, Corey Bryant wrote:
This option can be used for passing file descriptors on the
command line. It mirrors the existing add-fd QMP command which
allows an fd to be passed to QEMU
BW == Benjamin Wang (gendwang) gendw...@cisco.com writes:
BW Hi, When I changed code as following:
BW public class Connect {
BW // Load the native part
BW static {
BW Libvirt.INSTANCE.virInitialize();
BW try {
BW
Hi,
I am using JNA 3.4.1. The problem is caused by libvirt java. You are right.
B.R.
Benjamin Wang
-Original Message-
From: Claudio Bley [mailto:cb...@av-test.de]
Sent: 2012年10月19日 19:36
To: Benjamin Wang (gendwang)
Cc: libvir-list@redhat.com; Guannan Ren; Daniel Veillard; Yang Zhou
Recently, patches were added support for (managed)saving, restoring, and
migrating domains with host USB devices. However, qemu driver would
still forbid migration of such domains because qemuMigrationIsAllowed
was not updated.
---
src/qemu/qemu_migration.c | 22 +++---
1 file
On 19.10.2012 14:21, Jiri Denemark wrote:
Recently, patches were added support for (managed)saving, restoring, and
migrating domains with host USB devices. However, qemu driver would
still forbid migration of such domains because qemuMigrationIsAllowed
was not updated.
---
On Fri, Oct 19, 2012 at 14:37:57 +0200, Michal Privoznik wrote:
On 19.10.2012 14:21, Jiri Denemark wrote:
Recently, patches were added support for (managed)saving, restoring, and
migrating domains with host USB devices. However, qemu driver would
still forbid migration of such domains
On 10/19/2012 07:05 AM, Kevin Wolf wrote:
Am 18.10.2012 23:37, schrieb Corey Bryant:
On 10/18/2012 04:43 PM, Eric Blake wrote:
On 10/18/2012 01:19 PM, Corey Bryant wrote:
This option can be used for passing file descriptors on the
command line. It mirrors the existing add-fd QMP command
Having hostuuid in migration cookie is a nice bonus since it provides an
easy way of detecting migration to the same host. However, requiring it
breaks backward compatibility with older libvirt releases.
---
src/qemu/qemu_migration.c | 31 ---
1 file changed, 16
On 19.10.2012 16:31, Jiri Denemark wrote:
Having hostuuid in migration cookie is a nice bonus since it provides an
easy way of detecting migration to the same host. However, requiring it
breaks backward compatibility with older libvirt releases.
---
src/qemu/qemu_migration.c | 31
In v2 migration protocol, XML is obtained by calling domainGetXMLDesc.
This includes the default USB controller in XML, which breaks migration
to older libvirt (before 0.9.2).
Commit 409b5f549530e7b3a33f4505f2cad2e26896107c
qemu: Emit compatible XML when migrating a domain
only fixed this for
On Fri, Oct 19, 2012 at 16:53:38 +0200, Michal Privoznik wrote:
On 19.10.2012 16:31, Jiri Denemark wrote:
Having hostuuid in migration cookie is a nice bonus since it provides an
easy way of detecting migration to the same host. However, requiring it
breaks backward compatibility with older
On Thu, Oct 18, 2012 at 3:48 PM, Laine Stump la...@laine.org wrote:
On 10/17/2012 06:30 PM, Eric Blake wrote:
This v3 posting resolves all the comments I had from Doug, Laine,
and myself, and has passed my testing with SELinux enabled.
v2 was here:
On 10/19/2012 04:44 AM, Guannan Ren wrote:
Relabeling tapfd right after the tap device is created.
qemuPhysIfaceConnect is common function called both for static
netdevs and for hotplug netdevs.
---
src/qemu/qemu_command.c | 18 ++
1 file changed, 14 insertions(+), 4
On 10/19/2012 11:55 PM, Laine Stump wrote:
On 10/19/2012 04:44 AM, Guannan Ren wrote:
Relabeling tapfd right after the tap device is created.
qemuPhysIfaceConnect is common function called both for static
netdevs and for hotplug netdevs.
---
src/qemu/qemu_command.c | 18 ++
1
On 10/11/2012 03:15 PM, Viktor Mihajlovski wrote:
On 10/11/2012 02:27 PM, Eric Blake wrote:
That starts to feel rather complex.
well :-)
On the other hand, you have a point that returning maplen (number of
bytes allocated in the map) does NOT tell you how many cpus are online
without doing
On 10/18/2012 10:09 PM, Osier Yang wrote:
nodeinfo is not used in these two functions, and it's waste
of goto in qemuProcessSetEmulatorAffinites
---
src/qemu/qemu_process.c | 20
1 files changed, 4 insertions(+), 16 deletions(-)
ACK.
--
Eric Blake
On 10/18/2012 09:33 PM, Eric Blake wrote:
On 10/18/2012 05:20 PM, Cole Robinson wrote:
AUTHORS.in tracks the maintainers, as well as some folks who were
previously in AUTHORS but don't have a git commit with proper
attribution.
Generated output is sorted alphabetically and lacks pretty
On 10/19/2012 12:14 PM, Eric Blake wrote:
On 10/18/2012 09:33 PM, Eric Blake wrote:
On 10/18/2012 05:20 PM, Cole Robinson wrote:
AUTHORS.in tracks the maintainers, as well as some folks who were
previously in AUTHORS but don't have a git commit with proper
attribution.
Generated output is
On 10/19/2012 01:04 AM, Gene Czarcinski wrote:
The problem is that, without SO_BINDTODEVICE, there is no guarantee
that the kernel will route DHCP (v4 or v6) packets to the correct
instance of dnsmasq, when there is more than one.
Thanks for taking the time to investigate this (and the
https://bugzilla.redhat.com/show_bug.cgi?id=866364
pointed out a crash due to virNetworkObjAssignDef free'ing
network-newDef without NULLing it afterward. A fix for this is in
upstream commit b7e9202401ebaa039b8f05acdefda8c24081537a. While the
NULLing of newDef was a legitimate fix, newDef should
Several tests assume that VNC is always available and include it in
their configs and the expected command line. The tests have nothing to
do with graphics display so they shouldn't rely on VNC.
---
tests/qemuxml2argvdata/qemuxml2argv-bios.args |6 +++---
Currently its assumed that qemu always supports VNC, however it is
definitely possible to compile qemu without VNC support so we should at
the very least check for it and handle that correctly.
---
src/qemu/qemu_capabilities.c |5
src/qemu/qemu_capabilities.h |1 +
This is the initial series where I'll be exposing the graphical support that
QEMU has via capabilities but I'm breaking it up to get in as much as possible
based on my available time.
This initial set adds checks to see that your QEMU binary has VNC support
instead of assuming that it does. A
On 10/19/2012 11:34 AM, Laine Stump wrote:
https://bugzilla.redhat.com/show_bug.cgi?id=866364
pointed out a crash due to virNetworkObjAssignDef free'ing
network-newDef without NULLing it afterward. A fix for this is in
upstream commit b7e9202401ebaa039b8f05acdefda8c24081537a. While the
On 10/18/2012 12:50 PM, Laine Stump wrote:
On 10/17/2012 06:30 PM, Eric Blake wrote:
Previously, snapshot code did its own permission granting (lock
manager, cgroup device controller, and security manager labeling)
inline. But now that we are adding block-commit and block-copy
which also
On 10/17/2012 04:30 PM, Eric Blake wrote:
This v3 posting resolves all the comments I had from Doug, Laine,
and myself, and has passed my testing with SELinux enabled.
v2 was here:
https://www.redhat.com/archives/libvir-list/2012-October/msg00633.html
See below for interdiff, and individual
Gcc with optimization warns:
../../src/qemu/qemu_driver.c: In function 'qemuDomainBlockCommit':
../../src/qemu/qemu_driver.c:12813:46: error: 'disk' may be used uninitialized
in this function [-Werror=maybe-uninitialized]
../../src/qemu/qemu_driver.c:12698:25: note: 'disk' was declared here
cc1:
34 matches
Mail list logo
