STRUCT VIRTIO_DEVICE(9)

💖 NAME 💖

okay bestie, welcome to the struct virtio_device(9) page from the Kernel API Manual — it's literally the representation of a device using virtio. that's the whole vibe. periodt. ✨

✨ SYNOPSIS ✨

here's the struct in all its main-character glory, no edits, no cap:

       struct virtio_device {
           int index;
           bool failed;
           bool config_core_enabled;
           bool config_driver_disabled;
           bool config_change_pending;
           spinlock_t config_lock;
           spinlock_t vqs_list_lock;
           struct device dev;
           struct virtio_device_id id;
           const struct virtio_config_ops *config;
           const struct vringh_config_ops *vringh_config;
           const struct virtio_map_ops *map;
           struct list_head vqs;
           union {
             u64 features;
             u64 features_array[VIRTIO_FEATURES_U64S];
           };
           void *priv;
           union virtio_map vmap;
         #ifdef CONFIG_VIRTIO_DEBUG;
           struct dentry *debugfs_dir;
           u64 debugfs_filter_features[VIRTIO_FEATURES_U64S];
         #endif;
        };

🌸 Members 🌸

• index — its unique position on the virtio bus. like the bus's lil coordinate, bestie 🎀
• failed — saved value for the VIRTIO_CONFIG_S_FAILED bit (for restore). it's giving "remember this for later" energy 💅
• config_core_enabled — configuration change reporting enabled by core. core said "reporting on," slay ✨
• config_driver_disabled — configuration change reporting disabled by a driver. driver said "actually, off," okay then 💀
• config_change_pending — configuration change reported while disabled. it's waiting in the group chat, lowkey 🫶
• config_lock — protects configuration change reporting. the bodyguard for the config-change gossip 🔒
• vqs_list_lock — protects vqs. no cap, that's its whole job 🛡️
• dev — underlying device. the device underneath, literally 😌
• id — the device type identification (used to match it with a driver). matchmaker energy, fr fr 💘
• config — the configuration ops for this device. the config to-do list 🧚
• vringh_config — configuration ops for host vrings. host-vring config business 🌀
• map — the map operations for mapping virtio device memory. maps, but make it virtio memory 🗺️
• vqs — the list of virtqueues for this device. the virtqueue lineup 👑
• {unnamed_union} — anonymous. yes, that's the whole note, and honestly? iconic 🙈
• features — the 64 lower features supported by both driver and device. the lower 64, matching on both sides 🤝
• features_array — the full features space supported by both driver and device. the full feature space, no crumbs 🌈
• priv — private pointer for the driver's use. driver's lil private stash 🔐
• vmap — the map container with transport- or device-specific metadata. transport- or device-specific metadata lives here 🎀
• debugfs_dir — debugfs directory entry. a debugfs directory entry, periodt 📁
• debugfs_filter_features — features to be filtered set by debugfs. the features-to-be-filtered set by debugfs 🫧

👀 SEE ALSO 👀

Kernel file ./include/linux/virtio.h, plus struct virtqueue(9) and struct virtio_driver(9) — go read those if you want the full lore. iykyk 🦋

later bestie — this struct virtio_device(9) page came from ./include/linux, October 2026, and it's slaying into the sunset 💅🌈✨