Has Anyone Been Able to Run PVOPS DomU Against any nVidia Chipset?

Has Anyone Been Able to Run PVOPS DomU Against any nVidia Chipset?

[John McDermott (U.S. Navy Employee)]

Xen Developers,

This has already been posted to Xen-Users, but  I got no response.

Short version: has anyone been able to run a 2.6.32.18 PVOPS domU, on Xen 4.0.1, on Fedora 13, against any nVidia chipset? I'd like to know which chipset please.

Long version:

I have encountered what appears to be an interesting video or DRM problem with this combination.   Dom0 runs X11 without problems but this combination will not run X11 as dom U. While attempting to install Fedora 13 dom U as an HVM, using a 2.6.32.18 PVOPS dom0, running on Xen 4.0.1 on Fedora 13,  using virt-install --nographics, it reaches the point following the XML display of the boot guest configuration, reports an

(EE) FBDEV(0): FBIOBLANK: Invalid argument

error and then hangs with garbage displayed on my remote xterm console. (Virt-install --vnc dies also.) My serial console shows a bunch of hypervisor

(XEN) HVM2: int13_harddisk: function 41, unmapped device for ELDL=81
...

and then some

...
(XEN) vlapic.c:702:d2 Local APIC Write to read-only register 0x30

error messages.

I can get a pvops domain U to install --nographics, but the resulting guest cannot start X and fails with the same "(EE) FBDEV(0): FBIOBLANK: Invalid argument". No hypervisor error messages are generated by this failure.

I have tried to get this kernel-hypervisor combination working on 2 different boxes:

1)  a Dell Precision 690 with an Intel E6320 processor (I don't think this is the issue) and an nVidia Quadro NVS 285, which X11 reports as nVidia NV 44. Plain old Fedora 13 uses the nouveau driver with no problems. Udev tells me it is version 153. The problem remains even with the kernel booted nopat.

2) a "roll-your-own" with EVGA X58 SLI motherboard / Intel i7 combination, with an nVidia GEForce 9800 GTX+, which X11 reports as nVidia G92. Again, plain old Fedora 13 uses the nouveau driver for this, without problems. Trying a pvops domU gives me the same behavior: Fedora domU installs and runs fine, but cannot start X11.

