mirror of
https://github.com/linuxkit/linuxkit.git
synced 2026-04-06 09:56:10 +00:00
0eb21735ae
Note that this is not the latest (which was 95efd45db073 at time of writing) but the next commit 6428b4bad0c2 merges "Port ctr to use client package" breaks the use of `ctr run --runtime-config` (by removing that option). This contains https://github.com/containerd/containerd/pull/954 which was causing some services to fail to start. All previous uses of15541037b9are updated to5749f2e9e6. Signed-off-by: Ian Campbell <ian.campbell@docker.com>
This directory contains the files to build and run a container containing the
virtio and Hyper-V socket stress tests. ../../cases/test-virtsock-server.yml builds images which start the server inside the VM.
The client, to be run on the host as per this README, can be obtained compiled from here.
How to use (on Windows)
- Build the images:
moby build tests/cases/test-virtsock-server.yml - Copy the
test-virtsock-server.isoto a Windows system - Create a Type 1 Hyper-V VM (called
virtsock).- No Disk or network required
- Add the ISO to the CDROM device
- Make sure you enable a named pipe for COM1 (call it
virtsock)
- Start the VM
- Connect to the serial console (to get debug output) with
putty -serial \\.\pipe\virtsock
Run the client:
$vmId = (get-vm virtsock).Id
.\virtsock_stress.exe -c $vmId -v 1 -c 1000000 -p 10
This creates 1000000 connections from 10 threads to the VM and
sends some random amount of data of the connection before tearing it
down. There are more options to change the behaviour.
TODO
- Add scripts to create Hyper-V VM
- Enable virtio sockets in
moby runwith HyperKit - Add some sample client YAML files which would connect from the VM to the host
- Hook up to CI for both HyperKit and Hyper-V