#qcow2 — Public Fediverse posts

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

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 #масштабирование

One of the #Linux distributions we hear very little about in the industry for cloud/#VM usage is #GentooLinux. But that could change with the #Gentoo project now putting out official #QCOW2 disk images to make it easier deploying this source-based Linux distribution within #virtualmachines. With these QCOW2 images, the XFS file-system is their preferred choice used for its copy-on-write, reflinks, and other features.
https://www.phoronix.com/news/Gentoo-Linux-QCOW2-VMs

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

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

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

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

Gentoo Linux Offers Bootable QCOW2 Images For Cloud Deployment #Gentoo #Qcow2 #Cloud #Linux #Opensource
https://ostechnix.com/bootable-gentoo-qcow2-disk-images/

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

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.

$ sudo apt-get install --yes libguestfs-tools gnome-disk-utility

Step 2

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

$ sudo su

Step 3

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

# mkdir /var/lib/libvirt/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.

# cp /var/lib/libvirt/images/windows.qcow2 /var/lib/libvirt/backups/windows-backup.qcow2

Step 5

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

# virt-sparsify --in-place /var/lib/libvirt/images/windows.qcow2

Step 6

Rename the sparsified image file.

# mv /var/lib/libvirt/images/windows.qcow2 /var/lib/libvirt/images/windows-sparsified.qcow2

Step 7

Check the disk size of the sparsified image file.

# qemu-img info /var/lib/libvirt/images/windows-sparsified.qcow2

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.

image: /var/lib/libvirt/images/windows-sparsified.qcow2
file format: qcow2
virtual size: 64 GiB (68719476736 bytes)
disk size: 33.7 GiB
cluster_size: 65536
Format specific information:
    compat: 1.1
    compression type: zlib
    lazy refcounts: true
    refcount bits: 16
    corrupt: false
    extended l2: false

Step 8

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

# virt-filesystems --long -h --all -a /var/lib/libvirt/images/windows-sparsified.qcow2

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

Name       Type        VFS   Label  MBR  Size  Parent
/dev/sda1  filesystem  vfat  -      -    96M   -
/dev/sda3  filesystem  ntfs  -      -    63G   -
/dev/sda4  filesystem  ntfs  -      -    768M  -
/dev/sda1  partition   -     -      -    100M  /dev/sda
/dev/sda2  partition   -     -      -    16M   /dev/sda
/dev/sda3  partition   -     -      -    63G   /dev/sda
/dev/sda4  partition   -     -      -    768M  /dev/sda
/dev/sda   device      -     -      -    64G   -

Step 9

Load the network block device (NBD) kernel module.

# modprobe nbd max_part=8

Step 10

Connect the sparsified image.

# qemu-nbd --connect=/dev/nbd9 /var/lib/libvirt/images/windows-sparsified.qcow2

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.

# qemu-nbd -d /dev/nbd9

Step 13

Unload the NBD kernel module.

# modprobe -r nbd

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.

# qemu-img create -f qcow2 -o preallocation=full -o cluster_size=2M /var/lib/libvirt/images/windows-target.qcow2 128G

Step 15

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

# virt-resize --expand /dev/sda3 /var/lib/libvirt/images/windows-sparsified.qcow2 /var/lib/libvirt/images/windows-target.qcow2

Step 16

Confirm the size of the target image.

# qemu-img info /var/lib/libvirt/images/windows-target.qcow2

The overall disk size is now 128 GiB in total.

image: /var/lib/libvirt/images/windows-target.qcow2
file format: qcow2
virtual size: 128 GiB (137438953472 bytes)
disk size: 128 GiB
cluster_size: 2097152
Format specific information:
    compat: 1.1
    compression type: zlib
    lazy refcounts: false
    refcount bits: 16
    corrupt: false
    extended l2: false

Step 17

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

# virt-filesystems --long -h --all -a /var/lib/libvirt/images/windows-target.qcow2

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

