Skip to content

bug: vAccel misconfiguration errors silently swallowed in Exec() #698

@Chennamma-Hotkar

Description

@Chennamma-Hotkar

Description

In pkg/unikontainers/unikontainers.go errors returned by resolveVAccelConfig() are only printed at DEBUG level. In particular the function returns the same error type in two distinct cases: 1) when vAccel is disabled and 2) when
misconfiguration occured (missing or malformed RPCAddress). Thus the error is always ignored, and the container is launched without vAccel but with no warning.

System info

  • Urunc version: 0.7.0-154fc9e
  • Arch: x86_64
  • VMM: QEMU / Firecracker
  • Unikernel: any with vAccel annotations

Steps to reproduce

  1. Build an unconfined container spec with the following annotations set com.urunc.unikernel.vAccel=vsock
  2. Set com.urunc.unikernel.RPCAddress to a bogus value, e.g. badaddress
  3. Launch the container with urunc
  4. Notice urunc starts normally with no error or warning shown, vAccel silently not configured

LLM Disclosure

N/A

Metadata

Metadata

Assignees

No one assigned

    Labels

    HW accelHardware accelerationenhancementNew feature or request

    Type

    No fields configured for Task.

    Projects

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions