On 10/14/2014 01:28 PM, Jan-Frode Myklebust wrote:
On Wed, Oct 08, 2014 at 09:49:35AM +0200, Jiri Denemark wrote:
Technically you are correct and even QEMU added this feature to Westmere
in April 2013. However, our goal is to provide stable virtual hardware
that doesn't change when, e.g., a
supportedProtocols = ['2.2', '2.3']
supportedRHEVMs = ['3.0']
uuid = 49434D53-0200-9066-2500-66902500E853_00:25:90:66:53:E8
version_name = Snow Man
vlans = {}
vmTypes = ['kvm']
Птн 04 Май 2012 09:14:22 +0400, Itamar Heim ih...@redhat.com написал:
On 05/04/2012 06:49 AM, Nicholas Kesick wrote:
I managed
On 03/12/2012 10:19 PM, Ayal Baron wrote:
- Original Message -
On 03/12/2012 02:12 PM, Itamar Heim wrote:
On 03/12/2012 09:01 PM, Anthony Liguori wrote:
It's a trade off. From a RAS perspective, it's helpful to have
information about the host available in the guest.
If you're
On 03/11/2012 05:33 PM, Anthony Liguori wrote:
On 03/11/2012 09:56 AM, Gleb Natapov wrote:
On Sun, Mar 11, 2012 at 09:12:58AM -0500, Anthony Liguori wrote:
-cpu best wouldn't solve this. You need a read/write configuration
file where QEMU probes the available CPU and records it to be used
for
On 03/12/2012 09:01 PM, Anthony Liguori wrote:
On 03/12/2012 01:53 PM, Itamar Heim wrote:
On 03/11/2012 05:33 PM, Anthony Liguori wrote:
On 03/11/2012 09:56 AM, Gleb Natapov wrote:
On Sun, Mar 11, 2012 at 09:12:58AM -0500, Anthony Liguori wrote:
-cpu best wouldn't solve this. You need a read
On 03/12/2012 09:50 PM, Anthony Liguori wrote:
On 03/12/2012 02:12 PM, Itamar Heim wrote:
On 03/12/2012 09:01 PM, Anthony Liguori wrote:
It's a trade off. From a RAS perspective, it's helpful to have
information about the host available in the guest.
If you're already exposing a compatible
Original Message
Subject: oVirt Beijing - March 21st
Date: Fri, 03 Feb 2012 15:52:41 -0500
From: Carl Trieloff cctriel...@redhat.com
Spread the word/ come join us!
http://www.ovirt.org/news-and-events/workshop/
Carl
--
libvir-list mailing list
libvir-list@redhat.com
-Original Message-
From: libvir-list-boun...@redhat.com
[mailto:libvir-list-boun...@redhat.com] On Behalf Of Daniel Veillard
Sent: Thursday, June 09, 2011 16:20 PM
To: libvir-list@redhat.com
Subject: [libvirt] Availability of patchchecker
As some may have noticed, I'm often
From: libvir-list-boun...@redhat.com
[mailto:libvir-list-boun...@redhat.com]
On Behalf Of Daniel P. Berrange
...
Could containers make isolation exceptions for
- shared storage devices?
- shared /var/run/sync_manager/watchdog/ so that the system watchdog
could monitor all sync_manager
From: libvir-list-boun...@redhat.com [mailto:libvir-list-
boun...@redhat.com] On Behalf Of Daniel P. Berrange
...
A command would be something like this:
sync_manager daemon -i host_id -n vm_id -l lease -c command
args
host_id is integer between 1 and 2000 that is statically
From: libvir-list-boun...@redhat.com [mailto:libvir-list-
Hi,
This is an attempt to provide similar flexibility to CPU ID masking
without
being x86-specific and unfriendly to users. As suggested by Dan, we need
a
way
to specify both CPU flags and topology to achieve this goal.
From: libvir-list-boun...@redhat.com [mailto:libvir-list-
boun...@redhat.com] On Behalf Of Matthias Bolte
The VMX entry ethernet0.addressType may be set to 'vpx' beside
'static' and 'generated'. 'vpx' indicates that the MAC address was
generated by a vCenter.
The attached patch adds
From: Matthias Bolte [mailto:matthias.bo...@googlemail.com]
...
The ESX driver parses the VMX file of a virtual machine to gather the
information needed for the dump XML function. The VMX entry
ethernet0.addressType maybe set to vpx if the generated MAC address
was generated by a vCenter
From: libvir-list-boun...@redhat.com [mailto:libvir-list-
boun...@redhat.com] On Behalf Of Chris Lalancette
...
2) virsh on the controller connects to the src, and initiates the
migration
command. In turn, this causes the controller to also connect to the
dst. Now,
during the Prepare
From: libvir-list-boun...@redhat.com [mailto:libvir-list-
boun...@redhat.com] On Behalf Of Daniel P. Berrange
...
c) libvirtd is using SASL gssapi on the dst machine. When the src
machine tries
to connect to the dst, it needs to have the right configuration (i.e.
/etc/krb5.conf and
From: libvir-list-boun...@redhat.com [mailto:libvir-list-
boun...@redhat.com] On Behalf Of David Lutterkort
...
In particular, if you are part of the management system, you have a
much
better idea (on the node) what it means to have a working network
configuration, and can recover from
From: libvir-list-boun...@redhat.com [mailto:libvir-list-
boun...@redhat.com] On Behalf Of Daniel J Walsh
I think labeling can be done to allow the access to directories, and
files. So libvirt could go in an label a file/directory in such a way
that the running qemu_t:s0.c10 can read or
Thanks!
I assume the tests were added as well apart from the patch?
-Original Message-
From: Daniel Veillard [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 11, 2008 13:45 PM
To: Itamar Heim
Cc: Libvir-list@redhat.com
Subject: Re: [libvirt] [PATCH] add fullscreen support to qemu
variables)
-Original Message-
From: Daniel Veillard [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 10, 2008 9:49 AM
To: Itamar Heim
Cc: Libvir-list@redhat.com
Subject: Re: [libvirt] [PATCH] add fullscreen support to qemu sdl xml
(via fullscreen='true' attribute for the graphics
-Original Message-
From: Daniel Veillard [mailto:[EMAIL PROTECTED]
Looks overall fine to me, the syntactic construct sounds generic
enough.
I would still suggest 2 more changes:
- in virDomainGraphicsDefParseXML check the values coming from
the XML, I guess we should
-Original Message-
From: Daniel P. Berrange [mailto:[EMAIL PROTECTED]
In this bit of the code:
diff --git a/src/domain_conf.h b/src/domain_conf.h
index 51cf6d5..436d0b1 100644
--- a/src/domain_conf.h
+++ b/src/domain_conf.h
@@ -268,6 +268,7 @@ struct _virDomainGraphicsDef {
diff --git a/src/domain_conf.c b/src/domain_conf.c
index 32ed59f..018d07f 100644
--- a/src/domain_conf.c
+++ b/src/domain_conf.c
@@ -212,6 +212,7 @@ void virDomainGraphicsDefFree(virDomainGraphicsDefPtr
def)
case VIR_DOMAIN_GRAPHICS_TYPE_SDL:
VIR_FREE(def-data.sdl.display);
-Original Message-
From: Daniel P. Berrange [mailto:[EMAIL PROTECTED]
...
Basically take a look at libvirt.spec.in and make sure you
have all the 'BuildRequires lines installed
[IH] done that. Added the following list.
xen-devel libxml2-devel gnutls-devel cyrus-sasl-devel cvs
to a higher level of gcc
in fc10?
-Original Message-
From: Itamar Heim [mailto:[EMAIL PROTECTED]
Sent: Friday, December 05, 2008 1:26 AM
To: 'Daniel P. Berrange'
Cc: 'Libvir-list@redhat.com'
Subject: RE: [libvirt] broken pipe?
-Original Message-
From: Daniel P. Berrange
: Wednesday, December 03, 2008 11:28 AM
To: Itamar Heim
Cc: Libvir-list@redhat.com
Subject: Re: [libvirt] broken pipe?
On Wed, Dec 03, 2008 at 02:25:58AM -0500, Itamar Heim wrote:
As no one answered my previous problem., I'm trying to build latest
libvirt to be able to be more productive
/site-packages/libvirt.py, line 12, in
module
import cygvirtmod as libvirtmod
ImportError: No module named cygvirtmod
Thanks,
Itamar
Thanks,
Itamar
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Itamar Heim
Sent: Tuesday, December 02, 2008 1:08 AM
Hi,
I have a problem with a small python script (using fedora 10 with its
shipped rpm's - libvirt-0.4.6-3.fc10.x86_64,
libvirt-python-0.4.6-3.fc10.x86_64)
I'm running a simple stupid libvirt python script.
I happen to want to use SDL, and it fails on Could not initialize SDL -
exiting.
(and not relevant for images under
LVM for example)
Itamar
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Perry Myers
Sent: Tuesday, October 21, 2008 15:37 PM
To: Itamar Heim
Cc: libvir-list@redhat.com
Subject: Re: [libvirt] image locking?
In an oVirt network
there as well, just as a collaborative effort to notate to the
non-responding node to stop writing to the image).
-Original Message-
From: Perry Myers [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 21, 2008 21:09 PM
To: Itamar Heim
Cc: libvir-list@redhat.com
Subject: Re: [libvirt] image
Hi,
I am interested to find out how libvirt envisions image locking.
i.e., how do we make sure multiple nodes are not trying to access the
same storage volume, probably causing image corruption.
I know this can be solved by means of a cluster, but it seems excessive
(and not possible in
: Wednesday, October 15, 2008 21:59 PM
To: Itamar Heim
Cc: libvir-list@redhat.com
Subject: Re: [libvirt] image locking?
On Wed, Oct 15, 2008 at 10:23:03AM -0700, Itamar Heim wrote:
Hi,
I am interested to find out how libvirt envisions image locking.
i.e., how do we make sure multiple nodes
31 matches
Mail list logo
