From: Gleb Natapov <gleb@redhat.com>
To: K D <kdcalif@yahoo.com>
Cc: avi@redhat.com, mtosatti@redhat.com, kvm@vger.kernel.org
Subject: Re: qemu-kvm.0.12.2 aborts on linux
Date: Sun, 2 May 2010 08:23:16 +0300 [thread overview]
Message-ID: <20100502052316.GY10044@redhat.com> (raw)
In-Reply-To: <792291.45224.qm@web55507.mail.re4.yahoo.com>
On Thu, Apr 29, 2010 at 07:35:02AM -0700, K D wrote:
> Here are my ulimits
>
> $ ulimit -a
> core file size (blocks, -c) unlimited
> data seg size (kbytes, -d) unlimited
> scheduling priority (-e) 0
> file size (blocks, -f) unlimited
> pending signals (-i) 71680
> max locked memory (kbytes, -l) 32
> max memory size (kbytes, -m) unlimited
> open files (-n) 1024
> pipe size (512 bytes, -p) 8
> POSIX message queues (bytes, -q) 819200
> real-time priority (-r) 0
> stack size (kbytes, -s) 8192
> cpu time (seconds, -t) unlimited
> max user processes (-u) 1024
> virtual memory (kbytes, -v) 204800
Your virtual memory is limited to 200M. Make it unlimited.
> file locks (-x) unlimited
> $
>
> I'm using monta vista distribution. I went through qemu code and there is no place to raise rlimits. didn't want to touch it.
>
> thanks for looking.
>
>
>
>
>
> ________________________________
> From: Gleb Natapov <gleb@redhat.com>
> To: K D <kdcalif@yahoo.com>
> Cc: avi@redhat.com; mtosatti@redhat.com; kvm@vger.kernel.org
> Sent: Thu, April 29, 2010 3:17:06 AM
> Subject: Re: qemu-kvm.0.12.2 aborts on linux
>
> On Wed, Apr 28, 2010 at 10:19:37AM -0700, K D wrote:
> > Am using yahoo mail and my mails to this mailer gets rejected every time saying message has HTML content etc. Should I use some other mail tool? Below is my issue.
> >
> > I am trying to get KVM/qemu running on linux. I compiled 2.6.27.10 by enabling "KVM", "KVM for intel" options at configure time. My box is running with this KVM enabled inside kernel. I also built qemu-kvm-0.12.2 using above kernel headers etc. I enabled virtualization in BIOS. I didn't try to install any guest from CD etc. I made a hard disk image, installed grub on it, copied kernel, initrd onto it. Now when I try to create Vm as below, it crashes with following backtrace. What could be going wrong?
> >
> > Also when I try to say "-m 256" malloc (or posix_memalign) fails with ENOMEM. So right now "-m 128", which is default, works. Why is that? I have 4G RAM in my setup and my native linux is using less than 1G. Is there some rlimits for qemu that I need to raise?
> >
> > Sounds like I'm doing some basic stuff wrong. I'm using bios, vapic, pxe-rtl bin straight from the qemu-kvm dir.
> >
> > If I don't do '-nographic' its running into some malloc failure inside some vga routine. I pasted that backtrace too below.
> >
> What's your Linux distribution? First trace bellow shows that ptheard_create()
> failed which is strange. What ulimit -a shows?
>
>
> > Appreciate your help.
> > thanks
> >
> > qemu-system-x86_64 -hda /dev/shm/vmhd.img -bios ./bios.bin --option-rom ./vapic.bin -curses -nographic -vga none -option-rom ./pxe-rtl8139.bin
> >
> > #0 0x414875a6 in raise () from /lib/libc.so.6
> > (gdb) bt
> > #0 0x414875a6 in raise () from /lib/libc.so.6
> > #1 0x4148ad18 in abort () from /lib/libc.so.6
> > #2 0x080b4cb3 in die2 (err=<value optimized out>,
> > what=0x81f2662 "pthread_create") at posix-aio-compat.c:80
> > #3 0x080b5682 in thread_create (arg=<value optimized out>,
> > start_routine=<value optimized out>, attr=<value optimized out>,
> > thread=<value optimized out>) at posix-aio-compat.c:118
> > #4 spawn_thread () at posix-aio-compat.c:379
> > #5 qemu_paio_submit (aiocb=0x846b550) at posix-aio-compat.c:390
> > #6 0x080b57cb in paio_submit (bs=0x843c008, fd=5, sector_num=0,
> > qiov=0x84cefb8, nb_sectors=512, cb=0x81cb950 <dma_bdrv_cb>,
> > opaque=0x84cef80, type=1) at posix-aio-compat.c:584
> > #7 0x080cc7b8 in raw_aio_submit (type=<value optimized out>,
> > opaque=<value optimized out>, cb=<value optimized out>,
> > nb_sectors=<value optimized out>, qiov=<value optimized out>,
> > sector_num=<value optimized out>, bs=<value optimized out>)
> > at block/raw-posix.c:562
> > #8 raw_aio_readv (bs=0x843c008, sector_num=0, qiov=0x84cefb8, nb_sectors=1,
> > cb=0x81cb950 <dma_bdrv_cb>, opaque=0x84cef80) at block/raw-posix.c:570
> > #9 0x080b0593 in bdrv_aio_readv (bs=0x843c008, sector_num=0, qiov=0x84cefb8,
> > nb_sectors=1, cb=0x81cb950 <dma_bdrv_cb>, opaque=0x84cef80)
> > at block.c:1548
> > #10 0x081cbb26 in dma_bdrv_cb (opaque=0x84cef80, ret=0)
> > at /ws/pkoya-sjc/temp/qemu-kvm-0.12.2/dma-helpers.c:123
> > #11 0x081cbcde in dma_bdrv_io (bs=0x843c008, sg=0x846861c, sector_num=0,
> > cb=0x8074320 <ide_read_dma_cb>, opaque=0x8468f1c, is_write=0)
> > at /ws/pkoya-sjc/temp/qemu-kvm-0.12.2/dma-helpers.c:167
> > #12 0x0807441b in ide_read_dma_cb (opaque=0x8468f1c, ret=0)
> > at /ws/pkoya-sjc/temp/qemu-kvm-0.12.2/hw/ide/core.c:597
> > #13 0x080760ec in bmdma_cmd_writeb (opaque=0x8468f1c, addr=49152, val=9)
> > at /ws/pkoya-sjc/temp/qemu-kvm-0.12.2/hw/ide/pci.c:51
> > #14 0x080d9d5f in ioport_write (data=<value optimized out>,
> > address=<value optimized out>, index=<value optimized out>) at ioport.c:80
> > #15 cpu_outb (addr=6587, val=<value optimized out>) at ioport.c:198
> > #16 0xb60a3bc9 in ?? ()
> > #17 0x0000c000 in ?? ()
> > #18 0x00000009 in ?? ()
> > #19 0x00000000 in ?? ()
> > (gdb) q
> >
> > backtrace without "-nographic"
> > ============================
> > (gdb) bt
> > #0 0x414875a6 in raise () from /lib/libc.so.6
> > #1 0x4148ad18 in abort () from /lib/libc.so.6
> > #2 0x080b4c3c in qemu_memalign (alignment=4096, size=16777216) at osdep.c:96
> > #3 0x080b4c5a in qemu_vmalloc (size=16777216) at osdep.c:110
> > #4 0x08119995 in qemu_ram_alloc (size=16777216)
> > at /devel/temp/qemu-kvm-0.12.2/exec.c:2550
> > #5 0x0807ffd0 in vga_common_init (s=0x84be7e4, vga_ram_size=16777216)
> > at /devel/temp/qemu-kvm-0.12.2/hw/vga.c:2291
> > #6 0x080a1c4b in pci_cirrus_vga_initfn (dev=0x84be618)
> > at /devel/temp/qemu-kvm-0.12.2/hw/cirrus_vga.c:3209
> > #7 0x0805e61e in pci_qdev_init (qdev=0x84be618, base=0x8229700)
> > at /devel/temp/qemu-kvm-0.12.2/hw/pci.c:1482
> > #8 0x080fa7ee in qdev_init (dev=0x84be618)
> > at /devel/temp/qemu-kvm-0.12.2/hw/qdev.c:242
> > #9 0x080fa885 in qdev_init_nofail (dev=0x84be618)
> > at /devel/temp/qemu-kvm-0.12.2/hw/qdev.c:285
> > #10 0x0805d8ca in pci_create_simple (bus=0x845ab58, devfn=-1,
> > name=0x81ce0f8 "cirrus-vga")
> > at /devel/temp/qemu-kvm-0.12.2/hw/pci.c:1533
> > #11 0x080a2c71 in pci_cirrus_vga_init (bus=0x845ab58)
> > at /devel/temp/qemu-kvm-0.12.2/hw/cirrus_vga.c:3235
> > #12 0x0808abc3 in pc_init1 (ram_size=<value optimized out>,
> > boot_device=0xbf9fea17 "cad", kernel_filename=0x0,
> > kernel_cmdline=0x81f82f8 "", initrd_filename=0x0,
> > cpu_model=0x81eca10 "qemu64", pci_enabled=1)
> > at /devel/temp/qemu-kvm-0.12.2/hw/pc.c:1149
> > #13 0x080518db in main (argc=8, argv=0xbf9feaf4, envp=Cannot access memory at address 0x7730
> > )
> > at /devel/temp/qemu-kvm-0.12.2/vl.c:6055
> > (gdb) q
> >
>
> --
> Gleb.
>
>
>
>
--
Gleb.
next prev parent reply other threads:[~2010-05-02 5:23 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-28 16:15 [PATCHv2 00/23] next round of emulator cleanups Gleb Natapov
2010-04-28 16:15 ` [PATCHv2 01/23] KVM: x86 emulator: introduce read cache Gleb Natapov
2010-04-28 16:15 ` [PATCHv2 02/23] KVM: x86 emulator: fix Move r/m16 to segment register decoding Gleb Natapov
2010-04-28 16:15 ` [PATCHv2 03/23] KVM: x86 emulator: cleanup xchg emulation Gleb Natapov
2010-04-28 16:15 ` [PATCHv2 04/23] KVM: x86 emulator: cleanup nop emulation Gleb Natapov
2010-04-28 16:15 ` [PATCHv2 05/23] KVM: x86 emulator: handle "far address" source operand Gleb Natapov
2010-04-28 16:15 ` [PATCHv2 06/23] KVM: x86 emulator: add (set|get)_dr callbacks to x86_emulate_ops Gleb Natapov
2010-04-28 16:15 ` [PATCHv2 07/23] KVM: x86 emulator: add (set|get)_msr " Gleb Natapov
2010-04-28 16:15 ` [PATCHv2 08/23] KVM: x86 emulator: add get_cached_segment_base() callback " Gleb Natapov
2010-04-28 16:15 ` [PATCHv2 09/23] KVM: x86 emulator: cleanup some direct calls into kvm to use existing callbacks Gleb Natapov
2010-04-28 16:15 ` [PATCHv2 10/23] KVM: x86 emulator: make set_cr() callback return error if it fails Gleb Natapov
2010-04-28 16:15 ` [PATCHv2 11/23] KVM: x86 emulator: make (get|set)_dr() " Gleb Natapov
2010-04-28 16:15 ` [PATCHv2 12/23] KVM: x86 emulator: fix X86EMUL_RETRY_INSTR and X86EMUL_CMPXCHG_FAILED values Gleb Natapov
2010-04-28 16:15 ` [PATCHv2 13/23] KVM: fill in run->mmio details in (read|write)_emulated function Gleb Natapov
2010-04-28 16:15 ` [PATCHv2 14/23] KVM: x86 emulator: x86_emulate_insn() return -1 only in case of emulation failure Gleb Natapov
2010-04-28 16:15 ` [PATCHv2 15/23] KVM: remove export of emulator_write_emulated() Gleb Natapov
2010-04-28 16:15 ` [PATCHv2 16/23] KVM: do not inject #PF in (read|write)_emulated() callbacks Gleb Natapov
2010-04-28 16:15 ` [PATCHv2 17/23] KVM: handle emulation failure case first Gleb Natapov
2010-04-28 16:15 ` [PATCHv2 18/23] KVM: x86 emulator: advance RIP outside x86 emulator code Gleb Natapov
2010-04-28 16:15 ` [PATCHv2 19/23] KVM: x86 emulator: set RFLAGS " Gleb Natapov
2010-04-28 16:15 ` [PATCHv2 20/23] KVM: x86 emulator: use shadowed register in emulate_sysexit() Gleb Natapov
2010-04-28 16:15 ` [PATCHv2 21/23] KVM: x86 exmulator: handle shadowed registers outside emulator Gleb Natapov
2010-04-28 16:15 ` [PATCHv2 22/23] KVM: x86 emulator: move interruptibility state tracking out of emulator Gleb Natapov
2010-04-28 16:15 ` [PATCHv2 23/23] KVM: x86 emulator: do not inject exception directly into vcpu Gleb Natapov
[not found] ` <446597.86519.qm@web55502.mail.re4.yahoo.com>
2010-04-29 10:17 ` qemu-kvm.0.12.2 aborts on linux Gleb Natapov
[not found] ` <792291.45224.qm@web55507.mail.re4.yahoo.com>
2010-05-02 5:23 ` Gleb Natapov [this message]
[not found] ` <710443.70603.qm@web55504.mail.re4.yahoo.com>
2010-05-03 7:44 ` Gleb Natapov
2010-04-29 9:26 ` [PATCHv2 00/23] next round of emulator cleanups Avi Kivity
2010-05-05 7:57 ` Avi Kivity
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100502052316.GY10044@redhat.com \
--to=gleb@redhat.com \
--cc=avi@redhat.com \
--cc=kdcalif@yahoo.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.