The other day, I described how my attempt to implement Paolo's suggestion to add block properties to the machine ran into difficulties. To recap briefly, creating devices within a machine's .instance_init() crashes. Turns out device_post_init() calls qdev_get_machine(), which calls container_get() for QOM path "/machine". Since "/machine" doesn't exist, yet (we're busy creating it), container_get() "helpfully" creates it as a new "container" object. Oww. Fortunately, we crash soon after, when we try to create the real "/machine". I managed to rejigger global property application code to work without qdev_get_machine(). Good. Not so good: QEMU still crashes the same way. Turns out we *also* call qdev_get_machine() on the first sysbus_get_default(). We create the main system bus then, and immediately store it in "/machine/unattached/sysbus". So container_get() "helpfully" creates first "/machine" and then "/machine/unattached" for us. I managed to rejigger that, too. Now my QEMU survives creating a pflash device in pc_machine_initfn(), and I can add a machine property "pflash0" with object_property_add_alias(). Good. Not so good: attempting to set it with -machine pflash0=pflash0 fails with "Property 'cfi.pflash01.drive' can't find value 'pflash0'". Turns out we set the machine's properties around line 4250, some 140 lines before we create block backends. Block backend "pflash0" doesn't exist, yet. This is madness, but at least it's familiar madness; we've rejiggered the order of creating stuff in main() numerous times already. To be continued... -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list
