Re: [qubes-users] Re: qvm-create-windows-qube 2.0
Works. Thanks! On 20.01.2020 20:20, brendan.h...@gmail.com wrote: Try running qvm-start-gui when the window doesn’t appear. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/6c3ae1c5697e0e1a9fdb442075ac5fb2%40posteo.net.
Re: [qubes-users] Re: qvm-create-windows-qube 2.0
I had installed Win10 Enterprise and everything was running well until I
had to restart.
Now I can't figure out how to get Windows GUI to appear. When I've
installed Windows without this script I only have one menu option
"Start" and that boots the Windows interface. With the install using
this script I have three menu options: Command Prompt, Explorer,
Internet Explorer. I can run any of those and the Win10 Qube starts, but
there is no GUI interface for the selected app or for Windows in desktop
in general. There is Qubes Settings. I thought this issue might be due
to seamless mode, but clicking the button to disable it in Qubes
Settings just gives me this error:
line: raise exc
func: run_service_for_stdio
line no.: 287
file: /usr/lib/python3.5/site-packages/qubesadmin/__init__.py
line: self.vm.run_service_for_stdio("qubes.SetGuiMode",
input=b'FULLSCREEN')
func: disable_seamless
line no.: 762
file: /usr/lib/python3.5/site-packages/qubesmanager/settings.py
I also tried turning on "debug mode" and stopping and starting the Win10
qube. But that didn't produce anything I could see either.
Any other ideas?
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/1ab7ae4a4365b4298f465d5207c9be91%40posteo.net.
Re: [qubes-users] qvm-create-windows-qube 2.0
Thanks Dominique. Everything working now including Qubes Windows Tools - i can copy files over at least. This is great. Am I correct that the windows-mgmt qube is just for setting up the Windows qube and can be deleted? Certainly keeping it would expedite creating new Windows qubes in the future though. scallyob On 17.01.2020 14:16, Dominique St-Pierre Boucher wrote: Concerning the download of ISO, if you open a teminal in the windows-mgmt qube that is created by the script, there is a script in /home/user/Documents/qvm-create-windows-qube/windows-media/isos/ named download-windows.sh Run that script, it will tell you what are the options. Do not forget to give network access to the windows-mgmt qube before starting the download and to remove the access after. One of the possible reason you were not able to install Windows 10 is because of the version. The Windows 10 iso you got is probably not an Enterprise Eval version so the key wont work. Dominique On Thursday, January 16, 2020 at 10:48:02 PM UTC-5, scal...@posteo.net wrote: Thanks Elliot for posting this. I'm trying this now. I saw the note saying you could download a different version of Windows in the qvm-create-windows-qube.sh. But I didn't see how that was done. Seems like you can just reference an already downloaded iso, which is what I did. I already had a Windows 10 iso. So I set it to use that iso and to use the answer file provided for win10x64-enterprise-eval.xml, but ran into the problem below. But maybe it is because of the iso i'm using? On 13.01.2020 10:48, 'Elliot Killick' via qubes-users wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 * Hardcoding trial product key in answer files (or anywhere) is no longer necessary, Windows will use embedded trial key without any user interaction by default This doesn't seem to be the case. I'm getting the following: on "Commencing first part of Windows installation process..." in the install.sh script I get a popup from "Windows Setup" that says Windows cannot read the setting from the unattend answer file." I click "OK" and it reboots to a black screen from SeaBIOS that ends with "No bootable device." * windows-mgmt is air gapped What is this qube used for? Is it just for the setup? Can I delete it after done? Thanks. -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/d871a2b3-e34b-4eec-b89a-47f07dec0bc5%40googlegroups.com [1]. Links: -- [1] https://groups.google.com/d/msgid/qubes-users/d871a2b3-e34b-4eec-b89a-47f07dec0bc5%40googlegroups.com?utm_medium=email&utm_source=footer -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/e0c6ea93c0ee5056b053d199d531d602%40posteo.net.
Re: [qubes-users] qvm-create-windows-qube 2.0
Thanks Elliot for posting this. I'm trying this now. I saw the note saying you could download a different version of Windows in the qvm-create-windows-qube.sh. But I didn't see how that was done. Seems like you can just reference an already downloaded iso, which is what I did. I already had a Windows 10 iso. So I set it to use that iso and to use the answer file provided for win10x64-enterprise-eval.xml, but ran into the problem below. But maybe it is because of the iso i'm using? On 13.01.2020 10:48, 'Elliot Killick' via qubes-users wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 * Hardcoding trial product key in answer files (or anywhere) is no longer necessary, Windows will use embedded trial key without any user interaction by default This doesn't seem to be the case. I'm getting the following: on "Commencing first part of Windows installation process..." in the install.sh script I get a popup from "Windows Setup" that says Windows cannot read the setting from the unattend answer file." I click "OK" and it reboots to a black screen from SeaBIOS that ends with "No bootable device." * windows-mgmt is air gapped What is this qube used for? Is it just for the setup? Can I delete it after done? Thanks. -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/36e24de4971693d221cc8edaf5ca312b%40posteo.net.
Re: [qubes-users] Re: sys-usb issues recognizing devices & maintaining drive connections
Original Message Subject: Re: [qubes-users] Re: sys-usb issues recognizing devices & maintaining drive connections Date: 04.01.2020 19:14 From: scall...@posteo.net To: awokd On 04.01.2020 10:51, 'awokd' via qubes-users wrote: Lorenzo Lamas: On Friday, January 3, 2020 at 11:02:24 PM UTC+1, scal...@posteo.net wrote: But the other problem I've had with sys-usb is connecting to external drives. Here are the copy speeds I get on my machine to an external usb device: Tails OS 33mb/sec Qubes OS 12mb/sec This is my hardware: https://www.coreboot.org/Board:asus/kgpe-d16 Try adding irqpoll to the end of your kernelopts in qvm-prefs sys-usb. Had similar behavior with my Corebooted AMD. Please let me know if it helps you. I think root cause is IRQ setup table issues in Coreboot, but I'm not sure yet how to confirm or fix. Unfortunately it doesn't seem to have changed anything. My kernel opts are currently set to: dom0] qvm-prefs sys-usb ... kernelopts- nopat iommu=soft swiotlb=8192 irqpoll ... I rebooted sys-usb and am trying to copy a backup to an external USB drive and getting the same pauses and low transfer rates (if not worse actually). 253,591,552 0% 249.48kB/s 181:19:51 ^C rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(644) [sender=3.1.3] [sender] io timeout after 60 seconds -- exiting Thanks for the suggestion though. When it is not recognizing devices, the Qubes Devices Widget shows an additional device: "sys-usb:2-1:1 - 138a_003c_0030009d7e88". It is not visible when everything works fine. Do you have that as well? Lorenzo Lamas: I do not get this 'ghost' device. I either get none or a partial list of what should be there. But that is promising that your USB 3.0 works fine, maybe I should try installing an additional USB card. I currently have the onboard usb slots on the motherboard and a couple built into my case. They seem to behave similarly. Though in the past sometimes switching between them I could get things to show up. That was back on Qubes 3.2 though and have found rebooting to be the more effective solution when things aren't recognized at all. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/a5df2d4744464d972a1c67e90d7da69e%40posteo.net.
[qubes-users] sys-usb issues recognizing devices & maintaining drive connections
Since Qubes 3.2 I've had issues with sys-usb not recognizing devices. My solution has been to reboot until it works. 1 in 4 times it seems to work correctly. The device that I have the most trouble with is a trackpad. Sometimes after using the machine successfully for days, I'll wake it up and the trackpad mouse speed will be slowed down. Sometimes rebooting sys-usb will fix this. Other times I have to reboot the whole machine. All that i've been able to live with. But the other problem I've had with sys-usb is connecting to external drives. Here are the copy speeds I get on my machine to an external usb device: Tails OS 33mb/sec Qubes OS 12mb/sec HOWEVER, the Qubes # is misleading because it seems to have regular i/o issues so it is 12mb/sec when it is working, which is off and on. Then after some time the whole device will become read only and i'll get a i/o error message after copying for some time. This has become a serious problem because i can no longer do Backups to external drives. (Copying smaller files to/from usb is manageable.) Therefore I've decided to ask for help here. A search for "sys-usb" didn't reveal any examples of others having similar problems, but maybe someone can help me narrow down the problem here. This is my hardware: https://www.coreboot.org/Board:asus/kgpe-d16 Any advice is much appreciated. scallyob -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/eff15f60f1a86c2252647614dd05763c%40posteo.net.
