<HTML><HEAD> <META content="text/html; charset=utf-8" http-equiv=Content-Type> <META name=GENERATOR content="MSHTML 8.00.7601.19038"></HEAD> <BODY style="MARGIN: 4px 4px 1px; FONT: 10pt 微软雅黑"> <DIV>Hi list,</DIV> <DIV> </DIV> <DIV>I have a question about scsi controller while I create vm.</DIV> <DIV> </DIV> <DIV>For a existed vm, When user changed a virtual disk's bus type to scsi In VM details page,</DIV> <DIV>Then click 'apply' button, If this vm's configuration doesn't have any scsi controller, Libvirt</DIV> <DIV>will automatically add one and trigger a lifecycle event. Virt-manager rely on the event to</DIV> <DIV>refresh vm's hardware list, Then user can see the scsi controller which is automatically</DIV> <DIV>added by libvirt.</DIV> <DIV><BR>But when user installs a vm through virt-manager GUI, In VM details page(customize before</DIV> <DIV>install), User changes a virtual disk's bus type to scsi, Then click 'apply' button, There is no</DIV> <DIV>scsi controller in hardware list because libvirt won't help user to add a default scsi controller</DIV> <DIV>until user clicks 'Begin Installation' button. user may get user confused.<BR>In this case, If user wants to use virtio-scsi instead of the default one, User needs to manually</DIV> <DIV>add a scsi controller then change the scsi controller model.</DIV> <DIV> </DIV> <DIV>I refered to the logic of 'adding disk', want to write a patch to modify the logic of 'changing</DIV> <DIV>disk bus' to: Add a virtio-scsi scsi controller if needed while user change disk bus to scsi</DIV> <DIV>instead of relying on libvirt lifecycle event, Then user can see the scsi controller in hardware</DIV> <DIV>list before install.</DIV> <DIV> </DIV> <DIV>I'm not sure if the idea makes sense, or perhaps this is not an issue. So may I have your idea?</DIV> <DIV> </DIV> <DIV>Thanks,</DIV> <DIV>Lin</DIV></BODY></HTML>