is there a way to Remove scsi controller beyond what is available in prism.

  • 1 October 2015
  • 3 replies
  • 1016 views

Badge +2
I can remove the controller using 'virsh edit' or through virt-manager connected to the host, but those changes do not persist, and Acropolis adds the scsi controller back in when the VM is started.Is there any supported way to do edit VM properties beyond what is exposed in Prism and to have the changes persist?

This topic has been closed for comments

3 replies

Userlevel 2
Badge +10
Hi 

why would you need to remove SCSI controller for ?
Badge +2
Hi 

I can get the VM running on a bare-metal KVM instance (when the scsi is removed) however it is failing to load the application properly boot the VM on Acropolis.
  • The root cause appears to be an issue with the ISCSI controller being injected in to the VM on start-up.
  • We are able to modify the hardware to remove the ISCSI controller from the VM, however on reboot it gets put back in – presumably from Acropolis

Some anecdotal evidence points to the VRR getting stuck at the same stage if a scsi controller is attached to the KVM domain. Dropping to virsh on the CVM or the host does in fact confirm that a scsi controller is attached to the VM:

[root@NTNX-926f9432-A ~]# virsh dumpxml b92f4c7f-07d1-47df-b365-f58ff2a5d8e4 | grep -A 3 virtio-scsi






The VM's disk is attached to the IDE bus, so it doesn't need a scsi controller and it is possibly blocking a proper boot here.
Userlevel 6
Badge +29
- I stumbled across this thread, what sort of guest OS are you using?

It sounds like your guest OS doesnt support virtio.

Either way, if you haven't already, I'd recommend opening a ticket on portal.nutanix.com, so we can formally track this.