Re: [qubes-users] After updating Debian Kernel in VM, initramfs can't init

2017-10-14 Thread Marek Marczykowski-Górecki
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Wed, Feb 08, 2017 at 03:58:57PM -0800, nicholas roveda wrote:
> I've just update the Kernel inside of the Debian Template to the 4.9.2 
> version and now, the machine can't start.
> 
> 
> - I installed grub2-xen in dom0
> 
> - I installed 'qubes-kernel-vm-support', 'kernel-package' and 'grub2-common' 
> inside the Template VM
> - I downloaded the Debian Kernel Sources (4.9.2)
> - I ran 'make menuconfig' and activate all virtualization and xen support, 
> mantaining the related configs present in the dom0 Kernel
> - I created a Kernel .deb packages with 'make-kpkg --initrd -- linux-headers 
> linux-image' and I installed them
> - I update the GRUB2 with 'update-grub'
> 
> - I set 'pvgrub2' as Kernel in Qubes VM Manager
> 
> 
> 
> The machine manages to boot the VM GRUB2 and the GRUB2 can load the Kernel 
> and the initramfs,
> the initramfs can mount root, but can't complete init and the console remains 
> in the initramfs shell.
> 
> 
> 
> Console Logs:
> 
> Loading, please wait...
> error getting socket: Function not implemented
> error initializing udev control socketerror initializing udev control socket
> Begin: Loading essential drivers ... done.
> Begin: Running /scripts/init-premount ... done.
> Begin: Mounting root file system ... Begin: Running /scripts/local-top ... 
> Begin: Waiting for /dev/xvda* devices... ... done.
> Begin: Qubes: Doing R/W setup for TemplateVM... ... [1.402524]  xvdc: 
> xvdc1
> Partition #1 contains a swap signature.
> [1.404605]  xvdc: xvdc1
> Setting up swapspace version 1, size = 1073737728 bytes
> UUID=ae1bbd47-1b98-4502-818a-ac18b6ccbc73
> [1.415272] dmsetup (687) used greatest stack depth: 13688 bytes left
> done.
> done.
> Begin: Running /scripts/local-premount ... done.
> error getting socket: Function not implemented
> Begin: Will now check root file system ... fsck from util-linux 2.29.1
> [/sbin/fsck.ext4 (1) -- /dev/mapper/dmroot] fsck.ext4 -a -C0 
> /dev/mapper/dmroot 
> /dev/mapper/dmroot: clean, 453037/655360 files, 2474697/2621440 blocks
> done.
> [1.468729] EXT4-fs (dm-0): mounted filesystem with ordered data mode. 
> Opts: (null)
> done.
> Begin: Running /scripts/local-bottom ... done.
> Begin: Running /scripts/init-bottom ... error getting socket: Function not 
> implemented
> done.
> [1.496400] mount (718) used greatest stack depth: 13528 bytes left
> run-init: opening console: No such file or directory
> Target filesystem doesn't have requested /sbin/init.
> run-init: opening console: No such file or directory
> run-init: opening console: No such file or directory
> run-init: opening console: No such file or directory
> run-init: opening console: No such file or directory
> run-init: opening console: No such file or directory
> No init found. Try passing init= bootarg.
> 
> 
> BusyBox v1.22.1 (Debian 1:1.22.0-19+b1) built-in shell (ash)
> Enter 'help' for a list of built-in commands.
> 
> (initramfs) 

I wonder what those "error getting socket: Function not implemented"
are? Maybe you didn't enabled something needed by udev/mdev in kernel
config?


- -- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJZ4KXJAAoJENuP0xzK19cs/QsH/2XdP8UqfU2XEyDeMTUoYf4u
0GkP0J2ULMcPCeCOcSvv6+ES/pSRm/qmPcBxpvt8z9x/bDZ4povyG3a38KgbrW0g
iBRUyAp6MS8VjyoI7coGgl3C0xckiKn/GqeGHrLm84zyaJCWaEuv9At83wOTQH48
3vczi4st2cHoO0TPNgwVuLmj5fOJuA5jeAAkY5O7BtTBJiAQlpPMS24Fi+PhafNG
PDF4HTLUEvIft/zh0VoHwFRYzHH5ktbEFJLT6SfB6WZKQkwXHeKl3rzynZqmn28M
0J/Ha6L7qt2MBIPwjDVZnkhVfsHt57Lb0PDlq3wHIAQEA5XZ7LBZgu4yYYm0v3A=
=QaXZ
-END PGP SIGNATURE-

-- 
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/20171014161105.GI10749%40mail-itl.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] After updating Debian Kernel in VM, initramfs can't init

2017-10-14 Thread Holger Levsen
On Sat, Oct 14, 2017 at 03:03:39PM +, Holger Levsen wrote:
> I've done the same… just with a slightly different result, though the same 
> outcome, the VM
> in question doesnt boot :(

running "sudo update-initramfs -c -k all" fixed this for me…


-- 
cheers,
Holger

-- 
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/20171014154229.2ykamfugphks4t7b%40layer-acht.org.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: PGP signature


Re: [qubes-users] After updating Debian Kernel in VM, initramfs can't init

2017-10-14 Thread Holger Levsen
On Wed, Feb 08, 2017 at 03:58:57PM -0800, nicholas roveda wrote:
> I've just update the Kernel inside of the Debian Template to the 4.9.2 
> version and now, the machine can't start.
> 
> - I installed grub2-xen in dom0
> 
> - I installed 'qubes-kernel-vm-support', 'kernel-package' and 'grub2-common' 
> inside the Template VM
> - I downloaded the Debian Kernel Sources (4.9.2)
> - I ran 'make menuconfig' and activate all virtualization and xen support, 
> mantaining the related configs present in the dom0 Kernel
> - I created a Kernel .deb packages with 'make-kpkg --initrd -- linux-headers 
> linux-image' and I installed them
> - I update the GRUB2 with 'update-grub'
> 
> - I set 'pvgrub2' as Kernel in Qubes VM Manager

I've done the same… just with a slightly different result, though the same 
outcome, the VM
in question doesnt boot :(

this is what I got:

  Booting `Debian GNU/Linux'

Loading Linux 4.9.0-4-amd64 ...
Loading initial ramdisk ...   [ vmlinuz-4.9.0-4-amd6  3.64MiB  90%  2.27MiB/s ]
[0.104118] dmi: Firmware registration failed.a  18.40MiB  100%  1.49MiB/s ]
[1.399131] dmi-sysfs: dmi entry is absent.
[1.399653] mce: Unable to init device /dev/mcelog (rc: -5)
Gave up waiting for suspend/resume device
Gave up waiting for root file system device.  Common problems:
 - Boot args (cat /proc/cmdline)
   - Check rootdelay= (did the system wait long enough?)
 - Missing modules (cat /proc/modules; ls /dev)
ALERT!  /dev/mapper/dmroot does not exist.  Dropping to a shell!


BusyBox v1.22.1 (Debian 1:1.22.0-19+b3) built-in shell (ash)
Enter 'help' for a list of built-in commands.

(initramfs) 

any hints welcome.


-- 
cheers,
Holger

-- 
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/20171014150339.v7uwvwdvj6me5xmu%40layer-acht.org.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: PGP signature