I can get around the mount problem by explicitly specifying the filesystem
type (e.g., mount -t ext2 /dev/vda1 somedir)--is that some limitation of
busybox mount?
I still don't know why the system is having trouble starting up.
The recent kernel update included a fix for a KVM vunerability(
https
After the recent kernel updates one of my virtual machines won't start.
GRUB runs and messages indicate the kernel is loaded and the initial
ramdisk is loading. Then it says it can't find the root device (identified
by correct UUID, though it wouldn't be visible until the logical volumes
are activ
2 matches
Mail list logo