Re: [qubes-devel] Re: GVT-g Discussion

2020-01-02 Thread 'Dylanger Daly' via qubes-devel
 My bad, I accidentally replied directly to Demi

Hey Ivan,

This is fantastic work! I'll test this out today, I think this will help 
with Firefox's WebRender engine, meaning much less CPU spikes, and reduced 
wattage when I have like 2 Firefox Tabs open.
Not to mention watching YouTube.

Demi you make some valid Security points, however one major GPU activity is 
WebRender (Web Content being rendered within the iGPU)
It's also my understanding Marek mentioned R4.1 would support GVT-g.

I would love to see an approach similar to Genode as well, I just don't 
think it will happen, I'm almost certain GVT-g will be used.

Cheers!

*Demi Replied with*

> Hey Ivan,
> 
> This is fantastic work! I'll test this out today, I think this will help
> with Firefox's WebRender engine, meaning much less CPU spikes, and reduced
> wattage when I have like 2 Firefox Tabs open.
> Not to mention watching YouTube.
> 
> Demi you make some valid Security points, however one major GPU activity 
is
> WebRender (Web Content being rendered within the iGPU)
> It's also my understanding Marek mentioned R4.1 would support GVT-g.
> 
> I would love to see an approach similar to Genode as well, I just don't
> think it will happen, I'm almost certain GVT-g will be used.
> 
> Cheers!

Regarding WebRender: My personal approach (and recommendation) is to
just accept the higher power consumption.  If you can’t, a separate
computer is probably your best option.  The trend in QubesOS is to
emulate more devices (such as audio hardware), and rely on QEMU being
sandboxed for security.

GVT-g may be supported in QubesOS at some point, but not until it
doesn’t require unsandboxed QEMU.  Honestly, I consider QEMU
being in stubdoms to be one of QubesOS’s main selling points.
Especially since dom0 is so out of date that there is almost certain
to be a trivially-exploitable vulnerability there.

Sincerely,

Demi

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-devel/4e5e8079-8aba-4c9f-95c1-7d119db418eb%40googlegroups.com.


Re: [qubes-devel] Re: Compiling an ISO with kernel-latest and modifications

2019-12-12 Thread 'Dylanger Daly' via qubes-devel
--> Done:
The ISO can be found in iso/ subdirectory.
Thank you for building Qubes. Have a nice day!

Okay so I managed to successfully build an ISO, however, it appears to have 
totally ignored my kernel changes
[user@sys-usb BOOT]$ file vmlinuz 
vmlinuz: Linux kernel x86 boot executable bzImage, version 4.19.86-1.pvops.
qubes.x86_64 (user@build-fedora4) #1 SMP Sun Dec 1 07:16:00 UTC 2019, 
RO-rootFS, swap_dev 0x6, Normal VGA


This should read 5.4.2 (master at time of writing)

https://pastebin.com/z4hLjdBf

This is my builder, can someone please let me know if I need to specify 
that I want the kernel to be used for Installation as well?

Thank you for your help Marek & Frédéric!

