Hi Brian, Thanks for review! I think I fixed based on all of your comments. (branch will update soon) Also, regarding to the point 3 below, > 3. We can use the "arch" sub-field below for our project. Can we talk about adding > accelerator_info (for GPUs, FPGAs, or other co-procesors) and possibly network_info > for details on the physical network interface? We use cpu_info column to store an argument of compareCPU() in virConnect. You can get examples following by the below procedure. # python # import libvirt # conn = libvirt.openReadOnly() # conn.getCapabilities() Once you follow above, you get xml. We cut and store ... to db. I think some other result will be shown in your hardware environment. Then FPGA/GPU info is also included, I suppose. If libvirt don’t find any FPGA/GPU info, then please let me know. I have to give it much thought.. -----Original Message----- From: