On Wed, 2006-01-11 at 20:49 -0500, Mike D. Day wrote:
> Greg KH wrote:
> >>/sys/xen/version may not be the best example for this discussion. What
> >>is important is that this attribute is obtained from Xen using a
> >>hypercall. Sysfs works great to prove the xen version and other
> >>similar xen attributes to userspace.
> >
> >
> > Like what? Specifics please.
>
> What privileges are granted to the kernel by xen - can the kernel
> control real devices or just virtual ones.
Why wouldn't this simply be transparent from what devices Linux detects?
If Linux doesn't detect any raw PCI devices, then it obviously doesn't
have access to any.
Why don't any other hypervisors need this?
> How many other domains
> (virtual machines) are being hosted by xen? How much memory is available
> for ballooning (increasing the memory used by kernels through the
> remapping of pages inside the hypervisor).
There are definitely things that are exceedingly helpful. However,
there are at least two other hypervisor-ish things that I can think of
which do the exact same kinds of things. Perhaps it would be helpful to
collaborate with them and produce a common interface. (uml, s390, maybe
some of the powerpc hypervisors)
> Can the domain be migrated to another physical host?
> What scheduler is Xen using (xen has plug-in
> schedulers)? All the actual information resides within the xen
> hypervisor, not the linux kernel.
Other than debugging and curiosity, why are these things needed?
-- Dave
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