On Thursday, December 12, 2019 at 7:51:28 PM UTC+11, Dylanger Daly wrote:
>
> Quick update:
>
> I forced release4.0 for installer-qubes-os, after doing that I had issues 
> with symlinks, turns out I had like 40 mounts for chroot. Rebooting my 
> appVM seems to have fixed it.
>
> I'm successfully running `make iso`
>
> /me crosses fingers
>
> On Thursday, December 12, 2019 at 11:50:40 AM UTC+11, Dylanger Daly wrote:
>>
>> Thank you Marek!
>>
>> I've managed to `make qubes` this has compile my kernel successfully.
>>
>> However when trying to compile the iso with `make iso` I appear to be 
>> getting the same issue
>> [user@work qubes-builder]$ make iso
>> -> Preparing for ISO build...
>> --> Removing old rpms from the installer repos...
>> ---> Cleaning up repo: dom0-updates...
>> ---> Cleaning up repo: installer...
>> ---> Cleaning up repo: qubes-dom0...
>> --> Copying installer-qubes-os RPMs...
>> --> Copying linux-yum RPMs...
>> --> Copying builder-rpm RPMs...
>> --> Copying linux-kernel RPMs...
>> Qubes OS Builder Repository 
>> 
>>256 MB/s | 544 kB 00:00
>> Dependencies resolved.
>> Nothing to do.
>> Complete!
>> -> Installing installer-qubes-os build dependencies in fc25 environment
>> Qubes OS Builder Repository 
>> 
>>262 MB/s | 544 kB 00:00
>> No package pungi-legacy available.
>> Error: Unable to find a match.
>> make: *** [Makefile:532: iso] Error 1
>> [user@work qubes-builder]$ sudo chroot chroot-dom0-fc25 dnf install pungi
>> -legacy 
>> Qubes OS Builder Repository 
>> 
>>257 MB/s | 544 kB 00:00
>> No package pungi-legacy available.
>> Error: Unable to find a match.
>>
>>
>> I actually didn't have the BRANCH defined in my builder, after adding it 
>> I seem to still get the same error.
>>
>> Here's my builder.conf
>>
>> # vim: ft=make
>>
>> VERBOSE ?= 2
>>
>> BACKEND_VMM ?= xen
>>
>> NO_SIGN="1"
>>
>> GIT_BASEURL ?= https://github.com
>> GIT_PREFIX ?= QubesOS/qubes-
>>
>> BRANCH ?= release4.0
>>
>> RELEASE ?= 4.0
>>
>> DIST_DOM0 ?= fc25
>> DISTS_VM ?=
>>
>> COMPONENTS = \
>> installer-qubes-os \
>> linux-yum \
>> builder-rpm \
>> linux-kernel
>>
>> BUILDER_PLUGINS ?= builder-rpm
>>
>> USE_QUBES_REPO_VERSION=4.0
>>
>> INSTALLER_KICKSTART=/home/user/qubes-src/installer-qubes-os/conf/iso-full
>> -online.ks
>>
>>
>> It's my understanding this should build me a brand new latest-latest ISO 
>> with my compile kernel.
>>
>> I'm not sure how I can install this pungi-legacy package, that appears to 
>> be the hold up.
>>
>> Cheers!
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-devel/0fca6352-48db-4210-b68b-ec5741c0ec52%40googlegroups.com.


Re: [qubes-devel] Re: Compiling an ISO with kernel-latest and modifications

2019-12-12 Thread 'Dylanger Daly' via qubes-devel
Quick update:

I forced release4.0 for installer-qubes-os, after doing that I had issues 
with symlinks, turns out I had like 40 mounts for chroot. Rebooting my 
appVM seems to have fixed it.

I'm successfully running `make iso`

/me crosses fingers

On Thursday, December 12, 2019 at 11:50:40 AM UTC+11, Dylanger Daly wrote:
>
> Thank you Marek!
>
> I've managed to `make qubes` this has compile my kernel successfully.
>
> However when trying to compile the iso with `make iso` I appear to be 
> getting the same issue
> [user@work qubes-builder]$ make iso
> -> Preparing for ISO build...
> --> Removing old rpms from the installer repos...
> ---> Cleaning up repo: dom0-updates...
> ---> Cleaning up repo: installer...
> ---> Cleaning up repo: qubes-dom0...
> --> Copying installer-qubes-os RPMs...
> --> Copying linux-yum RPMs...
> --> Copying builder-rpm RPMs...
> --> Copying linux-kernel RPMs...
> Qubes OS Builder Repository   
> 
>  256 MB/s | 544 kB 00:00
> Dependencies resolved.
> Nothing to do.
> Complete!
> -> Installing installer-qubes-os build dependencies in fc25 environment
> Qubes OS Builder Repository   
> 
>  262 MB/s | 544 kB 00:00
> No package pungi-legacy available.
> Error: Unable to find a match.
> make: *** [Makefile:532: iso] Error 1
> [user@work qubes-builder]$ sudo chroot chroot-dom0-fc25 dnf install 
> pungi-legacy 
>
> Qubes OS Builder Repository   
> 
>  257 MB/s | 544 kB 00:00
> No package pungi-legacy available.
> Error: Unable to find a match.
>
>
> I actually didn't have the BRANCH defined in my builder, after adding it I 
> seem to still get the same error.
>
> Here's my builder.conf
>
> # vim: ft=make
>
> VERBOSE ?= 2
>
> BACKEND_VMM ?= xen
>
> NO_SIGN="1"
>
> GIT_BASEURL ?= https://github.com
> GIT_PREFIX ?= QubesOS/qubes-
>
> BRANCH ?= release4.0
>
> RELEASE ?= 4.0
>
> DIST_DOM0 ?= fc25
> DISTS_VM ?=
>
> COMPONENTS = \
> installer-qubes-os \
> linux-yum \
> builder-rpm \
> linux-kernel
>
> BUILDER_PLUGINS ?= builder-rpm
>
> USE_QUBES_REPO_VERSION=4.0
>
> INSTALLER_KICKSTART=/home/user/qubes-src/installer-qubes-os/conf/iso-full-
> online.ks
>
>
> It's my understanding this should build me a brand new latest-latest ISO 
> with my compile kernel.
>
> I'm not sure how I can install this pungi-legacy package, that appears to 
> be the hold up.
>
> Cheers!
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-devel/92187822-bedb-4066-ac58-7b9cd66356d1%40googlegroups.com.


