How should I resolve the following errors? about windows

[kroese]

Yes but this container is more for people who dont have something like VMM on their system. If you have VMM, it is much better for the job than this container.

By the way: I also made a version of DSM for Docker. And that one works 100 percent on a Synology too. See https://github.com/vdsm/virtual-dsm/ if you like.

[kroese]

Can you post your compose file? To see which settings you have configured?

[rongchun]

Can you post your compose file? To see which settings you have configured?

I established it through the following command.
docker run -it -p 8009:8006 -v /volume1/docker/win:/storage --device=/dev/kvm --cap-add=NET_ADMIN dockurr/windows

[kroese]

That looks normal! Can you tell me a bit more about your system? What OS is it? What CPU?

[rongchun]

That looks normal! Can you tell me a bit more about your system? What OS is it? What CPU?

Synology DSM 7.2.1 DOCKER 20.10.23-1437 INTEL Celeron J4125

[kroese]

Can you try these commands:

docker run -it -p 8009:8006 -v /volume1/docker/win:/storage -v /volume1/docker/winshm:/dev/shm --device=/dev/kvm --cap-add=NET_ADMIN dockurr/windows

docker run -it -p 8009:8006 -v /volume1/docker/win:/storage --shm-size 512m --device=/dev/kvm --cap-add=NET_ADMIN dockurr/windows

docker run -it -p 8009:8006 -v /volume1/docker/win:/storage --device=/dev/kvm --device=/dev/shm --cap-add=NET_ADMIN dockurr/windows

[rongchun]

Can you try these commands:

docker run -it -p 8009:8006 -v /volume1/docker/win:/storage -v /volume1/docker/winshm:/dev/shm --device=/dev/kvm --cap-add=NET_ADMIN dockurr/windows

docker run -it -p 8009:8006 -v /volume1/docker/win:/storage --shm-size 512m --device=/dev/kvm --cap-add=NET_ADMIN dockurr/windows

docker run -it -p 8009:8006 -v /volume1/docker/win:/storage --device=/dev/kvm --device=/dev/shm --cap-add=NET_ADMIN dockurr/windows

2024/01/23 08:16:10,stdout,"qemu-system-x86_64: -chardev socket,id=chrtpm,path=/dev/shm/tpm/swtpm-sock: Failed to connect to '/dev/shm/tpm/swtpm-sock': No such file or directory
The same error still exists. After adding/dev/shm/tpm/swtpm sock, the error is as follows:
ERROR: Status 1 while: swtpm socket -t -d --tpmstate dir=/dev/shm/tpm --ctrl type=unixio,path=/dev/shm/tpm/swtpm-sock --tpm2 (line 64/15)�[0m

[kroese]

I made some changes regarding to this issue. Can you please pull the lastest tag and see it fixed your issue?

[rongchun]

I made some changes regarding to this issue. Can you please pull the lastest tag and see it fixed your issue?

OK.I will give it a try when I have time.

[rongchun]

I made some changes regarding to this issue. Can you please pull the lastest tag and see it fixed your issue?

The stop error after startup is as follows:

dockurr-windows-1
date,stream,content
2024/01/23 13:15:08,stdout,"BdsDxe: starting Boot0001 "UEFI QEMU QEMU CD-ROM " from PciRoot(0x0)/Pci(0x5,0x0)/Scsi(0x0,0x0)

"
2024/01/23 13:15:08,stdout,"BdsDxe: loading Boot0001 "UEFI QEMU QEMU CD-ROM " from PciRoot(0x0)/Pci(0x5,0x0)/Scsi(0x0,0x0)

"
2024/01/23 13:15:07,stdout,"�[2J�[01;01H�[=3h�[2J�[01;01H�[2J�[01;01H�[=3h�[2J�[01;01H�[2J�[01;01H�[=3h�[2J�[01;01HBdsDxe: failed to load Boot0002 "UEFI QEMU QEMU HARDDISK " from PciRoot(0x0)/Pci(0xA,0x0)/Scsi(0x0,0x0): Not Found

"
2024/01/23 13:14:34,stdout,�[1;34m❯ �[1;36mBooting Windows using QEMU emulator version 8.1.2 ...�[0m

2024/01/23 13:14:34,stdout,�[1;31m❯ ERROR: TPM socket not found? Disabling TPM support...�[0m

2024/01/23 13:14:33,stdout,Waiting for TPM socket to become available...

2024/01/23 13:14:32,stdout,Waiting for TPM socket to become available...

2024/01/23 13:14:31,stdout,Waiting for TPM socket to become available...

2024/01/23 13:14:30,stdout,Waiting for TPM socket to become available...

2024/01/23 13:14:29,stdout,swtpm: seccomp_load failed with errno 125: Operation canceled

2024/01/23 13:14:05,stdout,Warning: creating filesystem that does not conform to ISO-9660.

2024/01/23 13:14:05,stdout,�[1;34m❯ �[1;36mGenerating the ISO image...�[0m

2024/01/23 13:13:45,stdout,�[1;34m❯ �[1;36mExtracting local ISO image...�[0m

2024/01/23 13:13:45,stdout,

2024/01/23 13:13:45,stdout,❯ For support visit https://github.com/dockur/windows

2024/01/23 13:13:45,stdout,❯ Starting Windows for Docker v1.10...

[rongchun]

I made some changes regarding to this issue. Can you please pull the lastest tag and see it fixed your issue?

Do I need to modify the BIOS？

[rongchun]

I made some changes regarding to this issue. Can you please pull the lastest tag and see it fixed your issue?
Keep spinning. It has been going on for an hour.

[kroese]

I am not sure what the problem is, it might have something to do with the kernel that Synology uses. But Virtual Machine Manager (VMM) on Synology also uses QEMU, and has much more options than this container. So maybe its easier that you use VMM to run Windows instead?

[rongchun]

I am not sure what the problem is, it might have something to do with the kernel that Synology uses. But Virtual Machine Manager (VMM) on Synology also uses QEMU, and has much more options than this container. So maybe its easier that you use VMM to run Windows instead?

Of course, I am also using VMM. I just want to try using it because you have released the DOCKER version. Thank you very much for your reply.

[rongchun]

Yes but this container is more for people who dont have something like VMM on their system. If you have VMM, it is much better for the job than this container.

By the way: I also made a version of DSM for Docker. And that one works 100 percent on a Synology too. See https://github.com/vdsm/virtual-dsm/ if you like.

OK. Thank you.

[kroese]

There is a way to solve this maybe.. You can start a Windows VM via Virtual Machine Manager. Then go to the SSH console and use a command like htop to view the running processes. Then you can see exactly the commandline parameters for the qemu-system-x86_64 process. If you post them here, we can compare the differences between what VMM uses, and what this container uses, and if we make them more the same then it should run on your NAS without problems.

[rongchun]

There is a way to solve this maybe.. You can start a Windows VM via Virtual Machine Manager. Then go to the SSH console and use a command like htop to view the running processes. Then you can see exactly the commandline parameters for the qemu-system-x86_64 process. If you post them here, we can compare the differences between what VMM uses, and what this container uses, and if we make them more the same then it should run on your NAS without problems.

OK.I will give it a try when I have free time

[kroese]

Can you try if Windows 7 works correctly on your NAS? By setting VERSION=win7.

It does not use secure boot or UEFI, so if the container works correctly when you choose Win7 we know a bit more about the possible cause.