I'm going to change it and try.
Yep, it works :)
I still don't understand why deboostrap overrided this.
Stefano
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/51
+ for i in '${EXTRA_CONF}'
+ '[' -d /etc/initramfs-tools/conf.d/driver-policy ']'
+ '[' -e /etc/initramfs-tools/conf.d/driver-policy ']'
+ . /etc/initramfs-tools/conf.d/driver-policy
++ MODULES=dep
[...]
As pointed out by Ben (on IRC), you're using MODULES=dep.
Mmm...actually I was just loo
Thanks, that looks ok-ish actually.
Now what's the output of:
lsinitramfs /tmp/initramfs | grep xen
?
Nothing at all :(
Stefano
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http:
Hi,
I agree that it should include xen-blkfront. I don't know why you
mention xen-blkback though.
Just because I noticed it was present on the self-generated domU
initramfs. But maybe it's not useful at all.
This should already be the case since we have:
| copy_modules_dir kernel/driver
Hi, thank you for looking at this.
So you're using initramfs-tools 0.109 with kernel 3.2.0-4-amd64?
Which linux-image-amd64 version exactly?
And which combination of initramfs-tools and linux-image works for
you? Because AFAIK we haven't had any changes in initramfs-tools that
could be responsi
Package: initramfs-tools
Version: 0.109
Severity: critical
Justification: breaks unrelated software
Dear Maintainer,
initramfs not including the xenblk-front (net, and back) modules, so cannot
boot any Debian Xen DomU using the same dom0 kernel. Not having the same
problem with an old (some mont
6 matches
Mail list logo
