GSOC Introduction
47 views
Skip to first unread message
Aju Tamang
Mar 23, 2020, 11:06:03 PM3/23/20
to qubes-devel
Hi there,
Hi, I'm Aju Tamang, currently freshman a college student and am new to the open source community.Its been months that i started coding(in python) and this GSoC program was introduced to me through blog article.
I've been looking forward to it since then and it would be great if you could help me out in USB passthrough to Windows qubes.
Aju Tamang
Marek Marczykowski-Górecki
Mar 25, 2020, 10:50:08 PM3/25/20
to Aju Tamang, qubes-devel
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On Mon, Mar 23, 2020 at 08:06:03PM -0700, Aju Tamang wrote:
> Hi there,
Hello Aju,
Have you tried Qubes before? If not, I would recommend trying to install
it somewhere first. For testing purposes it is ok to install on external
disk, or even sufficiently large USB stick (although it will be quite
slow).
If you install Qubes on a USB disk, you won't be able to use USB
passthrough with real devices (as the USB controller will be assigned to
the host system, to serve disk access). But there are plenty options for
using virtual devices, so it shouldn't be a blocker.
As for the task itself, you have some brief explanation on our GSoC
page:
https://www.qubes-os.org/gsoc/#usb-passthrough-to-windows-qubes
Some more details are:
- how we do it for Linux: https://github.com/QubesOS/qubes-app-linux-usb-proxy/
- general concept from the user point of view: https://www.qubes-os.org/doc/usb-devices/
Your task would be making it work also for Windows VMs. There are
various methods how to do that (two of them listed on our GSoC page),
but I would recommend going with the USBIP + qemu (second option), as it
would be mostly shell+python scripts, instead of Windows kernel drivers.
If you're still interested, the next step would be writing your
application with description of the project, above I have pointed you
where to look for inspiration.
- --
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/THMrX1ywFAl58GFYACgkQ24/THMrX
1yx5vgf+MZaq97Au6w9bmYnLkxUe8IDKaTLpqBo6Ty7ZVFu+WwOf0pLw/d1sAfPi
JUkbvBPsKlySb8uYhYyu9S3rhY99r9KUbORijobFUMTMJfNlpvKIFlNVPVnkJN9D
6fOtkBoObGGAXKvtSX6ThwV86Amx5EbcqjwRr5Rlvof0J0006FR6dRPgOcmqO90N
+0dz2LtKD4vRhUKgcvM829NFtPq5CptZRy2Vp8xQ3P126nknoYql3LR1cunWwsDY
dHHS1X1P1voYD3edrK8L+DKXvl3l/iWb+POexpOnftwaQuM1IWqsJm+HD1iw/vWc
hnHriDggWJO2VaIItDdy0x5thmrnhg==
=B10e
-----END PGP SIGNATURE-----
Hash: SHA256
On Mon, Mar 23, 2020 at 08:06:03PM -0700, Aju Tamang wrote:
> Hi there,
Hello Aju,
it somewhere first. For testing purposes it is ok to install on external
disk, or even sufficiently large USB stick (although it will be quite
slow).
If you install Qubes on a USB disk, you won't be able to use USB
passthrough with real devices (as the USB controller will be assigned to
the host system, to serve disk access). But there are plenty options for
using virtual devices, so it shouldn't be a blocker.
As for the task itself, you have some brief explanation on our GSoC
page:
https://www.qubes-os.org/gsoc/#usb-passthrough-to-windows-qubes
Some more details are:
- how we do it for Linux: https://github.com/QubesOS/qubes-app-linux-usb-proxy/
- general concept from the user point of view: https://www.qubes-os.org/doc/usb-devices/
Your task would be making it work also for Windows VMs. There are
various methods how to do that (two of them listed on our GSoC page),
but I would recommend going with the USBIP + qemu (second option), as it
would be mostly shell+python scripts, instead of Windows kernel drivers.
If you're still interested, the next step would be writing your
application with description of the project, above I have pointed you
where to look for inspiration.
- --
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/THMrX1ywFAl58GFYACgkQ24/THMrX
1yx5vgf+MZaq97Au6w9bmYnLkxUe8IDKaTLpqBo6Ty7ZVFu+WwOf0pLw/d1sAfPi
JUkbvBPsKlySb8uYhYyu9S3rhY99r9KUbORijobFUMTMJfNlpvKIFlNVPVnkJN9D
6fOtkBoObGGAXKvtSX6ThwV86Amx5EbcqjwRr5Rlvof0J0006FR6dRPgOcmqO90N
+0dz2LtKD4vRhUKgcvM829NFtPq5CptZRy2Vp8xQ3P126nknoYql3LR1cunWwsDY
dHHS1X1P1voYD3edrK8L+DKXvl3l/iWb+POexpOnftwaQuM1IWqsJm+HD1iw/vWc
hnHriDggWJO2VaIItDdy0x5thmrnhg==
=B10e
-----END PGP SIGNATURE-----
Reply all
Reply to author
Forward
0 new messages