Problems booting 4.10 kernel in HVMs

[Nicklaus McClendon]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

After updating an HVM to the 4.10 kernel, I have noticed the HVM will
no longer boot. I have experienced the behavior on the following version
s:

4.10.5_1 (Void Linux)
4.10.0-rc6 (Debian)

I haven't seen any 4.10 guest compatibility issues with Xen, so I'm
wondering if it is a bug with the version Qubes is using. Has anyone
else experienced these problems?
- --
kulinacs <nick...@kulinacs.com>
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEPL+ie5e8l/3OecVUuXLc0JPgMlYFAljUJOMACgkQuXLc0JPg
MlYZVg/8CPMoL2IxunWE1Z171a9Doqbc9ppPdrTb80/uUs0q4uF+FYJ5Pr0Zpi17
95CGQncaSkYbJg5Jyt6szew5dCu+T542o7euvWfDj9t3weEPRAHCOzNbb59/1KuF
+FNahC0IDWlIeg9n3sCr11EwAQnkUlyRM/r4LtCx7+W4Hjka4b0raGtHvKjylqt3
cqDRG9g4MxAmishnk+QIiYyDt3lIkUZZFqHgi1R229QJap9kzKBL0B4+CSttHD4u
5ENqF40A28rJfsdjO1GwFH7i2Xuztgyy7Fx3g/EQ+KkmMfdRrLeCpZgG2yx+yNKI
gblr32FC+pyTl+e2afRF6VoSytxBve9aOM2wHn87cvwMv6FTk0o3Sz21W4u57ZJt
HTERGh2lgZpk7g4icDMz8T7nvSBZsFz4mhDXKtaOxLtGH7phkSID8huf2ZbL8hRf
1csmJuS6eKTJQefUfcbempz5YDkhqr/mw0UYLCH83YC28afC5L6NgGfYSnDv5L38
a9c+EjSoWFNzqKFJwhAkXfFIZxJ4n7+/cXUezpu6ea+DsW8nbOhsw35HOFOdyvdA
5usYn8OeGXqYmQruvfzSLCKCTghVoBsFPHCXOi47PissNuNOgkYqNho3JL1xldvb
CrNRmRR6ZLPi3ikPUerwuGKU7YHfen4Heuv5/SdrDc276zfmQqc=
=0aCY
-----END PGP SIGNATURE-----

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Thu, Mar 23, 2017 at 02:41:27PM -0500, Nicklaus McClendon wrote:
> After updating an HVM to the 4.10 kernel, I have noticed the HVM will
> no longer boot. I have experienced the behavior on the following version
> s:
>
> 4.10.5_1 (Void Linux)
> 4.10.0-rc6 (Debian)
>
> I haven't seen any 4.10 guest compatibility issues with Xen, so I'm
> wondering if it is a bug with the version Qubes is using. Has anyone
> else experienced these problems?

Do you have any console output, any crash message?

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJY1DRbAAoJENuP0xzK19cswykIAIBeeG2H++nFKKKVKRjmEWxJ
NR2g6N91U4hg+Vea5VURxULMxPpDtMJBsPG7dQKMV/3O6SBHjIM566sZRSr/1DLP
3Kd7VUVUA+bUMvXTSgZbt2NU3MgCEiUamgmUfUXve/AB0aqmOkNc2GzcmHvIxO3D
qTg457ZWnXXZgMwD2W/2F6bD3hIyQ5nH03YCiwpAWcxFuQVTpquhfAuTRk+vUDtm
J5gpaO0ZQ25OG8Z3A9QHdZs3MjqNWvAlqK+s8w2o56CE64ZjnLolqr7gEyneJaHY
Pu0yFS4LdymtifLjQV3gDk1CRsr7L5vMYgtNlVNeVuOW8iEh3px6DlKbNV3u0qs=
=Nzhe
-----END PGP SIGNATURE-----

[Nicklaus McClendon]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 03/23/2017 03:47 PM, Marek Marczykowski-Górecki wrote:
> On Thu, Mar 23, 2017 at 02:41:27PM -0500, Nicklaus McClendon
> wrote:
>> After updating an HVM to the 4.10 kernel, I have noticed the HVM
>> will no longer boot. I have experienced the behavior on the
>> following version s:
>
>> 4.10.5_1 (Void Linux) 4.10.0-rc6 (Debian)
>
>> I haven't seen any 4.10 guest compatibility issues with Xen, so
>> I'm wondering if it is a bug with the version Qubes is using. Has
>> anyone else experienced these problems?
>
> Do you have any console output, any crash message?
>
>

It crashes while loading the initial ramdisk. In the case of Debian
the screen goes white, for Void Linux it just freezes. Neither display
any console output.

- --
kulinacs <nick...@kulinacs.com>
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEPL+ie5e8l/3OecVUuXLc0JPgMlYFAljUNpUACgkQuXLc0JPg
MlZc9A//Thy+uDaeiHBKxU0eemCVr8Y6WD7PoH9lTA7h985jQU+FKwXcM22IkwgL
I14/MvDMTW4Di3tV1aiOKq9IjVnIt5tTepAHMQei+F0yYcKwLBD4J4NM/EknHEF2
t0GLm46BSeTpUYLzQIK6klvJYGvYAAk/VrPChwzoQ1PCwSSkVYykuk18Yq6BUQtW
iY+NYfjs9p9FBrFmhoskumuLnuUEcAOXZxy+Vdwz8Uqk3Lts4+Ziu6OPIMa6fh9U
zBCIU8hZQe0kcELoJTagU87n6c9Ief19ClxP3RdeovaXpY1dsq0CofpOeHh+r7MD
qATEZWslBYMCttlLT34qNYGpE6/1fKO8XfOcgI35JEB/Jj6BJKy0r7ZbABV7z0Uj
vOcsZ32cQwA8I2Ia8ajA5xiA8EjXlR8b7bzQ3MD4zin0bboTtt/SxgxiPPRIhMiY
1SlmVUDZ1aNPCudCfrUtcZgD0AmAi/DYGFTB1OrQZoYU1iYiHfcuRNQGJDfq2QAO
t3yrZLDy90Uj2hpt+wyEKMVEv2/knE9b4Kz4Z93vfjkJVaX4XQRUEwbETpjNFC4+
7AeJuVfFziLISBQtUj059qWdGlcMw0HmFERHY/lNaJwqLy9gzD/nqyQgR2+t8DQ3
3nHmifI5ZuXdV14LPM4GKKWtK+IVYh1UnD6O26x0na6QM6U8OQ8=
=aGoz
-----END PGP SIGNATURE-----

[Nicklaus McClendon]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 03/23/2017 03:56 PM, Nicklaus McClendon wrote:
> On 03/23/2017 03:47 PM, Marek Marczykowski-Górecki wrote:
>> On Thu, Mar 23, 2017 at 02:41:27PM -0500, Nicklaus McClendon
>> wrote:
>>> After updating an HVM to the 4.10 kernel, I have noticed the
>>> HVM will no longer boot. I have experienced the behavior on
>>> the following version s:
>
>>> 4.10.5_1 (Void Linux) 4.10.0-rc6 (Debian)
>
>>> I haven't seen any 4.10 guest compatibility issues with Xen,
>>> so I'm wondering if it is a bug with the version Qubes is
>>> using. Has anyone else experienced these problems?
>
>> Do you have any console output, any crash message?
>
>
> It crashes while loading the initial ramdisk. In the case of
> Debian the screen goes white, for Void Linux it just freezes.
> Neither display any console output.
>
>

For anyone following this problem, I have successfully booted kernel
4.10.10_1 in an HVM following vmm-xen v4.6.5-26 (r3.2).

- --
kulinacs <nick...@kulinacs.com>
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEPL+ie5e8l/3OecVUuXLc0JPgMlYFAlj1ZPkACgkQuXLc0JPg
MlZaYw//ccfQ/oIKAXZ92h0uJn6Sh1dAUPEPYoKqMKHvA0UaQOX5gaj+ookefx6F
QwzkO6VA/w/tVoWj2n7akFXlg/tpfM4iZx4ElMyiWQ7UQIPrJUmwe0et/abcSuaY
rBnxgmlN7e5L9JxsAK3/a0k/cd59CKBknU9UTo9CJOLrvaNVF5kzQvUsEX2q2aL2
F1xOsQtnaKOFGc0eiQRKUA/MSEQU3UL4du16Uq/HbfjgA7TOZmbLUB6L5mYWf9Fm
/bft8T1Wo17cjDh5moDlMWdXY9ab8bjBrWoC1jUXIfB79aZkp34oyhQene9UX/l9
JeWcElShvOePBv+nC4WwMGUhXf8IScyM5wBtC3d/C+YLTvsagCTYP843Lu4xduGa
7aFjoXSaWk2pP1X/HO4H0EnRCBJRSEqeqcj/iwRFdDGfTeLbByp8EkcUE8l7HmLd
aGDukh8KzyFnFIY2M1NXRsQLoA8O7xSad3LsfjsY0Nlgz8tuuNuyLXTlde7rAIOG
hv8ftzjeNiYrTbl/J48vMSbz+a7IQ9VCetD80ON1HDDsNoA/ovS+MP9ucv07c4I5
3Q4ZJXF7578ssfE45L+fNRp8Yu7qj3L0/86SEwwqPB9kFm+v25oWiD2MB6Chbn9g
e39JXkZAmcSJDnU6sRpwCy7eRGzte3aUznl9El+ONdv2Nt226UM=
=VUVi
-----END PGP SIGNATURE-----