man. 24. feb. 2020 kl. 20.13 skrev A E <anneeyr...@gmail.com>:
> man. 24. feb. 2020 kl. 14.12 skrev A E <anneeyr...@gmail.com>:
>
>> ons. 19. feb. 2020 kl. 15.51 skrev A E <anneeyr...@gmail.com>:
>>
>>> tor. 13. feb. 2020 kl. 00.24 skrev M E <anneeyr...@gmail.com>:
>>>
>>>> søn. 26. jan. 2020 kl. 23.12 skrev 'Elliot Killick' via qubes-users <
>>>> qubes-users@googlegroups.com>:
>>>>
>>>>>
>>>>> On 2020-01-26 12:37, Claudio Chinicz wrote:
>>>>> > ׁHi Elliot,
>>>>> >
>>>>> > I've downloaded again and succeeded creating the HVM.
>>>>> >
>>>>> > I had a Windows 10 HVM I built manually just booting from the ISO
>>>>> and where
>>>>> > I did not succeed installing the QWT (boot after the QWT install
>>>>> would
>>>>> > freeze).
>>>>> >
>>>>> > Would you recommend building a Template from this HVM?
>>>>> >
>>>>> > The big advantage I saw in this implementation was that I can
>>>>> confortably
>>>>> > run my applications with 2GB (minimum) vs 6GB in my previous HVM.
>>>>> Another
>>>>> > advantage of the QWT is that I can send files from Windows to any
>>>>> other
>>>>> > PV/HPV VM using qrexec.
>>>>> >
>>>>> > What's intriguing me is that copy/paste between VMs is not working.
>>>>> When I
>>>>> > ctl+shift+C on my Windows VM I see the popup saying I can
>>>>> ctl+shift+V on
>>>>> > another VM but when I do so nothing is pasted. Any ideas?
>>>>> >
>>>>> > Thank you very much for this scripts/Windows VM builder.
>>>>> >
>>>>> > Regards
>>>>>
>>>>> By freeze do you mean it stops on the part where QWT tries to create
>>>>> the
>>>>> private disk? This is documented in the QWT Known Issues section of the
>>>>> README. Just exit that window with the error message and the
>>>>> installation will proceed as normal. Besides that for Windows
>>>>> 10/Windows
>>>>> Server 2019, you should not have to interact with any window or part of
>>>>> the installation. Sometimes, QWT may also just crash upon boot causing
>>>>> Windows to crash. This doesn't happen often, however, it is also
>>>>> documented in the README. This is more likely to happen if you
>>>>> installed
>>>>> Windows manually as you said because unstable QWT features like Qubes
>>>>> Memory Manager (qmemman) are enabled by default which we disable in the
>>>>> qvm-create-windows-qube.sh script (Thanks to @brendanhoar for that
>>>>> one).
>>>>>
>>>>> Due to that bug in making the private disk required, it's not possible
>>>>> to create templates for Windows 10/Windows Server 2019 anyway.
>>>>> Otherwise, I would recommend for must users to build a template with
>>>>> the
>>>>> software they want pre-installed and make AppVMs from that.
>>>>>
>>>>> Regarding copy/paste not working, it appears to work fine for others so
>>>>> I would just suggest you restart the Windows qube or possibly make a
>>>>> new
>>>>> one. If it's copying the data out correctly then there should be a
>>>>> notification saying "Copied X bytes to the clipboard".
>>>>>
>>>>> You're welcome, Claudio!
>>>>>
>>>>>
>>>>> Regards,
>>>>>
>>>>> Elliot
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> 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/2de7254e-c22c-3275-cdfd-30cdacd86a67%40zohomail.eu
>>>>> .
>>>>
>>>>
>>>>
>>>> I want to install Windows 10 from a DVD in a new HVM and have begun
>>>> following this guide: https://www.qubes-os.org/doc/windows-vm/
>>>>
>>>> It says:
>>>>
>>>> “Create a new Qube:
>>>> Name: Win10, Color: red
>>>> Standalone Qube not based on a template
>>>> Networking: sys-firewall (default)
>>>> Launch settings after creation: check
>>>> Click “OK”.”
>>>>
>>>> As I’m going to install Win 10 from a DVD, shall I then just follow the
>>>> guide and choose “Launch settings after creation” or shall I choose
>>>> “Install from device” ?
>>>>
>>>
>>>
>>> I have made a Windows domain and downloaded and installed Windows 7 and
>>> Qubes Windows Tools by executing this script in dom0 according to this
>>> guide (link: https://github.com/elliotkillick/qvm-create-windows-qube ):
>>>
>>> chmod +x install.sh && ./install.sh
>>>
>>> And now I would like to know how to get further.
>>>
>>> I have made a thread here about making a Win10 HVM, so you are welcome
>>> to answer there instead (I have just made this post in attempt to get a
>>> quicker response):
>>>
>>> https://groups.google.com/forum/m/#!topic/qubes-users/78DgmWxZf80
>>>
>>> How to use the script of the download-windows.sh file ?
>>
>> When I execute the script in the terminal, the different windows versions
>> are listed. But when I copy the label of one of them and paste it on the
>> line below it and press enter, the terminal says that it doesn’t recognize
>> the command.
>>
>
> More precisely worded: How to use the download-windows.sh file to
> download Win10 Pro 64 bit ?
>
A way to download Windows 10 Pro manually and install it.
I haven’t managed to download Windows 10 Pro by using the file
“download-windows.sh”. So instead I downloaded Windows 10 Pro manually and
ran the script afterwards.
You can follow these steps to do it the same way as I did it:
1) Open the “Qube Settings” for the domain “windows-mgmt”. Under
“Network”, choose “default” one and click on “Apply”.
2) Open the domains Firefox browser and search the web for “how to
download windows 10”.
One of the first results is a link to a Microsoft webpage from which
it is possible to download the file in the local language.
The file gets downloaded to the download folder in the domain.
3) Open the “Qube Settings” for the domain “windows-mgmt”. Under
“Network”, choose “(none)” and click on “Apply”.
4) Move or copy the file to this destination:
/Documents/qvm-create-windows-qube/windows-media/isos
5) Open the terminal in dom0 and execute the following script (remember to
write the name of the iso file you downloaded in step 2 instead of
“filename”):
./qvm-create-windows-qube.sh -n sys-whonix -oyw -i filename.iso -a
win10x64-pro.xml anon-win10
Info: anon-win10 will be the name of the domain. I don’t know if it is
possible to change the domain name without spoiling anything.
Do not close the terminal before it says the installation was complete
(successfully) !
Let the terminal do the job, it restarts the qube and so on when it is
necessary.
When I got into Windows there appeared three message boxes. One saying that
the pc has to be restarted. A second one saying that drive D has to be
formatted. And the third one saying something about a private drive as far
as I recall.
I started to click OK, I think on the third messaged, and then Windows
immediately closed and restarted and seemed to run fine afterwards.
And in the terminal it said the installation was completed successfully.
--
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/CABRRaUE5pMidzjZ5X%2BOUTRMK0Qp-uqqFC_hZ5oNQwy_T5-nkdg%40mail.gmail.com.
