|
|
|
|
|
|
|
|
|
|
xen-devel
Re: [Xen-devel] Re: pv_ops dom0 USB fixed
On Thu, Dec 11, 2008 at 09:19:21PM +0000, Ian Campbell wrote:
> On Thu, 2008-12-11 at 16:12 -0500, Todd Deshane wrote:
> > On Thu, Dec 11, 2008 at 3:25 PM, Jeremy Fitzhardinge <jeremy@xxxxxxxx>
> > wrote:
> > > Todd Deshane wrote:
> > >>
> > >> OK. I add this and now xend is trying to start.
> > >>
> > >> I am getting python xc level errors now though.
> > >>
> > >> I might need to rebuild something or I might
> > >> have broke a python path.
> > >>
> > >
> > > Yes, it looks like you've got something wrong on the python side. Have
> > > you
> > > rebuilt it lately? You'll need a moderately recent version of
> > > xen-unstable
> > > anyway.
> > >
> >
> > Just pulled the latest and re-compiled.
> >
> > Booted up and successfully started xend!
> >
> > Make a quick attempt at booting a guest, but ran into errors.
> >
> > Full log attached.
> >
> > I cat'd error logs and ran command that might give some
> > info.
> >
> > Is guest support implemented? workarounds/gotchas?
>
> Only blkback is present at the moment and I notice you have a vif
> configured, it's possible the lack of netback is confusing xend. A guest
> with disks but no network should work.
>
> > Also dom0 is using all of my memory (most of it,
> > left with with a small number of megabytes to work
> > with (i did free -m in the output)
>
> I think it should autoballoon down in the normal way if you have a new
> enough xen-unstable. Jeremy patched the tools to work with the pvops
> balloon a few week ago.
>
Is the pv_ops ballooning support the only thing that's required from
xen-unstable? Or is there something else too that's needed for pv_ops dom0
that is only in xen-unstable?
-- Pasi
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- Re: [Xen-devel] Re: pv_ops dom0 USB fixed, (continued)
- Re: [Xen-devel] Re: pv_ops dom0 USB fixed, Ian Campbell
- Re: [Xen-devel] Re: pv_ops dom0 USB fixed, Todd Deshane
- Re: [Xen-devel] Re: pv_ops dom0 USB fixed, Jeremy Fitzhardinge
- Re: [Xen-devel] Re: pv_ops dom0 USB fixed, Todd Deshane
- Re: [Xen-devel] Re: pv_ops dom0 USB fixed, Ian Campbell
- Re: [Xen-devel] Re: pv_ops dom0 USB fixed, Todd Deshane
- Re: [Xen-devel] Re: pv_ops dom0 USB fixed, Todd Deshane
- Re: [Xen-devel] Re: pv_ops dom0 USB fixed, Jeremy Fitzhardinge
- Re: [Xen-devel] Re: pv_ops dom0 USB fixed, Todd Deshane
- Re: [Xen-devel] Re: pv_ops dom0 USB fixed, Todd Deshane
- Re: [Xen-devel] Re: pv_ops dom0 USB fixed,
Pasi Kärkkäinen <=
- Re: [Xen-devel] Re: pv_ops dom0 USB fixed, Jeremy Fitzhardinge
- Re: [Xen-devel] Re: pv_ops dom0 USB fixed, Jeremy Fitzhardinge
- Re: [Xen-devel] Re: pv_ops dom0 USB fixed, Todd Deshane
- Re: [Xen-devel] Re: pv_ops dom0 USB fixed, Andrew Lyon
- Re: [Xen-devel] Re: pv_ops dom0 USB fixed, Pasi Kärkkäinen
- Re: [Xen-devel] Re: pv_ops dom0 USB fixed, Andrew Lyon
- Re: [Xen-devel] Re: pv_ops dom0 USB fixed, Jeremy Fitzhardinge
- Re: [Xen-devel] Re: pv_ops dom0 USB fixed, Ian Campbell
- Re: [Xen-devel] Re: pv_ops dom0 USB fixed, Andrew Lyon
- Re: [Xen-devel] Re: pv_ops dom0 USB fixed, Marc - A. Dahlhaus [ Administration | Westermann GmbH ]
|
|
|
|
|