On 04/15/2017 12:30 AM, Reg Tiangha wrote:
> On 04/15/2017 12:28 AM, Reg Tiangha wrote:
>> On 04/15/2017 12:12 AM, Vít Šesták wrote:
>>> IIUC, for pvgrub, you need to choose it as kernel for the particular AppVM.
>>> Have you done so?
>>>
>> I did; I boot coldkernel on Debian templates, so I know how to work with
>> pvgrub. The problem is that it just isn't generating a grub.cfg file.
>> This is the output of grub-mkconfig:
>>
>> user@xenial-snaps:~$ sudo grub-mkconfig
>> Generating grub configuration file ...
>> #
>> # DO NOT EDIT THIS FILE
>> #
>> # It is automatically generated by grub-mkconfig using templates
>> # from /etc/grub.d and settings from /etc/default/grub
>> #
>>
>> ### BEGIN /etc/grub.d/00_header ###
>> if [ -s $prefix/grubenv ]; then
>> set have_grubenv=true
>> load_env
>> fi
>> if [ "${next_entry}" ] ; then
>> set default="${next_entry}"
>> set next_entry=
>> save_env next_entry
>> set boot_once=true
>> else
>> set default="0"
>> fi
>>
>> if [ x"${feature_menuentry_id}" = xy ]; then
>> menuentry_id_option="--id"
>> else
>> menuentry_id_option=""
>> fi
>>
>> export menuentry_id_option
>>
>> if [ "${prev_saved_entry}" ]; then
>> set saved_entry="${prev_saved_entry}"
>> save_env saved_entry
>> set prev_saved_entry=
>> save_env prev_saved_entry
>> set boot_once=true
>> fi
>>
>> function savedefault {
>> if [ -z "${boot_once}" ]; then
>> saved_entry="${chosen}"
>> save_env saved_entry
>> fi
>> }
>> function recordfail {
>> set recordfail=1
>> grub-probe: error: cannot find a GRUB drive for /dev/mapper/dmroot.
>> Check your device.map.
>>
>> and what gets stored in /boot/grub.cfg.new. It doesn't even make a
>> regular grub.cfg file.
>>
>>
>> HOWEVER, I think this whole native kernel thing was a red herring. The
>> problem with the Anbox installer was that apparmor wasn't running, even
>> though the dom0 qubes-vm-kernel I'm running supports it. Easily fixed with:
>>
>> qvm-prefs -s XenialVM kernelopts "nopat apparmor=1 security=apparmor"
>>
>> And right now the installation is going. We'll see what happens when it
>> finishes.
>>
>> If I get this running, I might try again without installing
>> qubes-kernel-vm-support. That might be unnecessary after all and it
>> might have been apparmor not running that was the real problem.
>>
>>
> Edit: Err, maybe I spoke too soon. The Anbox installer is currently
> trying to install a 4.4 kernel right now. No idea what'll happen when
> it's done, but maybe pvgrub is actually needed in which case, I'll need
> to figure out how to get grub working after all.
>
>
I guess I was wrong. The Anbox installer tries to install a 4.4 kernel
and then fails compiling the Anbox dkms module due to the lack of kernel
sources (I'm running a Qubes dom0 vm kernel).
So I guess eventually, figuring out how to get a valid Grub
configuration working on this thing to boot a local Ubuntu kernel needs
to be done. It's weird that it doesn't work the same way as on my Debian
templates, though. My last resort is copying a valid grub.cfg from one
of my Debian templates over and manually editing it to point to use the
xenial kernel and initramfs, but I don't want to have to do that unless
absolutely necessary. But it's getting late in my part of the world, so
I'm calling it for now. If anyone else manages to figure this stuff out
in the meantime, please do share.
--
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/ocsf5i%24nk4%241%40blaine.gmane.org.
For more options, visit https://groups.google.com/d/optout.
