Hello, Am 04.03.20 um 14:04 schrieb Laurent Dumont: > If this is a regular laptop, make sure you have enabled VTX in the BIOS > options.
First I only found the "Diagnostic Tool" with F10. After using the search engine again I found the hint to use F1. There I found the option to enable virtualization. Thanks for that hints Kind regards > > On Wed, Mar 4, 2020, 2:46 AM Fabian Grünbichler <f.gruenbich...@proxmox.com> > wrote: > >> On March 3, 2020 9:14 pm, Mechtilde wrote: >>> I can also use the dialog to create a VM and connect it to the *.iso. >>> >>> After that I get the message "Failled to connect to server and the >>> splash screen for noVNC. >> >> did the VM actually start? you should have a visual indication of that >> in the left side tree (instead of the greyed out, inactive icon there >> should be an active icon with a small 'play symbol' overlayed), and in >> the VM view itself (after you selected the VM in the left-side tree) the >> summary should say 'running' instead of 'stopped'. >> >> you can also check by running "qm list" or "qm status <VMID>" on the >> CLI. >> >>> The status message is: "Failed to run vncproxy." >> >> this message usually occurs when the VM is not running. > -- Mechtilde Stehmann ## Apache OpenOffice ## Freie Office Suite für Linux, MacOSX, Windows ## Debian Developer ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F
signature.asc
Description: OpenPGP digital signature
_______________________________________________ pve-user mailing list pve-user@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user