[qubes-users] Re: attaching to VM consoles for debugging purposes
you can try 'qvm-start-gui --all' first, to see if that helps; otherwise, your best bet is 'sudo xl console -t pv VMNAME' -- 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/2e80f269-74d6-4864-a07e-c0b2ca56f185%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Why is there no qubes manager in V4.0?
While I do know how to use the cli tools I enjoy a gui for at a glance viewing and tasks, it is much easier to press start/stop on a nice list rather than type two commands. Thanks ADW! -- 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/bd5ea172-38b8-a4fa-fd05-390dd852939f%40gmx.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Qubes 4.0rc2 install on corebooted Lenovo G505s (AMD)
On Wed, October 25, 2017 20:32, awokd wrote: > Few issues on this attempt am hoping someone might have some insight into. > > 1) Installer warns "interrupt remapping" is not supported. > qubes-hcl-report shows IOMMU as enabled but "Remapping" is not. What > exactly are they looking for? > > 2) Install completes and reboots successfully after that but it only gets > part way through the first default template installation (whonix-gw) then > hard locks- no mouse or keyboard response. Is there a way to force these > to install in compatible mode or something so I can work on fixing them > later? > > 3) I can choose Do not configure anything and get logged in and to a > terminal window, but without any templates or VMs am pretty lost on how to > setup from scratch. qubes-template-fedora-25.noarch is listed in dnf but > when I try to create an AppVM there's nothing in the template dropdown. > > When I boot debian stretch on the same machine, I see AMD-Vi enabling > interrupt remapping. xl dmesg under 4.0 shows (Xen) enabling interrupt > remapping. Qubes 3.2 worked fine on this too. > > Suggestions welcomed! 1) I found https://github.com/QubesOS/qubes-issues/issues/3208 which seems to address this case and see "(XEN) Interrupt remapping enabled" [with lowercase "r"] in my xl dmesg output too. 2) This might be related but I'm having trouble finding if this patch has made it into the version of Xen Qubes uses. http://xen.1045712.n5.nabble.com/Xen-4-6-0-Dom0-freezes-at-creation-of-HVM-domain-with-activated-IOMMU-td5731709.html 3) I see what seem to be partially installed templates under /var/lib/qubes/vm-templates but fedora-25 for example has 4.5 1GB root.img.part.0? files and no root.img. -- 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/b25cf08c50e94163ab503564692bf6c8%40elude.in. For more options, visit https://groups.google.com/d/optout.
[qubes-users] attaching to VM consoles for debugging purposes
Hi, i've just installed qubes 4.0 rc2, and i'm having some issues with VMs, they start correctly, i see them running, but for some reasons certain VMs don't run the applications, not even a terminal emulator. since the VM is running i'd like to see what's the problem, so that i have something more useful to investigate or even ask about when coming here instead of just asking "help with this VM i cant start firefox" which i know can be really annoying. is there a way to attach to the console? i thought of virsh but it's not installed in dom0. anyway, the VM that is giving me issues is whonix-ws it starts up but i cant run any application from the menu, even qvm-run doesn't return anything and stays hung there. -- 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/fe2c1625-d303-4c38-9275-dfc1cadca774%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] DispVM and Word/docx - no go
Thank you. This fixed it perfectly. And I’ve become better acquainted with https://www.qubes-os.org/doc/dispvm-customization/ ….which I probably should have found before! :-) Cheers! > On Oct 20, 2017, at 12:34 PM, Noor Christensen > wrote: > > On Thu, Oct 19, 2017 at 11:08:07AM -0400, Ryan Tate wrote: >> In Qubes 3.2 from a fedora 25 AppVM, when I try and open a docx (Word) >> file via DispVM via the right-click menu, I just get a directory >> listing inside the DispVM. Instead of opening the file with >> LibreOffice it appears to unzip the file and show the underlying dir >> structure. (The docx format is zipped.) >> >> I have LibreOffice available to the app vm via the Fedora 25 template. >> Is there somewhere else I need to put it to make it available to the >> DispVM? Or is this a known/expected behavior for DispVM? > > First of all, you need to make sure that LibreOffice is installed in > your DispVM. > > Regenerate your DispVM image using that fedora-25 template you mentioned: > >$ qvm-create-default-dvm fedora-25 > > When it has completed, try opening the document in a DispVM again. > > -- noor > > |_|O|_| > |_|_|O| Noor Christensen > |O|O|O| 0x401DA1E0 > > -- > 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/20171020163437.6d25pqhwhvckzl5j%40mail. > 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/56A5B1C1-E926-4D13-B2F4-465E6F36141A%40ryantate.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Message signed with OpenPGP
Re: [qubes-users] Ledger Nano S works great with Qubes OS R3.2 [Debian 8 and Fedora 24 AppVMs]
Does it still work for your with Qubes R4? -- 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/8b48660a-f523-33f2-c212-54f7f01ae548%40riseup.net. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Setting up Jack Audio - can not detect virtual output
Hello, I'm using QubesOS 3.2 with default fedora 24 template for app vms and i'm struggling with getting Jack Audio working. I have installed packages with both jackdbus and pulseaudio modules for jack. I tried to follow tutorial for intergrating pulseaudio and jack from offitial jackaudio documentation. When i'm trying to load module via pacmd or pactl i'm getting Load failed, both duckduckgo and google did not helped much. Pulseaudio properly detects qubes vchan sink and uses it to output audio. My problem is that i can not instruct jack audio to send data to this output. I tried to look for more documentation of qubes sound architecture but without sucess. Alsamixer shows me (in app vm) nonly 'default soundcard' pavucontrol finds qubes vchan sink. Before installation of pulseaduio jack modules i was able to launch jackdbus via jack_control start, it used dummy output, jack fails to even start without telling me much what is wrong. I can paste apropiate logs etc, just please tell me what would be useful. -- Cranix -- 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/20171027170656.GC54552%40hackerspace.pl. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Qubes OS 4.0 second candidate (rc2) has been released!
2. Upgrade your templates to rc2 (make sure to keep some AppVMs running in case you need them), then do an offline re-partitioning of your template VMs (a 5-10 line script with losetup, fdisk & dd should suffice) either in dom0 or in a running AppVM, if you don't want your template VMs' file systems to be read inside dom0. Then upgrade dom0 & restart. I tested that one and it seems to work. (I think I was on rc2 even before knowing it...) I also noticed: - There are no additional repos for rc2, i.e. a straightforward rc1 dom0 update & template update should suffice. - rc1 partitioned templates also work in rc2. That may of course change. I guess they use the uuid so that partitioning doesn't really matter as long as you don't want to resize the image. - Other than that losetup, sfdisk & dd seem to do the trick. Make sure you have a backup before testing any of these though... Yes, at least make a copy of the original template root.img... -- 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/971573f3-f483-476c-e51d-d72c957388ef%40hackingthe.net. For more options, visit https://groups.google.com/d/optout. smime.p7s Description: S/MIME Cryptographic Signature
Re: [qubes-users] Qubes 4.0-rc2 :: VMs fail to start
On 10/25/17 13:26, '[799]' via qubes-users wrote: Hello, As at least one other Qubes user has the same problem, that VMs won't start, I'll add this as special topic. I've made a clean install of Qubes 4-rc2 but ~70% of the time I can't boot the VMs. This includes sys-net, sys-firewall, but also others. I tried to check the logs but I don't get any valuable information. See screenshot. I started the following command in dom0: watch -n 1 xl list When I try to launch a VM I can see that the VMs appears in the xl list output, but the State is -- and the Time(s) is 0.0. After ~30sec the start is aborted with error message: Cannot execute qrexec-daemon. Questions: 1) is anyone running Qubes 4.0-rc2 on a Lenovo X230? 2) is someone additionaly running Coreboot? 3) I am running the Qubes Installation with the default settings, any options to tweak on the Grub command line I created an issue for my VM start problems: https://github.com/QubesOS/qubes-issues/issues/3221 There is no libxenlight error, and I think the problem may be related to the initial run of sys-net. Shutting down sys-net (and all VMs) and starting it again seems to make a difference. Also, there is a RAM allocation problem that (so far) hasn't shown up after I re-start sys-net. 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/1ce1b0a4-5e39-a446-65c1-8ffa0b295f82%40posteo.net. For more options, visit https://groups.google.com/d/optout.
[qubes-users] 4.RC2 CANT create / install VM from local iso
So we need updated docs or somethings broken...
i copied the iso to /home/user from the AppVM tried to create an hvm
appvm got a unrecognized argument... ok
then tried without --hvm... seems ok however. qvm-start
results in a traceback
[dingo@dom0 ~]$ qvm-create BSD --hvm --label blue
usage: qvm-create [-h] [--verbose] [--quiet] [--class CLS]
[--property NAME=VALUE] [--pool VOLUME_NAME=POOL_NAME]
[-P POOL_NAME] [--template VALUE] [--label VALUE]
[--help-classes]
[--root-copy-from FILENAME | --root-move-from FILENAME]
[VMNAME]
qvm-create: error: unrecognized arguments: --hvm
[dingo@dom0 ~]$ qvm-create BSD --label blue
sudo qvm-start BSD --cdrom=/home/dingo/FreeBSD-11.1-RELEASE-amd64-disc1.iso
Traceback (most recent call last):
File "/bin/qvm-start", line 9, in
load_entry_point('qubesadmin==4.0.9', 'console_scripts', 'qvm-start')()
File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_start.py",
line 160, in main
drive_assignment = get_drive_assignment(args.app, args.drive)
File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_start.py",
line 98, in get_drive_assignment
backend_domain_name, ident = drive_str.split(':', 1)
ValueError: not enough values to unpack (expected 2, got 1)
[dingo@dom0 ~]$ qvm-start BSD
--cdrom=/home/dingo/FreeBSD-11.1-RELEASE-amd64-disc1.iso
Traceback (most recent call last):
File "/usr/bin/qvm-start", line 9, in
load_entry_point('qubesadmin==4.0.9', 'console_scripts', 'qvm-start')()
File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_start.py",
line 160, in main
drive_assignment = get_drive_assignment(args.app, args.drive)
File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_start.py",
line 98, in get_drive_assignment
backend_domain_name, ident = drive_str.split(':', 1)
ValueError: not enough values to unpack (expected 2, got 1)
[dingo@dom0 ~]$ qvm-start BSD
--cdrom=/home/dingo/FreeBSD-11.1-RELEASE-amd64-disc1.iso
Traceback (most recent call last):
File "/usr/bin/qvm-start", line 9, in
load_entry_point('qubesadmin==4.0.9', 'console_scripts', 'qvm-start')()
File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_start.py",
line 160, in main
drive_assignment = get_drive_assignment(args.app, args.drive)
File "/usr/lib/python3.5/site-packages/qubesadmin/tools/qvm_start.py",
line 98, in get_drive_assignment
backend_domain_name, ident = drive_str.split(':', 1)
ValueError: not enough values to unpack (expected 2, got 1)
[user@personal dom0]$
--
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/CAKYr3zxnfkSioGJF%3Dvj2JmMdW0YKs5XK7zG2uya5n_vi6S_KhA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Wifi problems on recent updates
On Tuesday, October 24, 2017 at 8:50:18 PM UTC-7, Dan Ballard wrote: > I upgraded my netbook from Linux 4.4.67 to 4.9.35 and lost wifi ability on > it. I believe it was an Atheros chip using the ath9k driver. At least with it > I've been able to boot the old 4.4.67 kernel and retain wireless. > > This week I upgraded my laptop to 4.9.45 and it also lost wifi ability with > an Intel iwlwifi driver. And worse, booting old 4.4 kernels is not working > for it. > > What data do I need to gather to help troubleshoot this and fix it? ticket for the intel issue https://github.com/QubesOS/qubes-issues/issues/3235 -- 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/2a5a3202-cab9-4066-9f8e-6153a627806d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Wifi problems on recent updates
On Tuesday, October 24, 2017 at 8:50:18 PM UTC-7, Dan Ballard wrote: > I upgraded my netbook from Linux 4.4.67 to 4.9.35 and lost wifi ability on > it. I believe it was an Atheros chip using the ath9k driver. At least with it > I've been able to boot the old 4.4.67 kernel and retain wireless. > > This week I upgraded my laptop to 4.9.45 and it also lost wifi ability with > an Intel iwlwifi driver. And worse, booting old 4.4 kernels is not working > for it. > > What data do I need to gather to help troubleshoot this and fix it? So I accidently discover this under an Ubuntu live usb but then it worked under Qubes too With my laptop with the intel wifi chip, while it boots up and rfkill lists it as hard blocked... putting it to sleep and waking it back up somehow fixes this. I have no idea -- 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/53810750-0582-4095-8a85-0e8c67ade884%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
AW: Re: [qubes-users] Re: Update sys-net and sys-firewall to fedora-25?
Hello, >> I hope we can still use a gui with mouse >> clicks to do this stuff in 4.0 lmao I also hope that there is a replacement for Qubes Manager as (even as regular Qubes 3.2 User) Qubes 4.x feels much more complicated, compared to 3.2. The Qubes Manager which was running on an own Workspace was the best way to see what is going on with one glance. It was also possible to make adaptions to several VMs in one go. If I want to switch the Net Template for 3 VMs it is much easier doing so from Qubes Manager instead of opening the upper left menu and click through the submenus to open AppVM Preferences. >> Otherwise once 3.2 is eol, my family >> will find other solutions... As it seems more users have issues with the current release (VMs not starting) and because of hardware dependencies I hope that 4 0 get "fixed". I don't want to buy new hardware for Qubes 4 as I like to stay with Coreboot and the possible hardware which has enough power, is in 12" form factor and support Coreboot AND (!) Qubes 4.x seems to be small. I still don't know if my X230 + Coreboot will run 4.x Thereof I have also migrated back to 3.2. [799] -- 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/jzXYriBYjxKmyG-MqyDxc5tq5eGg7nqIUm4qFUAQjDpclobtK8v2qd7jtgob6nnW59Rp8Pbi3MclMRi3iuIScJ5jPKJLcz0iXlMYnGMvRHw%3D%40protonmail.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: resize vm partition / 4.0RC2
On Friday, October 27, 2017 at 1:58:31 AM UTC-5, Outback Dingo wrote: > Ok so how do we resize a vm partition in 4.0RC2 i see the qvm-resize > is no longer there. qubes-vm-preferences vmname and then change private storage max size -- 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/fa1bf86b-7419-46e5-a710-0e8739810317%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Update sys-net and sys-firewall to fedora-25?
I am testing 4.0r2 right now, and the lack of qubes-manager is a bit difficult to grasp as I didn't use the command line management stuff too much. I'm sure it will come together though. OT: I ended up downloading the official fedora-25 templates and changed to those on 3.2. Thanks all! -- 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/96186ef7-6cb8-4700-a733-420ffed9ca37%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Update sys-net and sys-firewall to fedora-25?
On Saturday, October 21, 2017 at 9:39:44 AM UTC-4, [799] wrote: > Hello, > > > > here you can find my scripts, which will rebuild all your sys-vms: > > All scripts must be made executable with chmod +x FILENAME > > > > 1) qvm-destroy.sh > > this script is a helper script which can be used to kill and remove a VM in > one step > > I'd like to see an option in qvm-kill to get this done: > > something like: qvm-kill --purge > > Until then, this script should work (Warning: it will kill the VM without any > further questions :-) > > > > #!/bin/bash > > # Kill a running AppVM and remove it > > # Usage: qvm-destroy > > echo "Killing VM: $1" > > qvm-kill $1 > > echo "Removing VM: $1" > > qvm-remove $1 > > echo "Waiting for 5s (just to be sure)" > > sleep 5s > > > > 2) create-t-fedora-25-minimal.sh > > Built a custom template which will be used to create the new sys-vms > > mytemplatevm is the name of the new template, which will then be used in step > 3 to build the sys-vms. > > I like to work with clones of the default templates, so that I can always go > back to a standard template. > > I name my VMs with t-... to indicate that this VM is a template VM. > > > > #!/bin/bash > > # Variables > > templatebasevm=fedora-25-minimal > > mytemplatevm=t-fedora-25-minimal > > # Install templatebasevm (just to make sure it is available) > > sudo qubes-dom0-update qubes-template-$templatebasevm > > # Remove existing Template VM > > echo "Killing VM: $mytemplatevm" > > qvm-kill $mytemplatevm > > echo "Removing VM: $mytemplatevm" > > qvm-remove $mytemplatevm > > echo "Waiting for 10s until everything is finished" > > sleep 10s > > # Create a new template based on default template > > echo "Clone $templatebasevm to $mytemplatevm" > > qvm-clone $templatebasevm $mytemplatevm > > # Hide original template > > qvm-prefs -s $templatebasevm internal true > > qvm-prefs -s $mytemplatevm internal false > > # Launch new template > > echo Launch new template-vm $mytemplatevm > > qvm-start --tray $mytemplatevm > > echo "Wait for 10sec until $mytemplatevm VM is up" > > sleep 10s > > # Install Updates and additional packages > > echo "Install updates and additional applications in $mytemplatevm" > > qvm-run $mytemplatevm 'xterm -e "sudo dnf -y update && \ > > sudo dnf -y install mc nano pass langpacks-en langpacks-de > glibc-locale-source qubes-usb-proxy \ > > qubes-input-proxy-sender gnome-terminal terminus-fonts > less dejavu-sans-fonts \ > > NetworkManager NetworkManager-wifi > network-manager-applet wireless-tools dbus-x11 \ > > tinyproxy notification-daemon gnome-keyring > iwl6000g2a-firmware keepass \ > > linux-firmware && \ > > shutdown -h now "' > > echo "Wait until all updates have been installed" > > read -p "Press Enter to continue" > > > > 3) create-my-sysvms.sh > > This script will actually build the new sys-vms (and remove the old one > before). > > It will use the template you have created in step 2) > > > > #!/bin/bash > > systemplate=t-fedora-25-minimal > > ## Kill and remove existing vms > > ./qvm-destroy sys-firewall > > ./qvm-destroy sys-net > > ./qvm-destroy sys-usb > > ## Create a new Net VM > > qvm-create --template $systemplate --label=red --net --mem=300 --vcpus=2 > sys-net > > # Disable PCI_Strictreset > > # Attach PCI-Controllers to AppVM > > qvm-pci --add-class sys-net net > > # Fix Wifi when waking up from Resume > > # https://www.qubes-os.org/doc/wireless-troubleshooting > > sleep 10s > > qvm-run --auto sys-firewall 'xterm -e "sudo echo iwlmvm >> > /rw/config/suspend-module-blacklist && \ > > sudo echo iwlwifi >> > /rw/config/suspend-module-blacklist "' > > qvm-shutdown --wait --force sys-net > > ## Create a new Firewall VM > > qvm-create --template $systemplate --label=orange --proxy --mem=300 --vcpus=2 > sys-firewall > > # Set Net-VM > > qvm-prefs sys-firewall -s netvm sys-net > > ## Create a new USB Qube > > qvm-create --template $systemplate --label=red --net --mem=1024 --vcpus=2 > sys-usb > > # Disable PCI_Strictreset > > qvm-prefs sys-usb -s pci_strictreset false > > # Enable Autostart > > qvm-prefs sys-usb -s autostart true > > # Attach USB-Controllers to AppVM > > qvm-pci --add-class sys-usb usb > > ## Start sys-vms > > qvm-start sys-firewall > > qvm-start sys-usb > > > > 4) create-default-sys-vms.sh > > This script can be used to revert to the default sys-vms (based on the full > fedora-25 default image, not the minimal image) > > > > #!/bin/bash > > ## Kill and remove existing vms > > ./qvm-destroy sys-firewall > > ./qvm-destroy sys-net > > ./qvm-destroy sys-usb > > ## Create a new Net VM > > qvm-create --template fedora-25 --label=red --net --mem=300 --vcpus=2 sys-net > > # Disable PCI_St
Re: [qubes-users] Re: Update sys-net and sys-firewall to fedora-25?
On Saturday, October 21, 2017 at 9:39:44 AM UTC-4, [799] wrote: > Hello, > > > > here you can find my scripts, which will rebuild all your sys-vms: > > All scripts must be made executable with chmod +x FILENAME > > > > 1) qvm-destroy.sh > > this script is a helper script which can be used to kill and remove a VM in > one step > > I'd like to see an option in qvm-kill to get this done: > > something like: qvm-kill --purge > > Until then, this script should work (Warning: it will kill the VM without any > further questions :-) > > > > #!/bin/bash > > # Kill a running AppVM and remove it > > # Usage: qvm-destroy > > echo "Killing VM: $1" > > qvm-kill $1 > > echo "Removing VM: $1" > > qvm-remove $1 > > echo "Waiting for 5s (just to be sure)" > > sleep 5s > > > > 2) create-t-fedora-25-minimal.sh > > Built a custom template which will be used to create the new sys-vms > > mytemplatevm is the name of the new template, which will then be used in step > 3 to build the sys-vms. > > I like to work with clones of the default templates, so that I can always go > back to a standard template. > > I name my VMs with t-... to indicate that this VM is a template VM. > > > > #!/bin/bash > > # Variables > > templatebasevm=fedora-25-minimal > > mytemplatevm=t-fedora-25-minimal > > # Install templatebasevm (just to make sure it is available) > > sudo qubes-dom0-update qubes-template-$templatebasevm > > # Remove existing Template VM > > echo "Killing VM: $mytemplatevm" > > qvm-kill $mytemplatevm > > echo "Removing VM: $mytemplatevm" > > qvm-remove $mytemplatevm > > echo "Waiting for 10s until everything is finished" > > sleep 10s > > # Create a new template based on default template > > echo "Clone $templatebasevm to $mytemplatevm" > > qvm-clone $templatebasevm $mytemplatevm > > # Hide original template > > qvm-prefs -s $templatebasevm internal true > > qvm-prefs -s $mytemplatevm internal false > > # Launch new template > > echo Launch new template-vm $mytemplatevm > > qvm-start --tray $mytemplatevm > > echo "Wait for 10sec until $mytemplatevm VM is up" > > sleep 10s > > # Install Updates and additional packages > > echo "Install updates and additional applications in $mytemplatevm" > > qvm-run $mytemplatevm 'xterm -e "sudo dnf -y update && \ > > sudo dnf -y install mc nano pass langpacks-en langpacks-de > glibc-locale-source qubes-usb-proxy \ > > qubes-input-proxy-sender gnome-terminal terminus-fonts > less dejavu-sans-fonts \ > > NetworkManager NetworkManager-wifi > network-manager-applet wireless-tools dbus-x11 \ > > tinyproxy notification-daemon gnome-keyring > iwl6000g2a-firmware keepass \ > > linux-firmware && \ > > shutdown -h now "' > > echo "Wait until all updates have been installed" > > read -p "Press Enter to continue" > > > > 3) create-my-sysvms.sh > > This script will actually build the new sys-vms (and remove the old one > before). > > It will use the template you have created in step 2) > > > > #!/bin/bash > > systemplate=t-fedora-25-minimal > > ## Kill and remove existing vms > > ./qvm-destroy sys-firewall > > ./qvm-destroy sys-net > > ./qvm-destroy sys-usb > > ## Create a new Net VM > > qvm-create --template $systemplate --label=red --net --mem=300 --vcpus=2 > sys-net > > # Disable PCI_Strictreset > > # Attach PCI-Controllers to AppVM > > qvm-pci --add-class sys-net net > > # Fix Wifi when waking up from Resume > > # https://www.qubes-os.org/doc/wireless-troubleshooting > > sleep 10s > > qvm-run --auto sys-firewall 'xterm -e "sudo echo iwlmvm >> > /rw/config/suspend-module-blacklist && \ > > sudo echo iwlwifi >> > /rw/config/suspend-module-blacklist "' > > qvm-shutdown --wait --force sys-net > > ## Create a new Firewall VM > > qvm-create --template $systemplate --label=orange --proxy --mem=300 --vcpus=2 > sys-firewall > > # Set Net-VM > > qvm-prefs sys-firewall -s netvm sys-net > > ## Create a new USB Qube > > qvm-create --template $systemplate --label=red --net --mem=1024 --vcpus=2 > sys-usb > > # Disable PCI_Strictreset > > qvm-prefs sys-usb -s pci_strictreset false > > # Enable Autostart > > qvm-prefs sys-usb -s autostart true > > # Attach USB-Controllers to AppVM > > qvm-pci --add-class sys-usb usb > > ## Start sys-vms > > qvm-start sys-firewall > > qvm-start sys-usb > > > > 4) create-default-sys-vms.sh > > This script can be used to revert to the default sys-vms (based on the full > fedora-25 default image, not the minimal image) > > > > #!/bin/bash > > ## Kill and remove existing vms > > ./qvm-destroy sys-firewall > > ./qvm-destroy sys-net > > ./qvm-destroy sys-usb > > ## Create a new Net VM > > qvm-create --template fedora-25 --label=red --net --mem=300 --vcpus=2 sys-net > > # Disable PCI_St
[qubes-users] Re: Best laptop for qubes 4.0 ?
On Friday, 27 October 2017 09:17:49 UTC+1, rodge...@gmail.com wrote: > 0. bios > > coreboot > > https://firmware.intel.com/learn/fsp/about-intel-fsp > http://blog.ptsecurity.com/2017/08/disabling-intel-me.html > > 1. cpu > > SLAT (EPT) Intel VT-x > > https://ark.intel.com/Search/FeatureFilter?productType=processors&ExtendedPageTables=true&MarketSegment=Mobile > > 2. ram 32-64gb > > 3. video > > integrated intel HD or nVidia Quadro (?) > > 4. SSD 1TB + > > 5. Disabled micro and webcam > > Is that correctly ? such a laptop will cost about 2000 dollars, maybe its top > Thinkpad workstation, but coreboot flashes only T2xx/T4xx old models. Well, those requirements, I'd go for a W5XX, I believe it's the workstation series that should handle your requests. -- 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/486d5625-4ad5-4ce6-b301-06121c1f85f0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Hardware not supported on Qubes 4.0 rc2
Em quinta-feira, 26 de outubro de 2017 15:37:10 UTC-2, Anirban Kar escreveu: > My Hardware: > Processor- AMD Athlon X2 5200 > Mobo- Asrock 960GC-GS FX > RAM- DDR2 800 MHz 2× 2GB > HDD - Seagate 250 GB SATA 7200 rpm > > > I can install and use Qubes 3.2 without any hassel but facing a hardware > incompatibility notification while installing Qubes 4.0 rc2. Ignoring the > notification and installing Qubes 4.0 rc2 results to a system which does not > have a sys-net vm. I am adding a screenshot of the notification. I am quite > sure that my processor supports AMD-V. Dear Anirban, I have the same problem and I will change my motherboard. But until there, I changed to PV, insert some ip commands(ip link, ip addr, ip route) in /rw/config/rc.local (sys-net and sys-firewall) to enable networking. It is not the best solution but works. -- 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/97bbb59d-2570-449f-b47e-36777a3fd870%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Hardware not supported on Qubes 4.0 rc2
On Thursday, 26 October 2017 13:37:10 UTC-4, Anirban Kar wrote: > My Hardware: > Processor- AMD Athlon X2 5200 > Mobo- Asrock 960GC-GS FX > RAM- DDR2 800 MHz 2× 2GB > HDD - Seagate 250 GB SATA 7200 rpm > > > I can install and use Qubes 3.2 without any hassel but facing a hardware > incompatibility notification while installing Qubes 4.0 rc2. Ignoring the > notification and installing Qubes 4.0 rc2 results to a system which does not > have a sys-net vm. I am adding a screenshot of the notification. I am quite > sure that my processor supports AMD-V. iommu: 'no' Says it all. Read the release notes and blog posts on rc1 and rc2. PV vs. HVM was the difference between the two. qvm-prefs sys-net virt_mode pv This may work, but future versions of qubes are going away from PV all together, so AMD-Vi (IOMMU) will be a requirement. I upgraded my hardware for this reason. -- 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/9e711662-fa28-47f4-b1db-009a8485d2a3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Best laptop for qubes 4.0 ?
0. bios coreboot https://firmware.intel.com/learn/fsp/about-intel-fsp http://blog.ptsecurity.com/2017/08/disabling-intel-me.html 1. cpu SLAT (EPT) Intel VT-x https://ark.intel.com/Search/FeatureFilter?productType=processors&ExtendedPageTables=true&MarketSegment=Mobile 2. ram 32-64gb 3. video integrated intel HD or nVidia Quadro (?) 4. SSD 1TB + 5. Disabled micro and webcam Is that correctly ? such a laptop will cost about 2000 dollars, maybe its top Thinkpad workstation, but coreboot flashes only T2xx/T4xx old models. -- 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/f645d542-03f2-4258-ab94-3e6d706ab2ff%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Hardware not supported on Qubes 4.0 rc2
On Friday, 27 October 2017 08:58:55 UTC+5:30, Anirban Kar wrote: > Here is the HCL attached as per your request. Also sending the .cpio.gz as attachment. -- 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/9144d45c-9cb0-4d8d-b1f1-71b440cffb0d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. Qubes-HCL-ASRock-960GC_GS_FX-20171027-123548.cpio.gz Description: Binary data
