All of lore.kernel.org
 help / color / mirror / Atom feed
From: Herbert Poetzl <herbert@13thfloor.at>
To: list-qemu@alias.spaceandtime.org
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Debian 3.0 Problems
Date: Sun, 9 May 2004 14:56:28 +0200	[thread overview]
Message-ID: <20040509125628.GA4493@MAIL.13thfloor.at> (raw)
In-Reply-To: <1084089818.5383.196108898@webmail.messagingengine.com>

On Sun, May 09, 2004 at 03:03:38AM -0500, list-qemu@alias.spaceandtime.org wrote:
> Hello,
> 
> I installed Debian 3.0r2 under Qemu.  However, I have the following
> problems:
> 
> 1. During boot I get the message:
> 
> modprobe: modprobe: Can't locate module char-major-10-135
> 
> 2. During boot and at random times I get the message:
> 
> probable hardware bug: clock timer configuration lost - probably a
> VIA686a.
> probable hardware bug: restoring chip configuration.
> 
> Sometime it appears many times, sometimes not so many.
> 
> 3. Can't get network working at all.  I'm running a fully updated Fedora
> Core 1.  /dev/net/tun exists.  I put the qemu-ifup script in /etc.  I
> also tried the instructions on
> http://user-mode-linux.sourceforge.net/networking.html.  Nothing works. 
> Qemu always reports:
> 
> warning: could not open /dev/net/tun: no virtual network emulation

make sure the tun module on the Host system is loaded
(or configured for autoload on /dev/net/tun request)
and check if the device entry in /dev/net is present
(if you do not use devfs or udev)

HTH,
Herbert

> Thanks.
> 
> 
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://mail.nongnu.org/mailman/listinfo/qemu-devel

  reply	other threads:[~2004-05-09 12:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-09  8:03 [Qemu-devel] Debian 3.0 Problems list-qemu
2004-05-09 12:56 ` Herbert Poetzl [this message]
2004-05-10  3:37   ` [Qemu-devel] " list-qemu

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=20040509125628.GA4493@MAIL.13thfloor.at \
    --to=herbert@13thfloor.at \
    --cc=list-qemu@alias.spaceandtime.org \
    --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 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.