Re: [qubes-users] qvm-block issues
On 10/31/2016 05:24 AM, Drew White wrote:
> Hi folks,
>
> Well, I mounted an image to the guest. Then I finished, so I
> unmounted it in the vm and went to remove it to attach it to another
> guest...
>
> I tried several different methods... []
> But that detaches everything. I only wanted to detach xvdi
>
> To attach it I used
>
> [{username}@dom0 {foldername}]$ qvm-block -A {vmname}
> dom0:/run/media/{username}/{partition_label}/{imagename}.img
>
>
Hi Drew,
afair qvm-block needs the name of the original VM where the device is
attached for removal. So, if you attached your device from dom0, you
will need to use dom0 for removal too. As an example, but using usbvm:
dom0$ qvm-block -a work usbvm:sdd
This attaches /dev/sdd in usbvm to work
dom0$ qvm-block -d usbvm:sdd
This now detaches /dev/sdd in usbvm from work
And this is why, in the --help output, the -d command has
instead of just , to highlight the fact that
you need the original vm name. If you want to detach everything you can
use the second syntax suggested by --help, using the vm name, and this
will detach everything from that vm.
I do know that you are mounting an image file; and I don't know if this
works this way too - i.e. if you need to specify the full path to the
file, like this:
dom0$ qvm-block -a work dom0:/mnt/foo/bar.img
and then
dom0$ qvm-block -d dom0:/mnt/foo/bar.img
to detach it
You can probably check the output of "qvm-block" without parameters,
once the image file is mounted; the first column of the output contains
the names used to identify the devices (or files, I suppose) to be managed.
Hope this helps,
--
Alex
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/129ebc17-9407-8b41-6554-b39ad9afa229%40gmx.com.
For more options, visit https://groups.google.com/d/optout.
[qubes-users] qvm-block issues
Hi folks,
Well, I mounted an image to the guest.
Then I finished, so I unmounted it in the vm and went to remove it to attach it
to another guest...
I tried several different methods...
[{username}@dom0 {foldername}]$ qvm-block -d {vmname}:xvdi
Usage: qvm-block -l [options]
usage: qvm-block -a [options] :
usage: qvm-block -A [options] :
usage: qvm-block -d [options] :
usage: qvm-block -d [options]
List/set VM block devices.
qvm-block: error: Invalid VM or device name: {vmname}:xvdi
[{username}@dom0 {foldername}]$ qvm-block -d {vmname}:/dev/xvdi
Usage: qvm-block -l [options]
usage: qvm-block -a [options] :
usage: qvm-block -A [options] :
usage: qvm-block -d [options] :
usage: qvm-block -d [options]
List/set VM block devices.
qvm-block: error: Invalid VM or device name: {vmname}:/dev/xvdi
[{username}@dom0 {foldername}]$ qvm-block -d {vmname}:/dev/xvdi1
Usage: qvm-block -l [options]
usage: qvm-block -a [options] :
usage: qvm-block -A [options] :
usage: qvm-block -d [options] :
usage: qvm-block -d [options]
List/set VM block devices.
qvm-block: error: Invalid VM or device name: {vmname}:/dev/xvdi1
[{username}@dom0 {foldername}]$ qvm-block -d {vmname}
[{username}@dom0 {foldername}]$
So, the only one that worked was " qvm-block -d {vmname} "
But that detaches everything. I only wanted to detach xvdi
To attach it I used
[{username}@dom0 {foldername}]$ qvm-block -A {vmname}
dom0:/run/media/{username}/{partition_label}/{imagename}.img
I did this when it was saying that the device wasn't there, just to make 100%
sure it was.
[root@{vmname} {foldername}]# ls /dev/xv*
/dev/xvda /dev/xvdb /dev/xvdc /dev/xvdc1 /dev/xvdd /dev/xvdi /dev/xvdi1
[root@{vmname} {foldername}]#
What is it that has gone wrong here?
--
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/3e9ea427-974f-4570-b815-e4685571d088%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[qubes-users] Win 7 Template (QWT)
Windows 7 Template Boots. Loads video driver shows initial splash loading screen then front end dissappears. --- Before starting VM --- debug : on default_user : user qrexec_installed : False qrexec_timeout : 60 guiagent_installed : False seamless_gui_mode : False drive : None timezone : localtime internal : False --- After starting VM --- debug : on default_user : user qrexec_installed : True qrexec_timeout : 60 guiagent_installed : True seamless_gui_mode : False drive : None timezone : localtime internal : False Why does it change it back when I set it to be the other way? I tell it that those things aren't there, and yet when I start the VM, it says they are... Strange thing is.. debug : on default_user : user qrexec_installed : True qrexec_timeout : 60 guiagent_installed : True seamless_gui_mode : True drive : None timezone : localtime internal : False I set seamless_gui_mode to TRUE, and it doesn't load in seamless mode. WTH??? Then while I'm in there, the whole guest dies. The Video Driver still isn't working right either. It's still very buggy. Still has flashing Dom0 cursor. Still lags behind in a big way. Not very responsive. -- 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/c7d7668a-1e2f-44fd-b9fe-c9bc12c2f715%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Qubes 3 MacOSX
On 06/17/2016 04:11 AM, Drew White wrote: > > > On Sunday, 15 May 2016 14:05:50 UTC+10, Jeremy Rand wrote: > > FWIW, I think a legal argument could be made that such license > agreements are anti-competitive and therefore unenforceable. > However, > I am unaware of any specific precedent for this argument, so it would > indeed probably be unwise for ITL to violate the license agreement > unless their goal is to win the inevitable lawsuit and thus achieve a > beneficial precedent. (And while that would be laudable, I would > definitely not blame ITL if they decided that such activities are not > worth their effort or budget.) > > (And of course, I'm not a lawyer.) > > > Well, in the end, I own a mac, It's not breaking any agreement or > anything for me wanting to run it. Yeah you are. Check the licensing terms for the Mac OS X software that came with it. Not that it matters, as it's a bullshit "agreement" that transforms a purchase into somewhat of a feudal renting system of objects. -- Rudd-O http://rudd-o.com/ -- 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/87694b7c-33f9-8a1c-fd26-14d1f361e02e%40rudd-o.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] HCL - Lenovo ThinkPad Edge E531
Thanks for the info. niedz., 30.10.2016 o 19:47 użytkownik napisał: > On Saturday, March 5, 2016 at 3:56:18 PM UTC-8, Mirosław Wojciechowski > wrote: > > Ok, i Checking this, and in my bios not Vt-d fuctions. But i only inform > is that Qubes works well. > > > > Regards. > > > > > > > > sob., 5.03.2016 o 22:58 użytkownik Chris Laprise > napisał: > > > > > > > > > > On 03/05/2016 03:59 PM, Mirosław Wojciechowski wrote: > > > > > > > > > > This must be some error, i have enable intel virtualization in bios. > > > > > On Virtualbox & VMWARE all working great. Qubes worki gratuluję to. > > > > > > > > > > > > > > > > > > It may be that Vt-x (normal virtualization extensions) is enabled, but > > > > without Vt-d (I/O virtualization)... I think this indicates that Lenovo > > > > does not support IOMMU features in the Thinkpad Edge line. I have seen > > > > reports about older Edge models having the Vt-d feature greyed-out in > > > > the BIOS settings. > > > > > > > > Qubes can work without IOMMU, but the level of security is reduced > somewhat. > > > > > > > > Chris > > There are two reasons why VT-d is not supported. > > 1) > The Thinkpad Edge E531 has a HM77 chipset, which does not support VT-d. > Only their "business" and "workstation" lines (e.g. T530, W530) uses the > QM77 chipset, which does support VT-d. > > 2) > The Thinkpad Edge E531 has a socketed motherboard (which is a "good" > thing, in general, and allows swapping out CPU's for better ones, etc). > > The 3632QM rPGA package (as opposed to BGA--a.k.a. "soldered") does NOT > support VT-d. If you want VT-d, you will have to upgrade to a minimum of > 3720QM for socketed CPU's. However, see reason #1 for why it would not work > in your laptop. -- 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/CAKOvoGE5R7DbJcYfhnwB3yGTDuiFcZZ6ufk%2BJWZYBWZV%2BP-rCA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] HCL - Lenovo ThinkPad Edge E531
On Saturday, March 5, 2016 at 3:56:18 PM UTC-8, Mirosław Wojciechowski wrote: > Ok, i Checking this, and in my bios not Vt-d fuctions. But i only inform is > that Qubes works well. > > Regards. > > > > sob., 5.03.2016 o 22:58 użytkownik Chris Laprise > napisał: > > > > > On 03/05/2016 03:59 PM, Mirosław Wojciechowski wrote: > > > > > > This must be some error, i have enable intel virtualization in bios. > > > On Virtualbox & VMWARE all working great. Qubes worki gratuluję to. > > > > > > > > > > It may be that Vt-x (normal virtualization extensions) is enabled, but > > without Vt-d (I/O virtualization)... I think this indicates that Lenovo > > does not support IOMMU features in the Thinkpad Edge line. I have seen > > reports about older Edge models having the Vt-d feature greyed-out in > > the BIOS settings. > > > > Qubes can work without IOMMU, but the level of security is reduced somewhat. > > > > Chris There are two reasons why VT-d is not supported. 1) The Thinkpad Edge E531 has a HM77 chipset, which does not support VT-d. Only their "business" and "workstation" lines (e.g. T530, W530) uses the QM77 chipset, which does support VT-d. 2) The Thinkpad Edge E531 has a socketed motherboard (which is a "good" thing, in general, and allows swapping out CPU's for better ones, etc). The 3632QM rPGA package (as opposed to BGA--a.k.a. "soldered") does NOT support VT-d. If you want VT-d, you will have to upgrade to a minimum of 3720QM for socketed CPU's. However, see reason #1 for why it would not work in your laptop. -- 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/82d193a8-6a00-4091-8068-5d0aef2e8611%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] HCL - Intel NUC NUC5i5RYK, Samsung 850 EVO - 250GB - M.2 SATA III SSD, Crucial 16GB RAM
Overall, works very well. Tried very briefly (a day or two) with 3.1 but since the release of 3.2 have used this only. With Qubes 3.1, I couldn't use my Logitech TK820 USB wireless keyboard or Elecom mouse during installation or to enter the decryption password. Once the user login prompt appeared this worked fine. For Qubes 3.2, the wireless keyboard and mouse have been fine all through installation and from decryption to login. For both Qubes 3.2 and 3.1 ethernet and WiFi have worked without issue. Playing video and sound are no issues through both the headphone jack and the HDMI. The only issue I have had is from using an Asus VX228 Monitor (HDMI to miniHDMI or the mini display port). Switching the screen off and on is fine, waking from sleep is ok but if I unplug the monitor and plug it back in again the screen is blank and I cannot wake it. This issue doesn't occur when using booting from another Linux distribution such as TAILS or Fedora 24. I haven't yet downloaded any further drivers as I am unclear whether this is required. Any advice on how to resolve this? I would like to be able to leave Qubes operating on the NUC without a monitor and locked as I intend to have programs operating continually. -- 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/e6f9cc3d-35a5-4fe8-948c-1859ec04be67%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. Qubes-HCL-_-_-20161023-171525.yml Description: Binary data
[qubes-users] HCL - HP ENVY TS 17 Notebook PC
Hello, Kindly find attached HCL report. I just install Qubes 3.2, run and all works fine. Sleep mode is OK, network both adapters (WiFi and Ethernet) works fine too in default NetVM. Sent using Guerrillamail.com Block or report abuse: https://www.guerrillamail.com/abuse/?a=UFR2AB5NVqcQmh2U93EQdRjCStifx8dDiadNcQ%3D%3D -- 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/32fdc7d2e138dc8cdb635ed2eaf6c169e444%40guerrillamail.com. For more options, visit https://groups.google.com/d/optout. Qubes-HCL-Hewlett_Packard-HP_ENVY_TS_17_Notebook_PC-20161030-171952.yml Description: application/yaml Qubes-HCL-Hewlett_Packard-HP_ENVY_TS_17_Notebook_PC-20161030-171952.cpio.gz Description: application/gzip
[qubes-users] Trying to do an in-place upgrade from 3.1.17 to 3.2
I'm trying to upgrade my Qubes 3.1.17 to 3.2 I've followed the steps outlined here: https://www.qubes-os.org/doc/upgrade-to-r3.2/ However, when I run... sudo qubes-dom0-update --releasever=3.2 qubes-release I receive: Loaded plugins: yum-qubes-hooks Nothing to do No packages downloaded file:///var/lib/qubes/updates/repodata/repomd.xml: [Errno 14] curl#37 - "Couldn't open file /var/lib/qubes/updates/repodata/repomd.xml" Trying other mirror. Nothing to do So of course running... sudo qubes-dom0-update --clean also provides a similar error: Errno 14] curl#7 - "Failed to connect to pubmirror1.math.uh.edu port 443: No route to host" Trying other mirror. No new updates available No updates avaliable Is anybody able to advise me what I need to do to be able to do an in-place upgrade to 3.2? Thanks, Richard -- 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/c55fe766-d790-4f25-b54f-fa85a23f479f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. [user@dom0 ~]$ sudo qubes-dom0-update --releasever=3.2 qubes-release There is no selected ClockVM, aborting. Using sys-firewall as UpdateVM to download updates for Dom0; this may take some time... Running command on VM: 'sys-firewall'... (Note: dnf will complain that the yum command has been deprecated. This message is safe to ignore.) Yum command has been deprecated, use dnf instead. See 'man dnf' and 'man yum2dnf' for more information. Yum command has been deprecated, use dnf instead. See 'man dnf' and 'man yum2dnf' for more information. Loaded plugins: yum-qubes-hooks Nothing to do No packages downloaded file:///var/lib/qubes/updates/repodata/repomd.xml: [Errno 14] curl#37 - "Couldn't open file /var/lib/qubes/updates/repodata/repomd.xml" Trying other mirror. Nothing to do [user@dom0 ~]$ sudo qubes-dom0-update --clean There is no selected ClockVM, aborting. Using sys-firewall as UpdateVM to download updates for Dom0; this may take some time... Running command on VM: 'sys-firewall'... (Note: dnf will complain that the yum command has been deprecated. This message is safe to ignore.) Yum command has been deprecated, use dnf instead. See 'man dnf' and 'man yum2dnf' for more information. Loaded plugins: yum-qubes-hooks Cleaning repos: fedora qubes-dom0-current qubes-templates-itl updates Cleaning up everything Checking for dom0 updates... Yum command has been deprecated, use dnf instead. See 'man dnf' and 'man yum2dnf' for more information. https://pubmirror1.math.uh.edu/fedora-buffet/archive/fedora/linux/releases/20/Everything/x86_64/os/repodata/0054652738782478eff37604abc430cdf327795d157634e1dfcca0fa18d8fedf-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to pubmirror1.math.uh.edu port 443: No route to host" Trying other mirror. No new updates available No updates avaliable [user@dom0 ~]$ yum info qubes-core-dom0 Installed Packages Name: qubes-core-dom0 Arch: x86_64 Version : 3.1.17 Release : 1.fc20 Size: 1.6 M Repo: installed >From repo : qubes-dom0-cached Summary : The Qubes core files (Dom0-side) URL : http://www.qubes-os.org License : GPL Description : The Qubes core files for installation on Dom0. [user@dom0 ~]$ ^C [user@dom0 ~]$
Re: [qubes-users] Xscreensaver not working when app-menu is open
On 10/30/2016 03:48 PM, yaqu wrote: > On Sun, 30 Oct 2016 03:28:39 -0700 (PDT), "Mike A." > wrote: > >> But if I open the application menu band then close the lid, the >> screensaver does not kick in. When I open the lid later, I can >> start using the machine just where I left it. >> >> I am running Qubes 3.2 with Xfce. >> >> Can anyone else recreate this, or is it just a problem locally >> here (user error at my end)? > > I have tested it on Lenovo T520 (R3.2, Xfce) and got the same > behaviour - closing lid has no effect while appmenu is opened. I have > tested it with various settings in Xfce Power Manager (lock screen, > suspend, switch off display). When appmenu is closed, closing lid > works as expected. > > Additionally, locking screen manually (Ctrl-Alt-L) doesn't work too > while appmenu is opened. > It's a known problem of X (as an architecture); it prevents any succesful implementation of the concept of lock screens. It does not only affect Xfce, but all other desktop environments - actually, it affects all X11 implementations on any platform because screen locking is a scenario not provided by the architecture. You may check on https://blog.martin-graesslin.com/blog/2015/01/why-screen-lockers-on-x11-cannot-be-secure/ for an extended explanation of the concept, from the perspective of KDE developers. One common symptom is the one you described; i.e. opening any menu prevents screen-savers or screen-lockers from running. Our only reasonable hope in the relatively-near future is Wayland, whose architecture does provide for a screen-locking scenario; the adoption in Qubes may not be straightforward because of the way windows are cloned from the VMs into dom0. In short, qubes-guid needs to be able to screengrab every window, which is something Wayland tries to prevent for privacy and security concerns. -- Alex -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/07d28996-1615-6d96-7941-d0513c4a339d%40gmx.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Xscreensaver not working when app-menu is open
On Sun, 30 Oct 2016 03:28:39 -0700 (PDT), "Mike A." wrote: > But if I open the application menu band then close the lid, the > screensaver does not kick in. When I open the lid later, I can start > using the machine just where I left it. > > I am running Qubes 3.2 with Xfce. > > Can anyone else recreate this, or is it just a problem locally here > (user error at my end)? I have tested it on Lenovo T520 (R3.2, Xfce) and got the same behaviour - closing lid has no effect while appmenu is opened. I have tested it with various settings in Xfce Power Manager (lock screen, suspend, switch off display). When appmenu is closed, closing lid works as expected. Additionally, locking screen manually (Ctrl-Alt-L) doesn't work too while appmenu is opened. -- yaqu -- 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/20161030144820.EEFB5104434%40mail2.openmailbox.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Xscreensaver not working when app-menu is open
Installed qubes-os on a Lenovo T430s, and almost everything seem to work pretty well. Normally when I put the laptop away, I just close the lid and it goes to sleep. when I open the lid, Xscreensaver have kicked in, and I have to put in my password to start using it. So far, so good. But if I open the application menu band then close the lid, the screensaver does not kick in. When I open the lid later, I can start using the machine just where I left it. I am running Qubes 3.2 with Xfce. Can anyone else recreate this, or is it just a problem locally here (user error at my end)? Cheers, Mike A. -- 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/732425fd-cd23-47c0--1557ebae5e51%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
