Recent content by kakao73

Ouch. What a shame. I'm sorry for my mis-spelled "vm-123-disk1". I've missed dash between disk and 1. @Dominic Thank you for your kind answer!

@Dominic No. I expected that these commands work agnostically . Don't they work on Lvm-thin?

@Alwin Ah, thanks.

Hello, I've tried below but failed: $ pvesm alloc <lvm-thin-storage> 123 '' 5G successfully created '<lvm-thin-storage>:vm-123-disk-1' $ qm set 123 --scsihw virtio-scsi-pci --scsi1 <lvm-thin-storage>:vm-123-disk1,discard=on,ssd=1 update VM 123: -scsi1...

I'm the OP. It turns out that the tip linked and confirmed by @ujiam, @stfl is right to me. In my case, I confirmed ubuntu minimal cloud image .img file is a qcow2 image. Just rename its file extension: mv <ubuntu-minimal-cloud-image>.img <ubuntu-minimal-cloud-image>.qcow2 And use that .qcow2...

I tried below: $ qemu-img resize -f raw --shrink $(pvesm path <lvm-thin-storage>:<vm-disk>) -1G qemu-img: Cannot resize device files How can I shrink it?

@janssensm Thanks for your help and kind reply. It has encouraged me to go forward. Thank you!

@janssensm I've confirmed that removing TOTP for root user is required for enabling U2F for root user.

@janssensm Thanks to reply. I've configured Datacenter > Permissions > Authentication's TFAs to none but U2F still be disabled to root user. Interestingly it is ok for newly created user to select U2F. Do I need to disable TOTP for root user if I want to enable U2F for root user?

@janssensm Ok, my result is $ pveversion -v proxmox-ve: 6.0-2 (running kernel: 5.0.21-5-pve) pve-manager: 6.0-15 (running version: 6.0-15/52b91481) pve-kernel-helper: 6.0-12 pve-kernel-5.0: 6.0-11 pve-kernel-5.0.21-5-pve: 5.0.21-10 pve-kernel-5.0.21-4-pve: 5.0.21-9 pve-kernel-5.0.21-3-pve...

@Pravednik I've used latest qemu-server: 6.1-1. It does not solve the problem. Anyway, as a workaround I've used an old created ubuntu cloud image based template with cloud-init. It has no problems until now. I want to switch old images with new latest one safely. Is there a way to investigate...

I tried cloud-init with ubuntu-18.04-minimal-cloudimg-amd64.img from official link, ubuntu-18.04-server-cloudimg-amd64.img from this link and bionic-server-cloudimg-amd64.img from this link. They were all failed to boot with "No bootable disk" messages alike. I had followed Cloud-Init_Support...

Though the Proxmox VE has an appid in /etc/pve/datacenter.cfg like this link, TFA window's U2F tab is not activated in WebUI.

Thank you for very detail information!!! That is similar to mine but a VM disk type(I tried scsi and block), CPU related parts of host(to me, Intel) and Proxmox filesystem(me, ext4, LVM). I'll do a new trial based your information a few days later. Yes, already I found it. I doubt whether it...

I tried RX560 in windows 10 VM but met an error, VIDEO_TDR_FAILURE on atikmpag.sys. How did you do that? Please, could you post your config?