Operating system
Docker Desktop v4.58.0 on Windows 11 25H2
Description
It's expected to boot and run normally.
But when the boot is complete, after "You can now login" prompt, init will soon disconnect from D-Bus system bus, which will cause user to log off the DSM.
And when user logged back in, DSM just don't run any components and can only be able to use again after a restart.
Then D-Bus will be disconnected again and again.
This issue doesn't appear on DSM 7.* though, using the same "docker run" command.
Sorry for "KVM=N" but I didn't found a good way to enable KVM using run command.
Docker compose
docker run -it --privileged --name VirtualDSM -e "DISK_SIZE=32G" -e "RAM_SIZE=4G" -e "CPU_CORES=2" -e "MAC=[Secret]" -e "GUEST_SERIAL=[Secret]" -e "HOST_SERIAL=[Secret]" -e "HOST_MAC=[Secret]" -e "HOST_MODEL=[Secret]" -e "KVM=N" -p 5000:5000 -v "D:\Docker\dsm:/storage" -v "D:\Docker\dsm\DSM_VirtualDSM_25426.pat:/boot.pat" vdsm/virtual-dsm
Docker log
❯ Starting Virtual DSM for Docker v7.50...
❯ For support visit https://github.com/vdsm/virtual-dsm
❯ CPU: Intel Xeon E5 1620 v2 | RAM: 15/16 GB | DISK: 665 GB (v9fs) | KERNEL: 6.6.87.2-microsoft-standard-WSL2...
❯ Warning: KVM acceleration is disabled, this will cause the machine to run about 10 times slower!
❯ Warning: your container IP starts with 172.17.* which will cause conflicts when you install the Container Manager package inside DSM!
❯ Nested Hyper-V virtualization detected..
❯ Booting Virtual DSM using QEMU v10.0.6...
...
[ 99.593534] 2026-2-1 23:31:13 UTC
[ 99.593998] synobios: load, major number 201
[ 99.596977] Brand: Synology
[ 99.598424] Model: VirtualDSM
[ 99.604795] set group disks wakeup number to 4, spinup time deno 7
[ 99.605583] synobios cpu_arch proc entry initialized
[ 99.605583] synobios crypto_hw proc entry initialized
[ 99.605583] synobios syno_platform proc entry initialized
[ 99.609803] synobios ioctl TCGETS /dev/ttyS1 failed
[ 99.610349] synobios unable to set termios of /dev/ttyS1
[ 123.252709] init: dhcp-client (eth0) main process (6657) killed by TERM signal
[ 124.615712] BTRFS: device label 2026.02.01-23:10:01 v25426 devid 1 transid 30 /dev/sdb1
[ 124.671025] BTRFS info (device sdb1): enabling auto syno reclaim space
[ 124.683810] BTRFS info (device sdb1): turning on discard
[ 124.685036] BTRFS info (device sdb1): use ssd allocation scheme
[ 124.688771] BTRFS info (device sdb1): using free space tree
[ 124.691136] BTRFS info (device sdb1): has skinny extents
[ 156.847504] usbcore: registered new interface driver usb-storage
[ 157.336731] usbcore: registered new interface driver usblp
[ 158.220561] usbcore: registered new interface driver usbhid
[ 158.234399] usbhid: USB HID core driver
[ 187.441945] iSCSI:target_core_rodsp_server.c:1027:rodsp_server_init RODSP server started, login_key(0211320c37cd).
[ 187.800587] iSCSI:extent_pool.c:766:ep_init syno_extent_pool successfully initialized
VirtualDSM login: [ 188.275307] iSCSI:target_core_device.c:617:se_dev_align_max_sectors Rounding down aligned max_sectors from 4294967295 to 4294967288
[ 188.305874] iSCSI:target_core_lunbackup.c:361:init_io_buffer_head 512 buffers allocated, total 2097152 bytes successfully
[ 188.650569] iSCSI:target_core_file.c:146:fd_attach_hba RODSP plugin for fileio is enabled.
[ 188.687450] iSCSI:target_core_file.c:153:fd_attach_hba ODX Token Manager is enabled.
[ 188.710757] iSCSI:target_core_multi_file.c:91:fd_attach_hba RODSP plugin for multifile is enabled.
[ 188.734757] iSCSI:target_core_ep.c:786:ep_attach_hba RODSP plugin for epio is enabled.
[ 188.756485] iSCSI:target_core_ep.c:793:ep_attach_hba ODX Token Manager is enabled.
[ 192.310350] capability: warning: `nginx' uses 32-bit capabilities (legacy support in use)
[ 210.060040] init: scsi_plugin_server main process (9966) killed by TERM signal
[ 214.755895] init: iscsi_pluginengined main process (9961) killed by KILL signal
[ 215.076967] init: scsi_plugin_server main process (10724) killed by TERM signal
[ 216.383954] loop: module loaded
[ 228.460609] sfdisk (11156): drop_caches: 3
❯ -----------------------------------------------------------
❯ You can now login to DSM at port 5000
❯ -----------------------------------------------------------
[ 388.864863] init: synostoraged main process (7995) terminated with status 15
[ 391.462880] init: synonetd main process (5719) killed by TERM signal
[ 400.659351] init: synoguestcommd main process (5388) terminated with status 255
[ 403.069976] init: synoguestcmdd main process (5456) killed by TERM signal
[ 411.598635] init: scsi_plugin_server main process (10902) killed by TERM signal
[ 413.596547] init: smbd main process (10052) killed by TERM signal
[ 420.435970] init: pgsql pre-stop process (12978) terminated with status 2
[ 437.000902] init: hotplugd main process (8610) killed by TERM signal
[ 442.597509] init: Disconnected from D-Bus system bus
Screenshots (optional)
No response
Operating system
Docker Desktop v4.58.0 on Windows 11 25H2
Description
It's expected to boot and run normally.
But when the boot is complete, after "You can now login" prompt, init will soon disconnect from D-Bus system bus, which will cause user to log off the DSM.
And when user logged back in, DSM just don't run any components and can only be able to use again after a restart.
Then D-Bus will be disconnected again and again.
This issue doesn't appear on DSM 7.* though, using the same "docker run" command.
Sorry for "KVM=N" but I didn't found a good way to enable KVM using run command.
Docker compose
docker run -it --privileged --name VirtualDSM -e "DISK_SIZE=32G" -e "RAM_SIZE=4G" -e "CPU_CORES=2" -e "MAC=[Secret]" -e "GUEST_SERIAL=[Secret]" -e "HOST_SERIAL=[Secret]" -e "HOST_MAC=[Secret]" -e "HOST_MODEL=[Secret]" -e "KVM=N" -p 5000:5000 -v "D:\Docker\dsm:/storage" -v "D:\Docker\dsm\DSM_VirtualDSM_25426.pat:/boot.pat" vdsm/virtual-dsmDocker log
Screenshots (optional)
No response