Re: [qubes-users] How to use qvm-open-in-vm?
On Sun, May 30, 2021 at 8:13 PM Sven Semmler wrote: > check your /etc/qubes-rpc/policy/qubes.OpenURL > > If you want your example to work add this line before all others: > > $anyvm browser allow > > The first is the source qube ... the one calling qvm-open-in-vm. > The second is the target 'browser' in your example. The third is either > 'deny', 'ask' or 'allow' Thanks a lot! That does exactly what I'm after! Cheers Adam -- 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/CA%2Bmfgz03hU%3D7ngm5Wd1pQ4LYpEnd0Ep2yPcYhkTRypW6Z5pN7w%40mail.gmail.com.
[qubes-users] How to use qvm-open-in-vm?
Hi I'm trying to use qvm-open-in-vm to open a link in the browser of another AppVM, I run the following: $ qvm-open-in-vm browser https://www.google.com where "browser" is the name of the qube AppVM that I want to open the link in, this opens a dialog asking me to select a target domain. It is ignoring the name of the AppVM I specify on the command line. According to the help message for qvm-open-in-vm I should be able to specify the name of the AppVM, but it seems that it's being ignored. What am I doing wrong? Cheers Adam -- 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/CA%2Bmfgz2KUWq0ECfG%3D8m8mBWcCFv1-r1XB0d6ZS88gdk1bfunHA%40mail.gmail.com.
[qubes-users] error updating qubes-template-centos-7
Hi I'm trying to update the centos-7 template, installed from the community templates repo, using the Qubes Update utility and the process is failing with: Updating centos-7 Error on updating centos-7: Command '['sudo', 'qubesctl', '--skip-dom0', '--targets=centos-7', '--show-output', 'state.sls', 'update.qubes-vm']' returned non-zero exit status 20 centos-7: -- _error: Failed to return clean data retcode: 1 stderr: Traceback (most recent call last): File "/var/tmp/.root_dd8a91_salt/salt-call", line 27, in salt_call() File "/var/tmp/.root_dd8a91_salt/pyall/salt/scripts.py", line 437, in salt_call import salt.cli.call File "/var/tmp/.root_dd8a91_salt/pyall/salt/cli/call.py", line 6, in import salt.cli.caller File "/var/tmp/.root_dd8a91_salt/pyall/salt/cli/caller.py", line 14, in import salt.loader File "/var/tmp/.root_dd8a91_salt/pyall/salt/loader.py", line 7, in import contextvars File "/var/tmp/.root_dd8a91_salt/py3/contextvars.py", line 1, in from _contextvars import Context, ContextVar, Token, copy_context ModuleNotFoundError: No module named '_contextvars' stdout: How can I enusre then the template is updated? Cheers Adam -- 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/CA%2Bmfgz0yX5HKJ7qTPYupqUW7pLno1k4azhpV5PUYh2gb--fMLQ%40mail.gmail.com.
[qubes-users] HCL - Dell XPS 15 7590
Dear Qubes Users, Happy to report that after some little manual labour, Dell XPS 15 7590 is working with Qubes OS and Win 10 (dual OS) Things I have done to make it work: - Shrink Win root partition to make some space for Qubes - Burn Qubes 4.0.3 to USB - Disable EFI runtime services completely ( https://www.qubes-os.org/doc/uefi-troubleshooting/#installation-freezes-before-displaying-installer--disable-efi-runtime-services) otherwise we have XEN kernel panic at "ENABLING IO-APIC IRQs, Using old ACK method" - Update BIOS from 1.5 to 1.6 (not sure if needed, probably not) - Switch off the secure boot in BIOS: Secure Boot > Secure Boot Enable - Modify SATA in BIOS: System Configuration > SATA Operation > AHCI - Boot from USB (F12 for the boot menu) - Install Qubes carefully within the empty space, not to damage the Win partitions - Ready any usb wifi dongle, because the wifi does not work (Killer(R) Wi-Fi 6 AX1650x 160MHz Wireless Network Adapter (200NGW)) - Did not check for NVIDIA drivers, not needed for my work For Win 10, I enable secure boot and set SATA to Raid For Qubes, I disable secure boot and set SATA to AHCI With kind regards, Adam -- 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/CAM%3DdSs-uiF_Qdwq7%3DpaVjYM%3Dp-dvYarBBGSYnM_nKCgDhCuaSQ%40mail.gmail.com. Qubes-HCL-Dell_Inc_-XPS_15_7590-20200514-105114.cpio.gz Description: application/gzip Qubes-HCL-Dell_Inc_-XPS_15_7590-20200514-105114.yml Description: application/yaml
[qubes-users] Asus Touchpad - Mouse pointer movement weirdness
Hi all. I posted this HCL, which should help us to answer this particular question as well; https://groups.google.com/forum/#!searchin/qubes-users/HCL$20-$20ASUSTeK_COMPUTER_INC_-GL553VD$2020190519%7Csort:date/qubes-users/QDLjiYT6pEI/COi35_WxAwAJ This machine came to me with Windows 10 on it, which had no issues with the touchpad, suggesting that whatever is going on isn't hardware related. On qubes, however, I've used xev to identify that the touchpad doesn't send pointer movement events (generally speaking), unless I also hold a finger over either the left or right touchpad mouse buttons. If I do place a finger on either button, no matter how light or hard I press, the pointer will move as I like. It will also operate as desired if I place a finger somewhere else on the touchpad, but less reliably than on the buttons. Tap to click (left and right), and multifinger scrolling work perfectly no matter what. Holding the left/right mouse buttons of my external usb device doesn't influence whether it works or not, so perhaps the button press isn't as important as having a larger surface area to complete an electrical circuit? I've also tried using the synaptics driver, but it actually seems less functional than the libinput default. The only exception to the rule is that, rarely, the pointer will catch a movement request and jump before immediately reverting to being nonresponsive. This doesn't seem entirely dependent on "sweet spots" as I originally though, but I still think there is some correlation between it deciding to work and where I try from on the touchpad. All help is appreciated, and if I can provide more information, please just let me know. Much thanks, Adam -- 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/CAD78PXj6FrKb14BXiUtWdH1hsnTazrMMh9jb%3DSbLWzaE3%2BPa9A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] HCL - ASUSTeK_COMPUTER_INC_-GL553VD 20190519
Key changes required to get working were to set the following boot arg for both the installer USB and the live system * efi=no-rs The installer USB also required the nouveau blacklist args: 1. nouveau.modeset=0 2. rd.driver.blacklist=nouveau 3. video=vesa:off The final iso to USB method used was the Fedora Media Writer with Qubes R4.0.1 iso onto an HP 32 GB usb. Many USBs and writing methods were used, but I can't say which would have worked if I'd gotten my boot args right initially. Altering boot args was difficult, since mounting the /dev/sdX2 partition didn't allow direct manipulation of the BOOTX64.cfg file. Upon advisement from #qubes on freenode irc, I copied the file, altered it, and then moved it back in place on the USB partition, which worked well. Post installation, Qubes configuration after initial boot had to be done with TABs, because the mouse did not appear to work properly. After configuration, I found that the touchpad behavior seemed to depend on using a very specific section (top right corner, it seems). USB mouse was a preferred alternative, but it may be true that the initial configuration could have been done with the touchpad mouse if I'd known about the sensitive areas. Without efi=no-rs, post install allowed LUKS decryption before going black and freezing. Thanks to all who helped me figure this out, and hopefully this is sufficient payback for the support I got :), Adam/ilsonno -- 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/CAD78PXg8nokmXP5YQOh-92U-mHqLMJkgrs_6LGwb7Ehh%2BDkqbQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. Qubes-HCL-ASUSTeK_COMPUTER_INC_-GL553VD-20190519-175119.yml Description: application/yaml Qubes-HCL-ASUSTeK_COMPUTER_INC_-GL553VD-20190519-175119.cpio.gz Description: application/gzip
Re: [qubes-users] Qubes R4.0.1 Installer - The name org.freedesktop.UDisk2 was not provided by any .service files
Thanks for the response. Rereading my messages, it's clear that I was lacking some information about what my current state was, so I apologize for that. Issues were primarily occurring during installation from a live usb, before even getting the chance to select a storage device. I've done some screwing around and am working on submitting an HCL now. I did run into post installation issues, but those were due to a typo in my boot args, and correcting nouveau.modeset=0 (was nouveau.nomodeset=0) cleared that bit up for me. Thanks again. On Sat, May 18, 2019 at 7:51 PM awokd wrote: > Adam Lewis: > > Tried using YUMI per a similar Asus HCL report, but that was also > > unsuccessful. Using MBR rather than GPT/UEFI showed a little more info, > > though; > > "Problem description: failed to getinitiator name from iscsi firmware". > > This error can be traced to > > > https://github.com/QubesOS/qubes-installer-qubes-os/commit/3acd47647ee3284df548cc62d79a75e71efdd7e9#diff-dcea6ef93dbd70a795aab33230d481f5R55 > > > > On Fri, May 17, 2019 at 7:43 PM Adam Lewis wrote: > > > >> Manually transcribed errors, so typos are entirely possible. Attempting > to > >> install Qubes R4.0.1 on Asus ROG Strix GL753-RS71 Intel Core i7-7700HQ > >> Geforce GTX 1050 TI. > >> Attempted inst.text in boot args, blacklisting nouveau driver, and > >> commenting out noexitboot=1 and mapbs=1 lines with no changes apparent. > The > >> USB bypasses GRUB entirely and immediately launches anaconda installer, > >> with the following error shown in the Logs tab of anaconda. > > Just a guess, but if you're installing to an NVMe, try setting it to > SATA compatible mode if possible. Could also try installing to an actual > SATA drive of some type. > -- 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/CAD78PXikxi_CbacToEwze3F4nGPDHYWeXe-SFKqCLgw1fbsD%2Bw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes R4.0.1 Installer - The name org.freedesktop.UDisk2 was not provided by any .service files
Tried using YUMI per a similar Asus HCL report, but that was also
unsuccessful. Using MBR rather than GPT/UEFI showed a little more info,
though;
"Problem description: failed to getinitiator name from iscsi firmware".
This error can be traced to
https://github.com/QubesOS/qubes-installer-qubes-os/commit/3acd47647ee3284df548cc62d79a75e71efdd7e9#diff-dcea6ef93dbd70a795aab33230d481f5R55
On Fri, May 17, 2019 at 7:43 PM Adam Lewis wrote:
> Manually transcribed errors, so typos are entirely possible. Attempting to
> install Qubes R4.0.1 on Asus ROG Strix GL753-RS71 Intel Core i7-7700HQ
> Geforce GTX 1050 TI.
> Attempted inst.text in boot args, blacklisting nouveau driver, and
> commenting out noexitboot=1 and mapbs=1 lines with no changes apparent. The
> USB bypasses GRUB entirely and immediately launches anaconda installer,
> with the following error shown in the Logs tab of anaconda.
>
> """"""""""""""""""""""""""""""""
> Traceback
> File "/usr/lib/python3.5/site-packages/blivet/safe_dbus.py" line 147 in
> call_sync
> DEFAULT_DBUS_TIMEOUT, None
> GLib.GError: g-dbus-error-quark:
> GDBus.Error:org.freedesktop.DBus.Error.ServiceUnkown: The name
> org.freedesktop.UDisk2 was not provided by any .service files
> Traceback
> File "/usr/lib/python3.5/site-packages/blivet/iscsi.py" line 159 in
> __init__
> initiatorname =
> self._call_initiator_method("GetFirmwareInitiatorName")[0]
> File "/usr/lib/python3.5/site-packages/blivet/util.py" line 1105 in
> decorated
> if self.check_avail(onetime=just_onetime)
> File "/usr/lib/python3.5/site-packages/blivet/util.py" line 1093 in
> check_avail
> self._avail = self._check_avail()
> File "/usr/lib/python3.5/site-packages/blivet/iscsi.py" line 113 in
> _check_avail
> if not safe_dbus.check_object_available(STORAGED_SERVICE,
> STORAGED_MANAGER_PATH, MANAGER_IFACE)
> File "/usr/lib/python3.5/site-packages/blivet/safe_dbus.py" line 194 in
> check_object_available
> intro_data = call_sync(service, obj_path, DBUS_INTRO_IFACE,
> "Introspect", None)
> File "/usr/lib/python3.5/site-packages/blivet/safe_dbus.py" line 151 in
> call_sync
> raise DBusCallError(msg)
> blivet.safe_dbus.DBusCallError: Failed to call Introspect method on
> /org/freedesktop/UDisk2/Manager with None arguments:
> GDBus.Error:org.freedesktop.DBus.Error.ServiceUnkown: The name
> org.freedesktop.UDisk2 was not provided by any .service files
> """""""""""""""""""""""""""""""""""""
> https://pastebin.com/dAihmU2t
>
> *Attached txt, pastebin link, and above text are all identical.
>
> Much thanks, and please let me know if I can provide any additional
> information that would be useful,
>
> Adam
>
> PS Accidentally posted in qubes-devel initially. Sorry about that.
>
> --
> 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/a63e5379-8e0b-4082-aa63-103e888aa97f%40googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.
>
--
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/CAD78PXjrnGVk_ypaD2QfD7DWC0rKy7NE5a8HjS0iz_-S-Zypxg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
[qubes-users] Qubes R4.0.1 Installer - The name org.freedesktop.UDisk2 was not provided by any .service files
Manually transcribed errors, so typos are entirely possible. Attempting to
install Qubes R4.0.1 on Asus ROG Strix GL753-RS71 Intel Core i7-7700HQ
Geforce GTX 1050 TI.
Attempted inst.text in boot args, blacklisting nouveau driver, and commenting
out noexitboot=1 and mapbs=1 lines with no changes apparent. The USB bypasses
GRUB entirely and immediately launches anaconda installer, with the following
error shown in the Logs tab of anaconda.
""""""""""""""""""""""""""""""""
Traceback
File "/usr/lib/python3.5/site-packages/blivet/safe_dbus.py" line 147 in
call_sync
DEFAULT_DBUS_TIMEOUT, None
GLib.GError: g-dbus-error-quark:
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnkown: The name
org.freedesktop.UDisk2 was not provided by any .service files
Traceback
File "/usr/lib/python3.5/site-packages/blivet/iscsi.py" line 159 in __init__
initiatorname = self._call_initiator_method("GetFirmwareInitiatorName")[0]
File "/usr/lib/python3.5/site-packages/blivet/util.py" line 1105 in decorated
if self.check_avail(onetime=just_onetime)
File "/usr/lib/python3.5/site-packages/blivet/util.py" line 1093 in
check_avail
self._avail = self._check_avail()
File "/usr/lib/python3.5/site-packages/blivet/iscsi.py" line 113 in
_check_avail
if not safe_dbus.check_object_available(STORAGED_SERVICE,
STORAGED_MANAGER_PATH, MANAGER_IFACE)
File "/usr/lib/python3.5/site-packages/blivet/safe_dbus.py" line 194 in
check_object_available
intro_data = call_sync(service, obj_path, DBUS_INTRO_IFACE, "Introspect",
None)
File "/usr/lib/python3.5/site-packages/blivet/safe_dbus.py" line 151 in
call_sync
raise DBusCallError(msg)
blivet.safe_dbus.DBusCallError: Failed to call Introspect method on
/org/freedesktop/UDisk2/Manager with None arguments:
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnkown: The name
org.freedesktop.UDisk2 was not provided by any .service files
"""""""""""""""""""""""""""""""""""""
https://pastebin.com/dAihmU2t
*Attached txt, pastebin link, and above text are all identical.
Much thanks, and please let me know if I can provide any additional information
that would be useful,
Adam
PS Accidentally posted in qubes-devel initially. Sorry about that.
--
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/a63e5379-8e0b-4082-aa63-103e888aa97f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Traceback
File "/usr/lib/python3.5/site-packages/blivet/safe_dbus.py" line 147 in
call_sync
DEFAULT_DBUS_TIMEOUT, None
GLib.GError: g-dbus-error-quark:
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnkown: The name
org.freedesktop.UDisk2 was not provided by any .service files
Traceback
File "/usr/lib/python3.5/site-packages/blivet/iscsi.py" line 159 in __init__
initiatorname = self._call_initiator_method("GetFirmwareInitiatorName")[0]
File "/usr/lib/python3.5/site-packages/blivet/util.py" line 1105 in decorated
if self.check_avail(onetime=just_onetime)
File "/usr/lib/python3.5/site-packages/blivet/util.py" line 1093 in
check_avail
self._avail = self._check_avail()
File "/usr/lib/python3.5/site-packages/blivet/iscsi.py" line 113 in
_check_avail
if not safe_dbus.check_object_available(STORAGED_SERVICE,
STORAGED_MANAGER_PATH, MANAGER_IFACE)
File "/usr/lib/python3.5/site-packages/blivet/safe_dbus.py" line 194 in
check_object_available
intro_data = call_sync(service, obj_path, DBUS_INTRO_IFACE, "Introspect",
None)
File "/usr/lib/python3.5/site-packages/blivet/safe_dbus.py" line 151 in
call_sync
raise DBusCallError(msg)
blivet.safe_dbus.DBusCallError: Failed to call Introspect method on
/org/freedesktop/UDisk2/Manager with None arguments:
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnkown: The name
org.freedesktop.UDisk2 was not provided by any .service files
Re: [qubes-users] Realtek wifi adapter rtl8821ce
Hello Jayen, I have realtek wifi adapter in my lenovo laptop ideapad 330 15arr model. It > is not recognised by sys-net VM. I have a similar laptop to you (Ideapad 330S-15ARR). I was not able to compile the kernel module when using the Qubes provided virtual machine kernel. I switched sys-net to use the stock Fedora 29 kernel and I was able to install the driver successfully. Aside from that, the only other thing I had to do was manually run the command to upgrade grub when there is a kernel update in the template VM and I want to boot from it. Thanks, -Adam -- 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/CANh5szqy2SmuWeSQ3dKO9YXWcfpDxKeDssS6Frzo1yiZ07hnPA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] qubes-update-gui always has "updates available for 1 qubes"
> > Is there any way to see what qubes the qubes-update-gui tool thinks there > are updates for. Ever since installing Qubes 4.0 the gui has been telling > me there is "updates available for 1 qubes" even when the gui shows there > is not^1.Even manually selecting all listed quebes and running an > update on them all does not get rid of this notice. > > Is there somewhere on the command line I can look to see what > qubes-update-gui tool things needs updating and more importantly, clear it > :-) > I've seen the same behavior, I believe it is this bug - https://github.com/QubesOS/qubes-issues/issues/4667 >From looking at https://github.com/QubesOS/updates-status/issues/879 it appears that an update for this was posted to the stable repository a few hours ago. I haven't had a chance to try it myself though. -Adam -- 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/CANh5szqqEz3rbacaa%2B0QNmyUzkSbErgjHEJCy7cAjH%2BxKuuBwQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: QSB #43: L1 Terminal Fault speculative side channel (XSA-273)
> > Is this something that can eventually be resolved, allowing safe > re-enabling of hyperthreading? or is that even known yet? > I haven't been able to find many details on this for the Linux and Xen communities. Microsoft has a mitigation that allows for HyperThreading to remain enabled with Hyper-V which they have named HyperClear <https://blogs.technet.microsoft.com/virtualization/2018/08/14/hyper-v-hyperclear/>. Additionally, I know VMware recommends leaving HyperThreading enabled in the BIOS so that if a safe way to utilize HyperThreading on ESXi is implemented in the future you don't have to reconfigure your BIOS again. Thanks, Adam Robinson Virtualization and Cloud Infrastructure Information and Technology Services University of Michigan -- 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/CANh5szoXzEAajc8bmsPbGDapA49FY8Tto3_7bHV-O7ntO0ngHw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] High spec laptop for Qubes OS
Hello, I currently run Qubes OS on an XPS 13 from 2015 with an i5-6200U, 8GB RAM, slow NVMe. It can't really handle Qubes OS - it's quite laggy and struggles to play video on the 4K screen. The CPU and RAM are normally maxed with a couple of VMs running, even without video. I'm going to buy a new laptop with a higher spec which should hopefully handle things well. The following laptops are my final five contenders. They all have a discrete GPU, which I'm hoping to passthrough to a VM for playing streaming video (h264/h265/vp9 codecs). Do I have this right that it would be most efficient to use the Intel GPU in dom0 and the discrete GPU in the VM? I also do a lot of scientific computing, so it's useful to offload some computation to a GPU via CUDA. I get the impression from the HCL that they should all work fine as long as I replace any non-Intel wifi m.2 sticks with an Intel 8265. Do you have any thoughts on whether one would be more appropriate than another? Dell XPS 15 9560 (2017) Intel i7-7700HQ Quad Core 32GB RAM 512GB M.2 NVMe Intel + NVIDIA GTX 1050 Dell XPS 15 2018 Intel i7-8705G Quad Core 32GB RAM 512GB M.2 NVMe Intel + Radeon RX Vega M GL Dell Precision 5520 Intel Xeon E3-1505M v6 Quad Core 32GB RAM 512GB M.2 NVMe Intel + Nvidia Quadro M1200 Lenovo P51 Intel Xeon E3-1505M v6 Quad Core 32GB RAM 512GB M.2 NVMe Intel + NVIDIA Quadro M2200 Razer Blade Intel i7-7700HQ Quad Core 16GB RAM 512GB M.2 NVMe Intel + NVIDIA GTX 1060 Thanks, Adam -- 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/c5f7945f35c4bfe9cd47bc70ddd794f4%40adammccarthy.co.uk. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Qubes Network Setup Service
On Saturday, 16 July 2016 17:40:20 UTC+8, Adam wrote: > Does anyone actually have any ideas about my original post? > > Cheers > Adam to add some more debugging info, the windows event logger keeps showing this error Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected. -- 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/37c89884-d31b-4e3b-a963-3b06f5d4c6e1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Qubes Network Setup Service
Does anyone actually have any ideas about my original post? Cheers Adam -- 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/e7024f22-5e54-42ad-82f2-1ea3fe0fc33d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Qubes Network Setup Service
Hi Alex and Drew I understand the global view of networking in QubesOS, I have a net VM, a firewall VM, a proxy VM and a standard app VM all working nicely and my app VM can surf the web securely. I never said dom0 and win7 communicated via network, had had assumed, maybe incorrectly, that dom0 via Qubes db or something to each VM what it's IP address is and scripts inside the VM set the ip correctly. I know my problem is Qubes Network Setup service in side my windows HVM failing to start, and it won't start when I manually try to start it from the services app. I don't want to just assign the Nic an IP as that's not what's suppose to happen, I want to figure out what's going on, so I can tell others what went wrong, why it went wrong and how to fix it! Has anyone had a problem with "Qubes Network Setup" service failing to start? (please note this is a Windows application(service) Cheers Adam -- 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/a65836b4-36d3-4094-987b-e2b75d69ffa1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Qubes Network Setup Service
On Thursday, July 14, 2016 at 8:24:41 PM UTC+8, Drew White wrote: > On Thursday, 14 July 2016 22:09:21 UTC+10, Adam wrote: > > Hi > > > > I have successfully install Qubes 3.2-r1 on a lenovo x220 > > I have player around with templates and AppVMs and thought i would try > > Windows 7. > > > > I successfully install windows in a HVM Template and then installled Qubes > > Windows Tools which again appears to be successful. I am don't get any > > networking as Qubes Network Setup Fails to start. I am a Xen PV Netowrk > > adapter as installed by QWT. > > > > This networking issue is usual. > > It doesn't set the networking adaptor properly during initialisation. > > Check the settings. > then set the DNS server to something. > Google DNS A is 8.8.8.8 > > Then you should have an internet conection. > Or else, if that doesn't solve it, it could be the Gateway, so just set all > settings manually. > > Then it should work. I don't even get a ip so assigning a new dns server won't help. I think its a communication problem between windows and dom0, but i don't know enough to diagnose it 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 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/e4fee04b-75ab-4da5-a2b6-f36d4c465bb0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Qubes Network Setup Service
Hi I have successfully install Qubes 3.2-r1 on a lenovo x220 I have player around with templates and AppVMs and thought i would try Windows 7. I successfully install windows in a HVM Template and then installled Qubes Windows Tools which again appears to be successful. I am don't get any networking as Qubes Network Setup Fails to start. I am a Xen PV Netowrk adapter as installed by QWT. I am not sure where to start debugging this, i ran my windows HVM Tempate (win7) in debug mode and checked the logs /var/log/xen/console/guest-win7.log --> empty /var/log/xen/xonsole/guest-win7-dm.log - lots of output but the following line standsout XENNET|AdapterSetInformation: UNSUPPORTED OID 00010118 /var/log/qubes/guid.win7.log /var/log/qubes/qrexec.win7.log both don't show anything that stands out. inside win7 qga.log [20160714.103340.752-1900-E] QpsConnect: open read pipe failed with error 2: The system cannot find the file specified. [20160714.103340.752-1900-E] connect_to_daemon: connect to server failed with error 2: The system cannot find the file specified. [20160714.103340.752-1900-E] GetDomainName: qdb_open failed with error 2: The system cannot find the file specified. [20160714.103340.752-1900-W] Init: Failed to read domain name, using host name [20160714.103340.814-1900-W] VchanReceiveBuffer: (004A3B90, msg_xconf): no data, blocking read [20160714.103342.357-1900-W] HandleServerData: got unknown msg type 127, ignoring [20160714.103408.971-1900-W] VchanReceiveBuffer: (004A3B90, msg_motion): no data, blocking read [20160714.103422.933-1900-W] HandleButton: unknown button pressed/released 0x7 [20160714.103422.933-1900-W] HandleButton: unknown button pressed/released 0x7 [20160714.103424.664-1900-W] HandleButton: unknown button pressed/released 0x6 [20160714.103424.664-1900-W] HandleButton: unknown button pressed/released 0x6 [20160714.103424.883-1900-W] HandleButton: unknown button pressed/released 0x6 [20160714.103424.883-1900-W] HandleButton: unknown button pressed/released 0x6 [20160714.103426.115-1900-W] HandleButton: unknown button pressed/released 0x7 [20160714.103426.131-1900-W] HandleButton: unknown button pressed/released 0x7 [20160714.103426.568-1900-W] HandleButton: unknown button pressed/released 0x7 [20160714.103426.568-1900-W] HandleButton: unknown button pressed/released 0x7 [20160714.103426.677-1900-W] HandleButton: unknown button pressed/released 0x7 [20160714.103426.677-1900-W] HandleButton: unknown button pressed/released 0x7 [20160714.103427.098-1900-W] HandleButton: unknown button pressed/released 0x7 [20160714.103427.114-1900-W] HandleButton: unknown button pressed/released 0x7 [20160714.103435.522-1900-W] VchanReceiveBuffer: (004A3B90, msg_motion): no data, blocking read Not sure what to do now Cheers Adam -- 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/d3123ca6-2c74-472b-97d6-27df814f2117%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Fedora Minimal Template
On Tue, Jul 12, 2016 at 10:35 AM, Andrew David Wong <a...@qubes-os.org> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > On 2016-07-11 19:17, Adam Steen wrote: > > Edit: Include mailing list. > > > > Hi Andrew > > > > Thank you for all the hard work you put into the project, you seem to > have > > the patients of a saint, sometimes dealing with people is the hardest > > part! > > > > You're too kind. :) > > > yes, that is the command i issued. > > > > I get an error "Could not resolve host: mirror.switch.ch" after the > error > > i get the following > > > > Trying other mirror. No Match for argument > > qubes-template-fedora-23-minimal Nothing to download > > > > Cheers Adam > > > > Are you on R3.1 or R3.2-rc1? It looks like there's no fedora-minimal > template > available yet for R3.2-rc1: > > http://yum.qubes-os.org/r3.2/templates-itl/rpm/ > > But it's still available for R3.1: > > http://yum.qubes-os.org/r3.1/templates-itl/rpm/ > > > (P.S. - Please try to avoid top posting.) > I am using R3.2-rc1, that explains why it there is no match. is there instructions on building the minimal template? something similar to https://www.qubes-os.org/doc/templates/archlinux/? I might be able to work something out anyways, using that document as a loose guide. -- 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/CAH%3DSx985FjdtCSaX53vf%2BQe8R%2BFA3VTydQwBgu-qEScmEUGJbQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
