search for: criu

...isruptive migration by reconnecting if necessary after ECONNRESET. 3. Checkpoint/restore for seamless migration Applications that wish to communicate across live migration can do so but this requires extra application-specific checkpoint/restore code. This is similar to the approach taken by the CRIU project where getsockopt()/setsockopt() is used to migrate socket state. The difference is that the application process is not automatically migrated from the source host to the destination host. Therefore, the application needs to migrate its own state somehow. The flow is as follows: The appl...

...isruptive migration by reconnecting if necessary after ECONNRESET. 3. Checkpoint/restore for seamless migration Applications that wish to communicate across live migration can do so but this requires extra application-specific checkpoint/restore code. This is similar to the approach taken by the CRIU project where getsockopt()/setsockopt() is used to migrate socket state. The difference is that the application process is not automatically migrated from the source host to the destination host. Therefore, the application needs to migrate its own state somehow. The flow is as follows: The appl...

...that avoids confusion between class AF_VSOCK semantics and virtio socket semantics. Can we please treat AF_VSOCK semantics as the requirements we're trying to implement? It supports qemu-guest-agent and as I described in a previous mail could also support transparent connection migration a la CRIU sockets. Stefan -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: not available URL: <http://lists.linuxfoundation.org/pipermail/virtualization/attachments/20160406/86c1c5ef/attachment.sig>

...that avoids confusion between class AF_VSOCK semantics and virtio socket semantics. Can we please treat AF_VSOCK semantics as the requirements we're trying to implement? It supports qemu-guest-agent and as I described in a previous mail could also support transparent connection migration a la CRIU sockets. Stefan -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: not available URL: <http://lists.linuxfoundation.org/pipermail/virtualization/attachments/20160406/86c1c5ef/attachment.sig>

...gt; necessary after ECONNRESET. > > 3. Checkpoint/restore for seamless migration > > Applications that wish to communicate across live migration can do so > but this requires extra application-specific checkpoint/restore code. > > This is similar to the approach taken by the CRIU project where > getsockopt()/setsockopt() is used to migrate socket state. The > difference is that the application process is not automatically migrated > from the source host to the destination host. Therefore, the > application needs to migrate its own state somehow. > > The...

...gt; necessary after ECONNRESET. > > 3. Checkpoint/restore for seamless migration > > Applications that wish to communicate across live migration can do so > but this requires extra application-specific checkpoint/restore code. > > This is similar to the approach taken by the CRIU project where > getsockopt()/setsockopt() is used to migrate socket state. The > difference is that the application process is not automatically migrated > from the source host to the destination host. Therefore, the > application needs to migrate its own state somehow. > > The...

No need to get into the submenu to disable all VIRTIO-related config entries. This makes it easier to disable all VIRTIO config options without entering the submenu. It will also enable one to see that en/dis-abled state from the outside menu. This is only intended to change menuconfig UI, not change the config dependencies. Signed-off-by: Vincent Legoll <vincent.legoll at gmail.com> ---

No need to get into the submenu to disable all VIRTIO-related config entries. This makes it easier to disable all VIRTIO config options without entering the submenu. It will also enable one to see that en/dis-abled state from the outside menu. This is only intended to change menuconfig UI, not change the config dependencies. Signed-off-by: Vincent Legoll <vincent.legoll at gmail.com> ---

Hi, I am trying to implement something like an "LXC on CentOS 7 HowTo" for internal use. (Might as well get public afterwards.) I am following the HowTo for CentOS 6 (https://wiki.centos.org/HowTos/LXC-on-CentOS6). So, here's what I did so far (Steps 1-6 can easily be omitted, but I am trying to be complete.) 1.) Disable delta RPM's in /etc/yum.conf 2.) Remove LibreOffice

On Tue, Mar 15, 2016 at 06:12:55PM +0200, Michael S. Tsirkin wrote: > On Tue, Mar 15, 2016 at 03:15:29PM +0000, Stefan Hajnoczi wrote: > > On Mon, Mar 14, 2016 at 01:13:24PM +0200, Michael S. Tsirkin wrote: > > > On Thu, Mar 03, 2016 at 03:37:37PM +0000, Stefan Hajnoczi wrote: > > > > Michael pointed out that the virtio-vsock draft specification does not > >

On Tue, Mar 15, 2016 at 06:12:55PM +0200, Michael S. Tsirkin wrote: > On Tue, Mar 15, 2016 at 03:15:29PM +0000, Stefan Hajnoczi wrote: > > On Mon, Mar 14, 2016 at 01:13:24PM +0200, Michael S. Tsirkin wrote: > > > On Thu, Mar 03, 2016 at 03:37:37PM +0000, Stefan Hajnoczi wrote: > > > > Michael pointed out that the virtio-vsock draft specification does not > >

...ortant Bug #777821 [src:covered] covered: ftbfs with GCC-5 Severity set to 'important' from 'normal' > severity 777822 important Bug #777822 [src:cp2k] cp2k: ftbfs with GCC-5 Severity set to 'important' from 'normal' > severity 777827 important Bug #777827 [src:criu] criu: ftbfs with GCC-5 Severity set to 'important' from 'normal' > severity 777829 important Bug #777829 [src:dahdi-tools] dahdi-tools: ftbfs with GCC-5 Severity set to 'important' from 'normal' > severity 777831 important Bug #777831 [src:deborphan] deborphan...