Name       Type        VFS   Label  MBR  Size  Parent
/dev/sda1  filesystem  vfat  -      -    96M   -
/dev/sda3  filesystem  ntfs  -      -    127G  -
/dev/sda4  filesystem  ntfs  -      -    768M  -
/dev/sda1  partition   -     -      -    100M  /dev/sda
/dev/sda2  partition   -     -      -    16M   /dev/sda
/dev/sda3  partition   -     -      -    127G  /dev/sda
/dev/sda4  partition   -     -      -    768M  /dev/sda
/dev/sda   device      -     -      -    128G  -

Step 18

Rename the target image file.

# mv /var/lib/libvirt/images/windows-target.qcow2 /var/lib/libvirt/images/windows.qcow2

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.

#debian #howto #kvm #libvirt #linux #ntfs #qcow2 #qemu #ubuntu #virtualisation #windows

J'ai envie de tester trois solutions de virtualisation...
#VirtualBox
#VMware #Workstation
#KVM (#libvirt #virtmanager)
Ressources communes...
- 8 vCPU ;
- 8192 Mo de RAM ;
- Stockage virtuel de 240 Go sur disque physique #SSD #SATA ;
Stockage des solutions...
- VirtualBox : #vdi cache E/S hôte ;
- VMware Workstation : #vmdk cache write ;
- KVM : #qcow2 cache writeback ;
CPU des solutions...
- KVM : host-passthrough
Tâche à effectuer...
Build (construction) de la distribution #Emmabuntüs ...

Utilities for Copy-On-Write filesystems, call that cowtools.

#cowtools #CopyOnWrite #filesystems #QCOW2 #Btrfs (both are COW so I figure it would be relevant to anyone using them)

@eelco @OpenBSDAms #hetzner supports OpenBSD out of the box. Just create any Linux VPS and the reinstall using provided images. They have tons of images to choose from.

If you can't find the version you need, open a support ticket and they will ask you for an image to add to your collection.

Also https://netcup.eu supports #openbsd. You can upload your own installer images to FTP/SFTP and boot the installer from virtual dvd. You can also upload complete VM image (#qcow2) to boot VM. IMO #netcup beats hetzner atm, both price and feature wise.

#Proxmox VE - Disque format #RAW d'une VM en provenance d'un stockage #ZFS est envoyé vers un stockage type "Directory" ❗
Merde 😲
On perd la fonctionnalité "Instantanés" (#snapshot) 😡
Pas de panique 😉
On convertit alors le format RAW vers le format #QCOW2 en procédant à un déplacement de disque 👊

Dear Lazyweb. I have a #KVM #virtualmachine with a #qcow2 backing file. The file is sparse and uses ~ 5-6 GB for a 40GB virtual disk size. I want to take this and put it on an exfat 32GB USB stick which has #ventoy and several ISO files, and which will become part of my "recovery" strategy if something goes wrong with this specialized machine (it's going to run some microscope hardware). If I just copy it it will balloon to 40GB and fail. What is the right magic to accomplish this?

How To Import QCOW2 Image Into Proxmox #Proxmox #Qcow2 #VirtualDisk #Virtualization #Linux
https://ostechnix.com/import-qcow2-into-proxmox/

Is there any greater feeling than moving a two massive (500GB) VHDX images from a HyperV Hypervisor to a #KVM #Hypervisor and converting the images to #QCOW2, installing #VirtIO Windows Drivers and it all happening without a single problem?

I don't think soooooo.

Apart from running a QCOW2 snapshot, taking a copy of the main image, then committing the snapshot back into the main image, obviously. That's a great feeling too.

#virt-manager is an easy way of accessing your #virtual machines.

Supporting #KVM, #Xen, and LXC, virt-manager allows for one to easily create and run many virtual machines at once.

virt-manager supports raw image, qcow, #qcow2, qed, #vmdk, vpc, and #vdi disk files.

virt-manager additionally allows for great tuning of a virtual machine's virtual hardware through an easy to use GUI.

Website 🔗: https://virt-manager.org/

apt 📦: virt-manager

#foss #free #open_source #fossmendations #vm