[qubes-users] Is hibernation supposed to work in HVM mode?
In PV, I tried installing hibernate in debian and it complains saying kernel does not support. In HVM, I simply put my Kali linux to hibernate. When I started the VM again, it got stuck on "Resuming from hibernation" Was hibernation supposed to work? -- 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/997aa74f-e047-4a9a-bfdb-d2047ae93441%40googlegroups.com.
[qubes-users] No internet in Kali Linux (HVM)
I installed Kali Linux. It's in HVM mode. I have no internet. I tried to edit the network options, and choose eth0 as the adapter. ping google.com gives temporary failure in name resolution I tried adding 8.8.8.8 and 8.8.4.4 in the network options, but the error persists Windows 10, also in HVM mode, has internet normally. Also, I tried running in PV mode, choosing the most recent kernel. It simply halts rigth after the boot. Why? -- 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/37e7970a-e6ea-4f16-a148-ea1cc50fa8c0%40googlegroups.com.
Re: [qubes-users] Re: LibreOffice presentation mode with QubesOS
On Thu, Jan 16, 2020 at 12:00:05PM -0800, fabio.germ...@gmail.com wrote: > Am Mittwoch, 13. November 2019 09:30:08 UTC+1 schrieb Lorenzo Lamas: > > > > > > > > On Monday, November 4, 2019 at 7:42:26 PM UTC+1, Germann Fabio wrote: > >> > >> Hi qubes-users, > >> > >> Recently I tried to present a presentation using LibreOffice on qubes. > >> I'm not able to get into the presentation mode where I got the fullscreen > >> presentation on the HDMI display and the presentation mode screen (current > >> slide, next slide and comments) on the internal display. > >> > >> I assume this is because in the AppVM there is only one screen. Is there > >> any way around this? > >> Has anyone been able to get this working? > >> > >> Cheers, > >> Fabio > >> > > > > AppVM's by default don't have fullscreen access, have you enabled it first? > > https://www.qubes-os.org/doc/full-screen-mode/ > > > > Hi Lorenzo, > > I did not have this enabled. But also after turning it on (and rebooting) > the presentation mode does not work correctly. > With KDE it's straightforward. In the slide show settings set the presentation display. Start the slide show, and set the slide show window as full screen from the title bar. Now you have the control panel including notes on one screen and full screen slides on the other. You *may* be able to do this in Xfce. -- 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/20200120013952.GA24445%40thirdeyesecurity.org.
Re: [qubes-users] Why Windows 10 is slow? Is it because of HVM?
On Sunday, January 19, 2020 at 8:36:26 AM UTC-3, Claudia wrote: > > January 19, 2020 6:34 AM, "Guerlan" > > wrote: > > > Windows 10 VM is considerably slower than my traditional PV VMs, the > ones that come with Qubes. In > > fact no one would notice that my PV VMs are virtualized, they look just > like regular bare metal > > machines. > > However, Windows 10 has lags. Anyone would notice and think either the > computer is slow or the > > system is badly virtualized. For example, when I press Win button, it > takes a while for the menu to > > appear. I can only think that it's because Windows 10 is running in HVM > mode. Should I try running > > it in PV mode? If so, how? > > You could try it in PV mode. I'm not sure if it's supported by Qubes but > you could probably make it work. > https://xenproject.org/windows-pv-drivers/ > > Also consider that Windows might simply be slower than Linux, especially > in resource-constrained environments like a VM. Are your Linux HVMs also > slow/laggy? > I have kali linux in HVM mode and it's as fast as the PV VMs. The probem seems to be related to windows. I'm gonna try to make Windows 10 PV anyway -- 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/c0e25ff1-1e7f-4a65-b628-d6642485dc65%40googlegroups.com.
Re: [qubes-users] Re: Should I chose a TemplateVM or a StandaloneVM for a Windows 10 VM ?
On Sun, Jan 19, 2020 at 04:29:26AM -0800, trueriver wrote:
>
>
> On Thursday, 16 January 2020 17:55:22 UTC, M wrote:
> >
> > I read about a TemplateVM and a StandaloneVM in the ???Glossary of Qubes
> > Terminology???. But I???m still not sure about which kind of VM to choose
> > for a
> > Windows 10 VM.
> >
> > Can someone please tell me more clearly when to chose these kinds of
> > VM???s,
> > and which you would recommend for a Windows 10 VM and why ?
>
>
> Hi M,
>
> The quick rule of thumb is that if you are installing from an iso file, you
> need a standalone VM. This obvs includes any version of Windows. I will
> explain why.
>
> A template VM in Qubes is the base part of a Linux install, missing the
> parts that are specific to a particular user. So when you run "vault" and
> "untrusted" both using the same template, the two VMs have the same rnge of
> software available, but different histories: sharing the base install save
> space, havng different history means that if your untrusted machine has
> been hacked, vault is still safe.
>
> A second thing to know about the Qubes templates is that they include the
> Qubes magic software that enables you to send files from one VM to another,
> copy and paste across different machines, and so on (most of these programs
> have names beginning with "q" ("qrexec", and suchlike).
>
> Official templates exist for Fedora and Debian. The Wizardly enthusiasts in
> the Qubes user community have also created templates for other Linux
> distributions. If like me you are less endowed with Linux-hacking skills,
> you either start from someone else's template, or create a standalone
> machine using the .iso install "disk" for that operating system.
>
> In the case of Windows that is an easy decision: the internals of Windows
> are so different to Linux that I am told there is no chance of even a
> mighty wizard creating a Windows template. So its install from .iso onto a
> standalone VM. I think you will also find you need to choose HVM as the VM
> type.
>
> Finally, Microsoft may want a further fee from you to make that install
> official. Running Windows in a VM counts as a separate machine to the one
> that acts as host :( Be prepared to pay, or expect to run your system as
> an unregistered one which may have an impact on Windows Update :(
It's simple to create a Windows template *without* any wizardry. Just
proceed as normal creating a template and install windows from iso.
Any qubes you run using that template will be disposable - that is, any
changes you make will be lost on shutdown.
If you install the QWT in to the windows qube and move user directories
on to 2nd disk, then you have a fully featured windows qube running off
the template with user home surviving between reboots.
As to the "further fee" M$ licensing is notoriously difficult to get to
grips with, but if you have a license for the Windows version you are running,
that will do even if the install is in a VM - this has been the case for
some time.
You can register the template, and qubes based on it will (in my
experience) retain license. The only questionable activity would be
running multiple windows qubes at the same time - quite probably system
resource would prohibit that in any case.
unman
--
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/20200120002800.GB24247%40thirdeyesecurity.org.
Re: [qubes-users] Re: qvm-create-windows-qube 2.0
On Sun, Jan 19, 2020 at 08:53:10AM -0800, trueriver wrote: > In version 4 of Qubes, the Debian templates need a little extra software to > run as templates for the sys-XXX Qubes. Best to is to pieced as if for the > minimal Debian template, and apt-install what's needed for the three sys-XXX > Qubes. Some of those packages are already installed but apt will just tell > you so, and install the missing ones > The Debian template should be usable for sys-** qubes - it is for me, and I dont think I installed anything on the default template. (although I do build my own.) Please detail which software you think is missing. -- 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/20200120001822.GA24247%40thirdeyesecurity.org.
[qubes-users] Screen recording in Qubes VMs
I was wondering if anyone has had any luck with recording screen captures in Qubes. I tried the following FFmpeg line, which worked fine except it's only capturing a 640x480 corner of the screen. I'm not sure if this is Qubes-related or if I'm just not using it correctly. Note, I'm running this inside a Fedora VM, meaning other VMs' windows seem to be invisible (which is what I want in this case). Also, window borders and anything else drawn by dom0 seems to be invisible, but window content appears to be captured fine apart from the capture area being too small. $ ffmpeg -f x11grab -i :0.0 -vcodec libvpx -s 1920x1080 /tmp/ffout.webm [...] Input #0, x11grab, from ':0.0': Duration: N/A, start: 1579388031.870036, bitrate: N/A Stream #0:0: Video: rawvideo (BGR[0] / 0x524742), bgr0, 640x480, 29.97 fps, 29.97 tbr, 1000k tbn, 1000k tbc File '/tmp/ffout.webm' already exists. Overwrite ? [y/N] y Stream mapping: Stream #0:0 -> #0:0 (rawvideo (native) -> vp8 (libvpx)) Press [q] to stop, [?] for help [libvpx @ 0x56c7902a5900] v1.8.1 Output #0, webm, to '/tmp/ffout.webm': Metadata: encoder : Lavf58.20.100 Stream #0:0: Video: vp8 (libvpx), yuv420p, 1920x1080, q=-1--1, 200 kb/s, 29.97 fps, 1k tbn, 29.97 tbc Metadata: encoder : Lavc58.35.100 libvpx Side data: cpb: bitrate max/min/avg: 0/0/0 buffer size: 0 vbv_delay: -1 [...] Even though I'm setting the output resolution to my screen size, it seems to be detecting the input resolution at 640x480, and I haven't found any way to specify input resolution. I've tried with several different codec/container combinations but it still only captures the upper left corner. I was wondering if it could have something to do with Qubes because of the way the desktop is shared by different 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. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/e6656cf4c1a92e5766aad253a0fc252a%40disroot.org.
Re: [qubes-users] Qubes OS 4.0.3-rc1 has been released!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2020-01-16 4:46 PM, David Hobach wrote: > On 1/15/20 12:59 PM, Andrew David Wong wrote: >> Shortly after the announcement of 4.0.2 [1], a bug [2] was discovered in >> the dom0 kernel included in that release. Since the bug would have >> presented installation problems for the majority of users. That bug has >> now been fixed, along with a few installer fixes, resulting in >> 4.0.3-rc1. > >> >> What should I do? >> = >> >> If you installed Qubes 4.0, 4.0.1, or 4.0.2 and have fully updated [4], >> then your system is already equivalent to a Qubes 4.0.3 installation. No >> further action is required. > > I didn't get any dom0 or template update. > Kernel is 4.19.84-1, qubes-core-dom0 is at 4.0.48-1, > qubes-core-dom0-linux at 4.0.21.1. > > I also didn't get the updates for QSB #56 on the stable repo yet. > > Can someone confirm that? > > Thanks in advance! > I appear to have the same versions for all those components. I believe it is because we only have the "current" (and possibly "security-testing") repo enabled. If you were to enable "current-testing", I suspect you would see newer updates. - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAl4k270ACgkQ203TvDlQ MDDdkQ//XeHNPBen4vi+S8jZUc9NyARkKrCCHIqX4WPZcFnCZP+gl1A+tfJJviip IcHMnB6IXbVsGqYyhO38ob5EM2E80X8/TxN9J6RQIiRnT4P+MSVN+/pD9UD3VBgC Eg3i0o0kseWi3coeXauRyXCnCXBIHiuqjlkQt+EMhReC37v71I77NV0QRpoQjGec MY5cq9bT7Wr3YccUWPSMC8S1Cf/7HivYSGGcyUwX9/h+bJQ4HmxreRHbOmWqsk0q MdZEWTttqGVkFf68QBei1O4qmV+HrKvYMOWlZrfDQkUHLDk9DrUKWrXSbuLzYWCC 5pMphfvJn0yycC9w97R/+OYZ32RoMrJUET4mHUnR+5U0e5383R9fGVjdP5L56aUa 4Wh/53dVsP19PrKcwVkBtFxUizWNd04viQ/pYA0Mbf84qPBnaFtRiBXiZEfl5p0H SlO7YrP+ZNdzuGjBOD5oYp4QHjNlc9LhhK7S6pHVGKFWSV+w9M3yZVn3Gqy2sA2x akzganRIiTBZa6ZICgdeZfMzc5aG/06PvsNSm1CIgqFOPdj3VnlOb6ctxdAUxOFe ZDENTBmsoanBckF4BMSMqQHCV9aDlqttPQuz9GHVJuMlJ4UwtPHf6mYXk5Rvrm2I syoUKRuZbnfLHpTIPR8e4osWfueu77lewQNJCWz5dbaHp4hgmbg= =Gcvd -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/0f65eca1-b315-7408-7f4e-46c4f7a22b66%40qubes-os.org.
Re: [qubes-users] “Help! Qubes problems" : McAfee ENS not not installing on debian-10 Template vm
On 1/19/20 3:10 PM, 'awokd' via qubes-users wrote: Arshad Ali: Hi guys, I am new in Qubes OS, I need help regarding installation of McAfee on debian VM, I have installed McAfee Agent on debian-10 Template vm, When I am trying to push ENS package from McAfee server to debian-10 Template VM its getting fail. From McAfee server I can only see sys-net connectivity with McAfee, where as McAfee agent is installed on debian vm, I am not sure where the problem is actually exist. Do I need to do any port forwarding on sys net and sys firewall (If It is how it can be, ). As I didnot make any rules in Firewall which is by default allowing all and internet is running on debian vm. I think you're missing some of the basics of Qubes. Check out https://blog.invisiblethings.org/2011/09/28/playing-with-qubes-networking-for-fun.html, for example. Qubes' networking is designed to prevent things outside your PC from connecting with things inside it. If you really wanted to, see https://www.qubes-os.org/doc/firewall/. Keep in mind though, templates intentionally do not have a network connection, so what you're trying to do wouldn't work even with port forwarding. You should also consider in general if installing third party software raises or lowers your security posture, as antivirus suites have historically had multiple vulnerabilities and are designed to upload files for further analysis based on criteria set by the third party. I think the transfer model for third-party definition updates in template vms would be to utilize a dispvm to download an update pack (e.g. in .zip or .tar format) which can then be qvm-copied to the template vm and fed to the antivirus software. IOW, the antivirus vendor should have an offline update procedure you can follow, you just need to add qvm-copy to the process. -- Chris Laprise, tas...@posteo.net https://github.com/tasket https://twitter.com/ttaskett PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 -- 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/65849104-0e7e-c792-f8ae-3e7f6aa872d2%40posteo.net.
Re: [qubes-users] Re: qvm-create-windows-qube 2.0
On Friday, January 17, 2020 at 11:01:05 PM UTC, Elliot Killick wrote: > > On 2020-01-15 01:36, shiftedreality wrote: > > > You pointed me in the right direction. I was using Debian 10 as my > default > > Qubes template. > Debian 10 is supposed to be supported as a template. I didn't realize > the Debian 10 template qube didn't come with cURL. Bug fixed, thanks for > catching that. > On my nth install of Qubes...and learning the hard way about passing informal scripts to others... :) A reminder if using the standard lvm config : the cloning of VMs/templates only ends up using additional storage for the *divergence* of each from the other(s). So, I'd recommend, if scripting for others: keep a pristine un-updated copy of the target template(s) to test scripts against. Even better would be a pristine copy and an "up-to-date but not customized" copy. E.g. debian-10 <- installed by qubes, developer *disables* automatic update reminders and does not update (frozen) debian-10-up-to-date <- cloned by developer, not customized, only ever apply updates debian-10-custom <- cloned by developer, apply customizations (e.g. apt-install stuff), apply updates. For day to day use with your VMs. That way one can (without having to remove and recreate templates via dom0 salt, dnf invocations, etc) test your scripts against baseline expectations of other users. Brendan -- 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/dd9d8548-d1eb-4450-b946-1d4667dbc99d%40googlegroups.com.
Re: [qubes-users] “Help! Qubes problems" : McAfee ENS not not installing on debian-10 Template vm
Arshad Ali: > Hi guys, > > I am new in Qubes OS, I need help regarding installation of McAfee on > debian VM, > > I have installed McAfee Agent on debian-10 Template vm, When I am trying to > push ENS package from McAfee server to debian-10 Template VM its getting > fail. > > From McAfee server I can only see sys-net connectivity with McAfee, where > as McAfee agent is installed on debian vm, > I am not sure where the problem is actually exist. Do I need to do any port > forwarding on sys net and sys firewall (If It is how it can be, ). > As I didnot make any rules in Firewall which is by default allowing all and > internet is running on debian vm. > I think you're missing some of the basics of Qubes. Check out https://blog.invisiblethings.org/2011/09/28/playing-with-qubes-networking-for-fun.html, for example. Qubes' networking is designed to prevent things outside your PC from connecting with things inside it. If you really wanted to, see https://www.qubes-os.org/doc/firewall/. Keep in mind though, templates intentionally do not have a network connection, so what you're trying to do wouldn't work even with port forwarding. You should also consider in general if installing third party software raises or lowers your security posture, as antivirus suites have historically had multiple vulnerabilities and are designed to upload files for further analysis based on criteria set by the third party. -- - don't top post Mailing list etiquette: - trim quoted reply to only relevant portions - when possible, copy and paste text instead of screenshots -- 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/08fa44c6-185d-c01f-45d6-52d269f6943c%40danwin1210.me.
Re: [qubes-users] Cannot use bluetooth headset with Fedora-30 + Bluez
Claudio Chinicz: > Hi All, > > I've installed Bluez and Pulse Audio on a Fedora-30 based VM. When I attach > my Bluetooth USB dongle to the VM I see the Bluetooth icon in the upper > right corner. > > If I click on the icon it opens Bluetooth Manager and I can scan and find > my headset. Then I "trust" it and successfully pair it. > > To my surprise, when I open the browser and play any sound it comes out of > the embedded speakers in my computer (Dell Latitude 5590 Core i5 8th gen). > > When I open Pulse Audio Control to configure the audio I see only "Qubes > vChan Output/Input" and not the Bluez device. > > Any ideas? > > Thanks > Not an option for Qubes at the moment. Possibly 4.1. Keep an eye on and/or contribute to https://github.com/QubesOS/qubes-issues/issues/1590. -- - don't top post Mailing list etiquette: - trim quoted reply to only relevant portions - when possible, copy and paste text instead of screenshots -- 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/0fc21b1b-4646-76ca-ea2c-511608567008%40danwin1210.me.
Re: [qubes-users] Qubes OS Network installation - Possible to Mirror dom0 iso contents?
ryank...@gmail.com:
> I was trying to put together a network installer for QubesOS for
> netboot.xyz.
>
> You are already leveraging Dracut with the full network stack and livenet
> hooks so booting something like this example below in IPXE loads the
> installer interface: (if you rip isolinux/initrd.img isolinux/vmlinuz,
> and LiveOS/squashfs.img out of a Live CD)
>
> :CUSTOM
> imgfree
> set url http://192.168.10.13:8080/
> kernel ${url}vmlinuz root=live:${url}squashfs.img
> repo=https://ftp.qubes-os.org/repo/yum/r4.0/current/dom0/fc25/
> ro rd.live.image rd.lvm=0 rd.luks=0 rd.md=0 rd.dm=0 initrd=initrd
> initrd ${url}initrd
> boot
>
> The problem is that the hosted repo does not contain the base packages in
> the ISO repo (bash among others).
>
> Would it be possible to mirror the ISO repo contents to
> "/repo/yum/r4.0/current/dom0/fc25/" to support network based installs
> without a local repo?
>
> Let me know if you need anymore information.
>
If the Qubes team can't support that, couldn't you set up your own
internal repo server?
--
- don't top post
Mailing list etiquette:
- trim quoted reply to only relevant portions
- when possible, copy and paste text instead of screenshots
--
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/80a09c39-914d-735c-35c0-93b25cd06f5f%40danwin1210.me.
[qubes-users] Grayscale display settings
Hey there, what is the best way to switch my whole display to black and white / grayscale? I found this thread: https://askubuntu.com/questions/443335/how-can-ubuntu-be-made-grayscale/443346#443346 But I'm unsure where to implement this in dom0. Thanks! Max -- 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/fd2b19b5-cb4b-1fde-1681-04e1086bc9d4%40posteo.de.
[qubes-users] HCL - Tuxedo InfinityBook 14 v4
Hello Qubes OS runs very good on my system, although I had some problems with the installation. I had to follow this guide: https://www.qubes-os.org/doc/uefi-troubleshooting/#installation-freezes-before-displaying-installer After the installation i find it useful to follow this guide to make Qubes OS boot directly. https://www.qubes-os.org/doc/uefi-troubleshooting/#boot-device-not-recognized-after-installing Without this its necessary to select the UEFI file manual every time, the BIOS will ask how to boot and offers a option boot from file. AEM is not working, because the laptop uses a TPM2. The LTE module makes some problems after with reconnecting after you connected successfully. To solve this just restart sys-usb. Also I need to apply this guide for sys-net to make the LTE modem work: https://www.tuxedocomputers.com/en/Infos/Help-Support/Instructions/Setting-up-and-troubleshooting-UMTS/LTE-modules.tuxedo# For using the webcam the USB 2.0 controller must be set to non strict reset. Under my normal usage with Wireless disabled the battery has enough power for 6 hours. The Thunderbolt port works perfectly with USB-C devices, but I didn't test connecting Thunderbolt devices jet. -- 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/a9dba77a-625c-6d45-2479-fe715f6b29c5%40mail.de. Qubes-HCL-TUXEDO-TUXEDO-20200119-175853.yml Description: application/yaml signature.asc Description: OpenPGP digital signature
Re: [qubes-users] Re: qvm-create-windows-qube 2.0
In version 4 of Qubes, the Debian templates need a little extra software to run as templates for the sys-XXX Qubes. Best to is to pieced as if for the minimal Debian template, and apt-install what's needed for the three sys-XXX Qubes. Some of those packages are already installed but apt will just tell you so, and install the missing ones -- 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/06fa7a1f-b7eb-404b-997c-fc08739fe3bb%40googlegroups.com.
[qubes-users] Re: Should I chose a TemplateVM or a StandaloneVM for a Windows 10 VM ?
torsdag den 16. januar 2020 kl. 18.55.22 UTC+1 skrev M: > > I read about a TemplateVM and a StandaloneVM in the “Glossary of Qubes > Terminology”. But I’m still not sure about which kind of VM to choose for a > Windows 10 VM. > > Can someone please tell me more clearly when to chose these kinds of VM’s, > and which you would recommend for a Windows 10 VM and why ? You might try this: https://groups.google.com/d/msg/qubes-users/AdQcjg7XOFo/0bUFmyi7CgAJ Sincerely Max -- 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/3cb63b16-a65d-474a-abe0-5f90ea5e1b5f%40googlegroups.com.
[qubes-users] Re: Should I chose a TemplateVM or a StandaloneVM for a Windows 10 VM ?
Thank you very much for your detailed answer. May I ask: Which difference does it make to Microsoft update if I use a payed or unpayed version of Windows 10 ? - I didn’t know there were a difference although it seems fair. -- 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/bd65479d-1f1d-4b2a-9e32-9943f445805e%40googlegroups.com.
Re: [qubes-users] How to use QEMU with Qubes?
On Wednesday, 8 January 2020 11:46:52 UTC, Claudia wrote: > ...Xen uses QEMU just to emulate virtual hardware devices for HVMs, not > for the actual virtualization. "Normal" Qemu is actually Qemu/KVM, which is > not supported on Xen as far as I know. The next best thing is to create an > HVM, see > https://www.qubes-os.org/doc/standalone-and-hvm/#installing-an-os-in-an-hvm Here is a bit more background -- not strictly necessary to your immediate Q For Linux users, "normal" QEMU is indeed Qemu/KVM. However, some QEMU fans would probably argue that the definitive QEMU is the version that emulates everything. Obviously that leads to a slow running system, but will certainly run in an HVM. QEMU/KVM leverages the Linux kernel to run as much of the code as possible directly (ie on bare metal or in an HVM). There is also a Windows variant (iirr called KQEMU) which runs on Windows (but only after you install the KQEMU drivers). > qemu-img-xen is used for formatting image files or block devices for VMs. > qemu-nbd-xen is for network block devices, though I'm not sure if/how > they're used in Qubes. > Most, or maybe all, the programs whise name begins qemu-... are utilities borrowed from the QEMU project, rather than actually part of the QEMU emulator itself. Why write a utility when the QEMU team already did what you want? In fact, both KVM and XEN use QEMU code internally, but not in a way that you can easily leverage for what you are trying to do. So too does VirtualBox, which means Oracle cannot make it closed source without re-inventing a lot of QEMU wheels -- 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/51a4add5-ed79-46fa-9171-f70d7c86eb3e%40googlegroups.com.
Re: [qubes-users] Qubes booting in machine with Windows and Linux
Em qui, 16 de jan de 2020 às 06:27, > escreveu: > Rafael and trueriver, you mean boot into BIOS each time to choose the OS? >> That's the way I have it now. I hit f1 upon turning the computer on to go >> into BIOS, and then I have the choice between Qubes or Debian (which is >> done through Grub, which also gives me the option to choose Windows). Or if >> I don't boot into BIOS with f1, it goes directly to Grub. Is that what you >> guys mean? >> >> Exactly (but in my case it is esc, not F1) R~~ -- 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/989b10ed-5150-42fc-9638-4d6013492609%40googlegroups.com.
[qubes-users] Re: LibreOffice presentation mode with QubesOS
On Monday, 4 November 2019 18:42:26 UTC, Germann Fabio wrote: > > Hi qubes-users, > > Recently I tried to present a presentation using LibreOffice on qubes. I'm > not able to get into the presentation mode where I got the fullscreen > presentation on the HDMI display and the presentation mode screen (current > slide, next slide and comments) on the internal display. > > I assume this is because in the AppVM there is only one screen. Is there > any way around this? > Has anyone been able to get this working? > > Cheers, > Fabio > Hi, I have no experience with this use case, so this reply is purely theoretical. You will need to do something in the AppVM and something else in Dom0. This is because the functionality that you are trying to use is spread across those two VMs in the Qubes model. In Dom0, you will at least need to tell the Display manager that there will be more than one display. To do this, use the standard XFCE display settings icon, which you can reach through the menu system. At the very least, you need a tick in the checkbox for "configure new displays when connected". Without this, Dom0 wil not acknowledge that there is more than one display so cannot show different things on the respective displays. Once you have enabled the second display in Dom0, go into your AppVM and do what you normally do. I can't advise beyond that, except that if LibreOffice gives you two windows you can maybe drag each one to where you want it... Finally, the other setting that is also called "presentation mode" coerns the power settings, in order to stop the screen banking, or going into screen saver, during the presentation. You may have a checkbox called "presentation mode" in the battery status widget in the system tray -- if not you will have to go into the Power Mannager in settings and select "never" in the relevant places. Not sure if that will help... Good Luck River~~ -- 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/cfe74d2c-0346-4390-aa99-44b6d32eee69%40googlegroups.com.
[qubes-users] Re: Should I chose a TemplateVM or a StandaloneVM for a Windows 10 VM ?
On Thursday, 16 January 2020 17:55:22 UTC, M wrote:
>
> I read about a TemplateVM and a StandaloneVM in the “Glossary of Qubes
> Terminology”. But I’m still not sure about which kind of VM to choose for a
> Windows 10 VM.
>
> Can someone please tell me more clearly when to chose these kinds of VM’s,
> and which you would recommend for a Windows 10 VM and why ?
Hi M,
The quick rule of thumb is that if you are installing from an iso file, you
need a standalone VM. This obvs includes any version of Windows. I will
explain why.
A template VM in Qubes is the base part of a Linux install, missing the
parts that are specific to a particular user. So when you run "vault" and
"untrusted" both using the same template, the two VMs have the same rnge of
software available, but different histories: sharing the base install save
space, havng different history means that if your untrusted machine has
been hacked, vault is still safe.
A second thing to know about the Qubes templates is that they include the
Qubes magic software that enables you to send files from one VM to another,
copy and paste across different machines, and so on (most of these programs
have names beginning with "q" ("qrexec", and suchlike).
Official templates exist for Fedora and Debian. The Wizardly enthusiasts in
the Qubes user community have also created templates for other Linux
distributions. If like me you are less endowed with Linux-hacking skills,
you either start from someone else's template, or create a standalone
machine using the .iso install "disk" for that operating system.
In the case of Windows that is an easy decision: the internals of Windows
are so different to Linux that I am told there is no chance of even a
mighty wizard creating a Windows template. So its install from .iso onto a
standalone VM. I think you will also find you need to choose HVM as the VM
type.
Finally, Microsoft may want a further fee from you to make that install
official. Running Windows in a VM counts as a separate machine to the one
that acts as host :( Be prepared to pay, or expect to run your system as
an unregistered one which may have an impact on Windows Update :(
Hope that helps
R~~
--
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/9c1d40f2-d78b-4ff3-9b95-16d930e72559%40googlegroups.com.
Re: [qubes-users] Why Windows 10 is slow? Is it because of HVM?
January 19, 2020 6:34 AM, "Guerlan" wrote: > Windows 10 VM is considerably slower than my traditional PV VMs, the ones > that come with Qubes. In > fact no one would notice that my PV VMs are virtualized, they look just like > regular bare metal > machines. > However, Windows 10 has lags. Anyone would notice and think either the > computer is slow or the > system is badly virtualized. For example, when I press Win button, it takes a > while for the menu to > appear. I can only think that it's because Windows 10 is running in HVM mode. > Should I try running > it in PV mode? If so, how? You could try it in PV mode. I'm not sure if it's supported by Qubes but you could probably make it work. https://xenproject.org/windows-pv-drivers/ Also consider that Windows might simply be slower than Linux, especially in resource-constrained environments like a VM. Are your Linux HVMs also slow/laggy? -- 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/13bd70f93be3ec92017d4b60f9c15211%40disroot.org.
Re: [qubes-users] Re: Why Windows 10 is slow? Is it because of HVM?
January 19, 2020 6:58 AM, "Claudio Chinicz" wrote: > Hi, > > As far as I understand, HVMs should be faster than PV. With the latter, the > OS makes hyper calls to > the hyper-visor while HVMs simply see virtualized hardware through the hyper > visor. I always thought the opposite was true. PVs should be faster because they don't have to go through a hardware emulator, they can just communicate with the hypervisor using an efficient protocol. I think that was the only reason for creating PVs in the first place (other than historical reasons before VT-x maybe). Otherwise they would have made HVM the only mode, much like KVM does. Btw, Qubes 4.0 uses PVH as the default mode, except for PCI passthru VMs. The reason is that the PV, while efficient, has become really insecure and is becoming deprecated. PVH runs the VM under VT-x like an HVM, but also has special guest-side PV drivers to make I/O faster by bypassing the emulated hardware. For example, PV(H) guests use the blkback driver (e.g. xvda) while HVM guests use a virtual SATA controller (e.g. sda) which is emulated by Qemu in userspace. Similarly, PV(H) uses netfront (e.g. "vif0" network interface) while HVMs use an emulated ethernet device (e.g. "eth0"). For PCI devices, PV(H) uses pcifront, however I think this is deprecated, which is why Qubes 4.0 uses HVM for all passthru VMs. HVMs use the platform features (e.g. IOMMU) to passthru the actual PCI hardware. HVM: DomU driver -> Xen -> Qemu -> Dom0 hardware driver -> Dom0 hardware PV: DomU PV driver -> Xen -> Dom0 hardware At least that's my understanding. -- 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/e7845a66f425df1eceff215ed57821b8%40disroot.org.
Re: [qubes-users] Intel ax200, wifi 6, 2723 on X1 gen2 extreme
On Sun, 19 Jan 2020, man...@andaztech.com wrote: > I downloaded and ran RebornOS from a live USB, the Intel AX200 gets > picked up be default and works (used it for two hours with no issues) > The only difference I could see wa the firmware file loaded was > iwlwifi-cc-a0-50.ucode instead of the iwlwifi-cc-a0-46.ucode > > Will try that firmware on a qubes VM and update. > > Anyone tried that firmware file? Yes, I've tried also with -50 firmware (with a number combinations of kernel versions; firmwares -46, -48, and -50; and also with and w/o dkms backport). My problems did not go away with it nor was there any notable change. I've not tested is baremetal myself (and have no intention to). Perhaps the problems are related to having Xen in the equation (but that's just a guess). -- i. -- 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/alpine.DEB.2.20.2001191226470.26882%40whs-18.cs.helsinki.fi.
Re: [qubes-users] Intel ax200, wifi 6, 2723 on X1 gen2 extreme
Hi I downloaded and ran RebornOS from a live USB, the Intel AX200 gets picked up be default and works (used it for two hours with no issues) The only difference I could see wa the firmware file loaded was iwlwifi-cc-a0-50.ucode instead of the iwlwifi-cc-a0-46.ucode Will try that firmware on a qubes VM and update. Anyone tried that firmware file? -- 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/9f5f4f29-2785-44d9-85eb-8e92180e0415%40googlegroups.com.
[qubes-users] Failing to load kernel modules/X startup failed, aborting installation [AMD Ryzen 3200G, ASROCK X570M Pro4, 32 GB ram]
I have tried to install Qubes OS 4.0.1 and 4.0.2 by using a DL-DVD both in UEFI and Legacy mode. In UEFi the cursor ends up blinking on a black screen. In Legacy mode I end up just before loading the graphical interface by getting an error message: Failing to load kernel modules/X startup failed -> Aborting installation. For screenshots, see here: https://github.com/QubesOS/qubes-issues/issues/4510 I have also tried the other possibilities to install Qubes that the two ISO-DVD’s offer. But that also ended with the same result. Can anyone tell me how to get further... ? -- 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/d0d419ba-f511-4ef0-b6eb-94564c8898b1%40googlegroups.com.
