- Status Closed
- Percent Complete
- Task Type Anomalie
- Category Services locaux → VM
- Assigned To No-one
- Operating System Tous
- Severity Critical
- Priority Very High
- Reported Version 4.9.0
- Due in Version Undecided
-
Due Date
Undecided
- Votes
- Private
Opened by nbanba - 21/03/2025
Last edited by mmakassikis - 26/03/2025
FS#40130 - enable_screen=true bloque le démarrage des VM
Bonjour
Suite aux modifications dans les VM liées au firmware 4.9.0 à savoir:
changement de position de la carte réseau sur le BUS PCI de la position 3 à la position 5
Un nouveau BUG est apparu :
Quand le support de l’écran virtuel VNC est actif dans la configuration de la VM, celle-ci refuse de démarrer même après correction des configurations réseaux internes à la vm.
Les VM ne démarrent qu’avec le support VNC désactivé.
(désolé pas vu tout de suite je n’utilise pas les écrans virtuels dans les VM si ce n’est pour le maintien de la fonction vm_vnc)
Pour exemple:
$ # LE SUPPORT DE L'ÉCRAN VNC EST ACTIF DANS LA VM: $ vm_detail 16 VM-16 : Full details properties : name = 14RV-FSRV-16 id = 16 status = stopped memory = 4096 vcpus = 1 disk_type = qcow2 disk_path = /FBX24T/box-vm/14RV-FSRV-16.qcow2 cd_path = /FBX24T/iso/arm64_ipxe_simple-menu3.iso mac_address = 06:c2:93:c3:0b:df os = debian enable_screen = true bind_usb_ports = ["",""] enable_cloudinit = false cloudinit_hostname = cloudinit_userdata = json_vm_object = {"mac":06:c2:93:c3:0b:df,"cloudinit_userdata":,"cd_path":/FBX24T/iso/arm64_ipxe_simple-menu3.iso,"id":16,"os":debian,"enable_cloudinit":false,"disk_path":/FBX24T/box-vm/14RV-FSRV-16.qcow2,"vcpus":1,"memory":4096,"name":14RV-FSRV-16,"cloudinit_hostname":,"status":stopped,"bind_usb_ports":["",""],"enable_screen":true,"disk_type":qcow2} $ # ON TENTE DE DÉMARRER LA VM : $ vm_start 16 operation completed: {"success":true} $ # ON TENTE DE CONNECTER L'ÉCRAN VNC: $ vm_vnc 16 WebSocketError: WebSocketError: Received unexpected status code (502 Bad Gateway) $ # PUIS LA CONSOLE SÉRIE: $ vm_console 16 WebSocketError: WebSocketError: Received unexpected status code (502 Bad Gateway) $ # ON VÉRIFIE LE STATUS DE LA VM: $ vm_show 16 VIRTUAL MACHINE ID, NAME, MAC AND STATUS : ---------------------------------------------------------------------------------------------- VM-0: id: 16 status: stopped name: 14RV-FSRV-16 mac_address: 06:c2:93:c3:0b:df $ # EN FAIT LA VM N A PAS DÉMARRÉE => connexion websocket KO $ # ON DÉSACTIVE LE SUPPORT DE L'ÉCRAN VNC: $ vm_modify 16 disk_type=qcow2 vcpus=1 memory=4096 disk_path=/FBX24T/box-vm/14RV-FSRV-16.qcow2 name=14RV-FSRV-16 cd_path=/FBX24T/iso/arm64_ipxe_simple-menu3.iso enable_screen=false New values for vm ID 16 : name = 14RV-FSRV-16 id = 16 status = stopped memory = 4096 vcpus = 1 disk_type = qcow2 disk_path = /FBX24T/box-vm/14RV-FSRV-16.qcow2 cd_path = /FBX24T/iso/arm64_ipxe_simple-menu3.iso mac_address = 06:c2:93:c3:0b:df os = debian enable_screen = false bind_usb_ports = ["",""] enable_cloudinit = false cloudinit_hostname = cloudinit_userdata = <reset to null> json_vm_object_modif = {"mac":"06:c2:93:c3:0b:df","cd_path":"L0ZCWDI0VC9pc28vYXJtNjRfaXB4ZV9zaW1wbGUtbWVudTMuaXNv","id":"16","os":"debian","enable_cloudinit":false,"disk_path":"L0ZCWDI0VC9ib3gtdm0vMTRSVi1GU1JWLTE2LnFjb3cy","vcpus":"1","memory":"4096","name":"14RV-FSRV-16","cloudinit_hostname":"","status":"stopped","enable_screen":false,"disk_type":"qcow2"} VM-16 modification status: {success:true} $ # ON LANCE LA VM SANS L'ÉCRAN VNC: $ vm_start 16 operation completed: {"success":true} $ vm_show 16 VIRTUAL MACHINE ID, NAME, MAC AND STATUS : ---------------------------------------------------------------------------------------------- VM-0: id: 16 status: running name: 14RV-FSRV-16 mac_address: 06:c2:93:c3:0b:df $ # OK: VM STATUS = RUNNING ...! $ # ON SE CONNECT À LA CONSOLE SERIE (par websocket) : $ vm_console 16 Connecting Freebox websocket : wss://fbx.fbx.lan/api/v14/vm/16/console Type CTRL+K to EXIT 14RV-FSRV-16 login: 14RV-FSRV-16 login: nba Password: Linux 14RV-FSRV-16.fbx.lan 6.12.7-arm64 #0 SMP Fri Jan 3 17:47:25 CET 2025 aarch64 12:08:05 nba@14RV-FSRV-16:~$ ping -4 mafreebox.freebox.fr PING (212.27.38.253) 56(84) bytes of data. 64 bytes from freeplayer.freebox.fr (212.27.38.253): icmp_seq=1 ttl=64 time=0.125 ms 64 bytes from freeplayer.freebox.fr (212.27.38.253): icmp_seq=2 ttl=64 time=0.205 ms 64 bytes from freeplayer.freebox.fr (212.27.38.253): icmp_seq=3 ttl=64 time=0.230 ms ^C $ # LA VM ET SON RÉSEAU FONCTIONNENT
La VM a bien du réseau et est fonctionnel (sans sortie écran)
Mais quand on tente de démarrer la VM avec l’option enable_screen=true elle ne démarre pas.
Merci pour votre aide
Cordialement
nbanba
26.03.2025 15:07
Reason for closing: Résolu
Additional comments about closing:
firmware 4.9.1
Loading...
Available keyboard shortcuts
- Alt + ⇧ Shift + l Login Dialog / Logout
- Alt + ⇧ Shift + a Add new task
- Alt + ⇧ Shift + m My searches
- Alt + ⇧ Shift + t focus taskid search
Tasklist
- o open selected task
- j move cursor down
- k move cursor up
Task Details
- n Next task
- p Previous task
- Alt + ⇧ Shift + e ↵ Enter Edit this task
- Alt + ⇧ Shift + w watch task
- Alt + ⇧ Shift + y Close Task
Task Editing
- Alt + ⇧ Shift + s save task