[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] Re: [Xen-devel] PVOPS dom0 requires nomodeset to boot but video requires modesetting driver


We are focused on developing a secure version of the hypervisor, by removing 
and refactoring code instead of adding security features. We don't have much 
kernel expertise, so we just fiddle 'till we get a fairly current kernel that 
works for our development environments. However, we are set up to capture full 
debug info all the time, so if we get an interesting kernel manifestation, can 
we report it. In this case, I have schedule pressure, so I am going to 
re-organize the particular DQ35JO to be just a plain Fedora box. However, I 
will be trying all over again with a different box, to set up a new development 
environment with the latest pvops dom0. I will make sure we have drm.debug=255 
on all of our development systems, but I don't know what the i915 option is.

We are also doing some fuzz testing of the hypervisor, so if we get anything 
interesting related to pvops, we'll post.

I will follow up to let you know how near to the present we are able to get, 
with pvops dom0 versions, on my next attempt.



On May 31, 2011, at 9:52 AM, Konrad Rzeszutek Wilk wrote:

> Whooooa. What are the boot issues with the newer kernels

@Konrad, they just would not build. Usually at make modules, but not always, 
sometimes they died in modprobe.

> BTW, you hadn't provided me with the 'drm.debug=255' and 'i915..' debug 
> options.

What is the formal meaning of the one-line program
#include "/dev/tty"

J.P. McDermott                  building 12
Code 5542                       mcdermott@xxxxxxxxxxxxxxxx
Naval Research Laboratory       voice: +1 202.404.8301
Washington, DC 20375, US        fax:   +1 202.404.7942

Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.