Re: [qubes-users] Get help with HNS VM installation error
Le 11/11/2018 à 08:05, 'awokd' via qubes-users a écrit : unman: On Sat, Nov 10, 2018 at 03:36:09PM +, 'awokd' via qubes-users wrote: gdru...@gmail.com: Hi, I'm trying to install a VM in HVM mode called HNS (hybrid network simulation). Based on Debian, HNS seems to run on KVM/QEMU. Running a hypervisor like KVM inside another hypervisor like Xen is known as "nested virtualization". This is disabled and not supported in Qubes. I think that gdrub51 is saying that HNS runs under KVM, and they want to run it under Qubes, *not* that they are trying to run KVM within Qubes. OK. In any case, I dont believe that nested virtualization is "disabled" under Qubes. Not suppported certainly, but that's different. https://groups.google.com/d/msg/qubes-users/BwQskBAvMtY/AzZQ7Y-NAAAJ https://groups.google.com/d/msg/qubes-users/Y3P_moY4QN0/PdYhFWCvCAAJ Don't believe nestedhvm=1 out of the box. Ergo, it's disabled (at least for type 1 hypervisors). :) Hi, 8.1.4 Importing virtual machines (p40) : https://brage.bibsys.no/xmlui/bitstream/handle/11250/216822/ADalmo_MGKnudsen_JLovbraten.pdf "/Hynesim is not a hypervisor in itself, and therefore relies on other software to do the creation and running of the virtual machines./" GD. -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/480f7a6d-6a3b-788f-ea0b-29b93620d700%40gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes OS 4.0, full screen and HVM domain
Le 09/11/2018 à 15:20, unman a écrit : On Fri, Nov 09, 2018 at 01:11:53AM -0800, gdru...@gmail.com wrote: Hi, I'm trying to enable full screen mode two standalone VM(s). The following modus operandi does not work : https://www.qubes-os.org/doc/full-screen-mode/ No error displayed and no change right-clicking on a window’s title bar and selecting "Fullscreen". How can I fix it ? Any help and advice would be greatly appreciated. Best regards. GD Rub You dont say what the standaloneVMs are: On a Debian based HVM the simplest thing to do (under Xfce) is to set the display size in the HVM to that of the screen (or larger) and then select Fullscreen from the title bar. The same works in a Windows HVM. That works for me.ymmv Hi, Thanks so much. VMs Kali & Hynesim based based on Debian ;-) Frustrating how the answer was so simple. I searched for a long time and found nothing. GD Rub -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/9344b393-1d59-316f-6c66-51040b35a65d%40gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] BT adapter with Qubes OS 4.0
Le 21/09/2018 à 15:34, Franz a écrit : > > > On Fri, Sep 21, 2018 at 8:23 AM, 'awokd' via qubes-users > mailto:qubes-users@googlegroups.com>> > wrote: > > GDRUB: > > My system has only one USB controller. I haven't set up a USB qube. > > > > I achieved this objective on my desktop. > > > > %<- > > $ qvm-usb > > BACKEND:DEVID DESCRIPTION USED BY > > sys-usb:1-1 Broadcom_Corp_BCM20702A0_5CF37060F233 personal > > sys-usb:1-7 Logitech_USB_Receiver > > sys-usb:1-8 Logitech_USB_Receiver > > sys-usb:2-4 Seagate_M3_NM128GCP > > %<- > > > Today, I still have problems with BT and pulseaudio. PulseAudio Volume > > Control (pavucontrol) shows Bluetooth headset. I connect my > bluetooth > > A2DP headset but the video playback on YouTube stops with > message : "if > > playback doesn't begin shortly try restarting your device". With > > Spotify, the songs are playing but I can't hear it. :-( > > Good you got the sys-usb mostly working! I've seen other posts in this > mailing list about problems with BT and audio, but don't know if > anyone > was able to get it to work. Maybe try a wired headset instead? > > > There are also easy adapters that take sound from the 3.5 mm jack and > deliver it by BT 4.0/4.1, bypassing all huge BT security problems, > with the additional advantage of being able to work with all VMs. > > > -- > 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 > <mailto:qubes-users+unsubscr...@googlegroups.com>. > To post to this group, send email to qubes-users@googlegroups.com > <mailto:qubes-users@googlegroups.com>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/qubes-users/CAPzH-qD%2ByBG8ZkO6WhNUdUESj7MLsDgYV4M9SU0Bg2kYbKvb%3DQ%40mail.gmail.com > <https://groups.google.com/d/msgid/qubes-users/CAPzH-qD%2ByBG8ZkO6WhNUdUESj7MLsDgYV4M9SU0Bg2kYbKvb%3DQ%40mail.gmail.com?utm_medium=email_source=footer>. > For more options, visit https://groups.google.com/d/optout. It works like a charm! I forgot to change audio profile of BT headset device (High Fidelity Playback A2DP). I plan to use/adapt this script : https://m7i.org/tips/qubes-VM-bluetooth-audio/ Franz : I will test the 3.5 mm BT adapter for another use. Thx -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/2a9a0f75-1135-c859-9978-329cb5bde988%40gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] BT adapter with Qubes OS 4.0
Le 19/09/2018 à 21:41, 'awokd' via qubes-users a écrit : > gdru...@gmail.com: >> Hi, >> >> I'm trying to look for a USB bluetooth adapter. >> >> Why qvm-usb doesn't list available USB devices ? >> >> [user@dom0 ~]$ qvm-usb >> BACKEND:DEVID DESCRIPTION USED BY >> [user@dom0 ~]$ >> >> %<--- >> >> [user@dom0 ~]$ lsusb >> Bus 002 Device 002: ID 0bc2:61b6 Seagate RSS LLC >> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >> Bus 001 Device 005: ID 046d:c52b Logitech, Inc. Unifying Receiver >> Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver >> Bus 001 Device 002: ID 050d:065a Belkin Components F8T065BF Mini Bluetooth >> 4.0 Adapter <- >> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > I'm assuming you haven't set up a USB qube because you're using that > logitech receiver for keyboard & mouse. However, from the two busses > listed in lsusb, you may have two separate USB controllers. Check with > lspci. If you do, you can set up a USB qube per > https://www.qubes-os.org/doc/usb/#creating-and-using-a-usb-qube and > assign one of your two controllers to it (the one with the Seagate > device, assuming Qubes isn't on it). Then you should be able to plug > your Bluetooth adapter in that controller. You may still have trouble > with qvm-usb seeing it, but there are a couple other options at that point. > Hi awokd High regard ! Thx so much. My system has only one USB controller. I haven't set up a USB qube. I achieved this objective on my desktop. %<- $ qvm-usb BACKEND:DEVID DESCRIPTION USED BY sys-usb:1-1 Broadcom_Corp_BCM20702A0_5CF37060F233 personal sys-usb:1-7 Logitech_USB_Receiver sys-usb:1-8 Logitech_USB_Receiver sys-usb:2-4 Seagate_M3_NM128GCP %<- I have had some trouble. USB keyboard is disabled during USB qube creation. I had to plug a PS/2 keyboard otherwise I couldn't enter my passphrase to decrypt the luks drive. The below command indicates an error (R4.0, using salt). %<- $ sudo qubesctl state.sls qvm-usb-keyboard [ERROR ] Template was specified incorrectly: False local: Data failed to compile: -- No matching sls found for 'qvm-usb-keyboard' in env 'base' DOM0 configuration failed, not continuing %<- I had to edit the qubes.InputKeyboard policy file in dom0 (R3.2, manual) and hide all USB controllers from dom0 in GRUB2 (rd.qubes.hide_all_usb removed) Reference links : - https://www.qubes-os.org/doc/usb/#security-warning-about-usb-input-devices - https://www.qubes-os.org/doc/usb/#how-to-hide-all-usb-controllers-from-dom0 Qubes isn't on the Seagate device (using an SSD drive) ;-) Today, I still have problems with BT and pulseaudio. PulseAudio Volume Control (pavucontrol) shows Bluetooth headset. I connect my bluetooth A2DP headset but the video playback on YouTube stops with message : "if playback doesn't begin shortly try restarting your device". With Spotify, the songs are playing but I can't hear it. :-( GD -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/d4d9b7f4-9f29-8464-0a37-39c58fe61893%40gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] suspend to ram, r8169, networking in sys-net not working after resume
Le 10/09/2018 à 22:38, Alex a écrit : > On 9/10/18 10:34 PM, gdru...@gmail.com wrote: >>> My issue: >>> >>> On qubes version r4.0 after resuming from suspend networking isn't >>> working. On qubes r3.2 this wasn't an issue. >>> >>> [...] >> Hi, >> >> In 4.0, I have the same issue. >> [...] >> >> Help !! how can I fix it ? >> > This also happens to me; I'm using realtek ethernet adapter too. With > R3.2 this happened rarely, but with R4.0 this happens nearly every time > the computer resumes from sleep. > > As of now, I just issue a direct "shutdown now" to the sys-net, and then > just restart the VM. As soon as network is available again, all the > other Qubes reach it too - in R3.2 I had to shut them ALL down and then > bring them up in sequence, with R4.0 I can just powercycle sys-net and > it somehow works. > > Still, it's a bit of a problem... > Hi, I tried that but it didn't help. I replaced my network card TP-Link TG-3468 with a StarTech.com (port PCI) card. Now, it seems to work well. -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/b894edff-2b21-dc2d-05b7-9c3619dc7be2%40gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes-R4.0, Qubes VM Manager and VMs state
Le 07/09/2018 à 13:57, awokd a écrit :
> On Fri, September 7, 2018 11:45 am, gdru...@gmail.com wrote:
>> Hi,
>>
>>
>> Why do I have to click on "Refresh" button in Qubes VM Manager for
>> viewing/verifying the VMs state ('Started' or 'Stopped') ?
>>
>> On Qubes OS version 3.2, it was automatic, in real time.
>>
>>
>> How can I fix it ?
> There was an update about a month ago to 4.0 that addressed this. Have you
> updated dom0 lately? It's "sudo qubes-dom0-update" in a dom0 Terminal
> Emulator window.
>
Fixed after the update. Thx so much.
--
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/e3075870-d123-a24c-6832-5d4db735d9c8%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes-R4.0 : missing argument to qvm-create
Le 31/08/2018 à 19:51, Ivan Mitev a écrit : > > On 08/31/2018 08:42 PM, GDRUB wrote: >> Le 31/08/2018 à 14:43, GDRUB a écrit : >>> Le 31/08/2018 à 13:33, brendan.h...@gmail.com a écrit : >>>> On Thursday, August 30, 2018 at 4:43:42 PM UTC-4, GDRUB wrote: >>>>> Thank you for those explanations. >>>>> >>>>> However, Windows 10 fails with error code : 0xc225 "a required >>>>> device isn't connected or can't be accessed". >>>>> >>>>> win10.raw = 96.6 GB >>>>> >>>>> How to fix this error ? >>>>> >>>>> >>>>> Le 30/08/2018 à 11:58, Ivan Mitev a écrit : >>>>>> On 08/30/2018 11:10 AM, gd...@gmail.com wrote: >>>>>>> Hi, >>>>>>> >>>>>>> I'm trying to run the following command: >>>>>>> >>>>>>> $ qemu-img convert -O raw *.vmdk win10.raw >>>>>>> $ qvm-run --pass-io untrusted 'cat "/media/user/externalhd/win10.raw"' >>>>>>> > /home/user/win10-root.img >>>>>>> $ qvm-create --hvm win10 --label red --mem=4096 --root-move-from >>>>>>> /home/user/win10-root.img >>>>>>> >>>>>>> qvm-create: error: unrecognized arguments: --hvm --mem=4096 >>>>>>> >>>>>>> Source : https://www.qubes-os.org/doc/hvm/ >>>>>> You're using 3.2 commands, see the "R4.0: ..." paragraph below in the >>>>>> doc. >>>>>> >>>>>> The following command should do the trick: >>>>>> >>>>>> qvm-create win10 \ >>>>>> --class StandaloneVM \ >>>>>> --property virt_mode=hvm \ >>>>>> --property kernel='' \ >>>>>> --label=red \ >>>>>> --property memory=4096 \ >>>>>> --property maxmen=4096 \ >>>>>> --root-move-from /home/user/win10-root.img >>>>>> >>>>>> >>>>>> >>>>>>> How to create a new PVH instead of HVM in Dom0 with the root image from >>>>>>> R4.0 ? >>>>>>> >>>>>>> Thank you so much for your help. >>>>>>> >>>>>>> Best regards. >>>>>>> >>>> I think the issue of > 10GB images being truncated via ---root-copy-from >>>> during create still exists. See this Issue is still open in the tracker: >>>> >>>> https://github.com/QubesOS/qubes-issues/issues/3422 >>>> >>>> You'll likely need to qvm-create w/o the root-copy-from, then >>>> qvm-grow-root, then copy the image to the right volume listed in >>>> /dev/mapper. >>>> >>>> See this thread (and choose commands wisely!): >>>> >>>> https://groups.google.com/forum/#!topic/qubes-users/vBk-jjvoeT0 >>>> >>>> Brendan >>>> >>>> Your solution worked like a charm. I still have some difficulty with two issues : 1) in the panel of Qubes Manager, state indicator is yellow - something's not ok. That's troubling to me. 2) to get Windows HVM into real full screen mode. The procedure is carried out correctly (https://www.qubes-os.org/doc/full-screen-mode/) but Fullscreen stays grayed out into windows bar -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/0e07510d-3573-55dd-c363-d0fffaf1d0dd%40gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes-R4.0 : missing argument to qvm-create
Le 31/08/2018 à 14:43, GDRUB a écrit : > Le 31/08/2018 à 13:33, brendan.h...@gmail.com a écrit : >> On Thursday, August 30, 2018 at 4:43:42 PM UTC-4, GDRUB wrote: >>> Thank you for those explanations. >>> >>> However, Windows 10 fails with error code : 0xc225 "a required >>> device isn't connected or can't be accessed". >>> >>> win10.raw = 96.6 GB >>> >>> How to fix this error ? >>> >>> >>> Le 30/08/2018 à 11:58, Ivan Mitev a écrit : >>>> On 08/30/2018 11:10 AM, gd...@gmail.com wrote: >>>>> Hi, >>>>> >>>>> I'm trying to run the following command: >>>>> >>>>> $ qemu-img convert -O raw *.vmdk win10.raw >>>>> $ qvm-run --pass-io untrusted 'cat "/media/user/externalhd/win10.raw"' > >>>>> /home/user/win10-root.img >>>>> $ qvm-create --hvm win10 --label red --mem=4096 --root-move-from >>>>> /home/user/win10-root.img >>>>> >>>>> qvm-create: error: unrecognized arguments: --hvm --mem=4096 >>>>> >>>>> Source : https://www.qubes-os.org/doc/hvm/ >>>> You're using 3.2 commands, see the "R4.0: ..." paragraph below in the doc. >>>> >>>> The following command should do the trick: >>>> >>>> qvm-create win10 \ >>>>--class StandaloneVM \ >>>>--property virt_mode=hvm \ >>>>--property kernel='' \ >>>>--label=red \ >>>>--property memory=4096 \ >>>>--property maxmen=4096 \ >>>>--root-move-from /home/user/win10-root.img >>>> >>>> >>>> >>>>> How to create a new PVH instead of HVM in Dom0 with the root image from >>>>> R4.0 ? >>>>> >>>>> Thank you so much for your help. >>>>> >>>>> Best regards. >>>>> >> I think the issue of > 10GB images being truncated via ---root-copy-from >> during create still exists. See this Issue is still open in the tracker: >> >> https://github.com/QubesOS/qubes-issues/issues/3422 >> >> You'll likely need to qvm-create w/o the root-copy-from, then qvm-grow-root, >> then copy the image to the right volume listed in /dev/mapper. >> >> See this thread (and choose commands wisely!): >> >> https://groups.google.com/forum/#!topic/qubes-users/vBk-jjvoeT0 >> >> Brendan >> > Hi Brendan, > > It seems to be the solution to this problem. > > I'll test this with caution. > > Thank you so much for your help. > missing binary in PATH ! :-( $ qvm-grow-root win10 100g bash : qvm-grow-root : command not found -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/84167296-7970-71fe-0cc4-e4e267c4f5a6%40gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes-R4.0 : missing argument to qvm-create
Le 31/08/2018 à 13:33, brendan.h...@gmail.com a écrit : > On Thursday, August 30, 2018 at 4:43:42 PM UTC-4, GDRUB wrote: >> Thank you for those explanations. >> >> However, Windows 10 fails with error code : 0xc225 "a required >> device isn't connected or can't be accessed". >> >> win10.raw = 96.6 GB >> >> How to fix this error ? >> >> >> Le 30/08/2018 à 11:58, Ivan Mitev a écrit : >>> On 08/30/2018 11:10 AM, gd...@gmail.com wrote: >>>> Hi, >>>> >>>> I'm trying to run the following command: >>>> >>>> $ qemu-img convert -O raw *.vmdk win10.raw >>>> $ qvm-run --pass-io untrusted 'cat "/media/user/externalhd/win10.raw"' > >>>> /home/user/win10-root.img >>>> $ qvm-create --hvm win10 --label red --mem=4096 --root-move-from >>>> /home/user/win10-root.img >>>> >>>> qvm-create: error: unrecognized arguments: --hvm --mem=4096 >>>> >>>> Source : https://www.qubes-os.org/doc/hvm/ >>> You're using 3.2 commands, see the "R4.0: ..." paragraph below in the doc. >>> >>> The following command should do the trick: >>> >>> qvm-create win10 \ >>> --class StandaloneVM \ >>> --property virt_mode=hvm \ >>> --property kernel='' \ >>> --label=red \ >>> --property memory=4096 \ >>> --property maxmen=4096 \ >>> --root-move-from /home/user/win10-root.img >>> >>> >>> >>>> How to create a new PVH instead of HVM in Dom0 with the root image from >>>> R4.0 ? >>>> >>>> Thank you so much for your help. >>>> >>>> Best regards. >>>> > I think the issue of > 10GB images being truncated via ---root-copy-from > during create still exists. See this Issue is still open in the tracker: > > https://github.com/QubesOS/qubes-issues/issues/3422 > > You'll likely need to qvm-create w/o the root-copy-from, then qvm-grow-root, > then copy the image to the right volume listed in /dev/mapper. > > See this thread (and choose commands wisely!): > > https://groups.google.com/forum/#!topic/qubes-users/vBk-jjvoeT0 > > Brendan > Hi Brendan, It seems to be the solution to this problem. I'll test this with caution. Thank you so much for your help. -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/944cfb62-b580-df18-207d-8180e09e32fe%40gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Importing a VM from R3.2 and shortcuts
Le 31/08/2018 à 11:00, GDRUB a écrit :
> I'll test this.
>
> In the debian-9 VM:
>
> $ apt-ket exportall > /tmp/keys.txt
> $ qvm-copy-to-vm /tmp/keys.txt
>
> In the debian-8 VM:
>
> $ apt-key import ~/QubesIncoming/debian-9/keys.txt
>
> Le 30/08/2018 à 22:58, GDRUB a écrit :
>> Thank you for those explanations.
>>
>> I have adjusted the documentation on my restored template (debian 8.0).
>>
>> $ qvm-copy /etc/apt/sources.list.d/qubes-r4.list
>>
>> I have bypassed step 4, so I get :
>>
>> W: GPG error: http://deb.qubes-os.org stretch Release: The following
>> signatures couldn't be verified because the public key is not available:
>> NO_PUBKEY 43B760F197CA1BF5
>>
>> How to fix this error ?
>>
>> Le 30/08/2018 à 12:05, Ivan Mitev a écrit :
>>> On 08/30/2018 12:49 PM, gdru...@gmail.com wrote:
>>>> Hi,
>>>>
>>>> Qubes OS version: Qubes-R4.0
>>>>
>>>> After restoring VM from a backup (R3.2), all applications have been
>>>> automatically included in the list of available apps. They appear in the
>>>> VM’s submenu ("start menu" in dom0).
>>>>
>>>> When I click on shortcut, the assigned application is not running in its
>>>> AppVM.
>>> IIRC non working shortcuts were a symptom of using imported R3.2
>>> standaloneVMs/templateVMs.
>>> You should:
>>> - configure your imported R3.2 AppVMs to use R4.0's templates
>>> - or upgrade the imported R3.2 templateVMs:
>>>
>>> https://github.com/Qubes-Community/Contents/blob/master/docs/system/restore-3.2.md
>>>
>>>
>>>> I can start an AppVM only from command line :
>>>>
>>>> $ qvm-run -a personal terminator
>>>>
>>>> How can I fix it ?
>>>>
>>>> Thank you so much for your help.
>>>>
>>>> Best regards.
>>>>
ERRATUM
In the debian-9 VM:
$ apt-ket exportall > /tmp/keys.txt
$ qvm-copy /tmp/keys.txt
In the debian-8 VM:
$ apt-key add ~/QubesIncoming/debian-9/keys.txt
It worked like a charm.
Thx Ivan
--
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/5e424dde-e868-cf57-f2ab-7a6b0ad67d41%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Importing a VM from R3.2 and shortcuts
I'll test this.
In the debian-9 VM:
$ apt-ket exportall > /tmp/keys.txt
$ qvm-copy-to-vm /tmp/keys.txt
In the debian-8 VM:
$ apt-key import ~/QubesIncoming/debian-9/keys.txt
Le 30/08/2018 à 22:58, GDRUB a écrit :
> Thank you for those explanations.
>
> I have adjusted the documentation on my restored template (debian 8.0).
>
> $ qvm-copy /etc/apt/sources.list.d/qubes-r4.list
>
> I have bypassed step 4, so I get :
>
> W: GPG error: http://deb.qubes-os.org stretch Release: The following
> signatures couldn't be verified because the public key is not available:
> NO_PUBKEY 43B760F197CA1BF5
>
> How to fix this error ?
>
> Le 30/08/2018 à 12:05, Ivan Mitev a écrit :
>> On 08/30/2018 12:49 PM, gdru...@gmail.com wrote:
>>> Hi,
>>>
>>> Qubes OS version: Qubes-R4.0
>>>
>>> After restoring VM from a backup (R3.2), all applications have been
>>> automatically included in the list of available apps. They appear in the
>>> VM’s submenu ("start menu" in dom0).
>>>
>>> When I click on shortcut, the assigned application is not running in its
>>> AppVM.
>> IIRC non working shortcuts were a symptom of using imported R3.2
>> standaloneVMs/templateVMs.
>> You should:
>> - configure your imported R3.2 AppVMs to use R4.0's templates
>> - or upgrade the imported R3.2 templateVMs:
>>
>> https://github.com/Qubes-Community/Contents/blob/master/docs/system/restore-3.2.md
>>
>>
>>> I can start an AppVM only from command line :
>>>
>>> $ qvm-run -a personal terminator
>>>
>>> How can I fix it ?
>>>
>>> Thank you so much for your help.
>>>
>>> Best regards.
>>>
--
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/dcc25820-fb85-61af-f136-4f1bc7760bd5%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Importing a VM from R3.2 and shortcuts
Thank you for those explanations.
I have adjusted the documentation on my restored template (debian 8.0).
$ qvm-copy /etc/apt/sources.list.d/qubes-r4.list
I have bypassed step 4, so I get :
W: GPG error: http://deb.qubes-os.org stretch Release: The following
signatures couldn't be verified because the public key is not available:
NO_PUBKEY 43B760F197CA1BF5
How to fix this error ?
Le 30/08/2018 à 12:05, Ivan Mitev a écrit :
>
> On 08/30/2018 12:49 PM, gdru...@gmail.com wrote:
>> Hi,
>>
>> Qubes OS version: Qubes-R4.0
>>
>> After restoring VM from a backup (R3.2), all applications have been
>> automatically included in the list of available apps. They appear in the
>> VM’s submenu ("start menu" in dom0).
>>
>> When I click on shortcut, the assigned application is not running in its
>> AppVM.
> IIRC non working shortcuts were a symptom of using imported R3.2
> standaloneVMs/templateVMs.
> You should:
> - configure your imported R3.2 AppVMs to use R4.0's templates
> - or upgrade the imported R3.2 templateVMs:
>
> https://github.com/Qubes-Community/Contents/blob/master/docs/system/restore-3.2.md
>
>
>> I can start an AppVM only from command line :
>>
>> $ qvm-run -a personal terminator
>>
>> How can I fix it ?
>>
>> Thank you so much for your help.
>>
>> Best regards.
>>
--
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/6d62fe29-7cef-bb88-8498-5f49fd41620d%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes-R4.0 : missing argument to qvm-create
Thank you for those explanations. However, Windows 10 fails with error code : 0xc225 "a required device isn't connected or can't be accessed". win10.raw = 96.6 GB How to fix this error ? Le 30/08/2018 à 11:58, Ivan Mitev a écrit : > > On 08/30/2018 11:10 AM, gdru...@gmail.com wrote: >> Hi, >> >> I'm trying to run the following command: >> >> $ qemu-img convert -O raw *.vmdk win10.raw >> $ qvm-run --pass-io untrusted 'cat "/media/user/externalhd/win10.raw"' > >> /home/user/win10-root.img >> $ qvm-create --hvm win10 --label red --mem=4096 --root-move-from >> /home/user/win10-root.img >> >> qvm-create: error: unrecognized arguments: --hvm --mem=4096 >> >> Source : https://www.qubes-os.org/doc/hvm/ > You're using 3.2 commands, see the "R4.0: ..." paragraph below in the doc. > > The following command should do the trick: > > qvm-create win10 \ > --class StandaloneVM \ > --property virt_mode=hvm \ > --property kernel='' \ > --label=red \ > --property memory=4096 \ > --property maxmen=4096 \ > --root-move-from /home/user/win10-root.img > > > >> How to create a new PVH instead of HVM in Dom0 with the root image from R4.0 >> ? >> >> Thank you so much for your help. >> >> Best regards. >> -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/aef2fa8d-9c4a-30da-7eff-1e76684379c9%40gmail.com. For more options, visit https://groups.google.com/d/optout.
