Michael Tokarev wrote:
> Michael Goetze wrote:
>> Package: qemu-kvm
>> Version: 0.11.1+dfsg-1
>> Severity: important
>>
>> I'm trying to install virtual machines with FAI, and for this purpose
>> have installed a full FAI infrastructure (using dnsmasq) on my host
>> system, listening on br0. Currently I'm booting 2.6.31-grml64, but I
>> have tried this with standard Lenny kernels as well, both 32- and 64-bit.
>>
>> I create the virtual machine with:
>>
>> virt-install -n test -r 256 --vcpus=1 --os-variant=debianlenny --pxe
>> --disk path=/dev/vg2/test_root --disk path=/dev/vg2/test_swap -w
>> bridge=br0,mac=52:54:00:25:00:00,model=virtio --vnc
>>
>> The PXE boot works after a few tries (the boot ROM always claims to not
>> get an answer the first few times) and then the kernel boots. Once the
> 
> I use PXE here quite alot (with kvm and with real hardware) but never saw
> anything like you describe.  Probably worth the effort to experiment with
> various guest network drivers, but again: not the case here.
> 
>> initrd proclaims "Begin: Mounting root filesystem ..." I get the
>> following kernel messages:
>>
>> NET: Registered protocol family 17
>> Kernel panic - not syncing: Attempted to kill init!
>> Pid: 1, comm: init Not tainted 2.6.31-grml63 #1
>> Call Trace:
>>  [<ffffffff81529290>] panic+0xc6/0x17c
>>  [<ffffffff8105e03b>] ? put_files_struct+0xc9/0xec
>>  [<ffffffff8105935b>] ? mmput+0x49/0xde
>>  [<ffffffff81068125>] ? exit_ptrace+0xbf/0x153
>>  [<ffffffff8105f950>] do_exit+0x8d/0x6a6
>>  [<ffffffff8105fff0>] do_group_exit+0x87/0xb4
>>  [<ffffffff81060047>] sys_exit_group+0x2a/0x42
>>  [<ffffffff810120b2>] system_call_fastpath+0x16/0x1b
> 
> So your init (process with pid=1) is exiting while it should
> not do so.  This is not the cause, this is the symptom.  The
> cause is a few lines before.
> 
>> I have quite a bit of experience with FAI and I have never seen this
>> problem on real hardware. On my host system I am running squeeze with
>> 2.6.32-trunk-amd64 and a triple core AMD Phenom 8650.
> 
> I've no idea what is FAI.  But in any case it does not look like a
> bug related in any way to qemu-kvm.  There's something wrong with
> your initrd, and I don't think that BTS (Bug Tracking System) is a
> good place to find out what it is.
> 
> You have to find out why your initrd/initramfs (this is either kinit or
> the initial shell in the initrd or something like that) exits instead
> of calling the real init.
> 
> The fact that the previous line is "NET: Registered protocol family
> 17", which means the kernel finished initializing networking right
> before the panic, suggests that your initrd does not attempt to mount
> anything nor is trying to load any device drivers.  Usually you get
> this message right before initrd enters the game.  But you state that
> you do have some messages from initrd (Begin: Mounting root filesystem).
> 
> Your initrd is not functioning correctly.

It's probably a good idea to reassingn this to fai instead.  As I said
above, I don't know what FAI is.  Now I looked.  And it seems like it's
FAI who creates the initrd, not you.  Hence it might be FAI issue.

/mjt



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to