Recent content by L.O.S

DISCLAIMER: not sure this is really the best place to ask the question but let me start here :) /Cheers hi, I have setup am arch vm using q35 and virtgl for gpu acceeration. to access the VM I am using virt-viewr on mac. on Arch I have set up hyprland. I have also installed qemu-guest and...

the new install is even worst than the previous system. resizing a disk vm cause to through mdadm errors and then, revert to the no bootable device issue.

still having the issue. so finally decided to reset everything and go for a fresh install. the backups on the fresh install are all faillig the same way. also, creating a new cloud init vm on the new system fail on the same way. I found that creating a vm from a .img was failing. but, if i...

no I didn't change anything. and cloning to the original drive makes no difference. the simple acts of cloning make it not work. I have the same type of issue restoring from backups, or even a simple reboot of a working VM causing that VM not to boot. it lools like the boot partitions of...

9000 boot fine (it is the original VM) the clone 4052 doesn't

and for completeness root@saori:~# wipefs /dev/zvol/FileZilla/vm-4052-disk-0 DEVICE OFFSET TYPE UUID LABEL vm-4052-disk-0 0x438 ext4 43cf0ceb-1f9d-4018-89da-4f1585f40449 BOOT root@saori:~# wipefs /dev/zvol/FileZilla2/vm-9000-disk-0 DEVICE OFFSET...

root@saori:~# lsblk -o NAME,FSTYPE /dev/zvol/FileZilla2/vm-9000-disk-0 NAME FSTYPE zd400p16 ext4 root@saori:~# wipefs /dev/zvol/FileZilla2/vm-9000-disk-0 DEVICE OFFSET TYPE UUID LABEL vm-9000-disk-0 0x438 ext4 43cf0ceb-1f9d-4018-89da-4f1585f40449 BOOT

it iis woth noting that althought the cloning process does not show any errors, the disk of the cloned VM is not the same size as the orginal VM.

root@saori:~# fdisk -l /dev/zvol/FileZilla2/vm-9000-disk-0 Disk /dev/zvol/FileZilla2/vm-9000-disk-0: 913 MiB, 957350400 bytes, 1869825 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 8192 bytes I/O size (minimum/optimal): 8192 bytes / 8192 bytes...

and from journalctl Jan 15 12:48:43 saori pvedaemon[3981730]: <root@pam> starting task UPID:saori:000607CD:06114E8F:65A51B9B:qmclone:9000:root@pam: Jan 15 12:48:46 saori pvedaemon[3981730]: <root@pam> end task UPID:saori:000607CD:06114E8F:65A51B9B:qmclone:9000:root@pam: OK

so I cloned a new VM: root@saori:~# zfs get all FileZilla/vm-4052-disk-0 NAME PROPERTY VALUE SOURCE FileZilla/vm-4052-disk-0 type volume - FileZilla/vm-4052-disk-0 creation Mon Jan 15 12:48 2024...

correct ! the value on the original is FileZilla2/vm-9000-disk-0 referenced 1.24G -

here is the zpool status root@saori:~# zpool status -v pool: FileZilla state: ONLINE status: Some supported and requested features are not enabled on the pool. The pool can still be used, but some features are unavailable. action: Enable all features using 'zpool upgrade'. Once this...

and the journalctl Jan 13 17:02:34 saori smartd[2673]: Device: /dev/sdb [SAT], SMART Usage Attribute: 190 Drive_Temperature changed from 74 to 75 Jan 13 17:02:34 saori smartd[2673]: Device: /dev/sde [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 70 to 69 Jan 13 17:07:31...

here are the qm config root@saori:~# qm config 9000 boot: c bootdisk: scsi0 cipassword: ********** ciuser: cores: 2 ide2: FileZilla2:vm-9000-cloudinit,media=cdrom memory: 2048 meta: creation-qemu=8.1.2,ctime=1701100366 name: ubuntu-2310 nameserver: 10.10.10.10 net0...