From: iMil <imil@imil.net>
To: kvm-devel@lists.sourceforge.net
Subject: kvm > 61 segfaults when started with a bridged tap
Date: Sun, 4 May 2008 13:16:14 +0200 (CEST) [thread overview]
Message-ID: <20080504124714.M6003@senate.imil.net> (raw)
Hi,
Since I upgraded my ubuntu machine to 8.04,
/usr/local/bin/qemu-system-x86_64 segfaults when starting with -net
tap,ifname=tap0 flags. Of course, it's been recompiled.
$ sudo /usr/local/bin/qemu-system-x86_64 /data/virt/netbsd.img -net
nic,macaddr=00:56:01:02:03:04 -net tap,ifname=tap0,script=/etc/qemu-ifup
Segmentation fault
I see the same behaviour with any NIC, and for kvm from -62 to -67 (I
tested each version).
Downgrading to kvm-61 fixes the problem. It seems like there's a similar
bug report here:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=476469
The VM also start correctly with qemu.
$ modinfo kvm-intel
filename: /lib/modules/2.6.24-16-generic/extra/kvm-intel.ko
license: GPL
author: Qumranet
version: kvm-67
srcversion: 2E2C88C6F09E216FDAA6797
depends: kvm
vermagic: 2.6.24-16-generic SMP mod_unload 586
parm: bypass_guest_pf:bool
parm: enable_vpid:bool
parm: flexpriority_enabled:bool
$ uname -a
Linux tatooine 2.6.24-16-generic #1 SMP Thu Apr 10 13:23:42 UTC 2008 i686
GNU/Linux
$ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Core(TM)2 CPU 6300 @ 1.86GHz
stepping : 6
cpu MHz : 1596.000
cache size : 2048 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 2
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe lm
constant_tsc arch_perfmon pebs bts pni monitor ds_cpl vmx est tm2 ssse3
cx16 xtpr lahf_lm
bogomips : 3736.56
clflush size : 64
processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Core(TM)2 CPU 6300 @ 1.86GHz
stepping : 6
cpu MHz : 1596.000
cache size : 2048 KB
physical id : 0
siblings : 2
core id : 1
cpu cores : 2
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe lm
constant_tsc arch_perfmon pebs bts pni monitor ds_cpl vmx est tm2 ssse3
cx16 xtpr lahf_lm
bogomips : 3733.37
clflush size : 64
Interesting packages
ii bridge-utils 1.2-2
ii iproute 20071016-2ubuntu1
ii libc6 2.7-10ubuntu3
Hope this helps,
regards
----------------------------------------
Emile "iMil" Heitor <imil@home.imil.net> _
http://gcu-squad.org ASCII ribbon campaign ( )
- against HTML email X
& vCards / \
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
next reply other threads:[~2008-05-04 11:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-04 11:16 iMil [this message]
2008-05-04 13:16 ` kvm > 61 segfaults when started with a bridged tap Avi Kivity
-- strict thread matches above, loose matches on Subject: below --
2008-09-28 11:09 iMil
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=20080504124714.M6003@senate.imil.net \
--to=imil@imil.net \
--cc=kvm-devel@lists.sourceforge.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox