谁能告诉我fedora cloud 43 cloud init的user-data的标准配置以及磁盘挂载  

user-data
#cloud-config
users:
- name: jay
lock_passwd: false
passwd: "$6$.XXX"
sudo: ['ALL=(ALL) NOPASSWD:ALL']
groups: wheel
shell: /bin/bash
ssh_authorized_keys:
- ssh-rsa XXX

cloud-localds seed.iso user-data
添加seed.iso到磁盘
更改启动顺序为seed.iso——》fedora-*.qcow2

https://docs.aws.amazon.com/linux/al2023/ug/seed-iso.html
https://cloudinit.readthedocs.io/en/23.4.1/reference/datasources/nocloud.html
https://cloudinit.readthedocs.io/en/latest/index.html

#fedora #iso #cloud #cloud_init #linux #qcow2

quicktipp #101: Proxmox PVE: Using `virt-customize` (from `libguestfs-tools`) to inject the qemu-guest-agent into the Ubuntu cloudimage.

Other than i.e. the Fedora cloudimage, the stock Ubuntu cloudimage comes without the qemu-guest-agent preinstalled. Here's an easy way to add it using the `virt-customize` tool.

#proxmox #pve #proxmoxpve #qemu #ubuntu #cloudimage #cloudinit #qcow2 #virtualization #virt #vm #cloud

Интеграция компонентов OpenStack Glance в существующую инфраструктуру oVirt

В этой статье мы расскажем о нашем опыте совмещения серверной инфраструктуры на основе oVirt с компонентами OpenStack, наших мотивах для этого решения и тех сложностях, с которыми мы столкнулись во время реализации этой задачи.

https://habr.com/ru/companies/hostkey/articles/915594/

#hostkey #openstack_glance #ovirt #деплой #централизованное_управление #виртуальные_машины #openstack #qcow2 #cloudinit #масштабирование

Автоматизируем создание cloud native образов: пошаговая инструкция

Всем привет! С вами снова Иван Протченко — инженер из команды Читать дальше

https://habr.com/ru/companies/cloud_ru/articles/891806/

#packer #qemu #qemukvm #gitlabrunner #gitlab #gitlabci #cloudnative #qcow2 #ubuntuserver

Shrink, optimise and expand an existing QCOW2 image

"The overall objective is to shrink and optimise the 64 GiB disk image for random read and write operations before expanding it to a desired size of 128 GiB."

https://edafe.de/2025/02/shrink-optimise-and-expand-an-existing-qcow2-image/

#debian #gnome #kvm #libvirt #linux #linuxmint #ntfs #qcow2 #qemu #ubuntu #virtualisation #windows

Shrink, optimise and expand an existing QCOW2 image

edafe.de/qcow

A virtual disk image is a block device in a file. There are a number of different disk image formats to choose from when setting up a virtual machine. QEMU Copy On Write version 2 (QCOW2) is the default virtual disk image format for the Quick Emulator (QEMU). Features such as thin provisioning, snapshots and compression make QCOW2 one of the most versatile virtual disk formats available.

These instructions specifically target Debian 12 with a GNOME desktop as the host, but they should also be applicable to other Linux distributions such as Ubuntu or Linux Mint. The guest in this particular example is a Windows 11 virtual machine that has run out of space.

The overall objective is to shrink and optimise the 64 GiB disk image for random read and write operations before expanding it to a desired size of 128 GiB.

With thanks to Fam Zheng.

Before you begin

Shut down the virtual machine and delete all existing snapshots from the image file.

Never modify images currently in use by a running virtual machine.

Step 1

On the host, install the necessary tools for working with virtual disk images.

Step 2

Only root can access the host directory /var/lib/libvirt/images. Use the following command to obtain the necessary privileges.

Step 3

Continue by creating a directory in which to keep your virtual machine backups.

Step 4

Now create a backup of the virtual machine with the name windows by copying its QCOW2 image file to the backups directory.

Step 5

Sparsify the image file to convert any free space within the disk image to free space on the host.

Step 6

Rename the sparsified image file.

Step 7

Check the disk size of the sparsified image file.

The disk size should be smaller than the virtual size. In this particular case, the disk size is 33.7 GiB and the virtual size 64 GiB.

Step 8

Determine which partition to resize by obtaining more detailed information about the contents of the sparsified disk image.

On the virtual device /dev/sda, the partition /dev/sda3 is equivalent to the Local Disk (C:) of the Windows 11 virtual machine.

Step 9

Load the network block device (NBD) kernel module.

Step 10

Connect the sparsified image.

Step 11

The partition /dev/sda3 listed in Step 8 is equivalent to /dev/nbd9p3 connected as a network block device. Use GNOME Disks to shrink /dev/nbd9p3 to its Minimal Size.

Use a graphical utility to minimise the risk of introducing errors.

Step 12

Disconnect the resized image.

Step 13

Unload the NBD kernel module.

Step 14

Create a target image larger than the resized source image. In this example, the size of the target image is 128G and its format QCOW2 with full preallocation and a cluster size of 2M.

Step 15

Copy the source image to the target image. Specify the correct partition which to expand in the process.

Step 16

Confirm the size of the target image.

The overall disk size is now 128 GiB in total.

Step 17

Obtain more detailed information about the contents of the target disk image.

The partition /dev/sda3 of the virtual device /dev/sda is now 127G in size.

Step 18

Rename the target image file.

All done!

You can also modify format specific options for an existing image without having to create a target disk image. Or alternatively expand into a target image that uses a format compatible with other hypervisors, such as RAW, VMDK, VDI, VHD, VHDX or QED.