Recent content by tanyastawicki

I tried to get Chromeos Flex running on a Kali Linux and on a Windows 11 device, with on both qemu installed. The frustating thing is that it successfully runs on both devices. command line: qemu-system-x86_64.exe -drive format=qcow2,file=g:\linux2020.qcow2 -m 4G -display...

I finally was able to reboot the Proxmox server with monitor and keyboard... I indeed have a "grub-choice" to boot in kernel: 1) 5.15.149-1-pve 2) 6.8.4-2-pve when I choose the "5"-one the server boot successfully in kernel 5.15 , the server is reachable and working. But the crashes of...

you could try to boot into an older Kernel. Oke.. that is an idea As I mentioned: I upgraded the proxmox server, so maybe in the Grub start menu there is a possibility boot from an older kernel. I don't know: We don't have a monitor attached to the Proxmox server. we indeed have these...

I have tried different CPU setups x86-64-v2-AES x86-64-v2 x86-64-v3 kvm64 qemu64 some haswells on two different PVE8 hosts. This one: and this one: CPU(s) 40 x Intel(R) Xeon(R) Silver 4114 CPU @ 2.20GHz (2 Sockets) Kernel Version Linux 6.5.11-4-pve (2023-11-20T10:19Z) Boot...

No I'll give it a try ! It is now set on "host" 1 socket, 2 cores, ( the host processor on this host is AMD ryzen 7 2000 series )

problem partly solved ... dont start the console as usual: right clicking ther VM but start it in the right upper corner with the down arrow on the "console"-icon There we go: a "normal" noVNC console appears. But now we see an even bigger problem with pve8: ChromeOS Flex crashes...

Helo GFNG The display shows: "VirtIO-GPU (virtio)" here my VMID.conf The VM is one of more VMs running running ChromeOS flex. We use them for Chromebook testing. It used to work flawlessly on PVE 7.1 til 7.4. balloon: 0 boot: order=sata0 cores: 2 machine: q35 memory: 4096 meta...

Halo, After ( successfull ) upgrading our ProxMox PVE ( bulleye - bookworm, pve7 to pve8 ) the console of VMs, using the Display type VirtIO-gpu stopped working. When right-clicking the VM and choosing > console not the console opens, but a standard Save AS Windows with the file...