> I''m finally up and running again -- thanks once more for the help.
Here are a
> few notes:
>
> 1. The default config has "cpu" commented out and implies that
it defaults to
> -1. "xm create" won''t work unless this line is
uncommented and given an
> explicit value.
Thanks. cpu=-1 (unpinned) should be a default.
> 2. The directory /var/run/xend is not created during "make
world", "make
> install", or "make install-twisted". "xend start"
won''t fire up without it.
I think ''xend start'' should create this automatically.
> 3. After issuing "shutdown -h now" in a domain (or, more rudely,
"xm
> destroy") I''m unable to start up again without getting a name
conflict error.
> After running "xm list", however, I can restart without
difficulty.
Yep, I''ve spotted this too.
> From the papers and documentation I''ve read, xen doesn''t
have it''s own swap
> file or partition. This would make sense for QOS -- very hard to guarantee
> performance numbers for a domain when you don''t know if
it''s been swapped out
> to disk or not.
>
> However, I''m interested in QOS using the virtual timers only -- I
don''t
> particularly care about wall clock time (famous last words, I expect...
;-).
>
> Has any work been done on giving xen it''s own swap?
No, we haven''t.
You could swap whole VMs in and out using the save/resume stuff,
but the intended mechanism for adjusting domain memory footprints
is the balloon driver (let them page themselves).
Best,
Ian
-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xen-devel