On Fri, Jan 03, 2014 at 11:25:04AM +0100, Michal Skrivanek wrote:
> 
> On 26 Dec 2013, at 07:32, bigclouds wrote:
> 
> > the paramters received when vmCreate has a long part called custom,
> > do we use custom infomation?  what does the long key 
> > device_************************* means?
> 
> custom properties for devices
> see the UI Custom Properties tab in Edit VM

I think that bigclouds meant the bizarre-looking properties that are
sent by Engine automatically, with no human interventions, per VmDevice that is
reported by Vdsm but not managed by Engine:

'device_82934f8e-7470-4c46-b9ed-d1c73fb17477device_87f6330a-278d-4b2a-9674-db58eb0e7023device_a19855be-70a9-49d0-9ea4-ee746b2d9739':
 'VmDevice {vmId=46914913-8bcf-4fa0-b1fb-3680ca8b6c16, 
deviceId=a19855be-70a9-49d0-9ea4-ee746b2d9739, device=virtio-serial, 
type=CONTROLLER, bootOrder=0, specParams={}, address={bus=0x00, domain=0x0000, 
type=pci, slot=0x06, function=0x0}, managed=false, plugged=true, 
readOnly=false, deviceAlias=virtio-serial0, customProperties={}, 
snapshotId=null}'

It was an attempt for future-compatibility, by (ab)using the custom properties
interface. Certainly Eli or Igor can explain the motivation better.

Dan.
_______________________________________________
vdsm-devel mailing list
vdsm-devel@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel

Reply via email to