[Technical Issue]: qemu-system-x86_64: terminating on signal 15 from pid 3273

[5xdf]

Operating system

Debian GNU/Linux 12 (bookworm) [Running CasaOS]

Description

Not sure how to explain this.

This is on a newly made docker container, it tries starting up for a minute or two and then the container restarts, basically boot-looping. I've tried increasing the stop timeout, nothing, it restarts before the stop-timeout is even reached..

I am also using CasaOS for Docker Container management.

Docker compose

services:
  windows:
    cap_add:
      - NET_ADMIN
    cpu_shares: 90
    command: []
    deploy:
      resources:
        limits:
          memory: 7295M
    devices:
      - /dev/kvm:/dev/kvm
      - /dev/net/tun:/dev/net/tun
    environment:
      - CPU_CORES=2
      - RAM_SIZE=2
      - VERSION=10
    image: dockurr/windows:latest
    labels:
      icon: https://icon.casaos.io/main/all/windows.png
    ports:
      - target: 8006
        published: "8006"
        protocol: tcp
    restart: unless-stopped
    stdin_open: true
    stop_grace_period: 5m0s
    tty: true
    volumes: []
    network_mode: bridge
    privileged: false
    container_name: ""
    hostname: ""
x-casaos:
  author: self
  category: self
  hostname: ""
  icon: https://icon.casaos.io/main/all/windows.png
  index: /
  is_uncontrolled: false
  port_map: ""
  scheme: http
  store_app_id: yourprojectname
  title:
    custom: ""
    en_us: windows

Docker log

windows-1  | �[1;31m❯ Warning: unexpected clocksource: hpet�[0m
windows-1  | �[1;34m❯ �[1;36mBooting Windows using QEMU v9.1.1...�[0m
windows-1  | �[1;31m❯ ERROR: Timeout while waiting for QEMU to boot the machine!�[0m
windows-1  | qemu-system-x86_64: terminating on signal 15 from pid 3273 ()
windows-1  | ❯ Shutdown completed!
windows-1  | ❯ Starting Windows for Docker v4.06...
windows-1  | ❯ For support visit https://github.com/dockur/windows
windows-1  | ❯ CPU: AMD Ryzen 5 4500U | RAM: 4/8 GB | DISK: 329 GB (ext4) | KERNEL: 6.1.0-28-amd64...
windows-1  | 
windows-1  | �[1;31m❯ Warning: unexpected clocksource: hpet�[0m
windows-1  | �[1;34m❯ �[1;36mBooting Windows using QEMU v9.1.1...�[0m

Screenshots (optional)

What it shows on noVNC:

I have looked through other issues that are similar but couldn't find a solution that worked.

P.S. This also happens on the MacOS container

[5xdf]

If any more information is needed for this, please let me know!

Also note that I am really bad at following instructions... So if I get something wrong, please cooperate, I'll get there eventually.

[maeryo]

spec:
  template:
    spec:
      containers:
        - env:
            - name: CPU_CORES
              value: '12'
            - name: RAM_SIZE
              value: '12'
            - name: DISK_SIZE
              value: "64G"
          image: dockurr/windows
          imagePullPolicy: IfNotPresent
          name: windows
          ports:
            - containerPort: 8006
              protocol: TCP
          resources:
            limits:
              cpu: '12'
              memory: 12Gi
              nvidia.com/gpu: '1'
            requests:
              cpu: '12'
              memory: 12Gi
          securityContext:
            privileged: true
            capabilities:
              add:
                - NET_ADMIN
          volumeMounts:
            - mountPath: /dev/shm
              name: dshm
            - mountPath: /storage
              name: windows-volume
            - mountPath: /dev/kvm
              name: kvm-device
            - mountPath: /dev/net/tun
              name: dev-tun
      serviceAccount: default-editor
      volumes:
        - emptyDir:
            medium: Memory
          name: dshm
        - name: windows-volume
          persistentVolumeClaim:
            claimName: windows-volume
        - hostPath:
            path: /dev/kvm
          name: kvm-device
        - hostPath:
            path: /dev/net/tun
            type: CharDevice
          name: dev-tun

I'm getting the exact same error in Kubernetes.

[kroese]

I think the issue is:

Warning: unexpected clocksource: hpet

So you should first fix that, normally the clocksource is tsc on normal systems.