[qubes-devel] Re: Intel i7-1065G7 (10 Generation Support) - APIC Patches

2019-12-11 Thread 'Dylanger Daly' via qubes-devel
So I managed to get a little more info out of Xen during boot

Enabling IO-APIC IRQs
...
MP-BIOS bug: 8254 timer not connected to IO-APIC
... trying to set up timer (IRQ0) through the 8259A ... failed.
... trying to set up timer as Virtual Wire IRQ ... failed.
... trying to set up timer as ExtINT IRQ...spurious 8259A interrupt: IRQ7.
CPU0: No irq handler for vector e7 (IRQ -8)



On Thursday, December 12, 2019 at 3:24:09 PM UTC+11, Dylanger Daly wrote:
>
> Hi Guys,
>
>
> I'm trying to get Qubes 4.0.1RC2 running on a Surface Laptop 3, however I 
> appear to be getting the error
>
> IO-APIC + timer doesn't work! Boot with apic_verbosity=debug and send a 
> report. Then try booting with the 'noapic' option
>
>
> When adding 'noapic' to the options line (Not CMDLINE) I can see it try to 
> bring up dom0, then I think it resets and hangs at the OEM UEFI Logo, I 
> think this has something to do with the fact that Xen 4.8 doesn't support 
> the 10th Gen Intel CPU (Perhaps the ACPI Tables for the 10th Gen Intel 
> specifically)
>
> I also think the APIC is related to the IOMMU and must be enabled to run 
> Qubes / Xen.
>
> Fedora 31 boots perfectly with the APIC Enabled, however it appears to be 
> something specific to Xen, I can see past patches to support AMD's APIC (
> https://github.com/QubesOS/qubes-vmm-xen/blob/a4fc8004dd903e60f37db7b20caf1b95993b0a46/patch-xen-AMD-IOMMU-Support-IOAPIC-IDs-larger-than-128.patch
> )
>
> So I think I just need to add support/patches for Intel's latest 10th Gen 
> (i7-1065G7 Specifically) APIC.
>
> Any help with this would be greatly appreciated.
>

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-devel/a11537b1-ecf9-4115-b88e-973a86eb44ef%40googlegroups.com.


Re: [qubes-devel] Re: Compiling an ISO with kernel-latest and modifications

2019-12-11 Thread 'Dylanger Daly' via qubes-devel
Thank you Marek!

I've managed to `make qubes` this has compile my kernel successfully.

However when trying to compile the iso with `make iso` I appear to be 
getting the same issue
[user@work qubes-builder]$ make iso
-> Preparing for ISO build...
--> Removing old rpms from the installer repos...
---> Cleaning up repo: dom0-updates...
---> Cleaning up repo: installer...
---> Cleaning up repo: qubes-dom0...
--> Copying installer-qubes-os RPMs...
--> Copying linux-yum RPMs...
--> Copying builder-rpm RPMs...
--> Copying linux-kernel RPMs...
Qubes OS Builder Repository 

   256 MB/s | 544 kB 00:00
Dependencies resolved.
Nothing to do.
Complete!
-> Installing installer-qubes-os build dependencies in fc25 environment
Qubes OS Builder Repository 

   262 MB/s | 544 kB 00:00