I have tried this against 2 kernels: Jeremy's e6b92c and Michael Young's 2.6.32.21-167.xendom0.fc13.x86_64. (The latter fails in video during kernel boot, when I use init=/sbin/upstart, but boots OK without it, but then fails to run X on domU's.) When building these kernels, both complain about missing the nouveau module at depmod time.

Before I go swapping cards or outright buying one, has anyone run this pvops combination against any nVidia-based graphics card? Does pvops require an ATI chipset? Has pvops been run against an onboard Matrox chipset, as on a server?

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

Re: Has Anyone Been Able to Run PVOPS DomU Against any nVidia Chipset?

[Jeremy Fitzhardinge]

 On 09/17/2010 09:53 AM, John McDermott (U.S. Navy Employee) wrote:
> Xen Developers,
>
> This has already been posted to Xen-Users, but  I got no response.
>
> Short version: has anyone been able to run a 2.6.32.18 PVOPS domU, on Xen 4.0.1, on Fedora 13, against any nVidia chipset? I'd like to know which chipset please.

By "nVidia chipset" do you mean a system chipset, or specifically a
graphics card?

By "run ... pvops domU ... against any nVidia chipset" do you mean
passing the hardware through to the domU?

Are you running domU as HVM or PV?  If it is HVM, are you using stubdoms?

> Long version:
>
> I have encountered what appears to be an interesting video or DRM problem with this combination.   Dom0 runs X11 without problems but this combination will not run X11 as dom U. While attempting to install Fedora 13 dom U as an HVM, using a 2.6.32.18 PVOPS dom0, running on Xen 4.0.1 on Fedora 13,  using virt-install --nographics, it reaches the point following the XML display of the boot guest configuration, reports an
>
> (EE) FBDEV(0): FBIOBLANK: Invalid argument
>
> error and then hangs with garbage displayed on my remote xterm console. (Virt-install --vnc dies also.) My serial console shows a bunch of hypervisor
>
> (XEN) HVM2: int13_harddisk: function 41, unmapped device for ELDL=81
> ...
>
> and then some
>
> ...
> (XEN) vlapic.c:702:d2 Local APIC Write to read-only register 0x30
>
> error messages.

I think those are more warnings than errors.  Are there any other error
messages?

> I can get a pvops domain U to install --nographics, but the resulting guest cannot start X and fails with the same "(EE) FBDEV(0): FBIOBLANK: Invalid argument". No hypervisor error messages are generated by this failure.

If you're using an emulated FB then it should Just Work, and be
independent of whatever the host graphics chip is - and emulated is
probably what you should be using for install regardless of what you
plan to do once the guest is installed.

If you are passing through a graphics controller, how are you making
sure that dom0 isn't also using it?

> I have tried to get this kernel-hypervisor combination working on 2 different boxes:
>
> 1)  a Dell Precision 690 with an Intel E6320 processor (I don't think this is the issue) and an nVidia Quadro NVS 285, which X11 reports as nVidia NV 44. Plain old Fedora 13 uses the nouveau driver with no problems. Udev tells me it is version 153. The problem remains even with the kernel booted nopat.
>
> 2) a "roll-your-own" with EVGA X58 SLI motherboard / Intel i7 combination, with an nVidia GEForce 9800 GTX+, which X11 reports as nVidia G92. Again, plain old Fedora 13 uses the nouveau driver for this, without problems. Trying a pvops domU gives me the same behavior: Fedora domU installs and runs fine, but cannot start X11.
>
> I have tried this against 2 kernels: Jeremy's e6b92c and Michael Young's 2.6.32.21-167.xendom0.fc13.x86_64. (The latter fails in video during kernel boot, when I use init=/sbin/upstart, but boots OK without it, but then fails to run X on domU's.) When building these kernels, both complain about missing the nouveau module at depmod time.
>
> Before I go swapping cards or outright buying one, has anyone run this pvops combination against any nVidia-based graphics card? Does pvops require an ATI chipset?

Konrad has done a lot of work on making many different graphics cards
work, including nVidia, at least in dom0.

>  Has pvops been run against an onboard Matrox chipset, as on a server?

Yes, my home server machine has a Matrox controller which works OK.

    J

Re: Has Anyone Been Able to Run PVOPS DomU Against any nVidia Chipset?

[Boris Derzhavets]

[-- Attachment #1.1: Type: text/plain, Size: 3520 bytes --]

> Does pvops require an ATI chipset?

It just works fine with Radeon HD 4650.

Boris.

--- On Fri, 9/17/10, John McDermott (U.S. Navy Employee) <john.mcdermott@nrl.navy.mil> wrote:

From: John McDermott (U.S. Navy Employee) <john.mcdermott@nrl.navy.mil>
Subject: [Xen-devel] Has Anyone Been Able to Run PVOPS DomU Against any nVidia Chipset?
To: xen-devel@lists.xensource.com
Date: Friday, September 17, 2010, 12:53 PM

Xen Developers,

This has already been posted to Xen-Users, but  I got no response.

Short version: has anyone been able to run a 2.6.32.18 PVOPS domU, on Xen 4.0.1, on Fedora 13, against any nVidia chipset? I'd like to know which chipset please.

Long version:

I have encountered what appears to be an interesting video or DRM problem with this combination.   Dom0 runs X11 without problems but this combination will not run X11 as dom U. While attempting to install Fedora 13 dom U as an HVM, using a 2.6.32.18 PVOPS dom0, running on Xen 4.0.1 on Fedora 13,  using virt-install --nographics, it reaches the point following the XML display of the boot guest configuration, reports an

(EE) FBDEV(0): FBIOBLANK: Invalid argument

error and then hangs with garbage displayed on my remote xterm console. (Virt-install --vnc dies also.) My serial console shows a bunch of hypervisor

(XEN) HVM2: int13_harddisk: function 41, unmapped device for ELDL=81
...

and then some

...
(XEN) vlapic.c:702:d2 Local APIC Write to read-only register 0x30

error messages.

I can get a pvops domain U to install --nographics, but the resulting guest cannot start X and fails with the same "(EE) FBDEV(0): FBIOBLANK: Invalid argument". No hypervisor error messages are generated by this failure.

I have tried to get this kernel-hypervisor combination working on 2 different boxes:

1)  a Dell Precision 690 with an Intel E6320 processor (I don't think this is the issue) and an nVidia Quadro NVS 285, which X11 reports as nVidia NV 44. Plain old Fedora 13 uses the nouveau driver with no problems. Udev tells me it is version 153. The problem remains even with the kernel booted nopat.

2) a "roll-your-own" with EVGA X58 SLI motherboard / Intel i7 combination, with an nVidia GEForce 9800 GTX+, which X11 reports as nVidia G92. Again, plain old Fedora 13 uses the nouveau driver for this, without problems. Trying a pvops domU gives me the same behavior: Fedora domU installs and runs fine, but cannot start X11.

I have tried this against 2 kernels: Jeremy's e6b92c and Michael Young's 2.6.32.21-167.xendom0.fc13.x86_64. (The latter fails in video during kernel boot, when I use init=/sbin/upstart, but boots OK without it, but then fails to run X on domU's.) When building these kernels, both complain about missing the nouveau module at depmod time.

Before I go swapping cards or outright buying one, has anyone run this pvops combination against any nVidia-based graphics card? Does pvops require an ATI chipset? Has pvops been run against an onboard Matrox chipset, as on a server?

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



      

[-- Attachment #1.2: Type: text/html, Size: 4451 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: Has Anyone Been Able to Run PVOPS DomU Against any nVidia Chipset?

[Konrad Rzeszutek Wilk]

On Fri, Sep 17, 2010 at 12:53:56PM -0400, John McDermott (U.S. Navy Employee) wrote:
> Xen Developers,
> 
> This has already been posted to Xen-Users, but  I got no response.
> 
> Short version: has anyone been able to run a 2.6.32.18 PVOPS domU, on Xen 4.0.1, on Fedora 13, against any nVidia chipset? I'd like to know which chipset please.

I've been running it against the list in this Wiki:

http://wiki.xensource.com/xenwiki/XenPVOPSDRM

But I think you are referring to the nVidia motherboard chipset. In that case I've run
it on some MCP55 chipset, and there are also some other nForce chipsets - but I don't
remember the specific models.

> 
> Long version:
> 
> I have encountered what appears to be an interesting video or DRM problem with this combination.   Dom0 runs X11 without problems but this combination will not run X11 as dom U. While attempting to install Fedora 13 dom U as an HVM, using a 2.6.32.18 PVOPS dom0, running on Xen 4.0.1 on Fedora 13,  using virt-install --nographics, it reaches the point following the XML display of the boot guest configuration, reports an
> 
> (EE) FBDEV(0): FBIOBLANK: Invalid argument
> 
> error and then hangs with garbage displayed on my remote xterm console. (Virt-install --vnc dies also.) My serial console shows a bunch of hypervisor

Hm, remote xterm console does not require you to run Xorg on your DomU. So this looks
tobe two different issues you are hitting.

What happens when you do 'vncviewer :0' ? Can you see the GNOME startup of your DomU?

What kind of garbage do you see in you remote xterm console? CAn you take a screenshot and
send it?

Re: Has Anyone Been Able to Run PVOPS DomU Against any nVidia Chipset?

[John McDermott (U.S. Navy Employee)]

On Sep 20, 2010, at 5:08 PM, Konrad Rzeszutek Wilk wrote:

> On Fri, Sep 17, 2010 at 12:53:56PM -0400, John McDermott (U.S. Navy Employee) wrote:
>> Xen Developers,
>> 
>> This has already been posted to Xen-Users, but  I got no response.
>> 
>> Short version: has anyone been able to run a 2.6.32.18 PVOPS domU, on Xen 4.0.1, on Fedora 13, against any nVidia chipset? I'd like to know which chipset please.
> 
> I've been running it against the list in this Wiki:
> 
> http://wiki.xensource.com/xenwiki/XenPVOPSDRM
@Konrad, thanks, it helps to know that list is up2date. It is one reason I posted; this behavior is unexpected based on the length of that list and the fact that I get similar if not identical errors from a relatively old graphics card and also a fairly new one.


> 
> But I think you are referring to the nVidia motherboard chipset. In that case I've run
> it on some MCP55 chipset, and there are also some other nForce chipsets - but I don't
> remember the specific models.

@Konrad, both boxes are using nVidia graphics cards, not motherboard chipsets. My only interest in motherboard chipsets is that they are typically dumbed down and thus more likely to work?

> 
>> 
>> Long version:
>> 
>> I have encountered what appears to be an interesting video or DRM problem with this combination.   Dom0 runs X11 without problems but this combination will not run X11 as dom U. While attempting to install Fedora 13 dom U as an HVM, using a 2.6.32.18 PVOPS dom0, running on Xen 4.0.1 on Fedora 13,  using virt-install --nographics, it reaches the point following the XML display of the boot guest configuration, reports an
>> 
>> (EE) FBDEV(0): FBIOBLANK: Invalid argument
>> 
>> error and then hangs with garbage displayed on my remote xterm console. (Virt-install --vnc dies also.) My serial console shows a bunch of hypervisor
> 
> Hm, remote xterm console does not require you to run Xorg on your DomU. So this looks
> tobe two different issues you are hitting.

@Konrad, errors look the same running directly or remote; I checked that before posting.


> 
> What happens when you do 'vncviewer :0' ? Can you see the GNOME startup of your DomU?

@Konrad, I am running KDE :-) For the domU, I run the raw startx command, so I can see the X messages. Is that not a valid way to test X11?

> 
> What kind of garbage do you see in you remote xterm console? CAn you take a screenshot and
> send it?

@Konrad, well it is the same garbage, local or remote xterm (actually Konsole, but I don't think that matters), but I will try to get a screen shot and post 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