[ https://issues.apache.org/jira/browse/CLOUDSTACK-9083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15031563#comment-15031563 ]
ASF subversion and git services commented on CLOUDSTACK-9083: ------------------------------------------------------------- Commit cbb9c4acdf8262dd74d75df1309d46fa6c6102df in cloudstack's branch refs/heads/4.5 from [~rohit.ya...@shapeblue.com] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=cbb9c4a ] CLOUDSTACK-9083: Add disk serial to kvm virt xml Adds disk serial ids based on volume uuids to the virt xml. This may be useful for appliances/software that needs some serial ids on the VM disks. This does not impact existing/running VMs, the vm virt xmls will be updates for running VMs the next time they are stopped/started. For testing, disk serial (of debian based systemvm) in the virt xml matched that in /sys/devices/pci0000:00:0000:00:07.0/virtio4/block/vda/serial. Signed-off-by: Rohit Yadav <rohit.ya...@shapeblue.com> > Add disk serial to vm/libvirt xml in case of KVM > ------------------------------------------------ > > Key: CLOUDSTACK-9083 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9083 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Reporter: Rohit Yadav > Assignee: Rohit Yadav > Priority: Minor > Fix For: 4.5.3, 4.7.0, 4.6.1 > > > Certain appliances/software fail on KVM as they require disk serials (inside > of the VM). The fix would be to add a disk serial (from volume uuid) in the > generated libvirt xml for all disks except for lun/scsi block type disks > (which we don't support yet, so we can add in a deviceType for now and leave > some comment). -- This message was sent by Atlassian JIRA (v6.3.4#6332)