Bug 814494

Summary: usermode networking fails: slirp/arp_table.c:75: arp_table_search Assertion
Product: [Fedora] Fedora Reporter: Gustavo Padovan <gustavo>
Component: qemuAssignee: Fedora Virtualization Maintainers <virt-maint>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: amit.shah, berrange, cfergeau, crobinso, dwmw2, itamar, knoel, pbonzini, scottt.tw, virt-maint
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-09-11 06:18:44 EDT Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Gustavo Padovan 2012-04-19 22:07:42 EDT
Description of problem:

I'm running:

sudo qemu-kvm -hda /home/padovan/p/vdisk2.qcow2 -kernel arch/x86/boot/bzImage \
        -append "ro root=/dev/hda1 console=ttyS0 init=/bin/systemd" \
        -nographic \
        -net nic -net user,hostfwd=tcp::5555-:22 -smp 3 -m 312

and qemu-kvm fails with:

qemu-kvm: slirp/arp_table.c:75: arp_table_search: Assertion `(ip_addr & (__extension__ ({ register unsigned int __v, __x = (~(0xf << 28)); if (__builtin_constant_p (__x)) __v = ((((__x) & 0xff000000) >> 24) | (((__x) & 0x00ff0000) >> 8) | (((__x) & 0x0000ff00) << 8) | (((__x) & 0x000000ff) << 24)); else __asm__ ("bswap %0" : "=r" (__v) : "0" (__x)); __v; }))) != 0' failed.

If I run "-net none" qemu works fine, but then I don't have any network interface.

Version-Release number of selected component (if applicable):

padovan bluetooth-testing $ qemu-kvm --version
QEMU emulator version 1.0 (qemu-kvm-1.0), Copyright (c) 2003-2008 Fabrice Bellard


How reproducible:


Steps to Reproduce:
Actual results:
qemu fails.

Expected results:
QEMU should run the virtual machine without problems.

Additional info:
Comment 1 Paolo Bonzini 2012-09-11 06:18:44 EDT
This is fixed in F18.  We will backport 1.2.0 to F17 in some time.