OmniBox missing container configurations

[weipeilun]

entry.sh called the following scripts to initiate qemu arguments: ` cd /run

. reset.sh # Initialize system . define.sh # Define versions . install.sh # Run installation . disk.sh # Initialize disks . display.sh # Initialize graphics . network.sh # Initialize network . samba.sh # Configure samba . boot.sh # Configure boot . proc.sh # Initialize processor . power.sh # Configure shutdown . config.sh # Configure arguments ` But reset.sh, disk.sh, display.sh, network.sh, boot.sh, proc.sh, config.sh are missing from the commit, which will cause disk and network error when starting docker. Default docker compose shows as following: QEMU (omniparser-windows) - noVNC2.pdf

Then I wrote a disk.sh: ` #!/usr/bin/env bash

Initialize DISK_OPTS

DISK_OPTS=""

Create the disk if it doesn't exist

if [ ! -f "/storage/disk.qcow2" ]; then qemu-img create -f qcow2 "/storage/disk.qcow2" "${DISK_SIZE:-60G}" fi

Add disk arguments to QEMU

ARGS+=" -drive if=virtio,file=/storage/disk.qcow2,format=qcow2,id=disk" ARGS+=" -device virtio-scsi-pci,id=scsi" ARGS+=" -device scsi-hd,drive=disk"

Add DVD drive for installation

ARGS+=" -drive file=/custom.iso,media=cdrom,index=0"

Export DISK_OPTS for use in other scripts

export DISK_OPTS ` Docker compose shows as following, which solved the disk issue, but new network issue pops up. QEMU (omniparser-windows) - noVNC.pdf

Before all this, I set KVM: "N" for both of my windows and ubuntu pc failed with KVM and I couldn't solve it.

So is the docker error caused by KVM, or a missing args when calling qemu-system-x86_64? I'm not sure.