Created attachment 1363137 [details]
anaconda.log

Could you get a backtrace with symbols, or a core file?
The Xorg log has [  9610.271] (EE) qxl(0): error doing QXL_ALLOC
which corresponds to
    ret = drmIoctl(qxl->drm_fd, DRM_IOCTL_QXL_ALLOC, &alloc);
    if (ret) {
        xf86DrvMsg(qxl->pScrn->scrnIndex, X_ERROR,
                   "error doing QXL_ALLOC\n");
        free(bo);
        return NULL; // an invalid handle
    }

Is there anything in the kernel log when this happens?

Created attachment 1363452 [details]
ifcfg.log

Created attachment 1363453 [details]
packaging.log

Created attachment 1363454 [details]
program.log

Created attachment 1363455 [details]
rpm-script.log

Created attachment 1363456 [details]
rpm-script.log

Created attachment 1363457 [details]
storage.log

I'm sorry, this is happened when install the guest, and the installation is not finished, I didn't get any core file or get the backtrace with symbols, let me upload all the logs I collected as above.

Do you have the full libvirt XML for the VM which crashes? I've tried to reproduce this in virt-manager (no access to a RHEV instance), but the installation is working fine so far. Does the crash happens when the graphical installer starts? Or does it happen a bit later after you interacted with it?

I also want to reproduce it by virt-manager before filing this bug, but failed. It happened a bit later after I interacted with it. In the rpm-script.log, it shows:
...
iwl7265-firmware-22.0.7.0-56.el7.noarch (326/329)

I selected minimal installation.

Can you provide the full libvirt XML from RHV? Maybe this would be helpful to recreate a VM which triggers that crash.

Setting needinfo, moving to 7.6

Rerun with latest rhv4.2, install rhel7.4 release guests with QXL successfully, Xorg Segmentation fault is no longer existed.

Verified on packages:
vdsm-4.20.17-1.el7ev.x86_64
libvirt-3.2.0-14.el7_4.9.x86_64
qemu-kvm-rhev-2.9.0-16.el7_4.14.x86_64
ovirt-engine-4.2.1.1-0.1.el7.noarch
ovirt-engine-dashboard-1.2.1-1.el7ev.noarch

Test steps:
1. Install a minimal guest in latest RHV4.2 web console with Video Type: QXL successfully, the related xml is attached file: 7_4.xml

2. Install a "Server with GUI" guest in latest RHV4.2 web console with Video Type: QXL successfully, the related xml is attached file: 7_4-1.xml

As there is no Xorg Segmentation fault, and the guest can installed successfully in latest rhv4.2, I think this bug can changed to "Current release".

Created attachment 1391793 [details]
7_4.xml

Created attachment 1391794 [details]
7_4-1.xml

