John McDermott (U.S. Navy Employee)
2011-May-27 12:50 UTC
[Xen-devel] PVOPS dom0 requires nomodeset to boot but video requires modesetting driver
Xen Users, In trying to bring up a new machine, I have debugged to the point that it appears that nomodeset is required to boot a pvops dom0 on Xen 4.0.1, on this machine (otherwise a udevd failure), but the video will not work without KMS, i.e. dom0 gets a "No modesetting driver detected" error. Everything in dom0 works fine remotely, including X forwarding, but no GUI on the console. I have tried all combinations of iommu, nomodeset, and nopat. I have also tried intel_iommu=igfx_off, without changing the results. Any suggestions? Sincerely, John ---- What is the formal meaning of the one-line program #include "/dev/tty" J.P. McDermott building 12 Code 5542 mcdermott@itd.nrl.navy.mil Naval Research Laboratory voice: +1 202.404.8301 Washington, DC 20375, US fax: +1 202.404.7942 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Konrad Rzeszutek Wilk
2011-May-27 13:55 UTC
Re: [Xen-devel] PVOPS dom0 requires nomodeset to boot but video requires modesetting driver
On Fri, May 27, 2011 at 08:50:45AM -0400, John McDermott (U.S. Navy Employee) wrote:> Xen Users, > > In trying to bring up a new machine, I have debugged to the point that it appears that nomodeset is required to boot a pvops dom0 on Xen 4.0.1, on this machine (otherwise a udevd failure), but the video will not work without KMS, i.e. dom0 gets a "No modesetting driver detected" error. Everything in dom0 works fine remotely, including X forwarding, but no GUI on the console. I have tried all combinations of iommu, nomodeset, and nopat. I have also tried intel_iommu=igfx_off, without changing the results. >You need to give more details. lspci -vv, dmesg, serial console, which version of Dom0, etc.> Any suggestions?Couple, but not sure if they apply without the data above. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
John McDermott (U.S. Navy Employee)
2011-May-27 15:31 UTC
Re: [Xen-devel] PVOPS dom0 requires nomodeset to boot but video requires modesetting driver
Konrad, Thanks. Domain 0 is one of Jeremy''s pvops kernels, the latest 2.6.32.25, as far as I can tell, downloaded as a snapshot. The tarball called itself xen-51f9f52, but I don''t know if that is a unique id. I am trying to bring this up on Fedora 14. X forwarding works just fine. I have not set up the networking properly on this box, so that will not look right, but does not matter. Attached are the outputs from the serial console, dmesg, lspci, and X logs for bare metal and Xen boots of the dom0 kernel: Sincerely, John On May 27, 2011, at 9:55 AM, Konrad Rzeszutek Wilk wrote:> On Fri, May 27, 2011 at 08:50:45AM -0400, John McDermott (U.S. Navy Employee) wrote: >> Xen Users, >> >> In trying to bring up a new machine, I have debugged to the point that it appears that nomodeset is required to boot a pvops dom0 on Xen 4.0.1, on this machine (otherwise a udevd failure), but the video will not work without KMS, i.e. dom0 gets a "No modesetting driver detected" error. Everything in dom0 works fine remotely, including X forwarding, but no GUI on the console. I have tried all combinations of iommu, nomodeset, and nopat. I have also tried intel_iommu=igfx_off, without changing the results. >> > > You need to give more details. lspci -vv, dmesg, serial console, which version of Dom0, etc. > >> Any suggestions? > > Couple, but not sure if they apply without the data above.---- What is the formal meaning of the one-line program #include "/dev/tty" J.P. McDermott building 12 Code 5542 mcdermott@itd.nrl.navy.mil Naval Research Laboratory voice: +1 202.404.8301 Washington, DC 20375, US fax: +1 202.404.7942 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Konrad Rzeszutek Wilk
2011-May-27 15:52 UTC
Re: [Xen-devel] PVOPS dom0 requires nomodeset to boot but video requires modesetting driver
On Fri, May 27, 2011 at 11:31:01AM -0400, John McDermott (U.S. Navy Employee) wrote:> Konrad, > > Thanks. Domain 0 is one of Jeremy''s pvops kernels, the latest 2.6.32.25, as far as I can tell, downloaded as a snapshot. The tarball called itself xen-51f9f52, but I don''t know if that is a unique id. I am trying to bring this up on Fedora 14. X forwarding works just fine. I have not set up the networking properly on this box, so that will not look right, but does not matter. > > Attached are the outputs from the serial console, dmesg, lspci, and X logs for bare metal and Xen boots of the dom0 kernel: >Nothing jumps at me. The Xorg doesn''t boot b/c there is no /dev/fb0, but it is present when you boot baremetal. Can you fiddle with ''drm.debug=255'' and ''i915'' parameters to see if it can output some more details? Also, 2.6.32.25 is a bit old. You should try to update it. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
John McDermott (U.S. Navy Employee)
2011-May-27 16:17 UTC
Re: [Xen-devel] PVOPS dom0 requires nomodeset to boot but video requires modesetting driver
Konrad, Agreed. However, this is the newest kernel I have been able to build and boot, on the target box. I started with the latest and worked my way back down to 2.6.32.25, to get one that would build and boot. Most of our platforms are up to about 2.6.32.32 or thereabouts. The target is an Intel DG35JO board, which is a bit old itself? It does not expose all of the latest VT-d features, so perhaps it would be better to set the whole platform aside and put efforts into getting newer hardware that can do things like SR-IOV and EPT? Sincerely, John --- On May 27, 2011, at 11:52 AM, Konrad Rzeszutek Wilk wrote:> Also, 2.6.32.25 is a bit old. You should try to update it.---- What is the formal meaning of the one-line program #include "/dev/tty" J.P. McDermott building 12 Code 5542 mcdermott@itd.nrl.navy.mil Naval Research Laboratory voice: +1 202.404.8301 Washington, DC 20375, US fax: +1 202.404.7942 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Konrad Rzeszutek Wilk
2011-May-31 13:52 UTC
Re: [Xen-devel] PVOPS dom0 requires nomodeset to boot but video requires modesetting driver
On Fri, May 27, 2011 at 12:17:57PM -0400, John McDermott (U.S. Navy Employee) wrote:> Konrad, > > Agreed. However, this is the newest kernel I have been able to build and boot, on the target box. I started with the latest and worked my way back down to 2.6.32.25, to get one that would build and boot. Most of our platforms are up to about 2.6.32.32 or thereabouts.Whooooa. What are the boot issues with the newer kernels? BTW, you hadn''t provided me with the ''drm.debug=255'' and ''i915..'' debug options.> > The target is an Intel DG35JO board, which is a bit old itself? It does not expose all of the latest VT-d features, so perhaps it would be better to set the whole platform aside and put efforts into getting newer hardware that can do things like SR-IOV and EPT?It should work. I''ve some more ancient boxes than that and they boot fine. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
John McDermott (U.S. Navy Employee)
2011-May-31 17:37 UTC
[Xen-users] Re: [Xen-devel] PVOPS dom0 requires nomodeset to boot but video requires modesetting driver
Konrad, 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. Sincerely, John 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@itd.nrl.navy.mil Naval Research Laboratory voice: +1 202.404.8301 Washington, DC 20375, US fax: +1 202.404.7942 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users