No package pungi-legacy available.
Error: Unable to find a match.
make: *** [Makefile:532: iso] Error 1
[user@work qubes-builder]$ sudo chroot chroot-dom0-fc25 dnf install 
pungi-legacy 

Qubes OS Builder Repository 

   257 MB/s | 544 kB 00:00
No package pungi-legacy available.
Error: Unable to find a match.


I actually didn't have the BRANCH defined in my builder, after adding it I 
seem to still get the same error.

Here's my builder.conf

# vim: ft=make

VERBOSE ?= 2

BACKEND_VMM ?= xen

NO_SIGN="1"

GIT_BASEURL ?= https://github.com
GIT_PREFIX ?= QubesOS/qubes-

BRANCH ?= release4.0

RELEASE ?= 4.0

DIST_DOM0 ?= fc25
DISTS_VM ?=

COMPONENTS = \
installer-qubes-os \
linux-yum \
builder-rpm \
linux-kernel

BUILDER_PLUGINS ?= builder-rpm

USE_QUBES_REPO_VERSION=4.0

INSTALLER_KICKSTART=/home/user/qubes-src/installer-qubes-os/conf/iso-full-
online.ks


It's my understanding this should build me a brand new latest-latest ISO 
with my compile kernel.

I'm not sure how I can install this pungi-legacy package, that appears to 
be the hold up.

Cheers!

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-devel/1651b051-65e6-4a5c-ab97-3f20f7735675%40googlegroups.com.


Re: [qubes-devel] Re: Compiling an ISO with kernel-latest and modifications

2019-12-11 Thread 'Dylanger Daly' via qubes-devel
Okay, so I've switched back to using your link 'live' config

If I apply my commit over the top of master, it appears to keep it there

However after compiling, I appear to get stopped here

--> Done:
  qubes-src/linux-kernel/pkgs/dom0-fc25/x86_64/kernel-latest-5.4.2-
2.qubes.x86_64.rpm
  qubes-src/linux-kernel/pkgs/dom0-fc25/x86_64/kernel-latest-devel-5.4.2
-2.qubes.x86_64.rpm
  qubes-src/linux-kernel/pkgs/dom0-fc25/x86_64/kernel-latest-qubes-vm-
5.4.2-2.qubes.x86_64.rpm
make[2]: Leaving directory '/home/user/Apps/qubes-builder'
make[1]: Leaving directory '/home/user/Apps/qubes-builder'
-> Preparing for ISO build...
--> Removing old rpms from the installer repos...
---> Cleaning up repo: dom0-updates...
---> Cleaning up repo: installer...
---> Cleaning up repo: qubes-dom0...
--> Copying installer-qubes-os RPMs...
--> Copying linux-yum RPMs...
--> Copying builder-rpm RPMs...
--> Copying linux-kernel RPMs...
Qubes OS Builder Repository 
  242 MB/s | 544 kB 00:
00
Dependencies resolved.
Nothing to do.
Complete!
-> Installing installer-qubes-os build dependencies in fc25 environment
Qubes OS Builder Repository 
  246 MB/s | 544 kB 00:
00
No package pungi-legacy available.
Error: Unable to find a match.
make: *** [Makefile:532: iso] Error 1

Appears to be a simple package missing?

It appears to be an issue with `pungi-legacy`

Last metadata expiration check: 0:00:37 ago on Wed Dec 11 23:28:32 2019.
Error: 
 Problem: conflicting requests
  - nothing provides python2-functools32 needed by pungi-legacy-4.1.35-
1.fc30.noarch
(try to add '--skip-broken' to skip uninstallable packages)


If I try to install it myself.

Any help is greatly appreciated.

Cheers!


