From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Re: slirp regression
Date: Thu, 02 Jul 2009 13:03:41 +0300 [thread overview]
Message-ID: <4A4C85FD.4030100@redhat.com> (raw)
In-Reply-To: <4A4C6C75.5070000@siemens.com>
On 07/02/2009 11:14 AM, Jan Kiszka wrote:
> Avi Kivity wrote:
>
>> Slirp now defaults to direct connection (no gateway) to 10.0.0.0/8,
>> compared to 10.0.2.0/24 in the past. This renders my real 10.0.0.0/8
>> network inaccessible.
>>
>> Also, NetworkManager in F11 isn't able to bind to the network - I have
>> to dhclient manually. I don't know whether this is a regression or an
>> F11 bug.
>>
>
> Please post the corresponding pcap trace generated by "-net dump".
>
>
[avi@barcelona1 qemu-kvm (master)]$ q -m 1024 /images/F11.img -cdrom
/home/avi/iso/linux/Fedora-11-x86_64-DVD.iso -net nic -net user -drive
file=/dev/vg0/compile,if=virtio,cache=none -smp 8 -redir tcp:4444::22
-net dump
kvm_create_vcpu: Bad file descriptor
kvm_create_vcpu: Bad file descriptor
kvm_create_vcpu: Bad file descriptor
kvm_create_vcpu: Bad file descriptor
kvm_create_vcpu: Bad file descriptor
kvm_create_vcpu: Bad file descriptor
kvm_create_vcpu: Bad file descriptor
kvm_create_vcpu: Bad file descriptor
create_userspace_phys_mem: Bad file descriptor
kvm_cpu_register_physical_memory: failed
Looks like something is closing random file descriptors.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-07-02 10:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-02 8:11 [Qemu-devel] slirp regression Avi Kivity
2009-07-02 8:14 ` [Qemu-devel] " Jan Kiszka
2009-07-02 10:03 ` Avi Kivity [this message]
2009-07-02 10:06 ` Avi Kivity
2009-07-02 10:27 ` Jan Kiszka
2009-07-02 10:10 ` Avi Kivity
2009-07-02 10:23 ` Jan Kiszka
2009-07-02 10:58 ` Avi Kivity
2009-07-02 19:03 ` Jan Kiszka
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=4A4C85FD.4030100@redhat.com \
--to=avi@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).