External/cloud-hypervisor
1
0
Fork 0
mirror of https://github.com/cloud-hypervisor/cloud-hypervisor.git synced 2024-11-05 11:31:14 +00:00
Code Issues Packages Projects Releases Wiki Activity
4ac0cb9cff
cloud-hypervisor/test_data/cloud-init/clear/openstack/latest/user_data

55 lines
1.6 KiB
Plaintext
Raw Normal View History

tests: Add basic integration testing Add basic integration testing of the hypervisor using a cloud-init to configure the VM at boot and SSH to control it at runtime. Initial test just boots the VM up checks some basic resources and reboots. With a second test that calls into the first to check that subsequent tests work correctly. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-05-23 15:45:13 +00:00
#cloud-config
users:
tests: Move Clear Linux cloud-init files to subdirectory And rename the default user from "admin" to "cloud" as the admin user clashes with a standard user and group name on Ubuntu. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-07-30 10:46:13 +00:00
- name: cloud
tests: Add basic integration testing Add basic integration testing of the hypervisor using a cloud-init to configure the VM at boot and SSH to control it at runtime. Initial test just boots the VM up checks some basic resources and reboots. With a second test that calls into the first to check that subsequent tests work correctly. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-05-23 15:45:13 +00:00
passwd: $6$7125787751a8d18a$sHwGySomUA1PawiNFWVCKYQN.Ec.Wzz0JtPPL1MvzFrkwmop2dq7.4CYf03A5oemPQ4pOFCCrtCelvFBEle/K.
sudo:
- ALL=(ALL) NOPASSWD:ALL
write_files:
-
tests: Add VFIO integration test The VFIO integration test first boots a QEMU guest and then assigns the QEMU virtio-pci networking device into a nested cloud-hypervisor guest. We then check that we can ssh into the nested guest and verify that it's running with the right kernel command line. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-07-19 08:26:13 +00:00
path: /etc/systemd/network/00-static-l1.network
tests: Add basic integration testing Add basic integration testing of the hypervisor using a cloud-init to configure the VM at boot and SSH to control it at runtime. Initial test just boots the VM up checks some basic resources and reboots. With a second test that calls into the first to check that subsequent tests work correctly. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-05-23 15:45:13 +00:00
permissions: 0644
content: |
[Match]
vmm: Add support for multiple virtio-net devices Until now, the VMM was only accepting a single instance of virtio-net device. This commit extends the virtio-net support by allowing several devices to be created for a single VM. Fixes #71 Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2019-07-08 22:31:13 +00:00
MACAddress=12:34:56:78:90:ab
tests: Add basic integration testing Add basic integration testing of the hypervisor using a cloud-init to configure the VM at boot and SSH to control it at runtime. Initial test just boots the VM up checks some basic resources and reboots. With a second test that calls into the first to check that subsequent tests work correctly. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-05-23 15:45:13 +00:00
[Network]
Address=192.168.2.2/24
Gateway=192.168.2.1
tests: Add VFIO integration test The VFIO integration test first boots a QEMU guest and then assigns the QEMU virtio-pci networking device into a nested cloud-hypervisor guest. We then check that we can ssh into the nested guest and verify that it's running with the right kernel command line. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-07-19 08:26:13 +00:00
-
path: /etc/systemd/network/00-static-l2.network
permissions: 0644
content: |
[Match]
MACAddress=de:ad:be:ef:12:34
[Network]
Address=192.168.2.3/24
Gateway=192.168.2.1
-
path: /etc/systemd/system/vfio.service
permissions: 0644
content: |
[Unit]
Description=VFIO test systemd service
[Service]
Type=simple
ExecStart=/bin/bash /usr/bin/cloud-hypervisor-vfio.sh
[Install]
WantedBy=multi-user.target
-
path: /usr/bin/cloud-hypervisor-vfio.sh
permissions: 0755
content: |
#!/bin/bash
ci: Remove QEMU dependency for nested VFIO test Now that cloud-hypervisor can expose a virtual IOMMU to its guest VM, the integration test validating the VFIO support with virtio-net can be updated to use cloud-hypervisor exclusively. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2019-10-09 18:15:58 +00:00
mount -t virtio_fs virtiofs /mnt -o rootmode=040000,user_id=0,group_id=0,dax
bash -c "echo 0000:00:06.0 > /sys/bus/pci/devices/0000\:00\:06.0/driver/unbind"
tests: Add VFIO integration test The VFIO integration test first boots a QEMU guest and then assigns the QEMU virtio-pci networking device into a nested cloud-hypervisor guest. We then check that we can ssh into the nested guest and verify that it's running with the right kernel command line. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-07-19 08:26:13 +00:00
bash -c "echo 1af4 1041 > /sys/bus/pci/drivers/vfio-pci/new_id"
ci: Allow enough time for L2 VM to boot Because the L2 VM running in the VFIO integration test is actually running as L3 (since the CI runs in a VM), it can take quite some time for this VM to boot. The way to solve this issue is to extend the sleep time before to try communicating with the L2 VM, but also to speed up the boot time by using virtio-console instead of serial. We suspect the use of serial, implying PIO VM exits for each character on the serial port is quite expensive compared to the paravirtualized console. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2019-10-10 20:39:21 +00:00
/mnt/cloud-hypervisor --kernel /mnt/vmlinux --cmdline "console=hvc0 reboot=k panic=1 nomodules i8042.noaux i8042.nomux i8042.nopnp i8042.dumbkbd root=/dev/vda2 VFIOTAG" --disk path=/mnt/clear-cloudguest.img path=/mnt/cloudinit.img --cpus 1 --memory size=512M --rng --device /sys/bus/pci/devices/0000:00:06.0/
Reference in New Issue Copy Permalink