On Wednesday, December 11, 2019 at 8:57:33 PM UTC+11, Dylanger Daly wrote:
>
> Is this post still relevant? 
> https://groups.google.com/forum/#!searchin/qubes-devel/linux-kernel|sort:date/qubes-devel/NfVQi0HXWEY/AECwbKZ0AQAJ
>
>
>  - clear COMPONENTS (for the build time at least) 
>  - clear DISTS_VM (unless you want to use local template builds) 
>  - set USE_QUBES_REPO_VERSION=4.0 
>  - optionally set USE_QUBES_REPO_TESTING=1 
>  - set INSTALLER_KICKSTART=/tmp/
> qubes-installer/conf/travis-iso-full.ks 
>(file is in qubes-src/installer-qubes-os/conf/, but it's in that path 
> inside build chroot) 
>
> To be clear I'm trying to do exactly the same thing as that post
>
> On Wednesday, December 11, 2019 at 8:30:51 PM UTC+11, Dylanger Daly wrote:
>>
>> -> Updating sources for linux-kernel...
>> --> Fetching from https://github.com/QubesOS/qubes-linux-kernel.git 
>> master...
>> --> Verifying tags...
>> --> Switching branch from surface-acpi branch to master
>> Switched to branch 'master'
>> --> Merging...
>>
>>
>>
>> I can't seem to get my branch to stick
>>
>> On Wednesday, December 11, 2019 at 7:48:39 PM UTC+11, Dylanger Daly wrote:
>>>
>>> Awesome, thanks for that, I think I'll stick to stock and _just_ update 
>>> Kernel (On LTE)
>>>
>>> If you comment out linux-kernel from COMPONENTS builder won't over write 
>>> my branch in linux-kernel.
>>>
>>> If I up the rel file, builder still reverts to stable-4.14 branch.
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-devel/28c92519-49aa-4730-967d-c39b1fda863f%40googlegroups.com.


Re: [qubes-devel] Re: Compiling an ISO with kernel-latest and modifications

2019-12-11 Thread 'Dylanger Daly' via qubes-devel
Is this post still relevant? 
https://groups.google.com/forum/#!searchin/qubes-devel/linux-kernel|sort:date/qubes-devel/NfVQi0HXWEY/AECwbKZ0AQAJ


 - clear COMPONENTS (for the build time at least) 
 - clear DISTS_VM (unless you want to use local template builds) 
 - set USE_QUBES_REPO_VERSION=4.0 
 - optionally set USE_QUBES_REPO_TESTING=1 
 - set INSTALLER_KICKSTART=/tmp/
qubes-installer/conf/travis-iso-full.ks 
   (file is in qubes-src/installer-qubes-os/conf/, but it's in that path 
inside build chroot) 

To be clear I'm trying to do exactly the same thing as that post

On Wednesday, December 11, 2019 at 8:30:51 PM UTC+11, Dylanger Daly wrote:
>
> -> Updating sources for linux-kernel...
> --> Fetching from https://github.com/QubesOS/qubes-linux-kernel.git 
> master...
> --> Verifying tags...
> --> Switching branch from surface-acpi branch to master
> Switched to branch 'master'
> --> Merging...
>
>
>
> I can't seem to get my branch to stick
>
> On Wednesday, December 11, 2019 at 7:48:39 PM UTC+11, Dylanger Daly wrote:
>>
>> Awesome, thanks for that, I think I'll stick to stock and _just_ update 
>> Kernel (On LTE)
>>
>> If you comment out linux-kernel from COMPONENTS builder won't over write 
>> my branch in linux-kernel.
>>
>> If I up the rel file, builder still reverts to stable-4.14 branch.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-devel/9f306e45-17ca-40f5-b731-bfe63e4f35a4%40googlegroups.com.


Re: [qubes-devel] Re: Compiling an ISO with kernel-latest and modifications

2019-12-11 Thread 'Dylanger Daly' via qubes-devel
-> Updating sources for linux-kernel...
--> Fetching from https://github.com/QubesOS/qubes-linux-kernel.git 
master...
--> Verifying tags...
--> Switching branch from surface-acpi branch to master
Switched to branch 'master'
--> Merging...



I can't seem to get my branch to stick

On Wednesday, December 11, 2019 at 7:48:39 PM UTC+11, Dylanger Daly wrote:
>
> Awesome, thanks for that, I think I'll stick to stock and _just_ update 
> Kernel (On LTE)
>
> If you comment out linux-kernel from COMPONENTS builder won't over write 
> my branch in linux-kernel.
>
> If I up the rel file, builder still reverts to stable-4.14 branch.
>

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-devel/2664ab34-a562-4cb2-a533-d1f526d755fc%40googlegroups.com.


