On Fri, Aug 26, 2016 at 21:41:31 +0200, Michal Privoznik wrote:
> On 26.08.2016 11:25, Kothapally Madhu Pavan wrote:
> > Unlike postcopy migration there is no --live flag check for
> > postcopy-after-precopy.
> >
> > Signed-off-by: Kothapally Madhu Pavan
> > ---
> >
On 26.08.2016 11:25, Kothapally Madhu Pavan wrote:
> Unlike postcopy migration there is no --live flag check for
> postcopy-after-precopy.
>
> Signed-off-by: Kothapally Madhu Pavan
> ---
> tools/virsh-domain.c |6 ++
> 1 file changed, 6 insertions(+)
>
ACKed
On 11.08.2016 15:26, Michal Privoznik wrote:
>
Ping.
Michal
--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
On 16.08.2016 17:41, Michal Privoznik wrote:
>
Ping.
Michal
--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
On 19.08.2016 13:54, Michal Privoznik wrote:
>
Ping.
Michal
--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
On Thu, Aug 25, 2016 at 18:42:49 -0400, Peter Krempa wrote:
> Setting vcpu count when cpu topology is specified may result into an
> invalid configuration. Since the topology can't be modified, reject the
> setting if it doesn't match the requested topology. This will allow
> fixing the topology
25-Aug-16 12:25, Mikhail Feoktistov пишет:
On 25.08.2016 11:33, Nikolay Shirokovskiy wrote:
---
src/vz/vz_driver.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/src/vz/vz_driver.c b/src/vz/vz_driver.c
index b34fe33..f223794 100644
--- a/src/vz/vz_driver.c
+++ b/src/vz/vz_driver.c
On Thu, Aug 25, 2016 at 18:42:48 -0400, Peter Krempa wrote:
> Validating the vcpu count is more intricate and doing it in the XML
> parser will make previously valid configs (with older qemus) vanish.
>
> Now that we have the validation callbacks we can do it in a more
> appropriate place.
This
18-Aug-16 14:57, Olga Krishtal пишет:
While dettaching/attaching device in OpenStack, nova
calls vzDomainDettachDevice twice, because the update of the internal
configuration of the ct comes a bit latter than the update event.
As the result, we suffer from the second call to dettach the same
25-Aug-16 11:13, Nikolay Shirokovskiy пишет:
On 15.08.2016 19:02, Mikhail Feoktistov wrote:
We should query bus type for containers too, like for VM.
In openstack we add volume disk like SCSI, so we can't
hardcode SATA bus.
---
src/vz/vz_sdk.c | 32 +---
1 file
25-Aug-16 17:00, Pavel Glushchak пишет:
* Added VIR_MIGRATE_LIVE, VIR_MIGRATE_UNDEFINE_SOURCE and
VIR_MIGRATE_PERSIST_DEST to supported migration flags
Signed-off-by: Pavel Glushchak
---
src/vz/vz_driver.c | 7 +--
1 file changed, 5 insertions(+), 2
25-Aug-16 17:00, Pavel Glushchak пишет:
libvirt-python passes parameter bandwidth = 0
by default. This means that bandwidth is unlimited.
VZ driver doesn't support bandwidth rate limiting,
but we still need to handle it and fail if bandwidth > 0.
Signed-off-by: Pavel Glushchak
25-Aug-16 17:00, Pavel Glushchak пишет:
* Added VIR_MIGRATE_LIVE, VIR_MIGRATE_UNDEFINE_SOURCE and
VIR_MIGRATE_PERSIST_DEST to supported migration flags
Signed-off-by: Pavel Glushchak
---
src/vz/vz_driver.c | 7 +--
1 file changed, 5 insertions(+), 2
On 16/8/26 下午2:56, fuweiwei wrote:
in the previous version, I mentioned the scenario of long-term pause while
writing external memory checkpoints:
v1: https://www.redhat.com/archives/libvir-list/2016-August/msg01194.html
Daniel suggested not to hardcode the flag, but wire this upto the API.
Unlike postcopy migration there is no --live flag check for
postcopy-after-precopy.
Signed-off-by: Kothapally Madhu Pavan
---
tools/virsh-domain.c |6 ++
1 file changed, 6 insertions(+)
diff --git a/tools/virsh-domain.c b/tools/virsh-domain.c
index
in the previous version, I mentioned the scenario of long-term pause while
writing external memory checkpoints:
v1: https://www.redhat.com/archives/libvir-list/2016-August/msg01194.html
Daniel suggested not to hardcode the flag, but wire this upto the API. When
the user invokes the snapshot they
16 matches
Mail list logo