search

dockur / windows-arm

Windows for ARM in a Docker container.
MIT License
818 stars 91 forks source link

Encountering the “Display output is not active” issue, how can it be resolved? #170

Closed Hirsinkai closed 3 weeks ago

Hirsinkai commented 4 months ago

Operating system

Kylin-V10-SP3

Description

Encountering the “Display output is not active” issue, how can it be resolved?

Nested virtualization is not supported

KVM: N

Connection established.
To escape to local shell, press 'Ctrl+Alt+]'.

Authorized users only. All activities may be monitored and reported.

WARNING! The remote SSH server rejected X11 forwarding request.

Authorized users only. All activities may be monitored and reported.
Activate the web console with: systemctl enable --now cockpit.socket

Last login: Tue Jul  2 13:36:50 2024 from 192.168.100.95
[root@aaaa ~]# uname -a
Linux aaaa 4.19.90-52.38.v2207.ky10.aarch64 #4 SMP Wed May 8 19:16:35 CST 2024 aarch64 aarch64 aarch64 GNU/Linux
[root@aaaa ~]# lscpu
Architecture:                    aarch64
CPU op-mode(s):                  64-bit
Byte Order:                      Little Endian
CPU(s):                          16
On-line CPU(s) list:             0-15
Thread(s) per core:              1
Core(s) per socket:              8
Socket(s):                       2
NUMA node(s):                    1
Vendor ID:                       HiSilicon
Model:                           0
Model name:                      Kunpeng-920
Stepping:                        0x1
CPU max MHz:                     2600.0000
CPU min MHz:                     2600.0000
BogoMIPS:                        200.00
L1d cache:                       1 MiB
L1i cache:                       1 MiB
L2 cache:                        8 MiB
L3 cache:                        64 MiB
NUMA node0 CPU(s):               0-15
Vulnerability Itlb multihit:     Not affected
Vulnerability L1tf:              Not affected
Vulnerability Mds:               Not affected
Vulnerability Meltdown:          Not affected
Vulnerability Mmio stale data:   Not affected
Vulnerability Retbleed:          Not affected
Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl
Vulnerability Spectre v1:        Mitigation; __user pointer sanitization
Vulnerability Spectre v2:        Not affected
Vulnerability Srbds:             Not affected
Vulnerability Tsx async abort:   Not affected
Flags:                           fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm jscvt fcma dcpop asimddp asimdfhm ssbs
[root@aaaa ~]# cat /etc/kylin-release
Kylin Linux Advanced Server release V10 (Lance)

Docker compose

services:
  windows:
    image: dockurr/windows-arm:2.11
    container_name: wis
    privileged: true
    cap_add:
      - NET_ADMIN
    volumes:
      - ./data:/storage 
    environment:
      KVM: N
      CPU_CORES: "12" 
      RAM_SIZE: "32G" 
      DISK_SIZE: "128G" 
    devices:
      - /dev/kvm
    ports:
      - 8006:8006  
      - 3389:3389/tcp
      - 3389:3389/udp  
    stop_grace_period: 2m
    restart: on-failure

Docker log


[root@aaaa 01.wis]# docker-compose up
[+] Running 1/0
 ✔ Container wis  Created                                                                                                                                                 0.0s 
Attaching to wis
wis  | ❯ Starting Windows for Docker v2.11...
wis  | ❯ For support visit https://github.com/dockur/windows-arm
wis  | ❯ CPU: TaiShan v110 | RAM: 49/63 GB | DISK: 479 GB (xfs) | HOST: 4.19.90-52.38.v2207.ky10.aarch64...
wis  | 
wis  | ❯ Booting Windows using QEMU v8.2.4...
wis  | UEFI firmware (version 2024.05-1 built at 16:56:31 on Jun  4 2024)
wis  | 

BdsDxe: failed to load Boot0002 "UEFI QEMU QEMU HARDDISK " from PciRoot(0x0)/Pci(0xA,0x0)/Scsi(0x0,0x0): Not Found
wis  | BdsDxe: loading Boot0001 "UEFI QEMU QEMU CD-ROM " from PciRoot(0x0)/Pci(0x5,0x0)/Scsi(0x0,0x0)
wis  | BdsDxe: starting Boot0001 "UEFI QEMU QEMU CD-ROM " from PciRoot(0x0)/Pci(0x5,0x0)/Scsi(0x0,0x0)
wis  | 

  Loading files...

  lllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllll 

  Loading files...

  llllll                                                                      ❯ Windows started succesfully, visit http://localhost:8006/ to view the screen...

Screenshots (optional)

image

Loggsie commented 3 months ago

If there is no KVM support remove /dev/kvm from the compose YAML and redeploy

To fix X11 forwarding error uncomment the below line of your sshd_config file on the local machine - usually located at at /etc/ssh/sshd_config

From

X11Forwarding no

To

X11Forwarding yes

Save and restart ssh with

sudo systemctl restart sshd

kroese commented 3 weeks ago

Running the container without KVM may not always work