Re: [qubes-users] Re: new Desktop build recommendation
On Friday, December 8, 2017 at 5:28:12 PM UTC-8, tai...@gmx.com wrote: > On 12/08/2017 04:54 PM, Wael Nasreddine wrote: > > > On Friday, December 8, 2017 at 12:07:56 AM UTC-8, tai...@gmx.com wrote: > >> On 12/08/2017 02:43 AM, Yethal wrote: > >> > >>> W dniu czwartek, 7 grudnia 2017 21:23:18 UTC+1 użytkownik Wael Nasreddine > >>> napisał: > >>>> Hello, > >>>> > >>>> I'm looking to build a new Desktop specifically for Qubes OS, so my most > >>>> important requirement is compatibility. I currently have 64GB (4 x 16GB) > >>>> 288-Pin DDR4 SDRAM DDR4 3400 (PC4 27200)[0] that I'd like to use, and > >>>> I'm looking for a recommendation for the motherboard and CPU. Preferably > >>>> a 6+ cores CPU. What do you guys use? > >>>> > >>>> I'm aware of the HCL page, but I'm mostly interested in knowing your > >>>> personal experience with your current hardware. > >>>> > >>>> [0]: https://www.newegg.com/Product/Product.aspx?Item=N82E16820232264 > >>> Zero issues with i7-6800K on an AsRock X99 board. Has PS/2 port, > >>> disabling Management Engine is possible via built in flashing tool, all > >>> hardware sensors were detected and it supports PCI-E bifurcation > >>> alongside SR-IOV. I'm running Mini-itx version which may be unsuitable > >>> for your needs as it only takes 32GB of ram but it would be pretty safe > >>> to assume that full-size AsRock X99 motherboards would also be fully > >>> compatible with Qubes. > >> That isn't disabling ME, nor ME cleaner - you can NOT disable ME - it is > >> impossible even the HAP tool doesn't do so. > > What's the ME and why disable it? > > > >> Your only hope is to buy hardware without it such as the new enough to > >> be useful Socket G34 and C32 AMD PRE-PSP Systems, boards KGPE-D16 and > >> KCMA-D8 have libre firmware available and can play video games in a VM > >> via IOMMU-GFX, they also have dual onboard separate USB controllers (you > >> can use the second via a breakout bracket) > > So I looked at both of these boards[0], they take a DDR3 board, but I found > > this one[1] that takes DDR4, does it still have opensource firmware? > > > > [0]: > > https://www.newegg.com/Product/Productcompare.aspx?CompareItemList=%2D1%7C13%2D131%2D670%5E13%2D131%2D670%2C13%2D131%2D643%5E13%2D131%2D643 > > [1]: https://www.newegg.com/Product/Product.aspx?Item=N82E16813132257 > > > That is an entirely unrelated motherboard, the only thing in common is > that they re-used the model suffix "D16" other than that is is > completely different and as it is intel no it can't and it doesn't. > > Just get a KGPE-D16 or KCMA-D8 - they're great boards - not only do they > have libre firmware but they also have a secure libre OpenBMC firmware > for remote management. > https://www.raptorengineering.com/coreboot/kgpe-d16-bmc-port-status.php > > The D16 comes with the required BMC module (ASMB4-iKVM or ASMB5-iKVM) > but the D8 doesn't. > > Sell your DDR4 RAM, the only thing with open source firmware that > accepts DDR4 is the TALOS 2 for $4K - while that is an average price for > server hardware in its performance class (actually a good deal compared > with intel where a single xeon CPU alone costs thousands and only has > one thread per core vs POWER9 8 SMT threads per core) it is still a lot > of money unless you have a need for incredible speed and or incredible > security (POWER9 is open source hardware and entirely owner owner > controlled with no hardware code signing enforcement one can even modify > the microcode) What do you think of this build https://screenshots.firefox.com/fHb14uahx7lEeAGe/secure.newegg.com ? I'm still missing cooler, power supply and possibly a TPM, I'd love your recommendation for these. -- 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/171938a2-9f55-4409-be23-42a3216d7633%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: new Desktop build recommendation
On Friday, December 8, 2017 at 12:07:56 AM UTC-8, tai...@gmx.com wrote: > On 12/08/2017 02:43 AM, Yethal wrote: > > > W dniu czwartek, 7 grudnia 2017 21:23:18 UTC+1 użytkownik Wael Nasreddine > > napisał: > >> Hello, > >> > >> I'm looking to build a new Desktop specifically for Qubes OS, so my most > >> important requirement is compatibility. I currently have 64GB (4 x 16GB) > >> 288-Pin DDR4 SDRAM DDR4 3400 (PC4 27200)[0] that I'd like to use, and I'm > >> looking for a recommendation for the motherboard and CPU. Preferably a 6+ > >> cores CPU. What do you guys use? > >> > >> I'm aware of the HCL page, but I'm mostly interested in knowing your > >> personal experience with your current hardware. > >> > >> [0]: https://www.newegg.com/Product/Product.aspx?Item=N82E16820232264 > > Zero issues with i7-6800K on an AsRock X99 board. Has PS/2 port, disabling > > Management Engine is possible via built in flashing tool, all hardware > > sensors were detected and it supports PCI-E bifurcation alongside SR-IOV. > > I'm running Mini-itx version which may be unsuitable for your needs as it > > only takes 32GB of ram but it would be pretty safe to assume that full-size > > AsRock X99 motherboards would also be fully compatible with Qubes. > That isn't disabling ME, nor ME cleaner - you can NOT disable ME - it is > impossible even the HAP tool doesn't do so. What's the ME and why disable it? > > Your only hope is to buy hardware without it such as the new enough to > be useful Socket G34 and C32 AMD PRE-PSP Systems, boards KGPE-D16 and > KCMA-D8 have libre firmware available and can play video games in a VM > via IOMMU-GFX, they also have dual onboard separate USB controllers (you > can use the second via a breakout bracket) So I looked at both of these boards[0], they take a DDR3 board, but I found this one[1] that takes DDR4, does it still have opensource firmware? [0]: https://www.newegg.com/Product/Productcompare.aspx?CompareItemList=%2D1%7C13%2D131%2D670%5E13%2D131%2D670%2C13%2D131%2D643%5E13%2D131%2D643 [1]: https://www.newegg.com/Product/Product.aspx?Item=N82E16813132257 -- 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/faf6e263-8440-4c85-b5a8-6694d33ad830%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Q4RC3 - win7 install problems
On Sunday, December 3, 2017 at 2:43:53 PM UTC-8, gang...@oregonstate.edu wrote: > On Sunday, December 3, 2017 at 3:43:06 AM UTC-8, Jean-Luc Duriez wrote: > > Hi Qubists > > > > This is my first attempt to install Windows 7 in my Qubes system (Q4RC3): > > > > --- > > [jl@dom0 ~](0) qvm-create win7 --class StandaloneVM --label yellow > > > > [jl@dom0 ~](0) qvm-ls > > NAME STATECLASS LABEL TEMPLATE NETVM > > ... > > win7 Halted StandaloneVM yellow - sys-firewall > > > > [jl@dom0 ~](0) qvm-block > > BACKEND:DEVID DESCRIPTION USED BY > > dom0:sr0 CDDVDW_GP70N (GSP1RMCHPXFRER_FR_DVD) > > > > [jl@dom0 ~](0) qvm-start win7 --crom dom0:sr0 > > --- > > > > > > I get a console terminal from the win7 VM with a brief message and it > > closes after a few seconds (see attached sreenshot). I also tried with a > > .iso file but the same issue occurs. Am I doing things wrong ? > > > > Of course I checked the Win7 DVD and it is readable and fine. > > > > Any clue appreciated. Thanks. > > > > Jean-Luc > > I am experiencing the exact same issue. I also tried the "Boot Qube From > CD-ROM" option in the VM settings applet, but the "OK" option after selecting > sr0 has no response. I have the same problem installing Arch. See https://groups.google.com/forum/#!topic/qubes-users/8Yqpmwjs2pg -- 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/b2734fa5-ef01-4d59-bc4c-654da5ed99fe%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] new Desktop build recommendation
Hello, I'm looking to build a new Desktop specifically for Qubes OS, so my most important requirement is compatibility. I currently have 64GB (4 x 16GB) 288-Pin DDR4 SDRAM DDR4 3400 (PC4 27200)[0] that I'd like to use, and I'm looking for a recommendation for the motherboard and CPU. Preferably a 6+ cores CPU. What do you guys use? I'm aware of the HCL page, but I'm mostly interested in knowing your personal experience with your current hardware. [0]: https://www.newegg.com/Product/Product.aspx?Item=N82E16820232264 -- 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/e63c01c1-7c06-4ef4-a483-7d749311d2ac%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Bug in libxenlight
On Tuesday, November 28, 2017 at 10:28:38 AM UTC-8,
bm-2ctrx1tl5lg8cfa...@bitmessage.ch wrote:
> When I tried create new VM based on Fedora I saw something strange because
> it don't want run even if I created VM based on Debian. And when I open
> terminal and for test run this commands I see this.
I had this issue installing 4-RC2, not sure what it is due. First, check that
your system is capable of VT-d and VT-x. If both your CPU and your chipset
supports it, make sure it is enabled in the bios. Check `sudo xl dmesg | grep
VT` for hints. If VT-x and VT-d are enabled and you still get this error, try
this workaround:
- Make sure it's a fresh install (revert your progress so far)
- When you are greeted with the setup after install, hit Ctrl-Alt-F3 to go to
the console. If you got a black screen, try a few times Alt-F1 and Alt-F3 until
you can loging
- Start the following bash loop (what's inside the back ticks) ` while true; do
qvm-ls | grep -v NAME | awk '{print $1}' | xargs -I{} sudo qvm-prefs {}
virt_mode pv; sleep 0.5; done`. This will continuously change the virt_mode to
PV for all VMs
- Switch back to the setup with Alt-F2
- Continue setup, but do not login or reboot
- Switch back to Ctrl-Alt-F3
- Kill the loop and run `sudo qubes-dom0-update
--enablerepo=qubes-dom0-current-testing`
- Switch all VMs back to HVM: `qvm-ls | grep -v NAME | awk '{print $1}' | xargs
-I{} sudo qvm-prefs {} virt_mode hvm`
- Reboot
Sources:
- https://groups.google.com/forum/#!topic/qubes-users/Go04b5VsYfw
- https://groups.google.com/forum/#!topic/qubes-users/VD_U4k8qrbs
--
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/9b01ce82-0d64-48d1-a17b-28b09906cead%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Random sudden reboots
On Monday, November 27, 2017 at 6:25:58 PM UTC-8, Andrew David Wong wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > On 2017-11-27 13:37, Wael Nasreddine wrote: > > On Monday, November 27, 2017 at 11:09:12 AM UTC-8, David Hobach > > wrote: > >> On 11/27/2017 07:57 PM, David Hobach wrote: > >>> On 11/27/2017 07:47 AM, Wael Nasreddine wrote: > >>>> I'm running 4.0-RC2 on Asrock Z170 pro4/i7-6700k and I got > >>>> two hard reboots in the last few hours, often around the time > >>>> I start a VM. I do not see anything in the log. > >>>> > >>>> P.S: I've been running Citrix XenServer for two years on this > >>>> machine with no issues. > >>>> > >>>> [...] > >>> > >>> Yes, I can confirm that issue (except for the "around the time > >>> I start a VM"). Didn't find anything yet neither, my log looks > >>> similar. Some memory balancing tends to be the last entry. > >> > >> P.S.: I run a T530 with coreboot, some i5, ME cleaned. > >> > >> I'm not sure whether it's a heat issue, but I'd guess not as I > >> had tested it until ~95 Celsius and it tends to run at max 80 > >> with Qubes. I think it reboots at ~100 Celsius. > >> > >> But yes, it tends to happen at relatively high load. > > > > It happened to me regardless of load, I had only essential VMs with > > one Firefox opened the last time it happened, also I was not trying > > to start up a VM. > > > > It looks like you may be encountering this known bug: > > https://github.com/QubesOS/qubes-issues/issues/3079 > Not sure that it is, #3079 is about kernel killing X due to OOM, but my issue is that the entire server reboots, so the screen goes black and a few seconds later I'm greeted by the bios boot. -- 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/7b7ad5ef-e92a-475f-ac91-1e7671d7fb7e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Random sudden reboots
On Monday, November 27, 2017 at 11:09:12 AM UTC-8, David Hobach wrote: > On 11/27/2017 07:57 PM, David Hobach wrote: > > On 11/27/2017 07:47 AM, Wael Nasreddine wrote: > >> I'm running 4.0-RC2 on Asrock Z170 pro4/i7-6700k and I got two hard > >> reboots in the last few hours, often around the time I start a VM. I > >> do not see anything in the log. > >> > >> P.S: I've been running Citrix XenServer for two years on this machine > >> with no issues. > >> > >> Nov 26 22:36:38 dom0 sudo[911]: pam_unix(sudo:session): session closed > >> for user root > >> Nov 26 22:36:38 dom0 audit[911]: USER_END pid=911 uid=0 auid=1000 > >> ses=2 msg='op=PAM:session_close > >> grantors=pam_keyinit,pam_limits,pam_keyinit,pam_limits,pam_systemd,pam_ > >> Nov 26 22:36:38 dom0 audit[911]: CRED_DISP pid=911 uid=0 auid=1000 > >> ses=2 msg='op=PAM:setcred grantors=pam_env,pam_unix acct="root" > >> exe="/usr/bin/sudo" hostname=? addr=? > >> Nov 26 22:36:38 dom0 kernel: audit: type=1106 > >> audit(1511764598.490:447): pid=911 uid=0 auid=1000 ses=2 > >> msg='op=PAM:session_close grantors=pam_keyinit,pam_limits,pam_keyi > >> Nov 26 22:36:38 dom0 kernel: audit: type=1104 > >> audit(1511764598.490:448): pid=911 uid=0 auid=1000 ses=2 > >> msg='op=PAM:setcred grantors=pam_env,pam_unix acct="root" exe="/us > >> Nov 26 22:36:38 dom0 qmemman.daemon.algo[2304]: > >> balance_when_enough_memory(xen_free_memory=97794733, > >> total_mem_pref=5101760998.4, total_available_memory=60546306417.6) > >> Nov 26 22:36:38 dom0 qmemman.daemon.algo[2304]: > >> left_memory=24233992215 acceptors_count=1 > >> -- Reboot -- > >> Nov 26 22:38:00 dom0 systemd-journald[240]: Runtime journal > >> (/run/log/journal/) is 8.0M, max 196.7M, 188.7M free. > >> Nov 26 22:38:00 dom0 kernel: Linux version > >> 4.9.56-21.pvops.qubes.x86_64 (user@build-fedora4) (gcc version 6.4.1 > >> 20170727 (Red Hat 6.4.1-1) (GCC) ) #1 SMP Wed Oct 18 00:2 > >> Nov 26 22:38:00 dom0 kernel: Command line: placeholder > >> root=UUID=9b846465-f59a-4f83-adfa-5468c915defd ro > >> rootflags=subvol=root rd.luks.uuid=luks-1b3c3eda-7836-443a-bc07- > >> Nov 26 22:38:00 dom0 kernel: x86/fpu: Supporting XSAVE feature 0x001: > >> 'x87 floating point registers' > >> Nov 26 22:38:00 dom0 kernel: x86/fpu: Supporting XSAVE feature 0x002: > >> 'SSE registers' > >> Nov 26 22:38:00 dom0 kernel: x86/fpu: Supporting XSAVE feature 0x004: > >> 'AVX registers' > >> Nov 26 22:38:00 dom0 kernel: x86/fpu: xstate_offset[2]: 576, > >> xstate_sizes[2]: 256 > >> Nov 26 22:38:00 dom0 kernel: x86/fpu: Enabled xstate features 0x7, > >> context size is 832 bytes, using 'standard' format. > >> Nov 26 22:38:00 dom0 kernel: x86/fpu: Using 'eager' FPU context switches. > >> Nov 26 22:38:00 dom0 kernel: Released 0 page(s) > >> Nov 26 22:38:00 dom0 kernel: e820: BIOS-provided physical RAM map: > >> Nov 26 22:38:00 dom0 kernel: Xen: [mem > >> 0x-0x0009bfff] usable > >> Nov 26 22:38:00 dom0 kernel: Xen: [mem > >> 0x0009c800-0x000f] reserved > >> Nov 26 22:38:00 dom0 kernel: Xen: [mem > >> 0x0010-0x67e1] usable > >> Nov 26 22:38:00 dom0 kernel: Xen: [mem > >> 0x67e2-0x67e20fff] ACPI NVS > >> Nov 26 22:38:00 dom0 kernel: Xen: [mem > >> 0x67e21000-0x67e6afff] reserved > >> Nov 26 22:38:00 dom0 kernel: Xen: [mem > >> 0x67e6b000-0x67ebcfff] usable > >> Nov 26 22:38:00 dom0 kernel: Xen: [mem > >> 0x67ebd000-0x68bedfff] reserved > >> Nov 26 22:38:00 dom0 kernel: Xen: [mem > >> 0x68bee000-0x6ee48fff] usable > >> Nov 26 22:38:00 dom0 kernel: Xen: [mem > >> 0x6ee49000-0x6f7adfff] reserved > >> Nov 26 22:38:00 dom0 kernel: Xen: [mem > >> 0x6f7ae000-0x6ff99fff] ACPI NVS > >> Nov 26 22:38:00 dom0 kernel: Xen: [mem > >> 0x6ff9a000-0x6fffefff] ACPI data > >> Nov 26 22:38:00 dom0 kernel: Xen: [mem > >> 0x6000-0x6fff] usable > >> Nov 26 22:38:00 dom0 kernel: Xen: [mem > >> 0x7000-0x77ff] reserved > >> Nov 26 22:38:00 dom0 kernel: Xen: [mem > >> 0xe000-0xefff] reserved > >> Nov 26 22:38:00 dom0 kernel: Xen: [mem > >&g
Re: [qubes-users] Re: unable to start a freshly created VM (the first VM on a fresh install). Qubes 4.0-RC2
On Monday, November 27, 2017 at 1:19:04 AM UTC-8, Tom Zander wrote: > On Monday, 27 November 2017 07:03:51 CET Wael Nasreddine wrote: > > I'm trying to create a Standalone VM to run ArchLinux dedicated for work, > > but the VM fails to start, > > Where did you get the archlinux VM from? I created a new VM, not based on any template (a menu option in the create new VM prompt). The VM never got passed Bios boot, similar to [0] without the window re-appearing; So I was never able to actually install it. > > I successfully managed to get this working over the weekend by; > a) following the basics (dns install etc) here (point3 & 4). > Don’t do point 5 - 10. > https://www.qubes-os.org/doc/building-archlinux-template/ > > b) follow the simplest guide from this report; > https://github.com/QubesOS/qubes-issues/issues/3185 > > Then continue with points 10 - from the official docs. > Thanks for the tip, I might try that as well. > > Generally, after a weekend of intense working with qubes4r2 (testing) I > would say that creating new VMs based on a template and starting them is a > bit of a hit-and-miss. > I’m guessing that the daemon in dom0 has some race conditions that sometimes > leaves newly created vms broken. Stress the system less and it seems to work > more stable. > > -- > Tom Zander > Blog: https://zander.github.io > Vlog: https://vimeo.com/channels/tomscryptochannel [0]: https://github.com/QubesOS/qubes-issues/issues/3185#issuecomment-338470156 -- 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/f5513f01-80ba-468f-8f1f-b1e2aabbda8f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Random sudden reboots
I'm running 4.0-RC2 on Asrock Z170 pro4/i7-6700k and I got two hard reboots in the last few hours, often around the time I start a VM. I do not see anything in the log. P.S: I've been running Citrix XenServer for two years on this machine with no issues. Nov 26 22:36:38 dom0 sudo[911]: pam_unix(sudo:session): session closed for user root Nov 26 22:36:38 dom0 audit[911]: USER_END pid=911 uid=0 auid=1000 ses=2 msg='op=PAM:session_close grantors=pam_keyinit,pam_limits,pam_keyinit,pam_limits,pam_systemd,pam_ Nov 26 22:36:38 dom0 audit[911]: CRED_DISP pid=911 uid=0 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_env,pam_unix acct="root" exe="/usr/bin/sudo" hostname=? addr=? Nov 26 22:36:38 dom0 kernel: audit: type=1106 audit(1511764598.490:447): pid=911 uid=0 auid=1000 ses=2 msg='op=PAM:session_close grantors=pam_keyinit,pam_limits,pam_keyi Nov 26 22:36:38 dom0 kernel: audit: type=1104 audit(1511764598.490:448): pid=911 uid=0 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_env,pam_unix acct="root" exe="/us Nov 26 22:36:38 dom0 qmemman.daemon.algo[2304]: balance_when_enough_memory(xen_free_memory=97794733, total_mem_pref=5101760998.4, total_available_memory=60546306417.6) Nov 26 22:36:38 dom0 qmemman.daemon.algo[2304]: left_memory=24233992215 acceptors_count=1 -- Reboot -- Nov 26 22:38:00 dom0 systemd-journald[240]: Runtime journal (/run/log/journal/) is 8.0M, max 196.7M, 188.7M free. Nov 26 22:38:00 dom0 kernel: Linux version 4.9.56-21.pvops.qubes.x86_64 (user@build-fedora4) (gcc version 6.4.1 20170727 (Red Hat 6.4.1-1) (GCC) ) #1 SMP Wed Oct 18 00:2 Nov 26 22:38:00 dom0 kernel: Command line: placeholder root=UUID=9b846465-f59a-4f83-adfa-5468c915defd ro rootflags=subvol=root rd.luks.uuid=luks-1b3c3eda-7836-443a-bc07- Nov 26 22:38:00 dom0 kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' Nov 26 22:38:00 dom0 kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' Nov 26 22:38:00 dom0 kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' Nov 26 22:38:00 dom0 kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 Nov 26 22:38:00 dom0 kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format. Nov 26 22:38:00 dom0 kernel: x86/fpu: Using 'eager' FPU context switches. Nov 26 22:38:00 dom0 kernel: Released 0 page(s) Nov 26 22:38:00 dom0 kernel: e820: BIOS-provided physical RAM map: Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x-0x0009bfff] usable Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x0009c800-0x000f] reserved Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x0010-0x67e1] usable Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x67e2-0x67e20fff] ACPI NVS Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x67e21000-0x67e6afff] reserved Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x67e6b000-0x67ebcfff] usable Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x67ebd000-0x68bedfff] reserved Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x68bee000-0x6ee48fff] usable Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x6ee49000-0x6f7adfff] reserved Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x6f7ae000-0x6ff99fff] ACPI NVS Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x6ff9a000-0x6fffefff] ACPI data Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x6000-0x6fff] usable Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x7000-0x77ff] reserved Nov 26 22:38:00 dom0 kernel: Xen: [mem 0xe000-0xefff] reserved Nov 26 22:38:00 dom0 kernel: Xen: [mem 0xfe00-0xfe010fff] reserved Nov 26 22:38:00 dom0 kernel: Xen: [mem 0xfec0-0xfec00fff] reserved Nov 26 22:38:00 dom0 kernel: Xen: [mem 0xfed9-0xfed91fff] reserved Nov 26 22:38:00 dom0 kernel: Xen: [mem 0xfee0-0xfeef] reserved Nov 26 22:38:00 dom0 kernel: Xen: [mem 0xff00-0x] reserved Nov 26 22:38:00 dom0 kernel: Xen: [mem 0x0001-0x000191f95fff] usable -- 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/9959bd62-686c-4cd2-8d27-03f6f1b70478%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: unable to start a freshly created VM (the first VM on a fresh install). Qubes 4.0-RC2
On Sunday, November 26, 2017 at 9:14:57 PM UTC-8, Yuraeitha wrote:
> On Monday, November 27, 2017 at 1:06:55 AM UTC, Wael Nasreddine wrote:
> > Hello,
> >
> > I'm trying to create a Standalone VM to run ArchLinux dedicated for work,
> > but the VM fails to start, and the following message appears in the journal:
> >
> > Nov 26 16:48:13 dom0 qmemman.systemstate[2304]: Xen free = 48447639678 too
> > small for satisfy assignments! assigned_but_unused=48423368750,
> > domdict={'3': {'memory_maximum': 4194304000, 'slow_memset_react': False,
> > 'no_progress': False, 'last_target': 4179545269, 'memory_current':
> > 4181286912, 'id': '3', 'mem_used': 353308672, 'memory_actual': 4181286912},
> > '8': {'memory_maximum': 150994944, 'slow_memset_react': False,
> > 'no_progress': False, 'last_target': 150994944, 'memory_current':
> > 150994944, 'id': '8', 'mem_used': None, 'memory_actual': 150994944}, '1':
> > {'memory_maximum': 419430400, 'slow_memset_react': False, 'no_progress':
> > False, 'last_target': 402653184, 'memory_current': 417345536, 'id': '1',
> > 'mem_used': None, 'memory_actual': 417345536}, '5': {'memory_maximum':
> > 4194304000, 'slow_memset_react': False, 'no_progress': False,
> > 'last_target': 4179396425, 'memory_current': 4181147648, 'id': '5',
> > 'mem_used': 337453056, 'memory_actual': 4181147648}, '2':
> > {'memory_maximum': 150994944, 'slow_memset_react': False, 'no_progress':
> > False, 'last_target': 150994944, 'memory_current': 150994944, 'id': '2',
> > 'mem_used': None, 'memory_actual': 150994944}, '0': {'memory_maximum':
> > 68253908992, 'slow_memset_react': False, 'no_progress': False,
> > 'last_target': 52683417646, 'memory_current': 4260048896, 'id': '0',
> > 'mem_used': 929218560, 'memory_actual': 52683417646}, '11':
> > {'memory_maximum': 4194304000, 'slow_memset_react': False, 'no_progress':
> > False, 'last_target': 401604608, 'memory_current': 419430400, 'id': '11',
> > 'mem_used': None, 'memory_actual': 419430400}, '12': {'memory_maximum':
> > 150994944, 'slow_memset_react': False, 'no_progress': False, 'last_target':
> > 150994944, 'memory_current': 150994944, 'id': '12', 'mem_used': None,
> > 'memory_actual': 150994944}, '7': {'memory_maximum': 4194304000,
> > 'slow_memset_react': False, 'no_progress': False, 'last_target':
> > 4180124003, 'memory_current': 4181835776, 'id': '7', 'mem_used': 402833408,
> > 'memory_actual': 4181835776}, '6': {'memory_maximum': 150994944,
> > 'slow_memset_react': False, 'no_progress': False, 'last_target': 150994944,
> > 'memory_current': 150994944, 'id': '6', 'mem_used': None, 'memory_actual':
> > 150994944}, '4': {'memory_maximum': 150994944, 'slow_memset_react': False,
> > 'no_progress': False, 'last_target': 150994944, 'memory_current':
> > 150994944, 'id': '4', 'mem_used': None, 'memory_actual': 150994944}}
> >
> >
> > It seems to be a memory issue, which is weird given I have only the
> > essentials + personal VM running on a 64Gb system.
> >
> > I posted as many details about the issue and my system in this gist
> > https://gist.github.com/kalbasit/cb3d6a0a9f068f819706d08fe073b18a
> >
> > Am I doing it wrong or is there a problem with my installation?
>
> I can't say if it'll work. However if this feature is turned on (should be by
> default), maybe try disable the dynamic RAM allocation in the VM-preferences
> GUI advanced tab, or with qvm-prefs in terminal?
>
> It's similar with Windows VM atm, it seemingly has no Qubes tools inside the
> VM, so it can't talk with it, and thereby not dynamically allocate any
> memory.
>
> Maybe this is the fault?
Removing the dynamic memory did get rid of the error, but the VM is still dying
on boot.
--
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/cd015faa-dd2b-4de9-9072-72457e0636a7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[qubes-users] unable to start a freshly created VM (the first VM on a fresh install). Qubes 4.0-RC2
Hello,
I'm trying to create a Standalone VM to run ArchLinux dedicated for work, but
the VM fails to start, and the following message appears in the journal:
Nov 26 16:48:13 dom0 qmemman.systemstate[2304]: Xen free = 48447639678 too
small for satisfy assignments! assigned_but_unused=48423368750, domdict={'3':
{'memory_maximum': 4194304000, 'slow_memset_react': False, 'no_progress':
False, 'last_target': 4179545269, 'memory_current': 4181286912, 'id': '3',
'mem_used': 353308672, 'memory_actual': 4181286912}, '8': {'memory_maximum':
150994944, 'slow_memset_react': False, 'no_progress': False, 'last_target':
150994944, 'memory_current': 150994944, 'id': '8', 'mem_used': None,
'memory_actual': 150994944}, '1': {'memory_maximum': 419430400,
'slow_memset_react': False, 'no_progress': False, 'last_target': 402653184,
'memory_current': 417345536, 'id': '1', 'mem_used': None, 'memory_actual':
417345536}, '5': {'memory_maximum': 4194304000, 'slow_memset_react': False,
'no_progress': False, 'last_target': 4179396425, 'memory_current': 4181147648,
'id': '5', 'mem_used': 337453056, 'memory_actual': 4181147648}, '2':
{'memory_maximum': 150994944, 'slow_memset_react': False, 'no_progress': False,
'last_target': 150994944, 'memory_current': 150994944, 'id': '2', 'mem_used':
None, 'memory_actual': 150994944}, '0': {'memory_maximum': 68253908992,
'slow_memset_react': False, 'no_progress': False, 'last_target': 52683417646,
'memory_current': 4260048896, 'id': '0', 'mem_used': 929218560,
'memory_actual': 52683417646}, '11': {'memory_maximum': 4194304000,
'slow_memset_react': False, 'no_progress': False, 'last_target': 401604608,
'memory_current': 419430400, 'id': '11', 'mem_used': None, 'memory_actual':
419430400}, '12': {'memory_maximum': 150994944, 'slow_memset_react': False,
'no_progress': False, 'last_target': 150994944, 'memory_current': 150994944,
'id': '12', 'mem_used': None, 'memory_actual': 150994944}, '7':
{'memory_maximum': 4194304000, 'slow_memset_react': False, 'no_progress':
False, 'last_target': 4180124003, 'memory_current': 4181835776, 'id': '7',
'mem_used': 402833408, 'memory_actual': 4181835776}, '6': {'memory_maximum':
150994944, 'slow_memset_react': False, 'no_progress': False, 'last_target':
150994944, 'memory_current': 150994944, 'id': '6', 'mem_used': None,
'memory_actual': 150994944}, '4': {'memory_maximum': 150994944,
'slow_memset_react': False, 'no_progress': False, 'last_target': 150994944,
'memory_current': 150994944, 'id': '4', 'mem_used': None, 'memory_actual':
150994944}}
It seems to be a memory issue, which is weird given I have only the essentials
+ personal VM running on a 64Gb system.
I posted as many details about the issue and my system in this gist
https://gist.github.com/kalbasit/cb3d6a0a9f068f819706d08fe073b18a
Am I doing it wrong or is there a problem with my installation?
--
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/5d6d6580-be7f-46c4-9c35-70f40d7544dd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: update dom0 offline
On Sunday, November 26, 2017 at 1:12:49 AM UTC-8, Yuraeitha wrote:
> On Saturday, November 25, 2017 at 6:33:29 PM UTC, Wael Nasreddine wrote:
> > Hello,
> >
> > As I described in the other topic titled "How To Replace Libvirt Drivers";
> > Upon installation, I get the error `libvirtError.libvirt: libxenlight
> > failed to create new domain “domain name”` and updating the system seems to
> > have helped. I want to attempt to update all packages before continuing the
> > initial_setup, so how can I update dom0 offline?
> >
> > Another option I have is to perform a net-install, I tried using
> > `https://mirrors.kernel.org/qubes/repo/yum/r4.0/current-testing/dom0/fc25/`
> > as an additional repository in the installer but I got "Error setting up
> > base repository".
> >
> > Wael
>
> Do you have any solid reasoning for suspecting these packages? It's not
> always the package itself that is the problem, but a package or a tie to
> another patckage, or that other package, which is causing the issue. Simply
> replacing libvirt probably won't do you much good, especially if you need to
> find all those possible dependencies on something so fundamental as libvirt
> in Qubes.
>
> It might be better to first find out why it happens, and then perform a clean
> re-install.
So after some 10 re-installs, I finally managed to get it error-free all the
way. I do not know which package it is (although I can tell you libvirt was not
updated) but there is definitely a broken package in RC2. I ended up
brute-forcing the virt_mode to PV[0] in order to go through the setup without
any errors; knowing how to switch the default to PV would have helped,
unfortunately I'm fairely new to Qubes (first install). Once the initial setup
was over, I performed a qubes-dom0-update with testing repo enabled, switched
all VMs back to hvm and voila works like a charm.
>
> Also Qubes 4 RC-3 will be out either tomorrow, the day after tomorrow, or if
> freezing failed, then possibly next week.
> https://www.qubes-os.org/doc/releases/4.0/schedule/ It's uncertain for sure,
> however, you have reasonable chances are that it'll be out tomorrow.
>
I'm sure RC-3 would work out of the box, too bad I got stubborn on getting it
running this weekend :D
> However, are you sure you got VT-D enabled in your UEFI (BIOS)? You also
> enabled Virtualisation in general, in case the motherboard has a double
> enable/disable function like some boards do? Libvirt errors does sound like
> it could be related to missing hardware features that Qubes 4 requires.
>
> Remember that Qubes 4 is much less happy with missing security features,
> compared to Qubes 3.2. You muight get Qubes 4 running without, but it will
> likely be ugly, i.e. like your libvirt errors.
>
> There is even talks to prevent Qubes 4 to install at all if the hardware is
> not living up to the security requirements, in order to avoid situations like
> this. For example, something like that might even be in Qubes 4 RC-3 for all
> we know.
My hardware is good, but I do not have a TPM yet. I'm thinking of switching the
motherboard/CPU with something more performant, maybe a Xeon based system but I
want to play more with Qubes before I do that. Any recommendation on hardware?
>
> You made absolutely sure, that your hardware meets the requirements, and also
> absolutely sure, that all of them are enabled?
Yes :)
[0]: while true; do qvm-ls | grep -v NAME | awk '{print $1}' | xargs -I{} sudo
qvm-prefs {} virt_mode pv; sleep 0.5; done
--
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/893d6e91-ca42-428a-a5d2-bade68bd96e4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: HCL - ASRock Z170 Pro4 - i7-6700k
On Sunday, November 26, 2017 at 2:59:21 AM UTC-8, Yuraeitha wrote: > On Sunday, November 26, 2017 at 6:38:01 AM UTC, Wael Nasreddine wrote: > > Just installed Qubes 4.0-RC2. I had issues with the installation (was > > getting libvirt errors), I solved the errors by temporarily switching all > > VMs to PV, update dom0 and restore them back to HVM. > > I got Qubes 4 RC-2 running on a similar motherboard for someone else, the > Asus z170 Pro Gaming. I don't use this system actively my self, but it ran > smoothly from the hours I used to set it all up and to configure it, and it > had no libvirt errors. > > So the basic chipset features of the z170 line should not be an issue, and > you got immou enabled in your HCL rapport file, so I assume your VT-d must be > enabled in your UEFI (BIOS). Also the processor doesn't look like an issue > either. > > However, I remember this particular motherboard had two separate places to > activate the virtualisation technology, you may have only enabled one of them > in the UEFI? Both settings came disabled on the Asus z170 Pro Gaming board I > set up with Qubes 4. > > In your UEFI Advanced menu, try look for both: > - VT-d. (I suspect this is the one you enabled). > - Virtualization (something closely worded to this, I suspect this might be > the setting you miss to enable). > > So if the two boards are anything alike, then this might be it. If you can't > find this extra setting, then perhaps your model is different and it doesn't > have it extra required step. But it may very well be similar. Yes, there are two places to enable on this motherboard, both in Advanced settings, one under CPU configuration and another one under Chipset configuration and they are both enabled. -- 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/f06bc5da-cc0c-4fd8-bea4-5fdbc318d120%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] HCL - ASRock Z170 Pro4 - i7-6700k
Just installed Qubes 4.0-RC2. I had issues with the installation (was getting libvirt errors), I solved the errors by temporarily switching all VMs to PV, update dom0 and restore them back to HVM. -- 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/c40e27bf-74f1-43a0-9593-29ed09083869%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. Qubes-HCL-ASRock-Z170_Pro4-20171125-223100.yml Description: Binary data
[qubes-users] Re: How To Replace Libvirt Drivers
On Saturday, November 25, 2017 at 8:06:27 PM UTC-8, Person wrote: > “In an earlier install, after I got this error, I switched all VMs to using > pv virt_mode and managed to get `qubes-dom0-update` to run, after doing that, > I still got the same weird /proc/cpuinfo and lscpu output but VMs were > booting OK with hvm.” > > How exactly do you switch VMs to using pv virt_mode? The only thing I > actually want is for the VMs to book correctly, and that would save me a lot > of trouble. sudo qvm-prefs virt_mode pv -- 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/5f034717-237a-45aa-a158-bfaa00ca4110%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] update dom0 offline
Hello, As I described in the other topic titled "How To Replace Libvirt Drivers"; Upon installation, I get the error `libvirtError.libvirt: libxenlight failed to create new domain “domain name”` and updating the system seems to have helped. I want to attempt to update all packages before continuing the initial_setup, so how can I update dom0 offline? Another option I have is to perform a net-install, I tried using `https://mirrors.kernel.org/qubes/repo/yum/r4.0/current-testing/dom0/fc25/` as an additional repository in the installer but I got "Error setting up base repository". Wael -- 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/ddc651f0-3759-4de1-966f-e1a36200d963%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: How To Replace Libvirt Drivers
On Friday, November 24, 2017 at 9:44:50 PM UTC-8, Wael Nasreddine wrote: > On Friday, November 24, 2017 at 9:04:01 PM UTC-8, Person wrote: > > I entered that command in the terminal, and I received this reply: > > > > https://imgur.com/a/zH3hO > > > > It seems that I haven’t enabled many things, and I don’t know how to enable > > them. > > I'm having a similar issue, freshly installed Qubes 4.0-rc2, when it's > running the first_install configuration, I receive the error > `libvirtError.libvirt: libxenlight failed to create new domain “domain name”.` > > - VT-x/VT-d is enabled in the bios > - I booted ArchLinux install CD and in /proc/cpuinfo I see vmx/vme and lscpu > says VT-x is available but that's not the case in what I see in Qubes (lscpu > list Virtualisation as None) > > In an earlier install, after I got this error, I switched all VMs to using pv > virt_mode and managed to get `qubes-dom0-update` to run, after doing that, I > still got the same weird /proc/cpuinfo and lscpu output but VMs were booting > OK with hvm. > > I reinstalled Qubes because the initial_setup did not complete, and now I'm > stuck with the same issue. > > Is there a way to default all new VMs to PV so when the initial_setup creates > sys-net and sys-firewall it would work and I'd be able to run > `qubes-dom0-update` and then switch them back to hvm? If not, is there a way > during the installation to use Qubes repos for packages as opposed to using > the ISO? > > - ArchLinux: https://imgur.com/3eb9lWY > - QubesOS: https://imgur.com/mSpZFeq I forgot to add my HCL https://imgur.com/in30u6v -- 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/5e2079de-37cc-4e20-9019-58053bf0c838%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: How To Replace Libvirt Drivers
On Friday, November 24, 2017 at 9:04:01 PM UTC-8, Person wrote: > I entered that command in the terminal, and I received this reply: > > https://imgur.com/a/zH3hO > > It seems that I haven’t enabled many things, and I don’t know how to enable > them. I'm having a similar issue, freshly installed Qubes 4.0-rc2, when it's running the first_install configuration, I receive the error `libvirtError.libvirt: libxenlight failed to create new domain “domain name”.` - VT-x/VT-d is enabled in the bios - I booted ArchLinux install CD and in /proc/cpuinfo I see vmx/vme and lscpu says VT-x is available but that's not the case in what I see in Qubes (lscpu list Virtualisation as None) In an earlier install, after I got this error, I switched all VMs to using pv virt_mode and managed to get `qubes-dom0-update` to run, after doing that, I still got the same weird /proc/cpuinfo and lscpu output but VMs were booting OK with hvm. I reinstalled Qubes because the initial_setup did not complete, and now I'm stuck with the same issue. Is there a way to default all new VMs to PV so when the initial_setup creates sys-net and sys-firewall it would work and I'd be able to run `qubes-dom0-update` and then switch them back to hvm? If not, is there a way during the installation to use Qubes repos for packages as opposed to using the ISO? - ArchLinux: https://imgur.com/3eb9lWY - QubesOS: https://imgur.com/mSpZFeq -- 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/65044589-6a38-4c86-b80a-9d4d44f585b0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: advise on HP Zbook G3 (or another laptop with recommended spec and high RAM)
The SSD I chose is an NVMe according to the spec http://www8.hp.com/h20195/v2/GetDocument.aspx?docname=c04834946, last I checked, it's not possible to boot from NVMe, has that changed? On Saturday, December 31, 2016 at 5:51:11 PM UTC-8, wael.na...@gmail.com wrote: > Hello, > > I am considering purchasing an HP ZBook 15 G3. This would be my first Qubes > OS install, and I wanted to make sure my selection would work. > Their Xeon version seems to come with an integrated Intel Iris P580, but they > also propose adding Nvidia or AMD graphic cards which I am not sure if I > would need at all (or if it would work at all). If I select an additional > graphic card, say the Nvidia 2000M, would I still be able to use the Intel > Iris that's integrated? > > Unfortunately, HP does not provide a permanent link to a customization, so I > have created a screenshot of my selection that you can view here > https://www.awesomescreenshot.com/showImage?img_id=2008636 > > Does anyone know beforehand if this setup would work? Should I expect any > problems during install? Finally, do you recommend any additions? > > Happy New Years everyone! > > Thanks, > > Wael -- 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/9e801b51-5e9e-4372-aee3-9f422a1c2e96%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] advise on HP Zbook G3 (or another laptop with recommended spec and high RAM)
Hello, I am considering purchasing an HP ZBook 15 G3. This would be my first Qubes OS install, and I wanted to make sure my selection would work. Their Xeon version seems to come with an integrated Intel Iris P580, but they also propose adding Nvidia or AMD graphic cards which I am not sure if I would need at all (or if it would work at all). If I select an additional graphic card, say the Nvidia 2000M, would I still be able to use the Intel Iris that's integrated? Unfortunately, HP does not provide a permanent link to a customization, so I have created a screenshot of my selection that you can view here https://www.awesomescreenshot.com/showImage?img_id=2008636 Does anyone know beforehand if this setup would work? Should I expect any problems during install? Finally, do you recommend any additions? Happy New Years everyone! Thanks, Wael -- 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/e901100a-edf4-4663-b71c-217fe4900ffa%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