Re: [qubes-devel] Re: Compiling an ISO with kernel-latest and modifications

2019-12-11 Thread 'Dylanger Daly' via qubes-devel
Awesome, thanks for that, I think I'll stick to stock and _just_ update 
Kernel (On LTE)

If you comment out linux-kernel from COMPONENTS builder won't over write my 
branch in linux-kernel.

If I up the rel file, builder still reverts to stable-4.14 branch.

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-devel/e92c02c0-4558-4b8b-bc20-ee8e658a243d%40googlegroups.com.


Re: [qubes-devel] Re: Compiling an ISO with kernel-latest and modifications

2019-12-11 Thread 'Dylanger Daly' via qubes-devel
Currently I'm trying to build an ISO with Microsoft Surface ACPI Patches 
(https://groups.google.com/forum/#!topic/qubes-users/4iswU7cfJHY)

Issue seems to be related to ACPI, I think it's possible there's no support 
for 10th Gen Intel on Stable 4.14 that comes in the installation media, so 
I'm trying to compile an ISO with the patches on 5.3.11-1.

I'm not using USE_QUBES_REPO_VERSION anywhere in builder, I'll add it now 
and try again.


On Wednesday, December 11, 2019 at 6:57:31 PM UTC+11, Frédéric Pierret 
wrote:
>
> Hi,
>
> Can you detail a little bit more exactly? If you want to build only the 
> kernel and using other packages of qubes by using 
> "USE_QUBES_REPO_VERSION=4.0"?
>
> If so, in your local builder (not the chroot),
>
> 1) checkout the branch you want,
>
> 2) do the changes you want,
>
> 3) increment the release (rel file) else it will use certainly the qubes 
> repo one.
>
> Build the iso. That's it.
>
> Best,
> On 2019-12-11 08:46, 'Dylanger Daly' via qubes-devel wrote:
>
> If I run make qubes-os-iso it appears to override my changes in 
> linux-kernel.
>
> Anyone know how to make that not happen?
>
> On Monday, December 9, 2019 at 3:20:06 PM UTC+11, Dylanger Daly wrote: 
>>
>> Hey Guys,
>>
>> Apologies if someone has already asked this, is it possible to build a 
>> Qubes ISO with Kernel-Latest (Being 5.3.11-1 at time of writing) for both 
>> dom0 and appVMs?
>>
>> It looks like the linux-kernel folder in qubes-builder/qubes-src is using 
>> the stable-4.14 branch, can I simply checkout v5.4.2-1 for example and 
>> build away?
>>
>> TL;DR I'm trying to add Microsoft Surface Laptop 3 patches into the Qubes 
>> Installer and dom0 (https://github.com/qzed/linux-surfacegen5-acpi)
>>
>> Any help is appreciated, cheers!
>>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "qubes-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to qubes...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/qubes-devel/3415ecdd-80f8-45cf-8c79-1d2e6e19d768%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/qubes-devel/3415ecdd-80f8-45cf-8c79-1d2e6e19d768%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-devel/38d15c2f-513d-4165-bad9-145623f1831e%40googlegroups.com.


[qubes-devel] Re: Compiling an ISO with kernel-latest and modifications

2019-12-10 Thread &#x27;Dylanger Daly&#x27; via qubes-devel
If I run make qubes-os-iso it appears to override my changes in 
linux-kernel.

Anyone know how to make that not happen?

On Monday, December 9, 2019 at 3:20:06 PM UTC+11, Dylanger Daly wrote:
>
> Hey Guys,
>
> Apologies if someone has already asked this, is it possible to build a 
> Qubes ISO with Kernel-Latest (Being 5.3.11-1 at time of writing) for both 
> dom0 and appVMs?
>
> It looks like the linux-kernel folder in qubes-builder/qubes-src is using 
> the stable-4.14 branch, can I simply checkout v5.4.2-1 for example and 
> build away?
>
> TL;DR I'm trying to add Microsoft Surface Laptop 3 patches into the Qubes 
> Installer and dom0 (https://github.com/qzed/linux-surfacegen5-acpi)
>
> Any help is appreciated, cheers!
>

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-devel/3415ecdd-80f8-45cf-8c79-1d2e6e19d768%40googlegroups.com.