Re: [ovirt-users] oVirt 4.2: hostdev passthrough not working any more

2018-02-22 Thread Michal Skrivanek


> On 22 Feb 2018, at 16:45, Alexandr Krivulya  wrote:
> 
> 22.02.2018 11:37, Alexandr Krivulya пишет:
>> 
>> 22.02.2018 11:30, Martin Polednik пишет:
>>> On 22/02/18 10:40 +0200, Alexandr Krivulya wrote: 
 Hello, the same problem after upgrade to 4.2.1 :( 
 
 
 18.01.2018 11:53, Daniel Helgenberger пишет: 
> Hello, 
> 
> yesterday I upgraded to 4.2.0 from 4.1.8. 
> 
> Now I notice I cannot assign host dev pass though any more; in the GUI 
> the 'Pinnded to host' list is empty; I cannot select any host for pass 
> through host pinning. 
>>> 
>>> Does the host that previously worked report device passthrough 
>>> capability? In the UI it's the "Device Passthrough: Enabled" field. 
>>> (and similarly named field in vdsm-client getCapabilities call)
>> Now "Device Passthrough: Disabled", but usb passthrough works well on 4.1
> 
> After enabling intel_iommu usb passthrough works again. But why this option 
> needed for usb now?

it should not be
sounds like a regression
can you please open a bug on that and add logs?

Thanks,
michal

> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] oVirt 4.2: hostdev passthrough not working any more

2018-02-22 Thread Alexandr Krivulya

22.02.2018 11:37, Alexandr Krivulya пишет:

22.02.2018 11:30, Martin Polednik пишет:

On 22/02/18 10:40 +0200, Alexandr Krivulya wrote:

Hello, the same problem after upgrade to 4.2.1 :(


18.01.2018 11:53, Daniel Helgenberger пишет:

Hello,

yesterday I upgraded to 4.2.0 from 4.1.8.

Now I notice I cannot assign host dev pass though any more; in the GUI
the 'Pinnded to host' list is empty; I cannot select any host for pass
through host pinning.


Does the host that previously worked report device passthrough
capability? In the UI it's the "Device Passthrough: Enabled" field.
(and similarly named field in vdsm-client getCapabilities call) 

Now "Device Passthrough: Disabled", but usb passthrough works well on 4.1


After enabling intel_iommu usb passthrough works again. But why this 
option needed for usb now?
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] oVirt 4.2: hostdev passthrough not working any more

2018-02-22 Thread Alexandr Krivulya



22.02.2018 11:30, Martin Polednik пишет:

On 22/02/18 10:40 +0200, Alexandr Krivulya wrote:

Hello, the same problem after upgrade to 4.2.1 :(


18.01.2018 11:53, Daniel Helgenberger пишет:

Hello,

yesterday I upgraded to 4.2.0 from 4.1.8.

Now I notice I cannot assign host dev pass though any more; in the GUI
the 'Pinnded to host' list is empty; I cannot select any host for pass
through host pinning.


Does the host that previously worked report device passthrough
capability? In the UI it's the "Device Passthrough: Enabled" field.
(and similarly named field in vdsm-client getCapabilities call) 

Now "Device Passthrough: Disabled", but usb passthrough works well on 4.1
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] oVirt 4.2: hostdev passthrough not working any more

2018-02-22 Thread Martin Polednik

On 22/02/18 10:40 +0200, Alexandr Krivulya wrote:

Hello, the same problem after upgrade to 4.2.1 :(


18.01.2018 11:53, Daniel Helgenberger пишет:

Hello,

yesterday I upgraded to 4.2.0 from 4.1.8.

Now I notice I cannot assign host dev pass though any more; in the GUI
the 'Pinnded to host' list is empty; I cannot select any host for pass
through host pinning.


Does the host that previously worked report device passthrough
capability? In the UI it's the "Device Passthrough: Enabled" field.
(and similarly named field in vdsm-client getCapabilities call)


When I was creating the particular VM in 4.1 it was working as expected.

The hostdev from before the upgrades are still present. I tried to
remove them and got an NPE (see below).

As a workaround, is the old hostusb[1] method I know back from 3.x still 
working in the 4.x
line?

AFAICT IOMMU is working


dmesg | grep -e DMAR -e IOMMU
[0.00] ACPI: DMAR 7b7e7000 002C6 (v01 HP ProLiant 0001 
HP   0001)
[0.168032] DMAR: Host address width 46
[0.168034] DMAR: DRHD base: 0x00fbffc000 flags: 0x0
[0.168047] DMAR: dmar0: reg_base_addr fbffc000 ver 1:0 cap 8d2078c106f0466 
ecap f020de
[0.168050] DMAR: DRHD base: 0x00c7ffc000 flags: 0x1
[0.168061] DMAR: dmar1: reg_base_addr c7ffc000 ver 1:0 cap 8d2078c106f0466 
ecap f020de
[0.168063] DMAR: RMRR base: 0x0079174000 end: 0x0079176fff
[0.168065] DMAR: RMRR base: 0x00791f4000 end: 0x00791f7fff
[0.168067] DMAR: RMRR base: 0x00791de000 end: 0x00791f3fff
[0.168070] DMAR: RMRR base: 0x00791cb000 end: 0x00791dbfff
[0.168071] DMAR: RMRR base: 0x00791dc000 end: 0x00791ddfff
[0.168073] DMAR: ATSR flags: 0x0
[0.168075] DMAR: ATSR flags: 0x0
[0.168079] DMAR-IR: IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
[0.168082] DMAR-IR: IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
[0.168084] DMAR-IR: IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
[0.168086] DMAR-IR: HPET id 0 under DRHD base 0xc7ffc000
[0.168088] DMAR-IR: Queued invalidation will be enabled to support x2apic 
and Intr-remapping.
[0.169073] DMAR-IR: Enabled IRQ remapping in x2apic mode

Thanks,

[1] https://www.ovirt.org/develop/release-management/features/virt/hostusb/


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [ovirt-users] oVirt 4.2: hostdev passthrough not working any more

2018-02-22 Thread Alexandr Krivulya

Hello, the same problem after upgrade to 4.2.1 :(


18.01.2018 11:53, Daniel Helgenberger пишет:

Hello,

yesterday I upgraded to 4.2.0 from 4.1.8.

Now I notice I cannot assign host dev pass though any more; in the GUI
the 'Pinnded to host' list is empty; I cannot select any host for pass
through host pinning.

When I was creating the particular VM in 4.1 it was working as expected.

The hostdev from before the upgrades are still present. I tried to
remove them and got an NPE (see below).

As a workaround, is the old hostusb[1] method I know back from 3.x still 
working in the 4.x
line?

AFAICT IOMMU is working


dmesg | grep -e DMAR -e IOMMU
[0.00] ACPI: DMAR 7b7e7000 002C6 (v01 HP ProLiant 0001 
HP   0001)
[0.168032] DMAR: Host address width 46
[0.168034] DMAR: DRHD base: 0x00fbffc000 flags: 0x0
[0.168047] DMAR: dmar0: reg_base_addr fbffc000 ver 1:0 cap 8d2078c106f0466 
ecap f020de
[0.168050] DMAR: DRHD base: 0x00c7ffc000 flags: 0x1
[0.168061] DMAR: dmar1: reg_base_addr c7ffc000 ver 1:0 cap 8d2078c106f0466 
ecap f020de
[0.168063] DMAR: RMRR base: 0x0079174000 end: 0x0079176fff
[0.168065] DMAR: RMRR base: 0x00791f4000 end: 0x00791f7fff
[0.168067] DMAR: RMRR base: 0x00791de000 end: 0x00791f3fff
[0.168070] DMAR: RMRR base: 0x00791cb000 end: 0x00791dbfff
[0.168071] DMAR: RMRR base: 0x00791dc000 end: 0x00791ddfff
[0.168073] DMAR: ATSR flags: 0x0
[0.168075] DMAR: ATSR flags: 0x0
[0.168079] DMAR-IR: IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
[0.168082] DMAR-IR: IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
[0.168084] DMAR-IR: IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
[0.168086] DMAR-IR: HPET id 0 under DRHD base 0xc7ffc000
[0.168088] DMAR-IR: Queued invalidation will be enabled to support x2apic 
and Intr-remapping.
[0.169073] DMAR-IR: Enabled IRQ remapping in x2apic mode

Thanks,

[1] https://www.ovirt.org/develop/release-management/features/virt/hostusb/


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users