ropers wrote:
quoted text
> On 23/10/2007, Jeff Quast <af.dingo@gmail.com> wrote:
>> I would like to vouch for openbsd working great as a guest, but my
>> guest has crashed a dozen times. However I think this is due to the
>> debian linux dom0 having broken sata code for the controller in use.
>> dom0's dmesg is filled with debug statements from sata related places
>> in the kernel that should never be printed. We're in a messy
>> de-centralized linux development world trying to get a stable dom0
>> patched together. It sucks.
> 
> This is what I meant to hint at earlier: Running an OpenBSD DomU in
> connection with, say, a Linux Xen Dom0 possibly makes that OpenBSD
> installation subject to bugs in the hypervisor/Dom0, and that may be
> unavoidable. The question is, is that a worthwhile trade-off? Is this
> a reason not to support Xen? Or should the user be given that option
> regardless of the inherent limitations and consequences?
> 
> --ropers
> 
> 

IMHO I think that OpenBSD needs to capable to install and run as a 
paravirtualized domU guest, with some limitations if you like.

Last year I have do the same question. Then it was said that only needed NetBSD 
do the xen port, and from there just enough to carry to OpenBSD. The reality is 
that NetBSD long ago that can be installed and run as domU and OpenBSD not.

And my question is why?? i think that only one developer can't maintain this 
type of code ... needs more help. I am not developer but i can do tests if you 
needed ....


-- 
CL Martinez
carlopmart {at} gmail {d0t} com