Question about skipping virDomainDiskDefAssignAddress

[Motohiro Kawahito]

> From: "Daniel P. Berrangé" <berrange at redhat.com>
> To: Motohiro Kawahito <JL25131 at jp.ibm.com>
> Cc: libvir-list at redhat.com
> Date: 2021/07/16 17:22
> Subject: [EXTERNAL] Re: Question about skipping 
virDomainDiskDefAssignAddress
> 
> On Fri, Jul 16, 2021 at 01:01:50PM +0900, Motohiro Kawahito wrote:
> > > From: "Daniel P. Berrangé" <berrange at redhat.com>
> > > To: Motohiro Kawahito <JL25131 at jp.ibm.com>
> > > Cc: libvir-list at redhat.com
> > > Date: 2021/07/16 00:42
> > > Subject: [EXTERNAL] Re: Question about skipping 
> > virDomainDiskDefAssignAddress
> > > 
> > 
> > > With the exception of paravirtualized Xen guests, this field in
> > > libvirt XML is *completely* independant of the guest assigned
> > > device name.
> > > 
> > > eg the XML might say /dev/vda, but the guest might decde to
> > > call it /dev/sda, or /dev/whatever or really absolutely
> > > anything.
> > 
> > Thank you very much for this information! I understand it. 
> > However, I don't understand how we can pass the target device 
information 
> > (e.g. 0A80) without an error. Do you know how to do it?
> > 
> > My question was not good, so I opened another thread (How do we 
specify 
> > disk device names for non-Linux VMs in XML?).
> 
> There is nothing that needs passing. The guest OS decides its naming
> however it wants to.

We need to control device number from user. This device number would be 
used later, such as detach-disk. Can we pass device number from outside?

Thanks,
Motohiro Kawahito, Commercial Systems, IBM Research - Tokyo
19-21 Nihonbashi, Hakozaki-cho Chuo-ku, Tokyo 103-8510, Japan 


"Daniel P. Berrangé" <berrange at redhat.com> wrote on 2021/07/16 17:21:45:

> From: "Daniel P. Berrangé" <berrange at redhat.com>
> To: Motohiro Kawahito <JL25131 at jp.ibm.com>
> Cc: libvir-list at redhat.com
> Date: 2021/07/16 17:22
> Subject: [EXTERNAL] Re: Question about skipping 
virDomainDiskDefAssignAddress
> 
> On Fri, Jul 16, 2021 at 01:01:50PM +0900, Motohiro Kawahito wrote:
> > > From: "Daniel P. Berrangé" <berrange at redhat.com>
> > > To: Motohiro Kawahito <JL25131 at jp.ibm.com>
> > > Cc: libvir-list at redhat.com
> > > Date: 2021/07/16 00:42
> > > Subject: [EXTERNAL] Re: Question about skipping 
> > virDomainDiskDefAssignAddress
> > > 
> > 
> > > With the exception of paravirtualized Xen guests, this field in
> > > libvirt XML is *completely* independant of the guest assigned
> > > device name.
> > > 
> > > eg the XML might say /dev/vda, but the guest might decde to
> > > call it /dev/sda, or /dev/whatever or really absolutely
> > > anything.
> > 
> > Thank you very much for this information! I understand it. 
> > However, I don't understand how we can pass the target device 
information 
> > (e.g. 0A80) without an error. Do you know how to do it?
> > 
> > My question was not good, so I opened another thread (How do we 
specify 
> > disk device names for non-Linux VMs in XML?).
> 
> There is nothing that needs passing. The guest OS decides its naming
> however it wants to.
> 
> 
> Regards,
> Daniel
> -- 
> |: INVALID URI REMOVED
> u=https-3A__berrange.com&d=DwIDaQ&c=jf_iaSHvJObTbx-
> siA1ZOg&r=QxJ1l_N36pgeWfjA-
> 
IAUp8rdIFxYQBPq2WW0vIGQ9UE&m=3Ydoa2LishfBM6RsL-18A7A6B0KwJq5P1Pz1HUEFVR8&s=tsoEpMWLZOkv2Z2JnxoZX6IhaeqbXFHXKz-
> BKqYkXXo&e=       -o-    INVALID URI REMOVED
> u=https-3A__www.flickr.com_photos_dberrange&d=DwIDaQ&c=jf_iaSHvJObTbx-
> siA1ZOg&r=QxJ1l_N36pgeWfjA-
> 
IAUp8rdIFxYQBPq2WW0vIGQ9UE&m=3Ydoa2LishfBM6RsL-18A7A6B0KwJq5P1Pz1HUEFVR8&s=q1LDnF5y7kh5TDggyuQXXkjeUIkOTCE3ZzF-
> PMMUSas&e=  :|
> |: INVALID URI REMOVED
> u=https-3A__libvirt.org&d=DwIDaQ&c=jf_iaSHvJObTbx-
> siA1ZOg&r=QxJ1l_N36pgeWfjA-
> 
IAUp8rdIFxYQBPq2WW0vIGQ9UE&m=3Ydoa2LishfBM6RsL-18A7A6B0KwJq5P1Pz1HUEFVR8&s=mHcYlrzeVj8Xfa7aOJBVzaN6xwt0UOpisCw48oHyeZE&e=
> -o-            INVALID URI REMOVED
> u=https-3A__fstop138.berrange.com&d=DwIDaQ&c=jf_iaSHvJObTbx-
> siA1ZOg&r=QxJ1l_N36pgeWfjA-
> 
IAUp8rdIFxYQBPq2WW0vIGQ9UE&m=3Ydoa2LishfBM6RsL-18A7A6B0KwJq5P1Pz1HUEFVR8&s=X5oSjlmRkG8Q5WwavqgQCXQDLKdSReAdEnCbcqJXKTs&e=
> :|
> |: INVALID URI REMOVED
> u=https-3A__entangle-2Dphoto.org&d=DwIDaQ&c=jf_iaSHvJObTbx-
> siA1ZOg&r=QxJ1l_N36pgeWfjA-
> 
IAUp8rdIFxYQBPq2WW0vIGQ9UE&m=3Ydoa2LishfBM6RsL-18A7A6B0KwJq5P1Pz1HUEFVR8&s=QqOu1011otltc_p-
> N0vNWWAp5TthAuVvzdyew7DlF9Y&e=     -o-    https://
> urldefense.proofpoint.com/v2/url?
> u=https-3A__www.instagram.com_dberrange&d=DwIDaQ&c=jf_iaSHvJObTbx-
> siA1ZOg&r=QxJ1l_N36pgeWfjA-
> 
IAUp8rdIFxYQBPq2WW0vIGQ9UE&m=3Ydoa2LishfBM6RsL-18A7A6B0KwJq5P1Pz1HUEFVR8&s=NIQYzwvaiBVe9ypQAT6hvfHsJGi6rI5ws3TgL_MrYx8&e=
> :|
> 


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/libvir-list/attachments/20210716/0b439af1/attachment-0001.htm>