search for: postparse

Thanks for your reply what i want to know is that why there are many devices in $domain.xml, actully , i choose nothing in virt-manager? so, Do i need to look at qemuDomainDefineXMLFlags()? hours ago, i thought it's qemuDomainCreateWithFlags. -- Have a good day > -----原始邮件----- > 发件人: Michal Privoznik <mprivozn@redhat.com> > 发送时间: 2018年4月26日 星期四 > 收件人: "李卓瑶"

...#39;t select anything in virt-manager the domain will definitely have a PCI root controller, controller for disk bus (be it sata, scsi, ide, ..), then it'll also have a virtual NIC, some memory/cpu configuration, and so on. In the code, these devices are added once XML is parsed by virDomainDefPostParseInternal(). Each driver can pass this xmlopt structure filled in with callbacks (take a look at virQEMUDriverCreateXMLConf()). So in the end, devices are added only after XML is parsed. However, it is not done all in one place. For instance, controllers are added during device address assignment, ot...

...virt-manager the domain will definitely have a PCI root controller, > controller for disk bus (be it sata, scsi, ide, ..), then it'll also > have a virtual NIC, some memory/cpu configuration, and so on. > > In the code, these devices are added once XML is parsed by > virDomainDefPostParseInternal(). Each driver can pass this xmlopt > structure filled in with callbacks (take a look at > virQEMUDriverCreateXMLConf()). So in the end, devices are added only > after XML is parsed. However, it is not done all in one place. For > instance, controllers are added during device ad...

Folks, Following the discussion with Nico and others, I've created PR20683 to discuss about the implementation of a generic and externalised target specific parsing API for LLVM, Clang and others. I have a vague plan involving a generic class (say TargetParser) in lib/Target that is accessible as an API to any tool that needs target specific parsing. The idea is then to let targets implement