On 15/05/2015 08:34, Gerhard Wiesinger wrote:
Helllo,
I'm using latest qemu-kvm-2.3.0-3.fc21.x86_64 from libvirt repository
(updated afterwards). Running yum regularly crashes the VM like below.
VM is stripped down to minimum memory requirements (256MB) for owncloud.
See below.
Looks
On 15.05.2015 08:51, Paolo Bonzini wrote:
On 15/05/2015 08:34, Gerhard Wiesinger wrote:
Helllo,
I'm using latest qemu-kvm-2.3.0-3.fc21.x86_64 from libvirt repository
(updated afterwards). Running yum regularly crashes the VM like below.
VM is stripped down to minimum memory requirements
Helllo,
I'm using latest qemu-kvm-2.3.0-3.fc21.x86_64 from libvirt repository
(updated afterwards). Running yum regularly crashes the VM like below.
VM is stripped down to minimum memory requirements (256MB) for owncloud.
See below.
Looks like a problem in virtio-net or a kernel bug with
On 15/05/2015 09:37, Gerhard Wiesinger wrote:
Yes, yum takes memory. But there is ~2.2 GB virt memory available. That
should be enough. Therefore I think it is a kernel problem. As in
previous crashes on the mailing list there is a lot of swap available
(2GB) which isn't touched in ANY
On 15.05.2015 10:10, Paolo Bonzini wrote:
On 15/05/2015 09:37, Gerhard Wiesinger wrote:
Yes, yum takes memory. But there is ~2.2 GB virt memory available. That
should be enough. Therefore I think it is a kernel problem. As in
previous crashes on the mailing list there is a lot of swap
On Wed, Jun 6, 2012 at 4:38 AM, Charles.Tsai-蔡清海-研究發展部
charles.t...@cloudena.com wrote:
We hit a kernel panic when a VM was configured with bridge mode. After the
IpTable was disabled using the following command lines, the kernel panic was
gone. We would like to know if there is any fix in
We hit a kernel panic when a VM was configured with bridge mode. After the
IpTable was disabled using the following command lines, the kernel panic was
gone. We would like to know if there is any fix in latest kernel for this issue?
Note that we ran qemu 1.0 on Ubuntu 11.10
--
On Friday 19 October 2007 09:13:40 [EMAIL PROTECTED] wrote:
Then I try this command:
qemu -m 32 hda rootfs.img kernel linux-2.6.18.1/arch/i386/boot/bzImage
-append “root=/dev/hda \clock=pit”
and I get the error...
I tried to pass init=/sbin/init or init=/bin/init but it doesn't help...
Hi!
On 10/19/07, Kjel Delaey [EMAIL PROTECTED] wrote:
I came home and I tried the stuff at my desktop (I was in school in the
morning).
I followed your steps Christian and I have also downloaded the
detaolb_v06.iso file. I have also changed the line in .config.
I have extracted debug in my
Problem solved!Thanks for helping me out!
Kjel D.
From: [EMAIL PROTECTED]: [EMAIL PROTECTED]: RE: [Qemu-devel] Kernel panic - not
syncing: No init found. Trypassing init= option to kernel.Date: Fri, 19 Oct
2007 19:05:55 +0200
qemu screens
From: [EMAIL PROTECTED]: [EMAIL PROTECTED]: RE
Kjel,
I managed to compile the kernel with your config file and the vanilla
linux 2.6.18.1.
With the debug initramfs from DetaolB, I get similar error messages.
I enabled only CONFIG_BLK_DEV_INITRD=y and the problem was gone.
Could you please try this ? I can send you separately (off list) the
: [Qemu-devel] Kernel panic - not syncing: No init found.
Date: Fri, 19 Oct 2007 11:04:07 +0200
are you passing an initrd to qemu?
i call qemu like this:
qemu \
-hda image \
-boot c \
-net user \
-net nic,vlan=0,model=rtl8139 \
-initrd initrd \
-append root=/dev/hda1
I can't find the initramfs file. When I use locate initramfs I can find some
initramfs files, but none in the directory where I work in.
From: [EMAIL PROTECTED]
To: qemu-devel@nongnu.org
Subject: Re: RE: [Qemu-devel] Kernel panic - not syncing: No init found.
Date: Fri, 19 Oct 2007 11:04
read on a forum that this may be
a solution to the init problem. In my case it wasn't a working solution.
From: [EMAIL PROTECTED]
To: qemu-devel@nongnu.org; [EMAIL PROTECTED]
Subject: Re:[Qemu-devel] Kernel panic - not syncing: No init found.
Trypassinginit= option to kernel. Date
try to turn on these:
CONFIG_BLK_DEV_INITRD=y
CONFIG_BLOCK=y
CONFIG_PROC_SYSCTL=y (this one may not be valid for 2.6.18*)
--
Christian
--
http://detaolb.sourceforge.net/, a linux distribution for Qemu with Git inside !
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_KTIME_SCALAR=y
Date: Fri, 19 Oct 2007 10:12:51
+0200 From: [EMAIL PROTECTED] To: qemu-devel@nongnu.org Subject: Re:
[Qemu-devel] Kernel panic - not syncing: No init found
@nongnu.org; [EMAIL PROTECTED]
Subject: Re:[Qemu-devel] Kernel panic - not syncing: No init found.
Trypassinginit= option to kernel.
Date: Fri, 19 Oct 2007 09:19:59 +0200
CC:
On Friday 19 October 2007 09:13:40 [EMAIL PROTECTED] wrote:
Then I try this command:
qemu -m 32 hda rootfs.img
Hy,
I'm a student from Belgium and I have the following problem:
I'm trying to install qemu under ubuntu, but after the compilation of kernel
and after the installation of busybox I got the message:
Kernel panic - not syncing: No init found. Try passing init= option to kernel.
I didn't find a
/tty_io.c to change the lines where it sets noctty = 1; to
instead set it to 0. I recommend you instead run your shell on a real
console...
Date: Fri, 19 Oct 2007 14:19:55 +0200 From: [EMAIL PROTECTED] To:
qemu-devel@nongnu.org Subject: Re: [Qemu-devel] Kernel panic - not syncing:
No init found
support. I read on a forum that this may be
a solution to the init problem. In my case it wasn't a working solution.
From: [EMAIL PROTECTED]
To: qemu-devel@nongnu.org; [EMAIL PROTECTED]
Subject: Re:[Qemu-devel] Kernel panic - not syncing: No init found
Hello,
I've just installed Ubuntu Fiesty Fawn in a 4 GB raw partition using
qemu 0.8.2 and kqemu 1.3.0pre11. It works fine without the
-kernel-kqemu option, but with that option I get a kernel panic.
Specifically,
$ qemu -localtime -m 384 -boot c ubuntu.img
works great, but
qemu
Greetings,
I recently compiled kqemu for linux kernel version 2.6.19. I then proceeded
to attempt a debian etch installation. However when I use kqemu kernel
module I get a kernel panic when trying to boot the debian install cd. I do
not get a kernel panic when I specify -no-kqemu. So I
Hi,
I am using kqemu 1.3.0-pre9 and qemu 0.8.2 on Ubuntu Edgy, kernel
2.6.17-generic.
I run into kernel panic in the guest when launching qemu
-kernel-kqemu.
Some problems found on the net:
http://haiku-os.org/trac/ticket/748
hi,
I am running qemu (latest version from CVS) on my I32 Linux desktop to
emulate the MIPS arch. While running the mips-test-0.1.tar.gz
http://www.qemu.org/mips-test-0.1.tar.gz, everything works fine except
executing the exit command. I got the following information.
BusyBox v1.01 (Debian
Neo schrieb:
hi,
I am running qemu (latest version from CVS) on my I32 Linux desktop to
emulate the MIPS arch. While running the mips-test-0.1.tar.gz
http://www.qemu.org/mips-test-0.1.tar.gz, everything works fine
except executing the exit command. I got the following information.
BusyBox
Stefan Weil wrote:
Neo schrieb:
hi,
I am running qemu (latest version from CVS) on my I32 Linux desktop to
emulate the MIPS arch. While running the mips-test-0.1.tar.gz
http://www.qemu.org/mips-test-0.1.tar.gz, everything works fine
except executing the exit command. I got the following
On Saturday, September 2, 2006, 0:01:21, Neo wrote:
Thank you for your explanation. But why there is no kernel panic when
the target host is PC?
Specify init=/bin/sh on the kernel command line, and type exit when you get
the shell - you'll also get a kernel panic.
--
Jernej Simonèiè
Hey
I've been experiencing consistent kernel panics with the configuration
above and the -kernel-kqemu option. Solved it by simply ignoring the
BIOS's PCI table (kernel option pci=nobios).
Here's what the kernel spat out (if it helps):
general protection fault: 0060 [#1]
Modules linked in:
My system is: kqemu 1.3.0pre7 + qemu 0.8.1 + Suse 10 + Pentium D
and I'm tried to run Suse 10.0 and Auros 11.1 as guest OS.
Both do kernel panic on boot, but work fine with user-level virtualization.
WinXP Prof. runs fine with full virtualization, hope Linux would also be
supported...
Cheers
Frank,
Try adding the debug statement to your kernel boot options. It makes my
fc5 systems boot correctly with -kernel-kqemu emulation. Not sure why
this fixes it, and haven't had much time to see but it was a quick work
around for the performance increase.
--
Thank You,
Ben Dailey
[EMAIL
30 matches
Mail list logo
