Re: [Qemu-devel] [PATCH] s390: set DHCP client architecure id for netboot

2017-09-12 Thread Cornelia Huck
On Mon, 11 Sep 2017 12:33:47 +0200 Viktor Mihajlovski wrote: > Setting the client architecture DHCP option to 0x001f (s390 Basic) [1] > allows the DHCP server to return a s390-specific bootfile if wanted. > DHCP servers not configured for the option (or not yet

Re: [Qemu-devel] [PATCH] s390: set DHCP client architecure id for netboot

2017-09-11 Thread Viktor Mihajlovski
On 11.09.2017 15:58, Thomas Huth wrote: > On 11.09.2017 12:33, Viktor Mihajlovski wrote: >> Setting the client architecture DHCP option to 0x001f (s390 Basic) [1] >> allows the DHCP server to return a s390-specific bootfile if wanted. >> DHCP servers not configured for the option (or not yet

Re: [Qemu-devel] [PATCH] s390: set DHCP client architecure id for netboot

2017-09-11 Thread Thomas Huth
On 11.09.2017 12:33, Viktor Mihajlovski wrote: > Setting the client architecture DHCP option to 0x001f (s390 Basic) [1] > allows the DHCP server to return a s390-specific bootfile if wanted. > DHCP servers not configured for the option (or not yet recognizing the > option value) will continue to

Re: [Qemu-devel] [PATCH] s390: set DHCP client architecure id for netboot

2017-09-11 Thread Christian Borntraeger
On 09/11/2017 12:33 PM, Viktor Mihajlovski wrote: > Setting the client architecture DHCP option to 0x001f (s390 Basic) [1] > allows the DHCP server to return a s390-specific bootfile if wanted. > DHCP servers not configured for the option (or not yet recognizing the > option value) will continue

[Qemu-devel] [PATCH] s390: set DHCP client architecure id for netboot

2017-09-11 Thread Viktor Mihajlovski
Setting the client architecture DHCP option to 0x001f (s390 Basic) [1] allows the DHCP server to return a s390-specific bootfile if wanted. DHCP servers not configured for the option (or not yet recognizing the option value) will continue to work as they have done before. [1]