在 2012-10-18四的 01:03 -0500，Doug Goldstein写道：
> On Thu, Oct 18, 2012 at 12:47 AM, li guang wrote:
> > 在 2012-10-17三的 21:50 -0500，Doug Goldstein写道：
> >> On Sun, Oct 14, 2012 at 9:48 PM, liguang wrote:
> >> > help to create disk images copy-storage-* required,
> >> > try to do non-shared migration w
On Wed, Oct 17, 2012 at 7:42 PM, liguang wrote:
> original migration did not aware of offline case,
> so, try to support offline migration quietly
> (did not disturb original migration) by pass
> VIR_MIGRATE_OFFLINE flag to migration APIs if only
> the domain is really inactive, and
> migration pr
On Thu, Oct 18, 2012 at 1:06 AM, Doug Goldstein wrote:
> Supports migrating a domain that is currently inactive. This patchset
> adds a new migration flag called VIR_MIGRATE_OFFLINE, which can only be
> used on domains that are inactive. Offline migration does not support
> copying non-shared stor
Supports migrating a domain that is currently inactive. This patchset
adds a new migration flag called VIR_MIGRATE_OFFLINE, which can only be
used on domains that are inactive. Offline migration does not support
copying non-shared storage in any case.
---
src/qemu/qemu_driver.c| 29 +
On Thu, Oct 18, 2012 at 12:47 AM, li guang wrote:
> 在 2012-10-17三的 21:50 -0500，Doug Goldstein写道：
>> On Sun, Oct 14, 2012 at 9:48 PM, liguang wrote:
>> > help to create disk images copy-storage-* required,
>> > try to do non-shared migration without bothering to
>> > create disk images at target b
在 2012-10-17三的 21:50 -0500，Doug Goldstein写道：
> On Sun, Oct 14, 2012 at 9:48 PM, liguang wrote:
> > help to create disk images copy-storage-* required,
> > try to do non-shared migration without bothering to
> > create disk images at target by hand.
> >
> > consider this situation:
> > 1. non-share
于 2012年10月16日 20:23, Daniel P. Berrange 写道:
> On Mon, Oct 08, 2012 at 08:43:28AM +0800, Gao feng wrote:
>> 于 2012年09月26日 02:37, Daniel P. Berrange 写道:
>>> On Tue, Sep 11, 2012 at 10:54:48AM +0800, Gao feng wrote:
this patch addes fuse support for libvirt lxc.
we can use fuse filesystem to
On Sun, Oct 14, 2012 at 9:48 PM, liguang wrote:
> help to create disk images copy-storage-* required,
> try to do non-shared migration without bothering to
> create disk images at target by hand.
>
> consider this situation:
> 1. non-shared migration
>virsh migrate --copy-storage-all ...
> 2.
ping ...
在 2012-10-15一的 10:48 +0800，liguang写道：
> help to create disk images copy-storage-* required,
> try to do non-shared migration without bothering to
> create disk images at target by hand.
>
> consider this situation:
> 1. non-shared migration
>virsh migrate --copy-storage-all ...
> 2.
On 10/17/2012 06:09 PM, Laine Stump wrote:
> On 10/16/2012 06:03 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
original migration did not aware of offline case,
so, try to support offline migration quietly
(did not disturb original migration) by pass
VIR_MIGRATE_OFFLINE flag to migration APIs if only
the domain is really inactive, and
migration process will not puzzled by domain
offline and exit unexpectedl
On 10/16/2012 06:03 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 have to change permissions, it's better to r
Hi,
http://www.redhat.com/archives/libvir-list/2012-January/msg00629.html
added support only for when using the virtio channel to the guest.
However, QEMU Guest Agent support is most useful to guests that do
not implement ACPI shutdown support; these usually don’t have virtio
(especially since I
On 10/17/2012 08:48 AM, Viktor Mihajlovski wrote:
> The machine in the last output line of -M ?
> was always reported as default machine even if this wasn't the
> actual default. Trivial fix.
>
> Signed-off-by: Viktor Mihajlovski
> ---
> src/qemu/qemu_capabilities.c |2 +-
> 1 files changed
On 10/17/2012 07:54 AM, Peter Krempa wrote:
> This patch adds support for the "relaxed" feature implemented by
> previous patch.
> ---
> src/qemu/qemu_command.c | 38
> +
> tests/qemuxml2argvdata/qemuxml2argv-hyperv.args | 4 +++
> tests/qemuxml2ar
On 10/17/2012 07:54 AM, Peter Krempa wrote:
> Hypervisors are starting to support HyperV englightenment features that
> improve behavior of guests running Microsoft Windows operating systems.
s/englightenment/enlightenment/
>
> This patch adds support for the "relaxed" feature that improves time
On 10/17/2012 07:54 AM, Peter Krempa wrote:
> The apic-eoi feature enum and implementation can be made more universal
> to allow re-use of the enum for other features.
> ---
> src/conf/domain_conf.c | 6 +++---
> src/conf/domain_conf.h | 14 +++---
> src/libvirt_private.syms | 4 ++--
qemu 1.3 will be adding a 'block-commit' monitor command, per
qemu.git commit ed61fc1. It matches nicely to the libvirt API
virDomainBlockCommit.
* src/qemu/qemu_capabilities.h (QEMU_CAPS_BLOCK_COMMIT): New bit.
* src/qemu/qemu_capabilities.c (qemuCapsProbeQMPCommands): Set it.
* src/qemu/qemu_mo
Now that we can crawl the chain of backing files, we can do
argument validation and implement the 'shallow' flag. In
testing this, I discovered that it can be handy to pass the
shallow flag and an explicit base, as a means of validating
that the base is indeed the file we expected.
* src/qemu/qem
Minor cleanup made possible by previous simplifications.
* src/qemu/qemu_cgroup.h (qemuSetupDiskCgroup)
(qemuTeardownDiskCgroup): Alter signature.
* src/qemu/qemu_cgroup.c (qemuSetupDiskCgroup)
(qemuTeardownDiskCgroup, qemuSetupCgroup): Update all uses.
* src/qemu/qemu_hotplug.c (qemuDomainDetachP
We used to walk the backing file chain at least twice per disk,
once to set up cgroup device whitelisting, and once to set up
security labeling. Rather than walk the chain every iteration,
which possibly includes calls to fork() in order to open root-squashed
NFS files, we can exploit the cache of
In order to temporarily label files read/write during a commit
operation, we need to crawl the backing chain and find the absolute
file name that needs labeling in the first place, as well as the
name of the file that owns the backing file.
* src/util/storage_file.c (virStorageFileChainLookup): Ne
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 have to change permissions, it's better to reuse
common code for the task. While snapshot sho
Technically, we should not be re-probing any file that qemu might
be currently writing to. As such, we should cache the backing
file chain prior to starting qemu. This patch adds the cache,
but does not use it until the next patch.
Ultimately, we want to also store the chain in domain XML, so th
This is the bare minimum to kick off a block commit. In particular,
flags support is missing (shallow requires us to crawl the backing
chain to determine the file name to pass to the qemu monitor command;
delete requires us to track what needs to be deleted at the time
the completion event fires).
I finally have all the pieces in place to perform a block-commit with
SELinux enforcing. There's still missing cleanup work when the commit
completes, but doing that requires tracking both the backing chain and
the base and top files within that chain in domain XML across libvirtd
restarts. Furth
In order to search for a backing file name as literally present
in a chain, we need to remember if the chain had relative names.
Also, searching for absolute names is easier if we only have
to canonicalize once, rather than on every iteration.
* src/util/storage_file.h (_virStorageFileMetadata): A
Requiring pre-allocation was an unusual idiom. It allowed iteration
over the backing chain to use fewer mallocs, but made one-shot
clients harder to read. Also, this makes it easier for a future
patch to move away from opening fds on every iteration over the chain.
* src/util/storage_file.h (vir
At one point, the code passed through arbitrary strings for file
formats, which supposedly lets qemu handle a new file type even
before libvirt has been taught to handle it. However, to properly
label files, libvirt has to learn the file type anyway, so we
might as well make our life easier by onl
Actually use the enum in the domain conf structure.
* src/conf/domain_conf.h (_virDomainDiskDef): Store enum rather
than string for disk type.
* src/conf/domain_conf.c (virDomainDiskDefFree)
(virDomainDiskDefParseXML, virDomainDiskDefFormat)
(virDomainDiskDefForeachPath): Adjust users.
* src/xenxs
When an image has no backing file, using VIR_STORAGE_FILE_AUTO
for its type is a bit confusing. Additionally, a future patch
would like to reserve a default value for the case of no file
type specified in the XML, but different from the current use
of -1 to imply probing, since probing is not alwa
Backing chains can end on a network protocol, such as nbd:xxx; we
should not attempt to probe the file system in this case.
* src/storage/storage_backend_fs.c (virStorageBackendProbeTarget):
Only probe files.
---
src/storage/storage_backend_fs.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletio
This is the last use of raw strings for disk formats throughout
the src/conf directory.
* src/conf/snapshot_conf.h (_virDomainSnapshotDiskDef): Store enum
rather than string for disk type.
* src/conf/snapshot_conf.c (virDomainSnapshotDiskDefClear)
(virDomainSnapshotDiskDefParseXML, virDomainSnapsh
Previously, no one was using virStorageFileGetMetadata, and for good
reason - it couldn't support root-squash NFS. Change the signature
and make it useful to future patches, including enhancing the metadata
to recursively track the entire chain.
* src/util/storage_file.h (_virStorageFileMetadata)
We have historically allowed 'aio' as a synonym for 'raw' for
back-compat to xen, but since a future patch will move to using
an enum value, we have to pick one to be our preferred output
name. This is a slight change in the output XML, but the sexpr
and xm outputs should still be identical, and t
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 patches for more notes
about changes
Also avail
Express the default disk type as an enum, for easier handling.
* src/conf/capabilities.h (_virCaps): Store enum rather than
string for disk type.
* src/conf/domain_conf.c (virDomainDiskDefParseXML): Adjust
clients.
* src/qemu/qemu_driver.c (qemuCreateCapabilities): Likewise.
---
src/conf/capabili
On 10/17/2012 03:28 PM, Laine Stump wrote:
> On 10/13/2012 06:00 PM, Eric Blake wrote:
>> Now that we can crawl the chain of backing files, we can do
>> argument validation and implement the 'shallow' flag. In
>> testing this, I discovered that it can be handy to pass the
>> shallow flag and an ex
On 10/17/2012 03:06 PM, Dusty Mabe wrote:
> Hi,
>
> Would it be possible to augment the output produced in virsh
> capabilities to also provide the hyperthreaded sibling of a processor?
> For example the information would look something like:
>
>
>
>
>
>
>
>
On 10/13/2012 06:00 PM, Eric Blake wrote:
> Now that we can crawl the chain of backing files, we can do
> argument validation and implement the 'shallow' flag. In
> testing this, I discovered that it can be handy to pass the
> shallow flag and an explicit base, as a means of validating
> that the
On 10/16/2012 03:16 PM, Eric Blake wrote:
>>> +if (disk->format > 0)
>>> +format = disk->format;
>>> +else if (ctl->allowDiskFormatProbing)
>>> +format = VIR_STORAGE_FILE_AUTO;
>>> +else
>>> +format = VIR_STORAGE_FILE_RAW;
>>
>> It seems
On 10/13/2012 06:00 PM, Eric Blake wrote:
> This is the bare minimum to kick off a block commit. In particular,
> flags support is missing (shallow requires us to crawl the backing
> chain to determine the file name to pass to the qemu monitor command;
> delete requires us to track what needs to b
This simplifies the top-level code, at the cost of using a little more
stack space. The primary benefit is being able to send more fields
without knowing in advance how many of them, and of which types, these
fields will be, and without having to individually add buffer variables.
The code impose
When logging an error, don't throw away the detailed information.
Example record when using the journald output:
MESSAGE=Domain not found
PRIORITY=4
LIBVIRT_SOURCE=error
CODE_FILE=../../src/test/test_driver.c
CODE_LINE=1405
CODE_FUNC=testLookupDomain
This is independent from the rest of the series, sending it anyway for
consideration; this makes the metadata available to users on non-systemd
platforms. I believe the technical objections (primarily
async-signal-safety) have been resolved; the question of whether the
project wants to support thi
... and update all users. No change in functionality, the parameter
will be used in the next patch.
Signed-off-by: Miloslav Trmač
---
src/util/logging.c | 14 +-
src/util/logging.h | 2 ++
tests/testutils.c | 1 +
3 files changed, 12 insertions(+), 5 deletions(-)
diff --git a/sr
This is sort of a v2 of the "Structured syslog" series.
Patches 1-4 allow callers virLogMessage to add arbitrary additional data,
and use it in virRaiseErrorFull and its callers. This data is sent
to journal (and ignored for other outputs).
Because the additional fields for errors include virErr
... and update all users. No change in functionality, the parameter
will be used later.
The metadata representation is as minimal as possible, but requires
the caller to allocate an array on stack explicitly.
The alternative of using varargs in the virLogMessage() callers:
* Would not allow the
On 10/17/2012 06:02 PM, Michal Privoznik wrote:
> On 17.10.2012 17:38, Martin Kletzander wrote:
>> According to our recent changes (clarifications), we should be pinning
>> qemu's emulator processes using the 'cpuset' attribute in case
>> there is no specified. This however doesn't work
>> entir
On 10/17/2012 11:39 PM, Laine Stump wrote:
On 10/16/2012 11:32 PM, Guannan Ren wrote:
It should relabel tapfd of virtual network of type VIR_DOMAIN_NET_TYPE_DIRECT
rather than VIR_DOMAIN_NET_TYPE_NETWORK and VIR_DOMAIN_NET_TYPE_BRIDGE
(commit ae368ebfcc4923d0b32e83d4ca96a6f599625785 introduced t
On 17.10.2012 17:38, Martin Kletzander wrote:
> According to our recent changes (clarifications), we should be pinning
> qemu's emulator processes using the 'cpuset' attribute in case
> there is no specified. This however doesn't work
> entirely as expected and this patch should resolve all the
According to our recent changes (clarifications), we should be pinning
qemu's emulator processes using the 'cpuset' attribute in case
there is no specified. This however doesn't work
entirely as expected and this patch should resolve all the remaining
issues.
---
src/qemu/qemu_cgroup.c | 25 ++
Added an implemention of virNodeGetCPUMapFlags to nodeinfo.c,
(nodeGetCPUMapFlags) which can be used by all drivers for a Linux
hypervisor host.
Signed-off-by: Viktor Mihajlovski
---
src/libvirt_private.syms |1 +
src/nodeinfo.c | 49 ++
On 10/16/2012 11:32 PM, Guannan Ren wrote:
> It should relabel tapfd of virtual network of type VIR_DOMAIN_NET_TYPE_DIRECT
> rather than VIR_DOMAIN_NET_TYPE_NETWORK and VIR_DOMAIN_NET_TYPE_BRIDGE
> (commit ae368ebfcc4923d0b32e83d4ca96a6f599625785 introduced this bug)
> ---
> src/qemu/qemu_command.
On 10/17/2012 08:02 AM, Kevin Wolf wrote:
> Am 17.10.2012 06:16, schrieb Eric Blake:
>> I'm still seeing the corner case of:
>>
>> qemu-kvm -add-fd fd=3,set=1 -add-fd fd=4,set=2 4<&-
>>
>> where the dup(3) will populate fd 4 prior to the point where we get to
>> process the -add-fd fd=4 command to
Am 17.10.2012 17:01, schrieb Eric Blake:
> On 10/17/2012 08:02 AM, Kevin Wolf wrote:
>> Am 17.10.2012 06:16, schrieb Eric Blake:
>>> I'm still seeing the corner case of:
>>>
>>> qemu-kvm -add-fd fd=3,set=1 -add-fd fd=4,set=2 4<&-
>>>
>>> where the dup(3) will populate fd 4 prior to the point where
The machine in the last output line of -M ?
was always reported as default machine even if this wasn't the
actual default. Trivial fix.
Signed-off-by: Viktor Mihajlovski
---
src/qemu/qemu_capabilities.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/src/qemu/qemu_capa
Hi,
First, thanks Michal for your review.
Le lundi 15 octobre 2012 à 11:31 -0700, Laine Stump a écrit :
> On 10/15/2012 10:54 AM, Michal Privoznik wrote:
> > On 15.10.2012 12:27, Benjamin Cama wrote:
> >> It allows to specify forwarding only for IPv4 or IPv6. Not specifying it
> >> enables forwar
Hi everyone,
Le lundi 15 octobre 2012 à 09:36 -0700, Cole Robinson a écrit :
> On 10/15/2012 12:04 PM, Cole Robinson wrote:
> > On 10/15/2012 10:54 AM, Michal Privoznik wrote:
> >> On 15.10.2012 12:26, Benjamin Cama wrote:
> >>>
> >>> static int
> >>> networkSetIPv6Sysctls(virNetworkObjPtr net
Am 17.10.2012 06:16, schrieb Eric Blake:
> I'm still seeing the corner case of:
>
> qemu-kvm -add-fd fd=3,set=1 -add-fd fd=4,set=2 4<&-
>
> where the dup(3) will populate fd 4 prior to the point where we get to
> process the -add-fd fd=4 command to notice that the user started
> qemu-kvm with fd
The apic-eoi feature enum and implementation can be made more universal
to allow re-use of the enum for other features.
---
src/conf/domain_conf.c | 6 +++---
src/conf/domain_conf.h | 14 +++---
src/libvirt_private.syms | 4 ++--
src/qemu/qemu_command.c | 6 +++---
4 files changed,
This series adds framework to deal with various HyperV Enlightenment
features that improve behavior of Microsoft Windows guests.
First of the features implemented is "relaxed" that changes
the behavior of timers.
The series is designed to ease addition of other hyperv features in the
future.
Pet
This patch adds support for the "relaxed" feature implemented by
previous patch.
---
src/qemu/qemu_command.c | 38 +
tests/qemuxml2argvdata/qemuxml2argv-hyperv.args | 4 +++
tests/qemuxml2argvdata/qemuxml2argv-hyperv.xml | 28 ++
te
Hypervisors are starting to support HyperV englightenment features that
improve behavior of guests running Microsoft Windows operating systems.
This patch adds support for the "relaxed" feature that improves timer
behavior and also establishes a framework to add these features in
future.
---
docs
On Wed, Oct 17, 2012 at 14:34:25 +0200, Peter Krempa wrote:
> On 10/17/12 14:29, Jiri Denemark wrote:
> > When p2p migration fails early because qemuMigrationIsAllowed or
> > qemuMigrationIsSafe say migration should be cancelled, we fail to clear
> > the migration-out async job. As a result of that
Am 16.10.2012 20:08, schrieb Corey Bryant:
> qmp_add_fd() gets an fd that was received over a socket with
> SCM_RIGHTS and adds it to an fd set. This patch adds support
> that will enable adding an fd that was inherited on the
> command line to an fd set.
>
> Note: All of the code added to monito
On Wed, Oct 17, 2012 at 14:29:04 +0200, Jiri Denemark wrote:
> When p2p migration fails early because qemuMigrationIsAllowed or
> qemuMigrationIsSafe say migration should be cancelled, we fail to clear
> the migration-out async job. As a result of that, further APIs called
> for the same domain may
On 10/17/12 14:29, Jiri Denemark wrote:
When p2p migration fails early because qemuMigrationIsAllowed or
qemuMigrationIsSafe say migration should be cancelled, we fail to clear
the migration-out async job. As a result of that, further APIs called
for the same domain may fail with Timed out during
When p2p migration fails early because qemuMigrationIsAllowed or
qemuMigrationIsSafe say migration should be cancelled, we fail to clear
the migration-out async job. As a result of that, further APIs called
for the same domain may fail with Timed out during operation: cannot
acquire state change lo
On 15.10.2012 00:02, Doug Goldstein wrote:
> Added support for retrieving the XML defining a specific interface via
> the udev based backend to virInterface. Implement the following APIs
> for the udev based backend:
> * virInterfaceGetXMLDesc()
>
> Note: Does not support bond devices.
> ---
> sr
On 10/17/2012 04:30 PM, Daniel P. Berrange wrote:
On Wed, Oct 17, 2012 at 11:32:45AM +0800, Guannan Ren wrote:
It should relabel tapfd of virtual network of type VIR_DOMAIN_NET_TYPE_DIRECT
rather than VIR_DOMAIN_NET_TYPE_NETWORK and VIR_DOMAIN_NET_TYPE_BRIDGE
(commit ae368ebfcc4923d0b32e83d4ca96
V2 Changes:
Added python binding for virNodeGetCPUMapFlags.
Removed RFC stanza.
---
Viktor Mihajlovski (9):
virNodeGetCPUMapFlags: Define public API.
virNodeGetCPUMapFlags: Define driver API.
virNodeGetCPUMapFlags: Implement public API.
virNodeGetCPUMapFlags: Implement wire protocol.
- Defined the wire protocol format for virNodeGetCPUMapFlags and its
arguments
- Implemented remote method invocation (remoteNodeGetCPUMapFlags)
- Implemented method dispacher (remoteDispatchNodeGetCPUMapFlags)
Signed-off-by: Viktor Mihajlovski
---
daemon/remote.c | 44 +
On 10/17/2012 11:31 AM, Daniel P. Berrange wrote:
> From: "Daniel P. Berrange"
>
> Checking for 'function (...args...)' is quite difficult since it
> needs to ignore valid usage with keywords like 'if (...test...)'
> and while/for/switch. It must also ignore source comments and
> quoted strings.
On 10/17/2012 11:31 AM, Daniel P. Berrange wrote:
> From: "Daniel P. Berrange"
>
> The libvirt coding standard is to use 'function(...args...)'
> instead of 'function (...args...)'. A non-trivial number of
> places did not follow this rule and are fixed in this patch.
>
> Signed-off-by: Daniel P
I've accidentally added Li Zhang to
AUTHORS, even if he already was there.
---
Pushing under trivial rule.
AUTHORS |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/AUTHORS b/AUTHORS
index 221912d..27c4eda 100644
--- a/AUTHORS
+++ b/AUTHORS
@@ -268,7 +268,6 @@ Patches hav
On Wed, Oct 17, 2012 at 4:16 PM, Michal Privoznik wrote:
> On 15.10.2012 11:07, Li Zhang wrote:
>> CPU version can be got by PVR on PowerPC. So this PVR is defined in
>> the CPU data in cpuData structure.
>>
>> Signed-off-by: Li Zhang
>> Acked-by: Michal Privoznik
>
> We tend to write space betwe
From: "Daniel P. Berrange"
Checking for 'function (...args...)' is quite difficult since it
needs to ignore valid usage with keywords like 'if (...test...)'
and while/for/switch. It must also ignore source comments and
quoted strings.
It is not possible todo this with a simple regex in the norma
On Wed, Oct 17, 2012 at 4:21 PM, Michal Privoznik wrote:
> Oh, I've just hit 'Send' without noticing
>
> On 15.10.2012 11:07, Li Zhang wrote:
>> Currently, the CPU model driver is not implemented for PowerPC.
>> Host's CPU information is needed to exposed to guests' XML file some
>> time.
>>
Libvirt normally omits whitespace between the function name and its
args, but there are still approx 1000 places where whitespace is
included. Since people can't follow the style, clean this up and
then enforce it with syntax-check.
--
libvir-list mailing list
libvir-list@redhat.com
https://www.re
On Wed, Oct 17, 2012 at 4:22 PM, Michal Privoznik wrote:
> On 15.10.2012 11:07, Li Zhang wrote:
>> CPU model driver is to get host's CPU information and it also provides
>> one mechanism to expose host's CPU information to guests during migration.
>>
>> When migrating one guest from one machine to
On Wed, Oct 17, 2012 at 11:32:45AM +0800, Guannan Ren wrote:
> It should relabel tapfd of virtual network of type VIR_DOMAIN_NET_TYPE_DIRECT
> rather than VIR_DOMAIN_NET_TYPE_NETWORK and VIR_DOMAIN_NET_TYPE_BRIDGE
> (commit ae368ebfcc4923d0b32e83d4ca96a6f599625785 introduced this bug)
Why ? IMHO,
Oh, I've just hit 'Send' without noticing
On 15.10.2012 11:07, Li Zhang wrote:
> Currently, the CPU model driver is not implemented for PowerPC.
> Host's CPU information is needed to exposed to guests' XML file some
> time.
>
> This patch is to implement the callback functions of CPU model d
On 15.10.2012 11:07, Li Zhang wrote:
> CPU model driver is to get host's CPU information and it also provides
> one mechanism to expose host's CPU information to guests during migration.
>
> When migrating one guest from one machine to another machine, it will
> compare the CPU information. If it
On 15.10.2012 11:07, Li Zhang wrote:
> CPU version can be got by PVR on PowerPC. So this PVR is defined in
> the CPU data in cpuData structure.
>
> Signed-off-by: Li Zhang
> Acked-by: Michal Privoznik
We tend to write space between name and e-mail address.
> ---
> src/cpu/cpu.h |3
On 15.10.2012 11:07, Li Zhang wrote:
> There are some descriptions not right in PowerPC CPU model driver.
> This patch is to fix them.
>
> Signed-off-by: Li Zhang
> Acked-by: Michal Privoznik
> ---
> src/cpu/cpu_powerpc.c |4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
ACK
Mich
On 15.10.2012 11:07, Li Zhang wrote:
> Currently, the CPU model driver is not implemented for PowerPC.
> Host's CPU information is needed to exposed to guests' XML file some
> time.
>
> This patch is to implement the callback functions of CPU model driver.
>
> Signed-off-by: Li Zhang
> ---
> po
87 matches
Mail list logo
