[qubes-users] Create windows DispVM
Has anyone successfully created windows DispVM. I have a windows Install I'd like to make as a disposable template to open word documents if possible. Can you provide commands necessary to create the windows DispVM? -- 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/3ccedfb4-fe0a-404f-baf8-3e3739af338c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Open word document in DispVM via cmd.exe
I'm trying using windows command to open a word document in another vm or DispVM. I understand this is handled with open-in-vm.exe and I think qrexec_client_vm.exe is used to pass the commands to open-in-vm.exe. I'm wondering if this is possible or if anyone has done this. Can you provide an example command? -- 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/11d0e6c4-aa85-4b85-ae23-f4a01990cacf%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Boot / Installer Problem
Secureboot is disabled. As recommended in many forum entries on installing other Linux variants on this very device, network boot is also enabled (despite not booting from the network) - if not, it does not work either. However, UEFI is fixed as the only option available. As best as I understand, the device does not have Legacy BIOS boot anymore. Is there anything else worth trying? -- 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/376fff2c-3937-401c-af34-c6b5fc87fb80%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Loaded Kali in HVM- but it wont boot. should be a simple fix for someone with experience of Qubes.
On 8.5.19. 16:05, ajwwoodw...@gmail.com wrote: > On Wednesday, May 8, 2019 at 1:52:02 PM UTC, ajwwo...@gmail.com wrote: >> I have installed Kali as HVM standalone VM, but when the installation >> shutdown at the end and i restart the VM I get the following boot message. >> >> >> Seabios (version rel 1.11.2-0-gf9626cc prebuilt.qmeu-project.org) >> >> Machine UUID >> >> Booting from Hard Disk >> >> Boot failed; not bootable disk >> >> Booting from floppy >> >> Boot failed: could not read the boot disk >> >> >> No bootable device. >> >> I installed my iso image on a device vxdb in install and then took the >> option to install the grub boot loader on the same device in the >> installation. >> >> >> Is SEABIOS a virtual bios in QUBES and do i need to edit it? I'm not running >> coreboot on my lenovno t530. >> >> >> Some points of note on the various Kali installs i did; >> >> I could reach a time server, so the netowork routes were working. >> >> I could never attach to a mirror and proceeded with just the ISO image >> >> >> Any further advice would really help as it feels like I'm really close to >> this working now. > Update: I have tried the Katoolin approach that did not work either, so > please if someone, know how to this simple problem for hte ISO approach then > I will be ok. Ah really? Ok qubes 4 I suppose? I haven't tried that since 3. What didn't work? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To 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/72a9a6be-572e-58aa-5d9a-70e5a79686e3%40blunix.org. For more options, visit https://groups.google.com/d/optout. signature.asc Description: OpenPGP digital signature
[qubes-users] nvme0n1 may not have enough space for grub2 to embed core.img when using the ext4 file system on lvm
Hello, I got this problem when trying to install R4.0.1 on my Lenovo Thinkpad P7. It has 2 HDs of which the second contains an original Windows 10 install for which I can choose the boot loader if I want to run it. On the first HD I have the following partitioning scheme in Anaconda: Qubes Linux 4.0.1 for x86_64 System 920 GiB, device type: LVM encrypt, vol group: qubes_dom0, /file system: Ext4, Name: root qubes_dom)-root /boot/efi 100 MiB, device type: Standard partition, nvme0n1p3 file system: EFI System Partition, Name: nvme0n1p3 swap 30 GiB, device type: LVM encrypt, vol group: qubes_dom0 file system: swap, Name: 00 Unknown Unknown 128 MiB, nvme0n1p1 EFI Sys part200 MiB nvme0n1p2 I guess these Unknown and EFI Sys Partition are there to have some boot loader for Windows. Now when I accept these settings, I get the warning: "nvme0n1 may not have enough space for grub2 to embed core.img when using the ext4 file system on lvmlv" Does anyone know how to solve this problem? BIOS is set to 'Legacy'. -- 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/bfc80628-3030-4e78-bc86-43d80e7e1cca%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Loaded Kali in HVM- but it wont boot. should be a simple fix for someone with experience of Qubes.
On Wednesday, May 8, 2019 at 1:52:02 PM UTC, ajwwo...@gmail.com wrote: > I have installed Kali as HVM standalone VM, but when the installation > shutdown at the end and i restart the VM I get the following boot message. > > > Seabios (version rel 1.11.2-0-gf9626cc prebuilt.qmeu-project.org) > > Machine UUID > > Booting from Hard Disk > > Boot failed; not bootable disk > > Booting from floppy > > Boot failed: could not read the boot disk > > > No bootable device. > > I installed my iso image on a device vxdb in install and then took the option > to install the grub boot loader on the same device in the installation. > > > Is SEABIOS a virtual bios in QUBES and do i need to edit it? I'm not running > coreboot on my lenovno t530. > > > Some points of note on the various Kali installs i did; > > I could reach a time server, so the netowork routes were working. > > I could never attach to a mirror and proceeded with just the ISO image > > > Any further advice would really help as it feels like I'm really close to > this working now. Update: I have tried the Katoolin approach that did not work either, so please if someone, know how to this simple problem for hte ISO approach then I will be ok. -- 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/91a14518-4fe1-42b5-abb5-ded3a856e24b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Loaded Kali in HVM- but it wont boot. should be a simple fix for someone with experience of Qubes.
On Wednesday, May 8, 2019 at 1:54:18 PM UTC, Peter Thurner wrote: > You can install katoolin https://github.com/LionSec/katoolin in a debian > VM instead of installing kali itself. > > This doesn't fix your problem but you can just use a working debian > template as a starting point. > > > On 8.5.19. 15:52, ajwwoodw...@gmail.com wrote: > > I have installed Kali as HVM standalone VM, but when the installation > > shutdown at the end and i restart the VM I get the following boot message. > > > > > > Seabios (version rel 1.11.2-0-gf9626cc prebuilt.qmeu-project.org) > > > > Machine UUID > > > > Booting from Hard Disk > > > > Boot failed; not bootable disk > > > > Booting from floppy > > > > Boot failed: could not read the boot disk > > > > > > No bootable device. > > > > I installed my iso image on a device vxdb in install and then took the > > option to install the grub boot loader on the same device in the > > installation. > > > > > > Is SEABIOS a virtual bios in QUBES and do i need to edit it? I'm not > > running coreboot on my lenovno t530. > > > > > > Some points of note on the various Kali installs i did; > > > > I could reach a time server, so the netowork routes were working. > > > > I could never attach to a mirror and proceeded with just the ISO image > > > > > > Any further advice would really help as it feels like I'm really close to > > this working now. > > Thank Peter but i experience more problems that way and could never get it working, htis way seems like i'm really close, just need to know how to fis this boot issue. 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/014d9857-2375-43ab-9576-48401724816e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Loaded Kali in HVM- but it wont boot. should be a simple fix for someone with experience of Qubes.
You can install katoolin https://github.com/LionSec/katoolin in a debian VM instead of installing kali itself. This doesn't fix your problem but you can just use a working debian template as a starting point. On 8.5.19. 15:52, ajwwoodw...@gmail.com wrote: > I have installed Kali as HVM standalone VM, but when the installation > shutdown at the end and i restart the VM I get the following boot message. > > > Seabios (version rel 1.11.2-0-gf9626cc prebuilt.qmeu-project.org) > > Machine UUID > > Booting from Hard Disk > > Boot failed; not bootable disk > > Booting from floppy > > Boot failed: could not read the boot disk > > > No bootable device. > > I installed my iso image on a device vxdb in install and then took the option > to install the grub boot loader on the same device in the installation. > > > Is SEABIOS a virtual bios in QUBES and do i need to edit it? I'm not running > coreboot on my lenovno t530. > > > Some points of note on the various Kali installs i did; > > I could reach a time server, so the netowork routes were working. > > I could never attach to a mirror and proceeded with just the ISO image > > > Any further advice would really help as it feels like I'm really close to > this working now. > -- 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/a2b036bb-f7a1-030d-fdb5-f8ff890b3091%40blunix.org. For more options, visit https://groups.google.com/d/optout. signature.asc Description: OpenPGP digital signature
[qubes-users] Loaded Kali in HVM- but it wont boot. should be a simple fix for someone with experience of Qubes.
I have installed Kali as HVM standalone VM, but when the installation shutdown at the end and i restart the VM I get the following boot message. Seabios (version rel 1.11.2-0-gf9626cc prebuilt.qmeu-project.org) Machine UUID Booting from Hard Disk Boot failed; not bootable disk Booting from floppy Boot failed: could not read the boot disk No bootable device. I installed my iso image on a device vxdb in install and then took the option to install the grub boot loader on the same device in the installation. Is SEABIOS a virtual bios in QUBES and do i need to edit it? I'm not running coreboot on my lenovno t530. Some points of note on the various Kali installs i did; I could reach a time server, so the netowork routes were working. I could never attach to a mirror and proceeded with just the ISO image Any further advice would really help as it feels like I'm really close to this working now. -- 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/606138f4-382f-4177-a9ab-d98119ab19e9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] R4.0.1: Various tray icons transparent/invisible (nm-applet, etc.) in KDE
On 5/8/19 6:37 AM, peter.palen...@gmail.com wrote: A recurring topic since R3.2 and not yet solved: Some tray icons (in my case nm-applet and evolution-alarm-notify) are transparent (or invisible) in KDE. Hovering over or clicking them works. They are, however, visible in XFCE, but i can not use that due to 4K display issues (KDE does that much better unfortunately). Thanks for any recommendation! KDE does a lot a things better than XFCE. The three big issues for me were multi-monitor handling, screensaver behavior and color correction; plus about four more that are also important. The tray icon issue is not really Qubes-specific and appears to be caused by apps using a particularly old 'appindicator' library in a particular way. Last year I created some tests to reproduce the problem from python, but there was no obvious workaround for users to change the behavior of existing apps. Various troubleshooting threads around the net usually assume that KDE is installed with 'plasma-nm' widget, but my tests with a Qubes template running KDE show the problem still exists. -- Chris Laprise, tas...@posteo.net https://github.com/tasket https://twitter.com/ttaskett PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To 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/5c631bad-bc8d-e0bf-23f3-703f6271588b%40posteo.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] R4.0.1: RTL8152 USB Ethernet adapter (Dell XPS13 TB16 dock) fails
peter.palen...@gmail.com: Thanks for the tip. It leads me to the next question: How do i tell my sys-firewall VM to use two network VMs (sys-net and sys-usb)? Thanks! You can't do that. You can have multiple sys-firewall equivalents pointing to their own network VMs, and have a portion of AppVMs pointing as desired. Otherwise, you'd have to merge at least the USB controller handling your USB-Ethernet adapter into sys-net or your wireless controller into sys-usb. -- 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/7b3065e8-2ae7-066c-fbe0-a5ac4add0638%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] R4.0.1: RTL8152 USB Ethernet adapter (Dell XPS13 TB16 dock) fails
On Wednesday, May 8, 2019 at 8:41:42 AM UTC+2, awokd wrote: > peter.palen...@gmail.com: > > I have a Dell TB16 dock with Ethernet over USB, based on a Realtek 8152 > > chip. > > > > The device appears fine in sys-usb VM using r8152 driver and ehci/xhci. So > > it works fine with direct PCI access to the device. > > > > Connecting the usb device (via 'dom0$ qvm-usb attach...') to sys-net VM > > triggers loading of vhci. After some dmesg says "cannot enable. Maybe the > > usb cable is bad?" and the device does not work in sys-net VM. > > > > Blacklisting/disabling vhci-hcd in sys-net VM does not help (connecting > > fails immediately). Does qubes usb attaching require vhci? > > > > I upgraded dom0/vm kernels, BIOS -> no help. > > > > The dock worked fine on this computer using bare-metal Ubuntu with equal > > kernel version. > > > > I would like to avoid merging sys-usb and sys-net... > > > > Thanks for any hint. > > > You could leave the ethernet adapter in sys-usb, and use "qvm-prefs > sys-usb provides_network true". Then you should be able to point > sys-firewall to sys-usb as needed. Thanks for the tip. It leads me to the next question: How do i tell my sys-firewall VM to use two network VMs (sys-net and sys-usb)? 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/2d447c4b-b474-496a-8b2f-168a2bd3ad3f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users]
-- 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/CAJkYkOZTeKQD_CkWeLPxatzncaP1air09GQ_yg%3D4zOFkOmYNcw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] R4.0.1: Various tray icons transparent/invisible (nm-applet, etc.) in KDE
A recurring topic since R3.2 and not yet solved: Some tray icons (in my case nm-applet and evolution-alarm-notify) are transparent (or invisible) in KDE. Hovering over or clicking them works. They are, however, visible in XFCE, but i can not use that due to 4K display issues (KDE does that much better unfortunately). Thanks for any recommendation! -- 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/21e65bde-12c5-404a-9cb7-a3a500fb88c8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] "Run command doesn't work" in VM after updating vmtemplate
eduzw...@gmail.com: I am on R3.2 I know its not supported. I am going to update to R4. But before I update. I have been running on 3.2 for for a week and I used the arch vm to download and save some work. I updated archLinux vmtemplate to install new pkgs. After update I shutdown template before running my archvm. When I shut down the vmtemplate I got the msgbox with "it has been more than 20s" "cancel or kill it" I killed archLinux vmtemplate to shut it down. Now my arch VM starts but will not run any command whatsoever. Qvm-run arch command doesn't work either. Now If I start archlinux template I can not run any command in template as well. And if I run vmtemplate with arch vm. There's an indicator that looks like a loading arrows next arch VM under machine state column. But stopping vmtemplate so VM can commit changes doesn't work for some reason. Am I missing something One of the updates must have broken a Qubes package. You should be able to switch your ArchVM to use a different template if you need to recover data from it. If you catch the problem quickly enough, you can roll back your template to an earlier version, but you only get one chance. Once you power it on twice, it's gone. Many Qubes users clone their templates before upgrading one of them and testing. That way, if there is a problem, the bad template can be deleted and the clone renamed. -- 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/420a4ee7-63ea-14bc-f07d-7b592c16d615%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
