Re: [qubes-users] Must create HVM if I want to use a unsupported distro as a VM?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 9/10/18 8:07 PM, Stumpy wrote: > Am i understanding this right? Can't answer for unman, but in general this is possible and in my opinion advisable: - -> https://www.qubes-os.org/doc/dispvm-customization/ If you go this route, it comes with limitations: - -> NetVM will obviously "forget" previously connected networks - -> Firewall VM will obviously forget manually added rules I don't use manual firewall rules, so this is not an issue for me. And regarding the NetVM I have done the following to "teach" the DVM template my two most frequent WiFi passwords: 1) all my sys-vms are based on a clone of fedora-28-minimal named tpl-sy s 2) in tpl-sys I have installed additional packets as listed here: https://www.qubes-os.org/doc/templates/fedora-minimal/ (you also need gnome-keyring for the password dialog in the NetVM ... change request for the docu in already underway). 3) created app-vm named dvm-sys based on tpl-sys and temporarily set virt_mode to hvm and provides_network to true. 4) ran dvm-sys and connected it to my two frequent WiFi networks 5) reversed virt_mode to pvh and provides network to false 7) created sys-dvm-net as outlined in the docu mentioned at the beginning of this post using dvm-sys as disp vm template /Sven -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEE18ry22WNibwI1qeq2m4We49UH7YFAluXG8MACgkQ2m4We49U H7aQ1A//cAbCBplslNOt4120mW2G0qmXMGAVsgVhS7kWrXQaj3kTB0uQKldsA2qM JKYeKzll2t8dP4IiY1rtMhKOW4b8QEL0gv7n27o/tmVZPA8EeK5+rvMHuOg72jIt 77gQVApzRAaH/WuzyqJY/+mGxbTqo80zUpnG3ThVB/RIvqmm7HRoJsFA2jXA6VgX pAgYcxZBCT6tIuku1VfAIvJDHgaruerVZ5CVoTVoVFvFlWfgs7YjAsxD/TJ/gmUX GpxnqMVi7gQYzLFtKn63TyIhnrU95yDx0QutXZCfKv5dI5biZ0myLKHHNnFEQzMR llSVCgAB0HDyhTgaNKM5D7Z+Q+q3BJJC+Lma6pwixwdFvcGodBlzMdimG5RFt81Y uk2pEyZRlGUaHnAMMs2VF9lUdCbQBPM3CGHunRCf9kr2eB/yKV5lXDLoYLWth3SO ZCnDc3mKW/sXv1xznU78fPE9b2r8ydfH5DoVoueue2GxKueQoqlxt4Bx2xUvBFBj Nfolm+jsBiOaxlMjO+8/W6VInUbuNs2N8ATt5WQq1bLgG3YFsU/go/KCxTAXA1AW FVdu+9DIBrYn3u1og1Zz3gu8yW4r/4Y27PZwTLeKRXzcDXZtMWG5RyCEwrzMXHLV yYauiaQlcWtCIcdr27EYW+vGJHfolYW9eca6+2vUCKT+mkJJ3gk= =49Kr -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 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/557caf40-da05-4e0a-7371-ae210ba1bcfb%40SvenSemmler.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Must create HVM if I want to use a unsupported distro as a VM?
On 09/10/2018 08:47 AM, unman wrote: On Sun, Sep 09, 2018 at 02:12:45PM -0400, Stumpy wrote: On 09/08/2018 09:09 PM, unman wrote: On Sat, Sep 08, 2018 at 10:17:32AM -0400, Stumpy wrote: I want to use a linux distro that currently doesnt seem to have a template for Qubes. Does that if I want to use it I would have to either go the HVM route like for win or create my own template (probably beyond me). Yes, that's right. Bear in mind that you can use these as templates too. Thanks Unman So when you saud "can use these as templates too" you mean that a HVM can be used as a template? (oh god please say yes!!! if yes then I am assuming I could make a win7 template and create win7 appvms?) Pleased to say "Yes". Yes you can create win7 appVMs from a template. Unless you use QWT to set home directory to /dev/xvdb you will have effectively a disposableVM, which may throw you to start with. You can have this for any HVM - do full install on to /dev/xvda, and any qubes based on that template will act as disposableVMs. I have BSD netvms set up like this. unman ... I sent my previous email too soon, that is, it just occured to me that you said you have your netvms set up like this using BSD disposable templates? So your netvms are actually dvms? If yes, that sounds like a really good idea, so even if they are compromised they would be "disinfected" after reboot or after they are restarted? Am i understanding this right? thanks again! -- 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/3f705677-36c8-b359-84c1-1ec0a4e9df87%40posteo.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Must create HVM if I want to use a unsupported distro as a VM?
On 09/10/2018 01:15 PM, Sven Semmler wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 09/10/2018 07:47 AM, unman wrote: Yes you can create win7 appVMs from a template. Unless you use QWT to set home directory to /dev/xvdb you will have effectively a disposableVM, which may throw you to start with. I am using a Win7 HVM as template and have have two AppVMs based on it. Without QWT. You can move the user directory manually in the template VM and then use dd to copy the private section once when creating the AppVM. Steps: - -> In your Windows 7 HVM which will be your template use Disk Manager to format the private partition. By default it usually is 2 GB and unuse d. - -> https://lifehacker.com/5467758/move-the-users-directory-in-windows-7 (use the manual way later in the post!) If your HVM is not already a template use qvm-clone --class TemplateVM Then: - -> https://groups.google.com/d/msg/qubes-users/TJZQbB9CvrU/j6Zu1ZaJCQAJ Obviously try QWT first, if it works for you. Having the shared clipboard and the ability to send/receive files in an AppVM is gold. For me QWT doesn't work yet but there seem to be many who have no issues. The above could be your fallback, in case you have issues like me [1]. /Sven [1] https://github.com/QubesOS/qubes-issues/issues/3585#issuecomment-4107642 31 -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEE18ry22WNibwI1qeq2m4We49UH7YFAluWps8ACgkQ2m4We49U H7aylRAAvxsBhARpwQzJZnPxAqhxV7ISsE9WOJi6RreJoc9mGFw9o98Zi1SilrYf Qh2Y5UMmrHQhQuvGl2+O2IUfNzVuc4DdJ3ZZNARGA4sNDCxvQobDs+jYs7bbLFK9 N50wQCU0uiTtuppc03xRLNQGXtvGo6hpcRynpY7S2ak6Tai1dLkuAdKkSwfBc3zJ WQuyiTbOVyS3uv5llbdmrllurbJhgGkfxJAJ3Zomv2N4B2OumwKeNO99rgBCP5ll igrySVfubozfOd/6YC8Z8Yd7c2JojNBV6Tsmfw0Ut8FAnslUUIa8Qyv0K74gaWS/ S7sKsplQdjLxoJNvoyG6svVex49GsHrOjA3ibbQdyWLxsybkp8d2wvIFeYc0WoCR i2GT1yxVGiQghKW0G6Gz8L4z04e/yrVLN6pFKiwSTn7Cjvxpt3PsFp01LLUPJJEL yYDvh/J3mcrJtdgihnnXUiQRjqQCPwxyVH1FAA1+6NkiRT4BGDrLrWotzisvAG5p p7yZPMRZNy2d/6ssh/Tw8iMY24eVZDrF6Krluxgf8b/3T7oX1ufJOcPI5NhF2v6z N3uXjc1XvuPTxeIrWEo4VWy7NBbH+PLz4PEQMjwJ/8a/sMRGbIgaa0ovNIeCmIdc S9AVBX02t4vvLURbej7Pmrxsh4s60pUgk6n6LTCUnupeCRz12cs= =zSIj -END PGP SIGNATURE- Thanks you very much for the additional info end the links, will try to give it a whirl this weekend! Cheers -- 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/eccd76a9-12bf-0a2d-fb32-0098db48b807%40posteo.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Must create HVM if I want to use a unsupported distro as a VM?
On 09/10/2018 08:47 AM, unman wrote: On Sun, Sep 09, 2018 at 02:12:45PM -0400, Stumpy wrote: On 09/08/2018 09:09 PM, unman wrote: On Sat, Sep 08, 2018 at 10:17:32AM -0400, Stumpy wrote: I want to use a linux distro that currently doesnt seem to have a template for Qubes. Does that if I want to use it I would have to either go the HVM route like for win or create my own template (probably beyond me). Yes, that's right. Bear in mind that you can use these as templates too. Thanks Unman So when you saud "can use these as templates too" you mean that a HVM can be used as a template? (oh god please say yes!!! if yes then I am assuming I could make a win7 template and create win7 appvms?) Pleased to say "Yes". Yes you can create win7 appVMs from a template. Unless you use QWT to set home directory to /dev/xvdb you will have effectively a disposableVM, which may throw you to start with. You can have this for any HVM - do full install on to /dev/xvda, and any qubes based on that template will act as disposableVMs. I have BSD netvms set up like this. unman Yeah! Good to know thanks! -- 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/171609ab-c95f-001f-83c5-82e473b81b6b%40posteo.net. 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
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... -- Alex -- 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/3e271448-d0ee-800c-b123-eab5591b3db6%40gmx.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: OpenPGP digital signature
Re: [qubes-users] suspend to ram, r8169, networking in sys-net not working after resume
Le lundi 23 avril 2018 00:30:40 UTC+2, cooloutac a écrit : > On Sunday, April 22, 2018 at 1:44:18 PM UTC-4, Mike Keehan wrote: > > On Sat, 21 Apr 2018 14:20:02 +0200 (CEST) > > 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. > > > >> > > > >> > > > >> After resuming from suspend to ram, networking on sys-net isn't > > > >> working: $ ip addr > > > >> 6: ens5: mtu 1500 qdisc > > > >> fq_codel state DOWN group default qlen 1000 link/ether > > > >> 4c:cc:6a:30:f5:90 brd ff:ff:ff:ff:ff:ff > > > >> > > ...snip... > > > > > >> --- > > > >> After resuming I've tried: > > > >> [user@sys-net ~]$ sudo rmmod r8169 > > > >> [user@sys-net ~]$ sudo rmmod mii > > > >> [user@sys-net ~]$ sudo modprobe mii > > > >> [user@sys-net ~]$ sudo modprobe r8169 > > > > > > > > did you try to `rmmod` *before* suspending ? > > > > > > > Try adding the module names to the sys-net file > > /etc/qubes-suspend-module-blacklist, and Qubes should handle them > > for you. > > > > Mike. > > I tried that for my ethernet module but it didn't help. Hi, In 4.0, I have the same issue. Everything worked well. I added internal memory. After rebooting my computer, the network connection has been disabled. Cable is properly connected. $ lspci | grep 8139 00:05.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI EXpress Gigabit Ethernet Controller (rev 06) It isn't a hardware problem because Ethernet card (same product) has been changed (same issue two weeks ago). $ ifconfig -a ens5: flags=4098 mtu 1500 ether 00:00:00:00:00:00 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73 mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1000 (Local Loopback) RX packets 3608 bytes 292280 (285.4 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 3608 bytes 292280 (285.4 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 $ sudo dmesg | grep 8139 [1.61] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded [1.629483] r8169 :00:05.0 eth0: RTL8168e/8111e at 0x9becc019d000, 00:00:00:00:00:00, XID 0c20 IRQ 71 [1.629507] r8169 :00:05.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko] [1.720634] r8169 :00:05.0 ens5: renamed from eth0 Help !! how can I fix it ? Thank you so much. 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/e80972fd-a10a-4c37-b127-139243225ef6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] HCL - MSI MS-7980 (update)
93AHXr5APi+mIkH7qh1Q35ou6Q0Jm9ncoG4YDtGlWryUpb8P4GXXZ97r Jt4S0fiXO+h+UDLAWi4t/q+rsBU2QZfEZd9HcQ6/9idXinrng6i4oPjsQeB/4XvU j2K+efsE2yRveS621dXVbquZsBsWXkbiUyggMYb7EdHq03uHPYMBiQgzVdKy/gKh 4PGAwQPhdotWWUCoBQw979YkrM1JuuJgKYKglCp3s0lYzTrELG8b3YLAWaCQfChv 1vS5d8yhNbB8bnGuV6+wDB4lMnay1u0rE2/BhaxYxmOiP9uABTG8FaTXgdFbKKJi qky2/n6JijWanQm7Rww/oOOSmoY9RbA4fXx6tYz3UhXy4yuTkXnEZTb600nau2Wj bR1X/l5+3oR5LPp9LpFc+pYQO/+QSqpVHmRyqZfbslZC7XKTC4vkeTQGM8C6lJp0 O6Ks3I13i3xBWM6BHuMbw9wSZ+rmt7GUM5c2MZ0t06Y4mEQyoJu4XId+FSSGvmL7 D73mvG3eIxbFqwE07an34aY+c5J6viXWrYBCvd6lV9p9DgpqWcmgxZYUj4MNovXM Y9otc2flotkC/o1GlHeQQ/hJ3QmTlm6404TpjwAxkEbRF2jrdA6DPEFPa0vWOUIh OoWg0DD+AZx80VF4PjKKIud/cunOxIDBMgpRB1xiQKzz4bqEa3G2FNiMr7e9X9lE 3ILOr8oWpAlHQfimB7NGacvcrpj86mpKdOK9pSDmtlzYoVLLxMKE5f1giw0rnd8E lffN6Kj+HXf2bYF5wtQ/KrtzQNgPqPL2Zm4JZ847wom15nfkH3akEcyWlS5MA/sb yrqUGoAt8Q8ilb6Bq/zfdpxqIBOJO4qVAK7sfoWVuJkSxWrX5zZxZSP19kq24Y0w iRuMaNd/WZyPgdY85GTmUoaRbHjgig261KKBbhLzrRE9p4aP6SAeSm2/AuTeCZYz VvUur8lLRbk/0ijuY9t+DegnKJJ10s/1C0aLry4fck3UPvbn9htjXo5aFEK+lQId Bt5/nVmQvCG8JJ2LbAZ6dzyNVPzbtR9MHDPeUy8+pI5eq4CoPy/YCky9XfjRUvU1 cqJy6dy++y2lfqkvIwOdKE3zbDndi6L2DSvCnzMNEJ09oxlhdmyDJo8odoSCowRv POaJMG0ewthZzajEoRJWIzzesJRGhCS538j/Fb0OL+u6ZcET8YgzXSkEabv9iy7r DFPlUf6JPZXJkJGNHrFw7D+Q++D0iKJq5ekHGvttU0fKtlpKxNXx4xed6rqFLFij 55ZNSI+PLSKrPId8NNFWi1K/iZv+UznrPRWXCG+UrRgrQDXZM1xqjhM1+ojVHQrp uV6fxvaRXxegJHDHAUJsK6NRcZOHkE3p6OZ14f8n18ISn3m1I0EA/ERQ5lixviOL gMrbCnUD1tqe5gYgMjeqPqSoSoFk5gxeSFpB7H06jQmjwDfXVHd2nfojtYs5IP4I mWsGodOYOmI02Q/yiRAjbdwdW3wublSnXo9MEAAKJ6Ef9Hf+LiMHEwt2S0u9dQ/N NxK7RLXdO9p+sar9fMyj4rCcGZWWt6vY7FNxAMKUb0NM4w3R4WCB7htsYDIVW4Bp png5gMZM5O4rBbf5ANUVW+sVQUDYII6wcqZhZc4H4FsUQNcakMdLQkm0UoZaSBH/ 8N5msIFWqM4h05wUpVRD+/CV90cFXdvJYYJpVjI3P2MOQ6IKCFBVgq8/HuumVoz5 jiOwc3Ger6BGTm634+CcpAnpP38Il/78ZyPzXxTQJv/Vp4JucfLb/SM6leNs8JUo VBSSGdKnSrGGE//9wxPM8MGaAqwkMuM1ANDBrn+MzFVgOKV/oh2JGWJXnBoK0oHx xP44G2Vl2Ja0PFitztIPBLA+UF+aA0rykvsNj9FXQvio52IgWCRF8H8tfHOE0cGd DTAeoY5h+xP05WrN6lAldnFDz+YgzSc8gltLojU9bODbeC7SU5h+9F1ZTkKQTCC4 j9wFAlCE9keUUurJG1bRjuEVgnJD+cdA0cSUO0jUsTR1XlJVXi9nisx0JUKLRq/J rS+GLXleUfDtGmY7Yuj7AVc2DcfRs1KRvQp+t5WwPExQA7OZY/rc7yq9jY8hTfj7 xL2Y+vEM6Cm8n9v7eZjeAO+nsp7PIBFkcCphNj2TeeqzQn32L006VvLDZ1msgCN/ 0DKBfL2GwtSM2G+xKjOpz+wRRxWkG+6a+FA3AGoxahLjVsDTpiD2mM9VLPhSiCv/ eEfB9/dHMjWm/s896Ztyg0poAPT5h1ZLXLdLZM8Ig6zDMPAYq9eqzovgt4vtt0iC S1yhywi/9IHJ4V6deZXqMNcWyDavDyFN32WI5Ws75j43J5pOxCTF4FM/wzgz4Tjb pH05sWPYADxlOFpdzrM81NOfE8UiBFKFuYmdrfdyEPaDTxDAKq4aPmeUjwLuFWLA BoKyd6f06KYdUqAIDcI90iQVyg/ONM2En9H6zT+CNSX2EHb9j8P2z05xwcfp8+7D 8LzLbWlJj1WrdUFYq1LCRSdYSol3rzP6lRYgSnLwMZ71LnVqC2lJ1HNMzsDthIy9 ds9nBb5ygGF/pN3jXYdaiCtsX1nTVfHU6TMYrapqHPL3Rzrcz37/QVQBOdV5OBDE BvgdtThyOfjWe/VimDJvYLpogUO4CKTWQ6NFBnjkXrcGjRp4vr/MghG65+nn4GeI VAVncaoX5A== =PyOk -END PGP MESSAGE- Qubes-HCL-MSI-MS_7980-20180910-120203.yml Description: application/yaml
[qubes-users] Re: Screen dimension issue with qubes started before plugging in additional monitors
Issue fixed. In my fedora28 template I
changed /etc/X11/xorg-qubes.conf.template to have a hardcoded amount of RAM
for "Videocard0". So from:
VideoRam %MEM%
to
VideoRam 49576
49576 is just the amount of RAM which was calculated by the
`qubes-set-monitor-layout` script for a VM started after my external
monitors were plugged in. VMs started before extra monitors were plugged
in had about half that amount.
There appears to be a bug on github which may very well be the same thing,
and I'll try to circle back to that github issue and report what worked for
me when I get a moment tomorrow.
- Ralph
On Mon, Sep 10, 2018 at 2:01 PM, qubes-users-list - <
qubes-users-l...@ralphdouglass.com> wrote:
> I've been running into an issue where mouse events inside of a qube (i.e.
> clicking around inside of a window) aren't being recognized if I started a
> qube before plugging in additional monitors and the area I'm trying to
> click in is off-screen from the standpoint of the monitor layout I had when
> the qube was started.
>
> Moving windows 'off-screen' works just fine, not surprisingly, since I
> assume that's Dom0's job and it's not confused about my screens.
>
> xrandr in the problematic qube and dom0 match in terms of screen sizes,
> but it looks like all screens in the problematic qube are positioned at 0x0.
>
> Here's the output from xrandr in a problematic qube started before I
> plugged in more monitors, and a non-problematic qube I started afterwards
> plugging in more monitors. I left off the disconnected devices
> (DUMMY{3..15}).
>
> Started before I plugged in extra monitors:
>
> Screen 0: minimum 64 x 64, current 2560 x 1440, maximum 32767 x 32767
> DUMMY0 connected primary 2560x1440+0+0 325mm x 182mm
>QB2560x1440 34.61*+
> DUMMY1 connected 1920x1200+0+0 0mm x 0mm
>QB2560x1440 34.61 +
>QB1920x1200 59.88*
> DUMMY2 connected 1920x1200+0+0 0mm x 0mm
>QB2560x1440 34.61 +
>QB1920x1200 59.88*
>QB1200x1920 59.95
>
> Started after I plugged in extra monitors:
>
> Screen 0: minimum 64 x 64, current 3160 x 3360, maximum 32767 x 32767
> DUMMY0 connected primary 2560x1440+600+1920 0mm x 0mm
>QB3160x3360 14.85 +
>QB2560x1440 59.96*
> DUMMY1 connected 1920x1200+1200+300 0mm x 0mm
>QB3160x3360 14.85 +
>QB1920x1200 59.88*
> DUMMY2 connected 1200x1920+0+0 0mm x 0mm
>QB3160x3360 14.85 +
>QB1200x1920 59.95*
>
> I can move the problematic DUMMY0 screen around, but not all the way to
> 600x1920 as I want to match the actual layout of my monitors.
> Specifically, I can move DUMMY0 to the position 599x383 but no further on
> either the x or y dimension. If I do more, I get the following error:
>
> $ xrandr --output DUMMY0 --auto --pos 600x383
> X Error of failed request: BadMatch (invalid parameter attributes)
> Major opcode of failed request: 139 (RANDR)
> Minor opcode of failed request: 7 (RRSetScreenSize)
> Serial number of failed request: 100
> Current serial number in output stream: 101
>
> (Same is true for 599x384).
>
> 600x384 is obviously not a random number, but I haven't figured out where
> to take this further.
>
> Any thoughts on what to try next?
>
> Thanks in advance,
>
> Ralph
>
--
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/CAMVV%3Dfz8DgX5eVkguO-rimMQCwyf4fQDBeNW%3DbMfQF6wr3W4Lw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: debian-9 template
On Friday, September 7, 2018 at 10:15:49 AM UTC-4, John Maher wrote:
> On Friday, September 7, 2018 at 10:12:52 AM UTC-4, John Maher wrote:
> > On Friday, September 7, 2018 at 9:45:33 AM UTC-4, unman wrote:
> > > On Thu, Sep 06, 2018 at 09:31:09AM -0700, John Maher wrote:
> > > > On Thursday, September 6, 2018 at 9:42:02 AM UTC-4, unman wrote:
> > > > > On Thu, Sep 06, 2018 at 05:24:24AM -0700, John Maher wrote:
> > > > > > On Sunday, April 29, 2018 at 8:20:40 AM UTC-4, higgin...@gmail.com
> > > > > > wrote:
> > > > > > > tried ---
> > > > > > >
> > > > > > >
> > > > > > > sudo qubes-dom0-update --enablerepo=qubes-templates-community
> > > > > > > --action=reinstall qubes-template-debian-9
> > > > > > >
> > > > > > > Again it appears to reinstall - message appears saying
> > > > > > > successfully installed.
> > > > > > >
> > > > > > > Then try to start DEBIAN-9 VM and get
> > > > > > > "ERROR:VM directory does not exist:
> > > > > > > /var/lib/qubes/vm-templates/debian-9".
> > > > > > >
> > > > > > > Help!
> > > > > >
> > > > > > I just did a fresh install of Qubes OS 4.0 on new hardware and I'm
> > > > > > having the exact same problem. None of the suggestions here have
> > > > > > resulted in any change, although I did not try:
> > > > > >
> > > > > > sudo qubes-dom0-update --enablerepo=qubes-templates-community
> > > > > > --action=reinstall qubes-template-debian-9
> > > > > >
> > > > > > and I'm not that interested in going that route.
> > > > > >
> > > > > > I've been using Qubes OS 3.2 for over a year now without this type
> > > > > > of problem. Any more suggestions or fixes?
> > > > > >
> > > > > > Thanks.
> > > > > >
> > > > > > John
> > > > > >
> > > > >
> > > > > Have you tried the obvious, and created the missing directory?
> > > > > Ownership should be root:qubes - compare to the other template
> > > > > directories.
> > > > >
> > > > > The only content is a symlink icon.png, pointing to
> > > > > /usr/share/icons/hicolor/128x128/devices/appvm-black/png
> > > > > You could create this yourself also.
> > > >
> > > > Unman, thanks for replying. I didn't run that command (sudo
> > > > qubes-dom0-update --enablerepo=qubes-templates-community
> > > > --action=reinstall qubes-template-debian-9), so I don't know if I would
> > > > get the same error message, but I do have the directory
> > > > /var/lib/qubes/vm-templates/debian-9.
> > > >
> > > > I've performed an automatic re-install of the debian-9 template twice
> > > > and a manual re-install once. Still, no applications display under
> > > > Applications tab. I can't even run a terminal via dom0 using: qvm-run
> > > > debian-9 gnome-terminal
> > > >
> > > > I have to believe there is a simple command to make this debian-9
> > > > template functional, but I don't know where to go from here.
> > > >
> > > > Thanks.
> > > >
> > > > John
> > > >
> > >
> > > Sorry John, I misunderstood.
> > > The message you quoted referred to a VM directory that did not exist,
> > > and I assumed *that* was your problem.
> > >
> > > It appears that your problem is that the template does not show any
> > > applications. Have you tried running 'qvm-start debian-9' followed by
> > > 'qvm-sync-appmenus debian-9' ? What is the result?
> > >
> > > Incidentally, it would be helpful if you gave a little more information
> > > about the errors you are encountering. When you try to run
> > > gnome-terminal, what exactly happens? Do you see any error messages?
> > > Does the template start?
> > >
> > > Have you tried running other applications using qvm-run? xterm? firefox?
> > >
> > >
> > > unman
> >
> > Hi unman,
> >
> > Thanks for this. Sorry, I do need to provide more info.
> >
> > I ran the following and got the following:
> >
> > [maher@dom0 ~]$ qvm-start debian-9
> > [maher@dom0 ~]$ qvm-sync-appmenus debian-9
> > Traceback (most recent call last):
> > File "/usr/bin/qvm-sync-appmenus", line 9, in
> > load_entry_point('qubesdesktop==4.0.12', 'console_scripts',
> > 'qvm-sync-appmenus')()
> > File "/usr/lib/python3.5/site-packages/qubesappmenus/receive.py", line
> > 390, in main
> > new_appmenus = retrieve_appmenus_templates(vm, use_stdin=use_stdin)
> > File "/usr/lib/python3.5/site-packages/qubesappmenus/receive.py", line
> > 364, in retrieve_appmenus_templates
> > new_appmenus = get_appmenus(vm if not use_stdin else None)
> > File "/usr/lib/python3.5/site-packages/qubesappmenus/receive.py", line
> > 158, in get_appmenus
> > "Error getting application list")
> > qubesadmin.exc.QubesException: Error getting application list
> >
> > Regarding errors, I really haven't received any, and I've mostly worked in
> > the GUI. For example, I opened Qubes Manager and ran Qube settings for the
> > debian-9 template. Clicking the Applications tab displays no applications.
> > Clicking the Refresh Application button results in no applications,
> > regardless how long I wait.
> >
> > Running 'qvm-run
[qubes-users] Screen dimension issue with qubes started before plugging in additional monitors
I've been running into an issue where mouse events inside of a qube (i.e.
clicking around inside of a window) aren't being recognized if I started a
qube before plugging in additional monitors and the area I'm trying to
click in is off-screen from the standpoint of the monitor layout I had when
the qube was started.
Moving windows 'off-screen' works just fine, not surprisingly, since I
assume that's Dom0's job and it's not confused about my screens.
xrandr in the problematic qube and dom0 match in terms of screen sizes, but
it looks like all screens in the problematic qube are positioned at 0x0.
Here's the output from xrandr in a problematic qube started before I
plugged in more monitors, and a non-problematic qube I started afterwards
plugging in more monitors. I left off the disconnected devices
(DUMMY{3..15}).
Started before I plugged in extra monitors:
Screen 0: minimum 64 x 64, current 2560 x 1440, maximum 32767 x 32767
DUMMY0 connected primary 2560x1440+0+0 325mm x 182mm
QB2560x1440 34.61*+
DUMMY1 connected 1920x1200+0+0 0mm x 0mm
QB2560x1440 34.61 +
QB1920x1200 59.88*
DUMMY2 connected 1920x1200+0+0 0mm x 0mm
QB2560x1440 34.61 +
QB1920x1200 59.88*
QB1200x1920 59.95
Started after I plugged in extra monitors:
Screen 0: minimum 64 x 64, current 3160 x 3360, maximum 32767 x 32767
DUMMY0 connected primary 2560x1440+600+1920 0mm x 0mm
QB3160x3360 14.85 +
QB2560x1440 59.96*
DUMMY1 connected 1920x1200+1200+300 0mm x 0mm
QB3160x3360 14.85 +
QB1920x1200 59.88*
DUMMY2 connected 1200x1920+0+0 0mm x 0mm
QB3160x3360 14.85 +
QB1200x1920 59.95*
I can move the problematic DUMMY0 screen around, but not all the way to
600x1920 as I want to match the actual layout of my monitors.
Specifically, I can move DUMMY0 to the position 599x383 but no further on
either the x or y dimension. If I do more, I get the following error:
$ xrandr --output DUMMY0 --auto --pos 600x383
X Error of failed request: BadMatch (invalid parameter attributes)
Major opcode of failed request: 139 (RANDR)
Minor opcode of failed request: 7 (RRSetScreenSize)
Serial number of failed request: 100
Current serial number in output stream: 101
(Same is true for 599x384).
600x384 is obviously not a random number, but I haven't figured out where
to take this further.
Any thoughts on what to try next?
Thanks in advance,
Ralph
--
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/CAMVV%3DfwL9RfKEQ0ZMS5kQz2QVuspCGw1_cnPtJarrRRObA2SHw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
[qubes-users] Update: HCL - LENOVO Thinkpad P51 (20hjs0bx00) for R4.0
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Update to https://www.qubes-os.org/hcl/#lenovo_thinkpad-p51-20hjs0bx00_i7-7820hq_k aby-lake_nvidia Now running R4.0 (for several months actually) - -> still needs EFI boot fix - -> networking hardware now detected out of the box /Sven -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEE18ry22WNibwI1qeq2m4We49UH7YFAluWqU4ACgkQ2m4We49U H7ZdEBAA1rh6ysCqc7JN9Rg7K1RxHUvK/srcR5cf1QhRReytR7nfJorOBJ5aCmpI 9Kqxc6piSrW10+GNFiTXtPb1A4y/uw2X4pP78HS1hboI9ZNZ92z57YcJllQ9R/Bw jZjFQprowznJYA1M+5LnwkIDZAHYNkJQ318md/qsQ7r5Jyy/cjrrnXI4s8QZZXZ8 X1ZvGzpeFAlytQyfq1QxWO0loqX14c6cNhnvWg1SnQN6SMaUV3CoFApMKns8gUCe KX9rVBUaKZlThTv2bnBiAKB+g0//DoIci/R1F3H1N/pfwo72q//Zp/VsLVxcFgWY ipmx7yam1wJdXtWLCf2YuK7s2bfRrMfR3tbVv9JLCzITvDvaA7MkwC42tsecOGh7 6vNB9c71qN3mwlW0wnV6Y+mYzT9RZuPN/3SXrhLaAkfO+dnbjVd/IdsM1dw84Gba fIKfIk2JjOXUPOS5g+6gxrmO7Pj+fOiDNrgKtms5Ru0KGaybMs7/l/ZdDm+PZN+5 Bl9eLMBYEfsiBBLu68qfl6JnfM8hr4PcP44K1koOp7eUEpvYw3Ef+uY52nb3MJHn f+TZpKAAi4uuQtHdNpTtcyWG7tyIDcr4gpnGZAgFJYd/WGiW3y0YuvhHYV/Ic5d6 PZqLQsX2PAGvsGgg5ySMHHmNvNi3XbBUPJm7c71NvYLb1j4acGI= =52Or -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 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/bd2a1487-2b77-f22b-2794-959d702f90d3%40SvenSemmler.org. For more options, visit https://groups.google.com/d/optout. Qubes-HCL-LENOVO-20HJS0BX00-20180910-121945.yml Description: application/yaml Qubes-HCL-LENOVO-20HJS0BX00-20180910-121945.yml.sig Description: PGP signature
Re: [qubes-users] Must create HVM if I want to use a unsupported distro as a VM?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 09/10/2018 07:47 AM, unman wrote: > Yes you can create win7 appVMs from a template. Unless you use QWT > to set home directory to /dev/xvdb you will have effectively a > disposableVM, which may throw you to start with. I am using a Win7 HVM as template and have have two AppVMs based on it. Without QWT. You can move the user directory manually in the template VM and then use dd to copy the private section once when creating the AppVM. Steps: - -> In your Windows 7 HVM which will be your template use Disk Manager to format the private partition. By default it usually is 2 GB and unuse d. - -> https://lifehacker.com/5467758/move-the-users-directory-in-windows-7 (use the manual way later in the post!) If your HVM is not already a template use qvm-clone --class TemplateVM Then: - -> https://groups.google.com/d/msg/qubes-users/TJZQbB9CvrU/j6Zu1ZaJCQAJ Obviously try QWT first, if it works for you. Having the shared clipboard and the ability to send/receive files in an AppVM is gold. For me QWT doesn't work yet but there seem to be many who have no issues. The above could be your fallback, in case you have issues like me [1]. /Sven [1] https://github.com/QubesOS/qubes-issues/issues/3585#issuecomment-4107642 31 -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEE18ry22WNibwI1qeq2m4We49UH7YFAluWps8ACgkQ2m4We49U H7aylRAAvxsBhARpwQzJZnPxAqhxV7ISsE9WOJi6RreJoc9mGFw9o98Zi1SilrYf Qh2Y5UMmrHQhQuvGl2+O2IUfNzVuc4DdJ3ZZNARGA4sNDCxvQobDs+jYs7bbLFK9 N50wQCU0uiTtuppc03xRLNQGXtvGo6hpcRynpY7S2ak6Tai1dLkuAdKkSwfBc3zJ WQuyiTbOVyS3uv5llbdmrllurbJhgGkfxJAJ3Zomv2N4B2OumwKeNO99rgBCP5ll igrySVfubozfOd/6YC8Z8Yd7c2JojNBV6Tsmfw0Ut8FAnslUUIa8Qyv0K74gaWS/ S7sKsplQdjLxoJNvoyG6svVex49GsHrOjA3ibbQdyWLxsybkp8d2wvIFeYc0WoCR i2GT1yxVGiQghKW0G6Gz8L4z04e/yrVLN6pFKiwSTn7Cjvxpt3PsFp01LLUPJJEL yYDvh/J3mcrJtdgihnnXUiQRjqQCPwxyVH1FAA1+6NkiRT4BGDrLrWotzisvAG5p p7yZPMRZNy2d/6ssh/Tw8iMY24eVZDrF6Krluxgf8b/3T7oX1ufJOcPI5NhF2v6z N3uXjc1XvuPTxeIrWEo4VWy7NBbH+PLz4PEQMjwJ/8a/sMRGbIgaa0ovNIeCmIdc S9AVBX02t4vvLURbej7Pmrxsh4s60pUgk6n6LTCUnupeCRz12cs= =zSIj -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 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/7b746791-ae68-0852-9b40-6b9fc7f9566e%40SvenSemmler.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Unsupported hardware detected
-d On Mon, 10 Sep 2018 13:16:59 +0200 Marc Ballesteros wrote: > Hello. > I am trying to install qubes os 4 on my computer, but I receive the > "Unsupported hardware detected" message (Missing features: > HVM/VT-x/AMD.V, IOMMU/VT/) > I verified the CPU compatibility with lscpu and I see the VT-x > virtualization system enabled and the ept flag. > It is possible to install Qubes OS 4 on this system? Thanks > > > > Arquitectura:x86_64 > modo(s) de operación de las CPUs:32-bit, 64-bit > Orden de los bytes: Little Endian > CPU(s): 8 > Lista de la(s) CPU(s) en línea: 0-7 > Hilo(s) de procesamiento por núcleo: 2 > Núcleo(s) por «socket»: 4 > «Socket(s)» 1 > Modo(s) NUMA:1 > ID de fabricante:GenuineIntel > Familia de CPU: 6 > Modelo: 60 > Nombre del modelo: Intel(R) Core(TM) i7-4790 CPU @ > 3.60GHz > Revisión:3 > CPU MHz: 3396.892 > CPU MHz máx.:4000, > CPU MHz mín.:800, > BogoMIPS:7195.68 > Virtualización: VT-x > Caché L1d: 32K > Caché L1i: 32K > Caché L2:256K > Caché L3:8192K > CPU(s) del nodo NUMA 0: 0-7 > Indicadores: fpu vme de pse tsc msr pae mce > cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr > sse sse2 ss ht tm pbe > syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts > rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq > dtes64 monitor ds_ cpl vmx > smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic > movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm > cpuid_fault epb inv > pcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept > vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid xsaveopt > dtherm ida arat pln > pts flush_l1d > Hi Marc, Qubes 4 requires VT-d in addition to VT-x. Have a look in the bios setup to see if you can turn it on there. Mike. -- 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/20180910155448.36e0fe75.mike%40keehan.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Must create HVM if I want to use a unsupported distro as a VM?
On Sun, Sep 09, 2018 at 02:12:45PM -0400, Stumpy wrote: > On 09/08/2018 09:09 PM, unman wrote: > > On Sat, Sep 08, 2018 at 10:17:32AM -0400, Stumpy wrote: > > > I want to use a linux distro that currently doesnt seem to have a template > > > for Qubes. Does that if I want to use it I would have to either go the HVM > > > route like for win or create my own template (probably beyond me). > > > > Yes, that's right. Bear in mind that you can use these as templates too. > > > > Thanks Unman > So when you saud "can use these as templates too" you mean that a HVM can be > used as a template? (oh god please say yes!!! if yes then I am assuming I > could make a win7 template and create win7 appvms?) Pleased to say "Yes". Yes you can create win7 appVMs from a template. Unless you use QWT to set home directory to /dev/xvdb you will have effectively a disposableVM, which may throw you to start with. You can have this for any HVM - do full install on to /dev/xvda, and any qubes based on that template will act as disposableVMs. I have BSD netvms set up like this. 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 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/20180910124741.wrdmqgg5gugvqvik%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Unsupported hardware detected
Hello. I am trying to install qubes os 4 on my computer, but I receive the "Unsupported hardware detected" message (Missing features: HVM/VT-x/AMD.V, IOMMU/VT/) I verified the CPU compatibility with lscpu and I see the VT-x virtualization system enabled and the ept flag. It is possible to install Qubes OS 4 on this system? Thanks Arquitectura:x86_64 modo(s) de operación de las CPUs:32-bit, 64-bit Orden de los bytes: Little Endian CPU(s): 8 Lista de la(s) CPU(s) en línea: 0-7 Hilo(s) de procesamiento por núcleo: 2 Núcleo(s) por «socket»: 4 «Socket(s)» 1 Modo(s) NUMA:1 ID de fabricante:GenuineIntel Familia de CPU: 6 Modelo: 60 Nombre del modelo: Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz Revisión:3 CPU MHz: 3396.892 CPU MHz máx.:4000, CPU MHz mín.:800, BogoMIPS:7195.68 Virtualización: VT-x Caché L1d: 32K Caché L1i: 32K Caché L2:256K Caché L3:8192K CPU(s) del nodo NUMA 0: 0-7 Indicadores: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_ cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm cpuid_fault epb inv pcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid xsaveopt dtherm ida arat pln pts flush_l1d -- 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/CAO_Ax70R%2B2LrpmLL%3D3tzShwH_RUNMSEEMP3Pe_krvBQ3EYcj1A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
