Hi, Was just looking over the Xen roadmap and have a few questions. 1) Bi-directional console. Is this completed? If so, where can I find documentation on it? 2) The following is stated: "more flexible memory usage controls" What exactly does this mean? Does this mean something such as "Guarantee X amount of RAM, but let burst up to Y" ? If not, what does it mean? Is there any work done in this yet? 3) Is there any documentation on the new VBD code? Is there yet a way to make dynamically growing (sparse) disks or to be able to access a domain''s filesystem from domain 0? Sorry if this is answered already on the list, I didn''t find any of it obvious. Thanks, Matt Ayres ------------------------------------------------------- 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
> Hi, > > Was just looking over the Xen roadmap and have a few questions. > > 1) Bi-directional console. Is this completed? If so, where can I find > documentation on it?This is now in the unstable tree, in a somewhat incomplete state. When you use xc_dom_create.py it will print a TCP port that you can telnet to to get console I/O. e.g., from DOM0, the output from the first domain that you create will be available via: telnet localhost 9600 I''m working on rewriting the DOM0 daemon that controls th console -- after this you will be able to choose which port a given domain''s console output appears via. -- Keir> 2) The following is stated: > > "more flexible memory usage controls" > > What exactly does this mean? Does this mean something such as > "Guarantee X amount of RAM, but let burst up to Y" ? If not, what does > it mean? Is there any work done in this yet? > > 3) Is there any documentation on the new VBD code? Is there yet a way > to make dynamically growing (sparse) disks or to be able to access a > domain''s filesystem from domain 0? > > Sorry if this is answered already on the list, I didn''t find any of it > obvious. > > Thanks, > Matt Ayres > > > > ------------------------------------------------------- > 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
> Hi, > > Was just looking over the Xen roadmap and have a few questions. > > 1) Bi-directional console. Is this completed? If so, where can I find > documentation on it?There''s a first-cut version already in xeno-unstable. Run ''xenod'' and when you start a domain xc_dom_create will print out the TCP port number that you can access to get the console. (e.g. "telnet localhost 9600")> 2) The following is stated: > > "more flexible memory usage controls" > > What exactly does this mean? Does this mean something such as > "Guarantee X amount of RAM, but let burst up to Y" ? If not, what does > it mean? Is there any work done in this yet?Something like that. It will enable you to set the ''maximum'' and ''target'' memory for a domain. The ability to do this is sort-of already present from within a domain via the balloon driver, but the interface is totally unintuitive. We need to add the ability to tell a domain what its target should be from domain0 (by sending a message on the new comms rings that are used for console). We haven''t had time to do this, though its pretty straightforward if someone wants to volunteer.> 3) Is there any documentation on the new VBD code?Mark wrote a pretty good readme on VBDs and put it in the tree.> Is there yet a way to make dynamically growing (sparse) disks > or to be able to access a domain''s filesystem from domain 0?Yes, you can add the VBD to domain0 to populate it, back it up etc. Obviously, be careful if the domain is using it read-write at the same time. In this case, it might be better to export it via NFS. Ian ------------------------------------------------------- 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
> 3) Is there any documentation on the new VBD code? Is there yet a way > to make dynamically growing (sparse) disks or to be able to access a > domain''s filesystem from domain 0?The current generation of VBD stuff is documented in docs/VBD-HOWTO.txt - there''s some background about how VBDs and Virtual Disks are (currently) implemented, some info about the tools and a little walkthrough of an example task. The VBD / VD functionality is a bit like LVM and works in a similar way. The current state of play is this: * virtual disks are allocated from a pool of space set aside in one or more whole partitions or disks. They can''t, for instance, just be files on some other domain''s filesystem. * virtual disks can be created from that pool of free space as needed. Space reserved for a particular virtual disk is then allocated and hence unusable for other virtual disks, even if untouched by the domain it belongs to. This guarantees that space will be available if / when needed by the domain. As a result you can''t speculatively "overbook" your virtual disk free pool. * You can enlarge existing virtual disks, export them to files, import from files and various other useful things (details in the readme / howto). * You can add and remove VBD access to / from domains dynamically, rather like hot plugging (e.g. to access a filesystem from dom0). Like Ian said, make sure you don''t have filesystems writeable by more than one domain at once - most filesystems can''t cope (and will get very badly corrupted). (actually, Linux also gets confused if someone else is writing a filesystem it has mounted read only but this shouldn''t cause corruption). There''s some sanity checking for shared disk mappings in the tools. Some of the VBD / VD stuff might change in the new I/O world. HTH. Mark ------------------------------------------------------- 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