[qubes-users] Cloning AppVm to Secondary Drive fail on R4.0
I'm trying to clone an existing VM to a pool on a secondary drive.
I followed the instructions on https://www.qubes-os.org/doc/secondary-storage/
But when I run the `qvm-clone` I get the following error -
$ qvm-clone -v -P storage extra storage
2018-04-01 00:20:36,421 [MainProcess app.clone_vm:390] storage: Cloning private
volume
Traceback (most recent call last):
File "/usr/bin/qvm-clone", line 5, in
sys.exit(main())
File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_clone.py", line
73, in main
app.clone_vm(src_vm, new_name, new_cls=args.cls, pool=pool, pools=pools)
File "/usr/lib/python3.5/site-packages/qubesadmin/app.py", line 391, in
clone_vm
dst_volume.clone(src_volume)
File "/usr/lib/python3.5/site-packages/qubesadmin/storage.py", line 229, in
clone
self._qubesd_call('CloneTo', payload=token)
File "/usr/lib/python3.5/site-packages/qubesadmin/storage.py", line 76, in
_qubesd_call
payload_stream=payload_stream)
File "/usr/lib/python3.5/site-packages/qubesadmin/app.py", line 483, in
qubesd_call
return self._parse_qubesd_response(return_data)
File "/usr/lib/python3.5/site-packages/qubesadmin/base.py", line 102, in
_parse_qubesd_response
raise exc_class(format_string, *args)
qubesadmin.exc.StoragePoolException: b' Please use a single volume group name
("qubes_root0" or "qubes_-storage0").\n Run `lvcreate --help\' for more
information.\n'
Running `qvm-create` on the secondary pool seem to work with no issues
--
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/07e32240-0a35-4465-8bd3-52b397115600%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[qubes-users] Qubes 4.0 audio, x2go
I upgraded from Qubes 3.2 to 4.0. I had been using Qubes 3.2 for over a year. I have run into the following issues. 1. I have been using an external USB device for audio-conferencing etc. because of the Qubes latency issues. In Qubes 3.2 it worked great. I simply attached it to the VM I wanted to use it in and that was all there was to it. In Qubes 4.0, when I try to attach it I don't get an error but running the command "qvm-usb" does not show it attached. When I use a regular USB headset it attaches and works correctly, but of course will not solve the latency issue. Has anyone tested an external USB audio device successfully with Qubes 4.0. I did try making /dev/snd/* executable by all and reload PulseAudio's module-udev-detect but that didn't help. 2. In Qubes 3.2 I had issues getting x2go to work and I reported it at the time. After trying the fedora templates, I tried debian 8 and it worked. Now in Qubes 4.0 I am having the problem again with both fedora 26 and debian 9. debian 8 is no longer available it seems. I can ssh to the target server find over port 22 (which is the port x2go uses). Has anyone by any chance tried using x2go with Qubes 4.0 and had any success? I am of course using a VPN qube, which inherits from sys-firewall. There doesn't seem to be a ProxyVM setting anymore like there was in Qubes 3.2. I would like to note that so far the new Qubes Manager is, to me, more difficult to use than the old one. First of all, I have to constantly use the "Refresh qube list" button each time I do something and want to see if reflected. So the manager often is out of sync with reality, at least if you start or stop anything. Also, it seems to be slow when you do something (until the operation completes?). I do like the GUI for attaching/detaching devices. Unfortunately it shows the same behavior as the command line when attaching the external audio device. Thanks in advance for any enlightenment anyone can provide. Chris Seekamp -- 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/79fab8e1-8f48-369d-ab34-5c557e7e4317%40acm.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Slow dom0 boot - 33sec lvm2-pvscan service
On 03/31/2018 03:36 PM, Chris Laprise wrote: Is there a way to improve boot times here? I know Qubes 4 accumulates a lot of logical volumes, but it would be nice if the wait time wasn't so long. I added a kernel boot parameter "systemd.mask=lvm2-pvscan@.service" which allowed dom0 to boot in just a few seconds. This left qubesd.service unaware of vm- volumes however, so no appVMs could start. Manually running 'pvscan --cache --activate ay' then restarting qubesd.service seemed to get everything working. I wonder if the lvm2-pvscan@.service should be permanently disabled and then have the lvm.py driver on initialization run pvscan. -- 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/4b35c8e7-ed0a-4313-ed3a-f3e377f91112%40posteo.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] x220 coreboot 'out of memory'
On Sat, March 31, 2018 4:57 pm, get wrote: > Hi, qubes 4.0 is written dd. Onboard 16GB of RAM and coreboot / grub. > Other distributions are work but Qubes does not want to. I did not find > on the forum something similar. I think I read somewhere you can't use coreboot's grub to install, have to use Seabios. You can switch back to grub after install. -- 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/f4368e7fe79a6cb0c11322b7247c0875.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Slow dom0 boot - 33sec lvm2-pvscan service
Is there a way to improve boot times here? I know Qubes 4 accumulates a lot of logical volumes, but it would be nice if the wait time wasn't so long. -- 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/199cff60-d69e-9e07-b3f5-8ddb1cf6ecaf%40posteo.net. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Bug in qubes-input-sender
The problem is that after connecting the mouse to the computer, the mouse can run for 10 minutes, then the system disconnects it from sys-usb, and then connects it again without any user interaction. The second problem is that after connecting the keyboard via usb to sys-usb the keyboard does not work, only the backlight of the keyboard works, but the keyboard itself does not work. No buttons were detected in the system, therefore you can not write on it. Logs from sys-usb https://0bin.net/paste/B+3I3fbBsrNCHzFu#a97f-dAtLaVPeUlyqHNGW9a/0PqUKusDHTqEWrRJE2z -- 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/2028224823.118183.1522524881695%40ichabod.co-bxl. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: HOWTO: Compiling Kernels for dom0
I mostly followed this page and the GCC error was due to not having GCC-C++ installed. After that, all was well! $ sudo yum install gcc-c++ -- 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/c8d51143-a395-4bcb-89ed-183a6df0afd9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes No Longer Recognizes External Monitors
On Fri, March 30, 2018 4:54 pm, mpenterprises@gmail.com wrote: > System: > -Qubes current (4.0rc5 - I guess it's just 4.0 Stable now?) > -Thinkpad P70 with Skylake i7 > -Kernel Flags: i915.alpha_support=1 rd.blacklist.drivers=nouveau > nouveau.modeset=0 -Bios: > --USB UEFI BIOS Support: Enabled > --UEFI/Legacy Boot: UEFI Only > --Secure Boot: Disabled > > > > Previously: 4.0rc4 installed > -Plug in External Monitor via HDMI or MiniDP > -XFCE Display manager launches and external displays are configurable > -Displays show up in Display Manager and xrandr > > > > Now: Fresh Install of Qubes 4.0rc4, applied qubes updates to get > 4.0rc5/4.0 Stable > -Plug in External Monitor via HDMI or MiniDP > -Qubes Display manager launches > -No monitors are available except built-in are available on Display > Manager > -xrandr shows only built-in monitor > > > > Any ideas how I can get my external monitors back? It's odd the display manager is automatically detecting them to launch, but not showing them. Do they work if you plug them in before powering on the system and booting Qubes? Check the Xorg logs for errors too. -- 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/95ddfe7fe8523810ecac5e1eb9e87907.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: HOWTO: Compiling Kernels for dom0
On Fri, March 30, 2018 3:35 pm, sevas wrote: > Can someone please point me in the right direction? I don't know where to > look. > > I've created a standalone Fedora 26 and I'm looking at this page, the > qubes page : working with kernel, > > I've installed every Palast I can think of. > > > Error gcc plug-ins installation does not support plug-ins... > U2mfn v 4.0.17 > Kernel 4.14.18-1 > Dkms add u2mfn = ✓check > Yum group install development tools =✓check > The other errors don't look important or give any information, I think. > (Bad exit, error 2, g++ not found) You're following https://www.qubes-os.org/doc/managing-vm-kernel/#installing-kernel-in-fedora-vm on R3.2? What command are you entering when you get that error? Did you do the "sudo dnf install qubes-kernel-vm-support grub2-tools" step? -- 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/10a73454a3e01b5373c2ae552494c104.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Cannot Restore Qubes R2 VMs to Qubes R4
On Fri, March 30, 2018 3:28 pm, Nico De Musso wrote: > Trying to restore some VMs from Qubes R2 to a new Qubes 4 fresh install > but none of the Vms are showed in the [Dom0] Qubes Os - Restore > qubes.Plus i got the following error: > > [Dom0] Restore error! > Unsupported backup version None. > > > Is there any canche to restore my VMs? You might have to follow the R2 (or R3?) recovery procedure under here: https://www.qubes-os.org/doc/backup-restore/#emergency-backup-recovery-without-qubes -- 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/31cdf2493214c04ef6bb5a631e8aee47.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] How do I load firmware-atheros into Qubes 4.0 R5?
On Wednesday, March 28, 2018 at 5:37:04 PM UTC-4, Chris Laprise wrote: > On 03/28/2018 05:02 PM, Ringo wrote: > > Greetings. I have a Purism 15v3 laptop with an Atheros AR9462 wi-fi card. > > The card works under Qubes but it's slow, with bit-rate of only 6/mpbs. I > > had this issue before, on the same laptop when it was first shipped with > > the PureOS distribution (a debian distribution) and was able to fix it by > > installing a firmware package found at > > https://packages.debian.org/buster/firmware-atheros. However, I'm not > > able to install this same "firmware driver" under Qubes, since it's in > > debian format and not fedora. > > > > I downloaded a tool called "alien" which was able to convert the package > > into RPM format but then when I tried to install it using DNF in the > > SYS-NET cube, I received an error saying > > "firmware-atheros-20170823-2.noarch" conflicts with package > > linux-firmware-201771215-82.git2451bb.fc26.noarch. > > > > I'm thinking perhaps I should uninstall this conflicting package in order > > to install the atheros one that I know worked under PureOS, but frankly, > > I'm a bit out of my depth at this point and wondering if this makes sense > > to you all or might have other advice. Appreciate any thoughts you may > > have to assist. > > > > Warm Regards, Ringo > > > > I'd suggest using a Debian template for your sys-net; It takes time to > download but its fairly simple. You may want to try using the > Debian-supplied firmware first to see if that resolves the issue: > > sudo apt-get install firmware-atheros > > If that's not new enough you can follow Debian directions for installing > from a newer repository (e.g. Buster). > Update1: Wow, what a great suggestion! I didn't even need to download anything. All I had to do was change the template from fedora to debian in the sys-net virtual machine settings and presto, it worked! I couldn't believe how simple this was. Thanks for the suggestion! BTW, appreciate the other comments regarding Purism, etc. I'm new to this space and was not aware what all to consider. I'll look around in other posts to try and do more research for best libre machine next time I'm in the market. Thanks for your help! > -- > > 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/12c8816f-78da-4671-af3b-0d76c0bddbab%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Unable to play DVD's
Hello,
I have recently installed Qubes3.2 on a Thinkpad T430. I currently have the
problem that I cannot play any DVD's. I have tried to attach the DVD drive to a
Fedora and a Debian VM, made sure that libdvdcss2 is installed, tried different
media players, but nothing seems to work. Trying to play the DVD with VLC only
gives me the following error: "core input error: ES_OUT_RESET_PCR called".
I was thinking that the error might be caused by an invalid region. But running
regionset within a VM only produces an error ("Can't set region code").
Does anyone have any ideas what the issue could be and how to solve it?
Thanks in advance for any help.
--
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/1dc152cf-4a5e-4e62-a6c3-6de2d8c4eab5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes 4 does not see my RAID 5 disk but 3.2 does
Le vendredi 30 mars 2018 23:12:30 UTC+2, awokd a écrit : > On Fri, March 30, 2018 7:22 pm, Paf LeGeek wrote: > > Le vendredi 30 mars 2018 00:57:44 UTC+2, awokd a écrit : > > > >> On Thu, March 29, 2018 6:32 pm, Paf LeGeek wrote: > >> > >>> Hello, > >>> > >>> > >>> > >>> I installed Qubes OS 4 (final release) today, but it does not see my > >>> 3 > >>> disks array RAID 5 (encrypted with luks) even with the command "sudo > >>> pvs". It's an hardware RAID on a Asus Sabertooth 990FX V2 > >>> motherboard. > >>> > >>> > >>> So I got back to the Qubes OS 3.2 version which see the RAID 5 disk > >>> without any problem. > >>> > >>> Any idea ? > >>> > >> > >> Random ideas (from inside 4.0): > >> - check sudo lspci -v and see if it loaded the driver for your > >> controller - unless you added it to crypttab after installing 4.0, you > >> might have to run cryptsetup to decrypt it before LVM can detect it > > > > I just did sudo lspci -v and i confirm that the RAID Controler is loaded > > in RAID5 mode. > > Were you able to open it with cryptsetup? Is it showing up in /dev? No, it's not showing in /dev. Thanks for your help but after 3 days trying to use Qubes OS 4, I gave up and decided to go back to the 3.2 version witch work perfectly for me. There is a few things I dont like in the 4 version, like the new Qubes Manager. I love Qubes OS but this is not what I was expecting. So I will wait for the next version (or update). 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/37a3bace-364a-4168-9042-b0c7886637d7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
