From: Cam Macdonell <cam-edFDblaTWIyXbbII50Afww@public.gmane.org>
To: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Problem with vde/dnsmasq on CentOS 5.0
Date: Tue, 27 Nov 2007 16:32:57 -0700 [thread overview]
Message-ID: <474CA929.9020907@cs.ualberta.ca> (raw)
Hi,
Apologies for this not being a specific KVM issue. I cannot get
vde/dnsmasq working with KVM on CentOS 5.0. It works fine on FC6
basically following the instructions here
https://help.ubuntu.com/community/KVM.
However, when I move to CentOS 5, I constantly get the "Sendto: bad file
descriptor" error when I try to run with a vde tap interface. The error
happens when the guest tries to setup networking.
Has anyone had success with vde/dnsmasq on CentOS or another RHEL clone?
Is there an alternative tap-based approach other than vde?
Any help or pointers are appreciated.
Thanks,
Cam
-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
reply other threads:[~2007-11-27 23:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=474CA929.9020907@cs.ualberta.ca \
--to=cam-edfdblatwiyxbbii50afww@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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