(In reply to chhu from comment #0)
>       <model type='qxl' ram='65536' vram='8192' vgamem='16384' heads='1'
> primary='yes'/>

vram should be set to 32768 for RHEL 7 guest with 1 QXL, based on https://www.spice-space.org/multiple-monitors.html

If that works change that and it works, likely to be a bug in RHEV initial setup. (8192 is for UMS driver, RHEL6)

Hi, Victor

I used the default setting in latest RHV4.2 web console with Video Type: QXL, and didn't do other setting, just used `virsh dumpxml` to show the guest xml to file: 7_4.xml(minimal), 7_4-1.xml(Server with GUI).

Sorry, I was not clear in comment #18

For RHEL 7 (guest) VM with 1 QXL, the expected value for vram is 32768 instead of 8192. That could be causing the error on QXL_ALLOC mentioned by Christhophe in comment #3

Questions:
- Have you set the 'Operation systems' to RHEL 7.x while creating the VM in RHV4.2 ? If yes, RHV might have a bug.
- If you set the vram to 32768, does the problem goes away? (you should not see any error like `error doing QXL_ALLOC`)

(In reply to Victor Toso from comment #20)
> Sorry, I was not clear in comment #18
> 
> For RHEL 7 (guest) VM with 1 QXL, the expected value for vram is 32768
> instead of 8192. That could be causing the error on QXL_ALLOC mentioned by
> Christhophe in comment #3
> 
> Questions:
> - Have you set the 'Operation systems' to RHEL 7.x while creating the VM in
> RHV4.2 ? If yes, RHV might have a bug.

No, I set the 'Operation systems': Linux. And if I set it to: 'RHEL 7.x', 
the vram is 32768, and can install the guest successfully.
    <video>
      <model type='qxl' ram='65536' vram='32768' vgamem='16384' heads='1' primary='yes'/>
      <alias name='video0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
    </video>

But the machine type is: pc-i440fx-rhel7.3.0, it should be: pc-i440fx-rhel7.4.0
  <os>
    <type arch='x86_64' machine='pc-i440fx-rhel7.3.0'>hvm</type>
    <smbios mode='sysinfo'/>
  </os>

The full xml are in file: redhat7-4.xml

> - If you set the vram to 32768, does the problem goes away? (you should not
> see any error like `error doing QXL_ALLOC`)

As the test result in comment15, in latest rhv4.2, with the xml in 7_4.xml(vram='8192'), set the 'Operation systems': Linux, I can install the guest successfully.

Created attachment 1393011 [details]
redhat7-4.xml

Hi,

> > For RHEL 7 (guest) VM with 1 QXL, the expected value for vram is 32768
> > instead of 8192. That could be causing the error on QXL_ALLOC mentioned by
> > Christhophe in comment #3
> > 
> > Questions:
> > - Have you set the 'Operation systems' to RHEL 7.x while creating the VM in
> > RHV4.2 ? If yes, RHV might have a bug.
> 
> No, I set the 'Operation systems': Linux. And if I set it to: 'RHEL 7.x', 
> the vram is 32768, and can install the guest successfully.

As RHEL 7.x works but not as Linux, okay. Would be nice to know if this is a regression or not. I'll be moving the bug to RHEVM.

>     <video>
>       <model type='qxl' ram='65536' vram='32768' vgamem='16384' heads='1'
> primary='yes'/>
>       <alias name='video0'/>
>       <address type='pci' domain='0x0000' bus='0x00' slot='0x02'
> function='0x0'/>
>     </video>
> 
> But the machine type is: pc-i440fx-rhel7.3.0, it should be:
> pc-i440fx-rhel7.4.0
>   <os>
>     <type arch='x86_64' machine='pc-i440fx-rhel7.3.0'>hvm</type>
>     <smbios mode='sysinfo'/>
>   </os>

Maybe same bug (wrong config being used) or a different one (wrong value is set in the config)

> The full xml are in file: redhat7-4.xml
> 
> > - If you set the vram to 32768, does the problem goes away? (you should not
> > see any error like `error doing QXL_ALLOC`)
> 
> As the test result in comment15, in latest rhv4.2, with the xml in
> 7_4.xml(vram='8192'), set the 'Operation systems': Linux, I can install the
> guest successfully.

Doesn't mean that you can use it without issues.

*** Bug 1542214 has been marked as a duplicate of this bug. ***

I do not see anything wrong
RHEL 7 64bit is working correctly setting vram to 32MB, other guests are using 8MB
See https://bugzilla.redhat.com/show_bug.cgi?id=1275539#c12 for the result of discussions with SPICE team back then.
Are the recommendations different now? Christophe?

The machine type is the one we have been using in oVirt/RHV 4.2 at the time this bug was filed. Note since then we're using i440fx-rhel7.5.0 in RHV 4.2

Victor, any other issue?

(In reply to Michal Skrivanek from comment #32)
> I do not see anything wrong
> RHEL 7 64bit is working correctly setting vram to 32MB, other guests are
> using 8MB

The problem is when user uses 'Linux' for RHEL 7 installation. 8MB is not enough as it needs 32MB. We can't avoid guest failures due lack of memory...

> See https://bugzilla.redhat.com/show_bug.cgi?id=1275539#c12 for the result
> of discussions with SPICE team back then.
> Are the recommendations different now? Christophe?
> 
> The machine type is the one we have been using in oVirt/RHV 4.2 at the time
> this bug was filed. Note since then we're using i440fx-rhel7.5.0 in RHV 4.2
> 
> Victor, any other issue?

Not really. The problem here is user installing RHEL 7 with 'Linux' profile instead of 'RHEL 7.x' profile. Should we close as WONTFIX in this case?

adding back needinfo from comment #12 and adding David as well to advise about any potential update of memory settings for QXL

(In reply to Victor Toso from comment #33)
> Not really. The problem here is user installing RHEL 7 with 'Linux' profile
> instead of 'RHEL 7.x' profile. Should we close as WONTFIX in this case?

Seems so. Unless there are updates from SPICE team

(In reply to Michal Skrivanek from comment #34)
> adding back needinfo from comment #12 and adding David as well to advise
> about any potential update of memory settings for QXL
> 
> (In reply to Victor Toso from comment #33)
> > Not really. The problem here is user installing RHEL 7 with 'Linux' profile
> > instead of 'RHEL 7.x' profile. Should we close as WONTFIX in this case?
> 
> Seems so. Unless there are updates from SPICE team

Martin?

(In reply to Yaniv Kaul from comment #35)
> (In reply to Michal Skrivanek from comment #34)
> > adding back needinfo from comment #12 and adding David as well to advise
> > about any potential update of memory settings for QXL
> > 
> > (In reply to Victor Toso from comment #33)
> > > Not really. The problem here is user installing RHEL 7 with 'Linux' profile
> > > instead of 'RHEL 7.x' profile. Should we close as WONTFIX in this case?
> > 
> > Seems so. Unless there are updates from SPICE team
> 
> Martin?

Why does the Linux profile has 8MB instead of 32MB in the first place?
From my pov not only RHEL will fail but also every other Linux using XOrg with QXL driver.

So would it not be sensible increasing the Memory to 32MB for every Linux like profile?

I believe there is a Windows profile that covers all Windows right now, and I believe the RHEL and Linux profiles are all a bit different.

So as long as there is a reason for the 8MB for the Linux profile, I would say this is a somewhat expected behaviour, as the "wrong" profile was chosen.

In case there is no good reason for the 8MB we should adjust this to 32MB as well.

David?

(In reply to Martin Tessun from comment #36)
> (In reply to Yaniv Kaul from comment #35)
> > (In reply to Michal Skrivanek from comment #34)
> > > adding back needinfo from comment #12 and adding David as well to advise
> > > about any potential update of memory settings for QXL
> > > 
> > > (In reply to Victor Toso from comment #33)
> > > > Not really. The problem here is user installing RHEL 7 with 'Linux' profile
> > > > instead of 'RHEL 7.x' profile. Should we close as WONTFIX in this case?
> > > 
> > > Seems so. Unless there are updates from SPICE team
> > 
> > Martin?
> 
> Why does the Linux profile has 8MB instead of 32MB in the first place?
> From my pov not only RHEL will fail but also every other Linux using XOrg
> with QXL driver.
> 
> So would it not be sensible increasing the Memory to 32MB for every Linux
> like profile?
> 
> I believe there is a Windows profile that covers all Windows right now, and
> I believe the RHEL and Linux profiles are all a bit different.
> 
> So as long as there is a reason for the 8MB for the Linux profile, I would
> say this is a somewhat expected behaviour, as the "wrong" profile was chosen.
> 
> In case there is no good reason for the 8MB we should adjust this to 32MB as
> well.
> 
> David?

The quick answer is: there are no reasons for limiting vram to 8mb. 

Spice supports only 3 types of VMs: Windows ( xp, windows 7 and windows 10), rhel 7.x and rhel 6.x. Only rhel 7.x driver is using vram. 

I hope it helps

dnb

Michal, if there are no obvious drawbacks, let's change it for 4.3 and consider backport to 4.2.z

sure, but since we're changing it for all Linux guest OS types QE must test for regressions for older guests like RHEL 5 and 6 and at least one or two other common OSes

WARN: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason:

[Found non-acked flags: '{'rhevm-4.2.z': '?'}', ]

For more info please contact: rhv-devops: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason:

[Found non-acked flags: '{'rhevm-4.2.z': '?'}', ]

For more info please contact: rhv-devops

please clone properly

Verified on:
ovirt-engine-4.3.0-0.0.master.20181101091940.git61310aa.el7.noarch
vdsm-4.30.1-52.git5426c0c.el7.x86_64
qemu-kvm-rhev-2.12.0-18.el7_6.2.x86_64

Steps:
1. Create a new VM
2. Set Operating System: Linux, Console Video Type: QXL, SPICE
3. Run the VM and try to install OS.

Tested on OS:
RHEL6.9, RHEL7.4, RHEL7.5, RHEL7.6, CentOS7, Fedora28

Results:
On every test the engine xml shows:
<video>
      <model type='qxl' ram='65536' vram='32768' vgamem='16384' heads='1' primary='yes'/>
      <alias name='ua-b98dfc9d-5c01-40c8-88cf-68654f26f41a'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
</video>

in vdsm vm xml:
<video>
    <model heads="1" ram="65536" type="qxl" vgamem="16384" vram="32768"/>
    <alias name="ua-b98dfc9d-5c01-40c8-88cf-68654f26f41a"/>
    <address bus="0x00" domain="0x0000" function="0x0" slot="0x02" type="pci"/>
</video>

The vram is set correctly. 
The guest successfully installed the OS.

*** Bug 1671186 has been marked as a duplicate of this bug. ***

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2019:1085

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days