Re: [Xen-devel] 4.7 qemu regression: HVM guests fail to boot from xvda

[Olaf Hering <olaf@xxxxxxxxx>]

On Tue, May 31, Olaf Hering wrote:

> On Tue, May 31, George Dunlap wrote:
> 
> > Do you have a concrete proposal?
> 
> I have to give it some more thought what the impact really is, what
> config variants are affected.

Here is a list. Essentially it means that upgrading dom0 to xen-4.7
might break existing domU if they happen to use xvd* in domU.cfg:

 device names which the emulated BIOS can boot from:
  num       tool_ver        vdev_str        bootable
  01        xen-4.2           hd              yes
  02        xen-4.2           xvd             no
  03        xen-4.3           hd              yes
  04        xen-4.3           xvd             yes
  05        xen-4.4           hd              yes
  06        xen-4.4           xvd             yes
  07        xen-4.5           hd              yes
  08        xen-4.5           xvd             yes
  09        xen-4.6           hd              yes
  10        xen-4.6           xvd             yes
  11        xen-4.7-rc        hd              yes
  12        xen-4.7-rc        xvd             no

 block frontend drivers which will use the vdev_str:
  a) pvops    no  (defaults to xvd)
  b) xenlinux yes
  c) solaris  ??? (Konrad suggests yes)
  d) bsd      ???
  e) windows  ??? (likely no due to drive letters)

domU.cfg configuration which will break with xen-4.7:
04|06|08|10 -> 12
after adjusting to 11 to allow boot again:
b + 11

In real life this means existing SLE11/SLE12/openSUSE domU with
vdev_str==xvd when dom0 is upgraded to xen-4.7, and the domU makes use
of kernel device names.

Olaf

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel