Re: [qubes-users] Re: New Install is Missing sys-USB, How to recover - Update
Ray Joseph: > I opened sys-usb settings and found the controller listed in the settings > pane (on the right). The control button/bar at the bottom entitled > "Configure strict reset for PCI devices". I clicked on the controller in > the ‘selected’ window, then clicked the strict reset button. The > controller was then highlighted. After applying the changes, I restarted > sys-usb. It worked. > > > > It was unclear that the controller did not already have the strict reset > button ‘on’. > > The newly built vm uses the usb mouse. > > It is curious that the mouse is also active in dom0. Great! I suggest changing sys-usb back to HVM. PV is not as secure. > I am using a windows laptop to take notes and work the web including this > session. While the mouse works on dom0 on the other machine and the vm, it > does not work on the windows machine (probably because it is not plugged > into it). I am excited to learn how to work in qubes – being able to jump > from dom0 to vms, take notes, post messages, email smoothly. Qubes uses the mouse in sys-usb for all VMs. This should include a Windows VM as well, but I am not following from the above if that is what you are trying to do. -- 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/6e450e25-8fb3-b707-4531-53276d995d1a%40danwin1210.me.
Re: [qubes-users] Re: New Install is Missing sys-USB, How to recover - Update
On Saturday, December 14, 2019 at 12:29:03 PM UTC-6, awokd wrote: > > r...@aarden.me : > > > It has taken four years to get to here. I have tried this with Debian > and > > Qube OS. I could not get Xen on Debian to work due to my wireless only > > networking of my laptop. With Qubes, it has been getting wireless and > USB > > to both work. This time, wireless worked maybe. > > > > There is a sys-USB qube. This will be my next challenge. I want to be > > able to use a mouse and, as this is a laptop, and I would like to > connect > > to my USB3 docking station and test out the functionality. > > Mouse shouldn't be too hard, but some USB controllers don't like running > inside a qube. To see the log, you need to be in su mode in a dom0 > session, so "sudo nano /var/log/libvirt/libxl/libxl-driver.log" should > work. Check it shortly after attempting to start sys-usb if it is > failing to start. > > -- > - don't top post > Mailing list etiquette: > - trim quoted reply to only relevant portions > - when possible, copy and paste text instead of screenshots > On Saturday, December 14, 2019 at 12:29:03 PM UTC-6, awokd wrote: > > r...@aarden.me : > > > It has taken four years to get to here. I have tried this with Debian > and > > Qube OS. I could not get Xen on Debian to work due to my wireless only > > networking of my laptop. With Qubes, it has been getting wireless and > USB > > to both work. This time, wireless worked maybe. > > > > There is a sys-USB qube. This will be my next challenge. I want to be > > able to use a mouse and, as this is a laptop, and I would like to > connect > > to my USB3 docking station and test out the functionality. > > Mouse shouldn't be too hard, but some USB controllers don't like running > inside a qube. To see the log, you need to be in su mode in a dom0 > session, so "sudo nano /var/log/libvirt/libxl/libxl-driver.log" should > work. Check it shortly after attempting to start sys-usb if it is > failing to start. > > Thank you for the info. The sys-usb showed up in the qube manager. Clicking start on the start/resart context menu initiated start up. An error window popped up pointing to the log file you indicate, libxl-driver.log. The log reported: 1. …libxl__device_pci_reset: The kernel doesn’t support reset from sysfs for PCI device :00:14.0 2. …libxl__xenstor_child_wait_deprecated: Device Model not ready 3. ,,,qemu_pci_add_xenstore: qemu refuse to add device: :00:14.0, mistranslate=0,power_mgmt=0: 4. …libxl__add_pcidevs: libxl_device_pci_failed: -3 5. …domcreate_attach_devices: unable to add pci devices 6. …libxl__device_pci_reset: The kernel doesn’t support reset from sysfs for PCI device :00:14.0 --- [Dom0] Settings: sys-usb “PVH mode is recommended if possible (Linux kernel 4.11 or newer, no PCI passthrough). For Windows qubes always use HVM” Virtualization Mode: HVM “PVH mode is hidden since it doesn’t support PCI passthrough.” --- I changed the setting to PV (the only choice). A note opened stating “Using PV mode exposes ore hypervisor attack surface.” I selected start from the qube manager sys-usb item. A note popped up stating it started, then the same error message was reported. Note: I previously selected both USB controllers in sys-usb Devices. On removing the erroring controller (14.0): Resulted in the same error. On removing the other controller (no controllers selected): Resulted in “Resource temporarily unavailable”. On adding the alternate controller: 1. …xc_assign_device failed: Operation not permitted 2. …libxl__add_pcidevs: libxl_device_pci_failed: -3 3. …domcreate_attach_devices: unable to add pci devices Next: From: https://groups.google.com/forum/#!topic/qubes-users/wdfpne96xhI To be sure I went into Qube Manager, sys-usb->Qubes Setting->Devices and used the "Configure strict reset for PCI devices" button to set it on 00:14.0. I opened sys-usb settings and found the controller listed in the settings pane (on the right). The control button/bar at the bottom entitled "Configure strict reset for PCI devices". I clicked on the controller in the ‘selected’ window, then clicked the strict reset button. The controller was then highlighted. After applying the changes, I restarted sys-usb. It worked. It was unclear that the controller did not already have the strict reset button ‘on’. The newly built vm uses the usb mouse. It is curious that the mouse is also active in dom0. I am using a windows laptop to take notes and work the web including this session. While the mouse works on dom0 on the other machine and the vm, it does not work on the windows machine (probably because it is not plugged into it). I am excited to learn how to work in qubes – being able to jump from dom0 to vms, take notes, post messages, email smoothly. It is
Re: [qubes-users] Re: New Install is Missing sys-USB, How to recover - Update
r...@aarden.me: > It has taken four years to get to here. I have tried this with Debian and > Qube OS. I could not get Xen on Debian to work due to my wireless only > networking of my laptop. With Qubes, it has been getting wireless and USB > to both work. This time, wireless worked maybe. > > There is a sys-USB qube. This will be my next challenge. I want to be > able to use a mouse and, as this is a laptop, and I would like to connect > to my USB3 docking station and test out the functionality. Mouse shouldn't be too hard, but some USB controllers don't like running inside a qube. To see the log, you need to be in su mode in a dom0 session, so "sudo nano /var/log/libvirt/libxl/libxl-driver.log" should work. Check it shortly after attempting to start sys-usb if it is failing to start. -- - 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/800374d2-f11e-1bf4-758b-8fc4c8c4c8ac%40danwin1210.me.
Re: [qubes-users] Re: New Install is Missing sys-USB, How to recover - Update
> > These are notes on the solution path used. rc2 was tried one day, rc3 the > next. 20191212 Qubes OS R4.02-rc2-86_64 I would like to have network connection and USB support. On installation to a Toshiba laptop and booting up the first time, I was able to use a USB mouse and selected the enable system and template updates over the Tor anonymity network using Whonix and the combined net and usb qube option. The system rebooted. It reported: (Dom0) Error starting Qube! Start failed: internal error: Unable to reset PCI device .00:14: internal error: libxenlight failed to create new domain /sys-net', see /var/log/libvirt/libxl/libxl-driver.log. When attempting to read the log, permission denied was returned. The USB mouse did not work. I would expect to see sys-net to connect, USB mouse to work, and be able to view the referenced file. The first two failed and when attempting to view the referenced file with cat, the system reported permission denied. I can cd to 'var', then 'log', but when cd to libvirt, I get a permission denied. How might I go about resolving the sysnet/usb issue and how might I access the referenced file? I attempted to start sys-net from the qube manager but the computer rebooted. 20191213 Used Rufus 3.4 to write Qubes-R4.0.2-rc3-x86_64.iso the 32GB stick as a DD. Installed Qubes OS without Using sys-net for both networking and USB. System rebooted Saw Debian loading, Qubes configuration, setting up networking ... Screen went black, after touching touch pad: [Dom0] error ['systemctl', 'start', 'qubes-vm@sys-usb.service'] failed: stdout:"" stderr:"Job for qubes-vm@sys-usb.service failed because the control process exited with error code. See 'systemctl status qubes-vm@sys-usb.service' and "journalctl -xe" for details. OK Then the initial setup page started stated System Qubes os Clicking on "Qubes OS" openned up the page that provides for a repeated selection opportunity setups such as 'Create default system qubes, Creat defau...Use sys-net qube for both networking and USB devices. I did not change any (left sys-net for USB unchecked). I selected 'Done' It started Qubes OS Setup again. New error message: [Dom0] Error ['/usr/bin/qvm-start-firewall] failed: stdout:"" stderr: "domain sys-firewall is already running" OK I repeated the click on Qubes OS and the configuration started again. The previous error repeated. Rather than clicking on Qubes OS, I clicked on Finish Configuration. A sign-on screen came up. I successfully logged in. As this is a 4K display, the font is very small so I openned System tools|display and an icon came up on the desktop (usually, it just opens the tool). When I clicked the icon, a warning came up as Dom0 Untrusted application launcher stating the executable not in the right location and stated to open it if I trusted it. I clicked on it and a second pop up opened stating the launch failed, something about a wrong location. So I closed these to start again from the menu. This time it worked (I can read the display much better at lower resolution). I removed the icon from the desktop. Qube Manager shows sys-firewall and sys-net running. A red icon in the upper right corner displays no network connected. Clicking on the red icon produced a menu to select Ethernet or wireless with an ID of my hotspot. After finally entering the correct password, it stated a connection was made. I started a fedora firefox and was able to browse. It has taken four years to get to here. I have tried this with Debian and Qube OS. I could not get Xen on Debian to work due to my wireless only networking of my laptop. With Qubes, it has been getting wireless and USB to both work. This time, wireless worked maybe. There is a sys-USB qube. This will be my next challenge. I want to be able to use a mouse and, as this is a laptop, and I would like to connect to my USB3 docking station and test out the functionality. I appreciate the help from everyone here in helping me learn. -- 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/9beab449-0f39-45de-b9c3-98a9c9f5a7b1%40googlegroups.com.
Re: [qubes-users] Re: New Install is Missing sys-USB, How to recover
Ray Joseph: I very much appreciate all the input. The keyboard is a PS/2. I am in question. We are talking about creating a new AppVM for usb. Is this any different than running: qubesctl state.sls qvm.sys-usb Only other thing that does is add rd.qubes.hide_all_usb to your Linux boot options line, if it's not already there. After entering the above command for usb, the output addressed sys-net: Comment: The following requisition were not found: require: sls: qvm.sys-net Take a look at the file Unman mentioned; might explain why it's doing 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/4d9e785d-f654-e373-9e34-5ec5939121c2%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: New Install is Missing sys-USB, How to recover
I very much appreciate all the input. The keyboard is a PS/2. I am in question. We are talking about creating a new AppVM for usb. Is this any different than running: qubesctl state.sls qvm.sys-usb After entering the above command for usb, the output addressed sys-net: Comment: The following requisition were not found: require: sls: qvm.sys-net -- 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/439addea-31f8-4ecf-b9a0-af11c971e1b2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: New Install is Missing sys-USB, How to recover
unman: Not quite as simple as that. sys-usb is created with label red, mem 300, and virt-mode hvm. Also autostart is True, and pci_strictreset is false. You also need to disable memory balancing. However, only that and HVM mode are required in the VM config to support a sys-usb, and both are mentioned in the configuration when you add a PCI device. Pci_strictreset varies by USB controller, although the majority do need it. -- 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/c4105db2-4bac-b8ba-ec47-8f9cf8605daa%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: New Install is Missing sys-USB, How to recover
On Thu, May 02, 2019 at 11:40:48PM +, 'awokd' via qubes-users wrote: > Ray Joseph wrote on 4/28/19 5:21 AM: > > > > jrsm, > > > > Thank you, that was a lot of info. This took me to here: > > https://www.qubes-os.org/doc/usb-qubes/ > > > > From which as root, I executed: > > qubesctl state.sls qvm.sys-usb > > > > 4 succeeded and 1 failed. > > > > In sequence: > > ID: hide-usb-from-dom0-legacy > > Function: file.append > > Name: /etc/default/grub > > ... This one succeeded > > > > ID: grub2-mkconfig -o /boot/grub2/grub.cfg > > Function: cmd.run > > Result: True > > Comment: State was not run because none of the onchanges reqs changed > > Changes: > > ... This one succeeded > > > > ID: sys-net-usb > > Function: qvm.prefs > > Name: sys-net > > Result: False > > Comment: The following requisition were not found: > >require: > >sls: qvm.sys-net > > Changes: > > ... This one failed > > > > Then there were two other successes for: > > ID: qubes-input-proxy > > ID: sys-usb-input-proxy > > > > That was the complete emission. I guess the failure signal was the > > 'Result: False" and all the text was in red. > > > > I have checked the terms in the emission but was not able to find anything > > that looked relevant. > > > > It is not clear why sys-net was addressed in the usb process. But I do > > recall that a usb controller was installed in the sys-net but no wifi. > > While I have read some about the possibility of using sys-net for usb > > functions, I don't recall any reference to the installation doing that. > > > > Any suggestions? > > If you aren't using a USB keyboard, creating your own sys-usb is simple. > Create an AppVM, disable networking on it, and assign your USB controllers > to it. If you are using a USB keyboard, refer to that same document. It can > be tricky. > Not quite as simple as that. sys-usb is created with label red, mem 300, and virt-mode hvm. Also autostart is True, and pci_strictreset is false. Ray - if you look in /srv/formulas.base/virtual-machines-formula/qvm you will find the salt file sys-usb.sls. That is what is run when you execute the qubesctl command, and you'll see there the reference to sys-net. -- 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/20190503005330.wo2pcb2eydjfhqx2%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: New Install is Missing sys-USB, How to recover
Ray Joseph wrote on 4/28/19 5:21 AM: jrsm, Thank you, that was a lot of info. This took me to here: https://www.qubes-os.org/doc/usb-qubes/ From which as root, I executed: qubesctl state.sls qvm.sys-usb 4 succeeded and 1 failed. In sequence: ID: hide-usb-from-dom0-legacy Function: file.append Name: /etc/default/grub ... This one succeeded ID: grub2-mkconfig -o /boot/grub2/grub.cfg Function: cmd.run Result: True Comment: State was not run because none of the onchanges reqs changed Changes: ... This one succeeded ID: sys-net-usb Function: qvm.prefs Name: sys-net Result: False Comment: The following requisition were not found: require: sls: qvm.sys-net Changes: ... This one failed Then there were two other successes for: ID: qubes-input-proxy ID: sys-usb-input-proxy That was the complete emission. I guess the failure signal was the 'Result: False" and all the text was in red. I have checked the terms in the emission but was not able to find anything that looked relevant. It is not clear why sys-net was addressed in the usb process. But I do recall that a usb controller was installed in the sys-net but no wifi. While I have read some about the possibility of using sys-net for usb functions, I don't recall any reference to the installation doing that. Any suggestions? If you aren't using a USB keyboard, creating your own sys-usb is simple. Create an AppVM, disable networking, and assign your USB controllers to it. If you are using a USB keyboard, refer to that same document. It can be tricky. -- 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/618b2ac0-9cd4-3c56-c74f-e61dbfe5d6a0%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: New Install is Missing sys-USB, How to recover
Ray Joseph wrote on 4/28/19 5:21 AM: jrsm, Thank you, that was a lot of info. This took me to here: https://www.qubes-os.org/doc/usb-qubes/ From which as root, I executed: qubesctl state.sls qvm.sys-usb 4 succeeded and 1 failed. In sequence: ID: hide-usb-from-dom0-legacy Function: file.append Name: /etc/default/grub ... This one succeeded ID: grub2-mkconfig -o /boot/grub2/grub.cfg Function: cmd.run Result: True Comment: State was not run because none of the onchanges reqs changed Changes: ... This one succeeded ID: sys-net-usb Function: qvm.prefs Name: sys-net Result: False Comment: The following requisition were not found: require: sls: qvm.sys-net Changes: ... This one failed Then there were two other successes for: ID: qubes-input-proxy ID: sys-usb-input-proxy That was the complete emission. I guess the failure signal was the 'Result: False" and all the text was in red. I have checked the terms in the emission but was not able to find anything that looked relevant. It is not clear why sys-net was addressed in the usb process. But I do recall that a usb controller was installed in the sys-net but no wifi. While I have read some about the possibility of using sys-net for usb functions, I don't recall any reference to the installation doing that. Any suggestions? If you aren't using a USB keyboard, creating your own sys-usb is simple. Create an AppVM, disable networking on it, and assign your USB controllers to it. If you are using a USB keyboard, refer to that same document. It can be tricky. -- 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/9ac4e1a9-cdaa-f556-cc38-64e91040cb87%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: New Install is Missing sys-USB, How to recover
jrsm, Thank you, that was a lot of info. This took me to here: https://www.qubes-os.org/doc/usb-qubes/ >From which as root, I executed: qubesctl state.sls qvm.sys-usb 4 succeeded and 1 failed. In sequence: ID: hide-usb-from-dom0-legacy Function: file.append Name: /etc/default/grub ... This one succeeded ID: grub2-mkconfig -o /boot/grub2/grub.cfg Function: cmd.run Result: True Comment: State was not run because none of the onchanges reqs changed Changes: ... This one succeeded ID: sys-net-usb Function: qvm.prefs Name: sys-net Result: False Comment: The following requisition were not found: require: sls: qvm.sys-net Changes: ... This one failed Then there were two other successes for: ID: qubes-input-proxy ID: sys-usb-input-proxy That was the complete emission. I guess the failure signal was the 'Result: False" and all the text was in red. I have checked the terms in the emission but was not able to find anything that looked relevant. It is not clear why sys-net was addressed in the usb process. But I do recall that a usb controller was installed in the sys-net but no wifi. While I have read some about the possibility of using sys-net for usb functions, I don't recall any reference to the installation doing that. Any suggestions? -- 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/99ab8587-2135-4822-8dbc-4910d236fad5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
