[Qemu-devel] [Bug 1186984] Re: large -initrd crashes qemu
I'm using qemu from git (f10acc8b38d65a66ffa0588a036489d7fa6a593e). -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1186984 Title: large -initrd crashes qemu Status in QEMU: New Bug description: We don't use large -initrd in libguestfs any more, but I noticed that a large -initrd file now crashes qemu spectacularly: $ ls -lh /tmp/kernel /tmp/initrd -rw-r--r--. 1 rjones rjones 273M Jun 3 14:02 /tmp/initrd lrwxrwxrwx. 1 rjones rjones 35 Jun 3 14:02 /tmp/kernel -> /boot/vmlinuz-3.9.4-200.fc18.x86_64 $ ./x86_64-softmmu/qemu-system-x86_64 -L pc-bios \ -kernel /tmp/kernel -initrd /tmp/initrd -hda /tmp/test1.img -serial stdio \ -append console=ttyS0 qemu crashes with one of several errors: PFLASH: Possible BUG - Write block confirm qemu: fatal: Trying to execute code outside RAM or ROM at 0x000b96cd If -enable-kvm is used: KVM: injection failed, MSI lost (Operation not permitted) In all cases the SDL display fills up with coloured blocks before the crash (see the attached screenshot). To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1186984/+subscriptions
[Qemu-devel] [Bug 1186984] Re: large -initrd crashes qemu
One way to reproduce this is to just use a large (200 MB) completely random initrd. Note this error seems to happen a long time before even the kernel starts up, so the actual content of the initrd doesn't matter. dd if=/dev/urandom of=/tmp/initrd bs=1M count=200 qemu-system-x86_64 -kernel /boot/vmlinuz -initrd /tmp/initrd -serial stdio -append console=ttyS0 -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1186984 Title: large -initrd crashes qemu Status in QEMU: New Bug description: We don't use large -initrd in libguestfs any more, but I noticed that a large -initrd file now crashes qemu spectacularly: $ ls -lh /tmp/kernel /tmp/initrd -rw-r--r--. 1 rjones rjones 273M Jun 3 14:02 /tmp/initrd lrwxrwxrwx. 1 rjones rjones 35 Jun 3 14:02 /tmp/kernel -> /boot/vmlinuz-3.9.4-200.fc18.x86_64 $ ./x86_64-softmmu/qemu-system-x86_64 -L pc-bios \ -kernel /tmp/kernel -initrd /tmp/initrd -hda /tmp/test1.img -serial stdio \ -append console=ttyS0 qemu crashes with one of several errors: PFLASH: Possible BUG - Write block confirm qemu: fatal: Trying to execute code outside RAM or ROM at 0x000b96cd If -enable-kvm is used: KVM: injection failed, MSI lost (Operation not permitted) In all cases the SDL display fills up with coloured blocks before the crash (see the attached screenshot). To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1186984/+subscriptions
[Qemu-devel] [Bug 1186984] Re: large -initrd crashes qemu
OK I see what's happening. Because I forgot about the -m option, qemu allocates 128 MB of RAM. It's obviously wrapping around in memory and overwriting all the low memory. If you add (eg) -m 1024 it works. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1186984 Title: large -initrd crashes qemu Status in QEMU: New Bug description: We don't use large -initrd in libguestfs any more, but I noticed that a large -initrd file now crashes qemu spectacularly: $ ls -lh /tmp/kernel /tmp/initrd -rw-r--r--. 1 rjones rjones 273M Jun 3 14:02 /tmp/initrd lrwxrwxrwx. 1 rjones rjones 35 Jun 3 14:02 /tmp/kernel -> /boot/vmlinuz-3.9.4-200.fc18.x86_64 $ ./x86_64-softmmu/qemu-system-x86_64 -L pc-bios \ -kernel /tmp/kernel -initrd /tmp/initrd -hda /tmp/test1.img -serial stdio \ -append console=ttyS0 qemu crashes with one of several errors: PFLASH: Possible BUG - Write block confirm qemu: fatal: Trying to execute code outside RAM or ROM at 0x000b96cd If -enable-kvm is used: KVM: injection failed, MSI lost (Operation not permitted) In all cases the SDL display fills up with coloured blocks before the crash (see the attached screenshot). To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1186984/+subscriptions
