Qubes 4.0 qemu device controller mptsas1068 not seen by ReactOS
36 views
Skip to first unread message
Steve Coleman
unread,
Aug 31, 2018, 3:07:37 PM8/31/18
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to qubes...@googlegroups.com
I saw that a while back a Qubes discussion on qemu's disk controller vs
Windows support, which if I recall correctly required a modification to
the qemu device being passed to the HVM. It appears that Qubes HVM is
currently passing "-device mptsas1068 -id=scsi0" which appears to not be
seen by ReactOS. I know that ReactOS used to work under Q3.2, but my
current Q4.0 system doesn't present any drive at all to ReactOS, other
than the cdrom from which to boot from.
How is windows being handled right now? The mptsas is working there I
assume?
Is there any kind of user level qvm-prefs setting to change this device
presentation based on the OS requirements? If not, is there any kind of
configuration file for this kind of mod within QEMU itself?
thanks,
Steve.
awokd
unread,
Sep 7, 2018, 7:35:36 AM9/7/18
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Steve Coleman, qubes...@googlegroups.com
For reference, the related issue is
https://github.com/QubesOS/qubes-issues/issues/2809. Looks like that
controller is specified in vmm-xen/patch-stubdom-linux-0005.patch, which
patches tools/libxl/libxl_dm.c. I don't see a user level way to change it,
but possibly one could: