@factcheckingnewbie

Describe the bug

New arg to firecracker --enable-pci generates socket which not match per name with the referenced socket in the firecracker/docs

/getting-started.md

[Author TODO: A clear and concise description of what the bug is.]
Resulting socket is ls -la /tmp/firecracke* srwxr-xr-x. 1 root root 0 Aug 26 18:44 '/tmp/firecracker.socket --enable-pci'

To Reproduce

Start firecracker with the new arg intrduced in commit 431d77e.
`$API_SOCKET="/tmp/firecracker.socket"
$sudo ./firecracker --api-sock "${API_SOCKET} --enable-pci" &
$echo ${API_SOCKET}
/tmp/firecracker.socket
$ls -l /tmp/firecracker.*
srwxr-xr-x. 1 root root 0 Aug 26 18:57 '/tmp/firecracker.socket --enable-pci'

[Author TODO: Steps to reproduce the behaviour:]

1. Start Firecracker via....
2. Configure Firecracker via...
3. ...

Expected behaviour

[Author TODO: A clear and concise description of what you expected to happen.]

Environment

[Author TODO: Please supply the following information):]

• Firecracker version:Firecracker v1.12.1

• Host and guest kernel versions:Ubuntu 25.04

• Rootfs used:ext4

• Architecture:Ix86

• Any other relevant software versions:No, I believe this bug is reproducable everywhere, because the arg --enable-pci is quoted together with the declared socket path.

Additional context

[Author TODO: How has this bug affected you?]

[Author TODO: What are you trying to achieve?]

[Author TODO: Do you have any idea of what the solution might be?]

Checks

• Have you searched the Firecracker Issues database for similar problems?
• Have you read the existing relevant Firecracker documentation?
• Are you certain the bug being reported is a Firecracker issue?