All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Barry Silverman" <barry@disus.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.sourceforge.net
Subject: RE: Problems with latest unstable 1.3
Date: Tue, 30 Mar 2004 19:46:16 -0500	[thread overview]
Message-ID: <IGEMLBGAECDFPIKMIMLCMELMCFAA.barry@disus.com> (raw)
In-Reply-To: <E1B7y4O-0000Gb-00@mta1.cl.cam.ac.uk>

In the new I/O world if xen owns the network interface, what does xenolinux
have to use as eth0?

Are there any devices (such as virtual disks) that I can use with the code
as is on a non-0 guest?

Barry Silverman

-----Original Message-----
From: xen-devel-admin@lists.sourceforge.net
[mailto:xen-devel-admin@lists.sourceforge.net]On Behalf Of Keir Fraser
Sent: Monday, March 29, 2004 9:49 AM
To: Keir Fraser
Cc: Barry Silverman; xen-devel@lists.sourceforge.net
Subject: Re: [Xen-devel] Problems with latest unstable 1.3



Okay, I checked in a patch to sort out all these problems. Please try
it out on QEMU again and let me know if probing fails.

Note that only DOM0 will be useful in such a setup right now --- there
is no way for other domains to access devices that are controlled by
DOM0. New inter-domain virtual device drivers to cope with this are in
the pipeline...

 -- Keir

>
> The PCI- and IRQ-virtualisation is not quite there yet -- but hopefully
> it will be in a couple of days.
>
> Issues at the moment are:
>  - probing and routing of device interrupt pins -> IRQs is broken.
>  - passing of physical interrupts to guest OSes is untested and thus
>    probably broken in some way or another.
>
> I'm currently addressing all these problems.
>
>  -- Keir
>
> > I have been trying out the latest unstable with the new i/o and have
found
> > the following issue. I created a xen.gz with nodev=y set, and tried it
out
> > with all my devices in xenolinux.
> >
> > The "machine" I am running on is "qemu", and it doesn't have emulation
for
> > PCI. Therefore xenolinux is doing its ideprobes independent of the pci
ide
> > code.
> > It is calling the routine "probe_irq_on" in irq.c, and it is failing
with
> > the following messages:
> >
> > ide: Assuming 50MHz system bus speed for PIO modes; override with
idebus=xx
> > Kernel panic: Failed to obtain physical IRQ 127
> >
> > "Probe_irq_on" is used to enable ALL unallocated irqs, the caller code
will
> > then twig the device you are probing (in my case it is the ide drives
for
> > ide0 disk, and ide0 cdrom) - and then will record the irq that actually
got
> > the interrupt thus figuring out which irq belongs to which device.
> >
> > The reasons it is failing seem to be the following:
> > 1) The probe enables 127 physical IRQs (NR_PIRQS), but xen fails to bind
any
> > pirq > 63. This is because sched.h only defines pirq_to_evtchn with a
size
> > of 64
> > 2) When I tried making that constant from 64->128, it still failed on
IRQ 12
> > (which I think was already allocated to another device).
> >
> > I was able to get much much further by setting "ide0=0x1f0,0x3f6,14
> > ide1=noprobe ide2=noprobe ide3=noprobe" on the command line. It still
failed
> > much later on with an MMU update failure. I am currently tracking that
one
> > down further before reporting it.
> >
> >
> > Barry Silverman
> >
> >
> >
> > -------------------------------------------------------
> > This SF.Net email is sponsored by: IBM Linux Tutorials
> > Free Linux tutorial presented by Daniel Robbins, President and CEO of
> > GenToo technologies. Learn everything from fundamentals to system
> > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/xen-devel
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: IBM Linux Tutorials
> Free Linux tutorial presented by Daniel Robbins, President and CEO of
> GenToo technologies. Learn everything from fundamentals to system
> administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xen-devel



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xen-devel



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click

  reply	other threads:[~2004-03-31  0:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-29  0:18 Problems with latest unstable 1.3 Barry Silverman
2004-03-29  7:49 ` Keir Fraser
2004-03-29 14:48   ` Keir Fraser
2004-03-31  0:46     ` Barry Silverman [this message]
2004-03-30 17:05       ` Rolf Neugebauer
2004-03-31  3:15         ` Barry Silverman
2004-03-31  6:53           ` Keir Fraser

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=IGEMLBGAECDFPIKMIMLCMELMCFAA.barry@disus.com \
    --to=barry@disus.com \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=xen-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 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.