Skip to content
This repository was archived by the owner on May 12, 2021. It is now read-only.

backports: Bp 1.6.4 rel#1675

Merged
jodh-intel merged 5 commits intokata-containers:stable-1.6from
ganeshmaharaj:bp-1.6.4-rel
May 15, 2019
Merged

backports: Bp 1.6.4 rel#1675
jodh-intel merged 5 commits intokata-containers:stable-1.6from
ganeshmaharaj:bp-1.6.4-rel

Conversation

@ganeshmaharaj
Copy link
Contributor

@ganeshmaharaj ganeshmaharaj commented May 14, 2019

This stable backport includes the below changes.
#1513
#1606
#1641

The below changes marked as stable-candidate were not included cause of missing base changes.
#1623
#1628
#1630
#1651

Pennyzct and others added 4 commits May 14, 2019 15:07
We should refine unit test which involves func SupportsVsocks and newly
reconstructed struct kernelModule.

Fixes: kata-containers#1512

Signed-off-by: Penny Zheng <penny.zheng@arm.com>
(cherry picked from commit bce0d60)
Signed-off-by: Ganesh Maharaj Mahalingam <ganesh.mahalingam@intel.com>
Since we prefer vsock over virtio serial port, we add 'vhost_vsock'
in kernel mosules list.
But vhost_vsock.ko shouldn't be the definitely required kernel modules,
afterall, we could also use virtio serial port.
if kata-env shows SupportsVSocks as false, users could run kata-check
to manually load vhost_vsock.ko and get detailed info(errors)

Fixes: kata-containers#1512

Signed-off-by: Penny Zheng <penny.zheng@arm.com>
(cherry picked from commit 9b23d4f)
Signed-off-by: Ganesh Maharaj Mahalingam <ganesh.mahalingam@intel.com>
QEMU opens /dev/vhost-vsock and this causes vhost_vsock.ko to be
automatically loaded.
So, checking the existence of /dev/vhost-vsock is enough.

Fixes: kata-containers#1512

Signed-off-by: Penny Zheng <penny.zheng@arm.com>
(cherry picked from commit f21d5a3)
Signed-off-by: Ganesh Maharaj Mahalingam <ganesh.mahalingam@intel.com>
sockets * cores * threads should be equal to maxcpus otherwise a
warning is thrown: 'warning: Invalid CPU topology deprecated:
    sockets * cores * threads != maxcpus'

This warning in the future will be an error and won't be possible to run
kata containers.

fixes kata-containers#1605

Signed-off-by: Julio Montes <julio.montes@intel.com>
(cherry picked from commit fa5de87)
Signed-off-by: Ganesh Maharaj Mahalingam <ganesh.mahalingam@intel.com>
@jcvenegas
Copy link
Member

/test

when kata container start fails, netns will leak, add a defer func
to fix it

Fixes: kata-containers#1640

Signed-off-by: Ace-Tang <aceapril@126.com>
(cherry picked from commit a5bc98c)
Signed-off-by: Ganesh Maharaj Mahalingam <ganesh.mahalingam@intel.com>
@ganeshmaharaj
Copy link
Contributor Author

/retest

Copy link

@jodh-intel jodh-intel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @ganeshmaharaj.

lgtm

@jodh-intel jodh-intel merged commit 3e439ad into kata-containers:stable-1.6 May 15, 2019
@ganeshmaharaj ganeshmaharaj deleted the bp-1.6.4-rel branch July 17, 2019 17:00
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants