Disk problems when installing ReactOS 0.4.5 on HVM

[Giulio]

Hello,
i need to run some simple windows applications that should run on ReactOS that compared to Windows has the advantage to be open source and very lightweight.

I have read
 - https://github.com/QubesOS/qubes-issues/issues/2809
 - https://github.com/Jeeppler/QubesOS-notes/blob/master/ReactOS/Qubes-ReactOS.md
 - https://mark911.wordpress.com/2017/12/09/procedure-for-installing-newest-reactos-operating-system-in-stand-alone-hvm-in-qubes-os-3-2/

My HCL report is attached.

This is the command i use to create the StandaloneVM

qvm-create reactos --class StandaloneVM --property virt_mode=hvm --property kernel="" property memory=4096 --property maxmem=4096 --label green

If i try booting the installation ISO the the procedure fails because it cannot recognize the block device. (install_error.png)
If i convert the VirtualBox image a similar error occur during boot. (virtualbox_error.png)

Is there someway i can change the device type in HVM? i.e. set it as an IDE device? I tried also installing Windows XP and it failed for a related reason.


[Marek Marczykowski-Górecki]

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

I've tried that already and it doesn't help (you exchange disk not found error
for crashing installation). This may be related to *much* newer qemu
version in Qubes 4.x, than was used in Qubes 3.x, apparently devices
emulated there are not supported by ReactOS drivers.

But, ReactOS live image seems to work much better.

- --
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-----

iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlqoDHAACgkQ24/THMrX
1yzpjgf/Zp0TKl3RHFJ1G4PLjIz/vlgdgOYJtI2mtYl4e/vvhbQH3arH93Jy7qzu
hXJkTGWlfTcaeIlJIFIqXOabRc++e0Q4/adp9XPYNazamRJb/BHMRnCwNTwZrl4L
5TyBB483HBBaXkRHUzBRxawfIqfKxPqG7rP7KJQMNbm4N3J2GBNHawintyj2hSEJ
Envau4J7wSzWaPlpaBD820j1EO2qzdgq8jANf+gCdJg5THcpWAXElzUzU4ulIM6M
BTfcsHdU+iQff0GUL8IV+Axec8+nW85iPhEvrNs5O6Ffxp/ETVp/3/pYMEi52ETv
XX0813yWsB4eckrWstnrOy2zpDRQxw==
=Wodv
-----END PGP SIGNATURE-----

[Marek Marczykowski-Górecki]

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

On Mon, Mar 19, 2018 at 11:21:39AM +0100, Giulio wrote:
>
> > I've tried that already and it doesn't help (you exchange disk not found error
> > for crashing installation). This may be related to *much* newer qemu
> > version in Qubes 4.x, than was used in Qubes 3.x, apparently devices
> > emulated there are not supported by ReactOS drivers.
> >
> > But, ReactOS live image seems to work much better.
>

> Thanks for the reponse. Whose issue do you think is it?

I'm not really sure. But there are other issues related to disk
currently emulated in Qubes, for example:
https://github.com/QubesOS/qubes-issues/issues/3651

> Should i continue
> the thread about reactos on qubes-issues or try to open an issue on reactos
> itself?

Getting in touch with ReactOS people is a good idea. My previous try
was on FOSDEM this year, having Colin Finck next to me, but we haven't
figured out what was wrong.
Later I may try recover logs from those failed attempts.

There is also tracking issue in their bugtracker:
https://jira.reactos.org/browse/CORE-13358
Probably not the best idea to add detailed problems directly there, but
linking related issues should help.

- --
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-----

iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlqpGfsACgkQ24/THMrX
1yz8qQf9FrI2VpNa5mD/UT24jNY6aofvqYvLE7/9ACwooAtSivWD3kPcXrrFx6kz
t2gbDDj4Y780tzf/fBRZBBm4zrZxh9e9wpgOoPla46JYEyK3FEFCH5hXkBGqE1+O
/1qK5Qt/wh5utdP3sjGYEUI//jtyUGJhP5gkSuyJBmiychDbzPFva/UNG1yLiiHF
r9M1OkngJaEv2WkJa6y3OHEnhqVOuiFenfYR451cQ2HFq72pRKKqIi2cqF9q12j1
mt42zQZEVw4AE+BTnkwktqz4zDLyupuVXpPR8KfIBLQ+tyMkIp4nVpyOTaIKkSyq
O0P4jPfVVEwli7tMwOh9m0ApHFudDg==
=EdgQ
-----END PGP SIGNATURE-----

[Marek Marczykowski-Górecki]

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

On Mon, Mar 19, 2018 at 11:37:10AM +0100, Marek Marczykowski-Górecki wrote:
> On Mon, Mar 19, 2018 at 11:21:39AM +0100, Giulio wrote:
> >
> > > I've tried that already and it doesn't help (you exchange disk not found error
> > > for crashing installation). This may be related to *much* newer qemu
> > > version in Qubes 4.x, than was used in Qubes 3.x, apparently devices
> > > emulated there are not supported by ReactOS drivers.
> > >
> > > But, ReactOS live image seems to work much better.
> >
> > Thanks for the reponse. Whose issue do you think is it?
>
> I'm not really sure. But there are other issues related to disk
> currently emulated in Qubes, for example:
> https://github.com/QubesOS/qubes-issues/issues/3651
>
> > Should i continue
> > the thread about reactos on qubes-issues or try to open an issue on reactos
> > itself?
>
> Getting in touch with ReactOS people is a good idea. My previous try
> was on FOSDEM this year, having Colin Finck next to me, but we haven't
> figured out what was wrong.
> Later I may try recover logs from those failed attempts.
>
> There is also tracking issue in their bugtracker:
> https://jira.reactos.org/browse/CORE-13358
> Probably not the best idea to add detailed problems directly there, but
> linking related issues should help.

There is an update from Colin about possible cooperation between Qubes
OS and React OS:
https://github.com/QubesOS/qubes-issues/issues/2809#issuecomment-377487490

- --
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-----

iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlq0MQwACgkQ24/THMrX
1yzoAAgAlsQL0l57lE91Cy4w0D2Pn9OvZqkf2IgpSGeHi/5Ukmw68DFkqI3kevYN
SRJjSKJ5qr7uPp4dquIFJQQaGgSbCfXjSkfcGYHpcN37YUHoDwCAPXV0VD80hrnU
S9XdV4+U4z04ZpFcu/CCfuoYdBYYe4DdOni0i42bC+BubtcjAeS9pZrUGIwLVfOr
PqcbG26kf7qVos+157jgbAfnVqLvzkwoYL92LXsJVzj3GqpG6NAtnMyP4T8ICWA4
B/Ckc4n20/8xScYAsJ7h8ve79K252r6turFUeirmmueTp/a6Jt7HqYlbDZHKPHF5
GYnXsBntjJuFQx2pedY6So5bTFuNjA==
=k8Le
-----END PGP SIGNATURE-----

[robertoc...@gmail.com]

I have the same problem
Is there a satisfactory answer?