Issue #3175 has been updated by tuxillo. Status changed from New to In Progress
The following parameters were used for booting with the same result, no disk found: CAM debugging options compiled in: options CAMDEBUG options CAM_DEBUG_BUS=-1 options CAM_DEBUG_TARGET=-1 options CAM_DEBUG_LUN=-1 options CAM_DEBUG_FLAGS="CAM_DEBUG_INFO|CAM_DEBUG_TRACE" options CAM_MAX_HIGHPOWER=4 options SCSI_DELAY=8000 # Be pessimistic about Joe SCSI device loader.conf has the following tunables: dm_load="YES" vfs.root.mountfrom="ufs:da0s2a" hw.vtscsi.debug_level=2 hint.ehci.0.disabled=1 hint.xhci.0.disabled=1 hw.virtio.pci.disable_msix=1 ---------------------------------------- Bug #3175: DragonFly won't boot on GCE http://bugs.dragonflybsd.org/issues/3175#change-13603 * Author: tuxillo * Status: In Progress * Priority: Normal * Assignee: * Category: Kernel * Target version: master ---------------------------------------- Hi, DragonFly does not detect disks when running on GCE, the virtio-scsi controller is detected tho. Here are there storage requirements that custom images need to fulfill [1]: SCSI Storage Controller: Virtio-SCSI Storage Controller vendor = 0x1AF4 (Qumranet/Red Hat) device id = 0x1004. Subsystem ID 0x8. SCSI Primary Commands 4 and SCSI Block Commands 3 are supported Only one request queue is supported Persistent disks report 4 KiB physical sectors / 512 byte logical sectors Only block devices (disks) are supported The Hotplug / Events feature bit is supported See attached dmesg with CAMDEBUG enabled and virtio debug set to level 5. [1] https://cloud.google.com/compute/docs/images/building-custom-os ---Files-------------------------------- dmesg_gce_camdebug.txt (920 KB) -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
