Bug 1079992

Could you provide vdsm.log & supervdsm.log from the host as well ?

(In reply to Jiri Belka from comment #0)
> Created attachment 878066 [details]
> engine.log, server.log
> 
> Description of problem:
> 
> 1. What is 'Dual mode rtl8139, VirtIO' type for new network interface. Is it
> a bug? It is old realtek garbage hw emulation in reality...
> 
>                 <interface type="bridge">
>                         <mac address="00:1a:4a:64:5a:3f"/>
>                         <model type="rtl8139"/>
>                         <source bridge="rhevm"/>
>                         <filterref filter="vdsm-no-mac-spoofing"/>
>                         <link state="up"/>
>                         <boot order="1"/>
> 
> 2. When hot-adding this 'Dual mode rtl8139, VirtIO' network interface type
> there's failure:
> 
> "Failed to add Interface nic3 (Dual mode rtl8139, VirtIO) to VM bbb. (User:
> admin)"
> 
> And in engine.log:
> 
> 2014-03-24 14:11:32,263 ERROR
> [org.ovirt.engine.core.vdsbroker.vdsbroker.HotPlugNicVDSCommand]
> (ajp-/127.0.0.1:8702-11) [6ea325b4] Command HotPlugNicVDSCommand(HostName =
> dell-r210ii-04, HostId = 3bda7e71-e78e-4373-a7e0-5587314f485d,
> vm.vm_name=bbb, nic=nic3 {id=57678bb4-a544-45d3-a904-3a1973d330e7,
> networkName=rhevm, vnicProfileName=null,
> vnicProfileId=0000000e-000e-000e-000e-000000000202, speed=1000, type=0,
> macAddress=00:1a:4a:64:5a:51, active=true, linked=true, portMirroring=false,
> vmId=4ea52536-5985-4a56-8afc-0d6120b9ab91, vmName=null, vmTemplateId=null},
> vmDevice=VmDevice {vmId=4ea52536-5985-4a56-8afc-0d6120b9ab91,
> deviceId=57678bb4-a544-45d3-a904-3a1973d330e7, device=bridge,
> type=INTERFACE, bootOrder=3, specParams={}, address=, managed=true,
> plugged=true, readOnly=false, deviceAlias=, customProperties={},
> snapshotId=null}) execution failed. Exception: VDSErrorException:
> VDSGenericException: VDSErrorException: Failed to HotPlugNicVDS, error = An
> error occurred, but the cause is unknown, code = 49
> 2014-03-24 14:11:32,263 INFO 
> [org.ovirt.engine.core.vdsbroker.vdsbroker.HotPlugNicVDSCommand]
> (ajp-/127.0.0.1:8702-11) [6ea325b4] FINISH, HotPlugNicVDSCommand, log id:
> 5827b44b
> 2014-03-24 14:11:32,264 ERROR
> [org.ovirt.engine.core.bll.network.vm.ActivateDeactivateVmNicCommand]
> (ajp-/127.0.0.1:8702-11) [6ea325b4] Command
> org.ovirt.engine.core.bll.network.vm.ActivateDeactivateVmNicCommand throw
> Vdc Bll exception. With error message VdcBLLException:
> org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException:
> VDSGenericException: VDSErrorException: Failed to HotPlugNicVDS, error = An
> error occurred, but the cause is unknown, code = 49 (Failed with error
> ACTIVATE_NIC_FAILED and code 49)
> 2014-03-24 14:11:32,264 DEBUG
> [org.ovirt.engine.core.bll.network.vm.ActivateDeactivateVmNicCommand]
> (ajp-/127.0.0.1:8702-11) [6ea325b4] Command
> org.ovirt.engine.core.bll.network.vm.ActivateDeactivateVmNicCommand throw
> Vdc Bll exception: org.ovirt.engine.core.common.errors.VdcBLLException:
> VdcBLLException:
> org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException:
> VDSGenericException: VDSErrorException: Failed to HotPlugNicVDS, error = An
> error occurred, but the cause is unknown, code = 49 (Failed with error
> ACTIVATE_NIC_FAILED and code 49)
>         at
> org.ovirt.engine.core.bll.VdsHandler.handleVdsResult(VdsHandler.java:116)
> [bll.jar:]
>         at
> org.ovirt.engine.core.bll.VDSBrokerFrontendImpl.
> RunVdsCommand(VDSBrokerFrontendImpl.java:33) [bll.jar:]
>         at
> org.ovirt.engine.core.bll.CommandBase.runVdsCommand(CommandBase.java:1971)
> [bll.jar:]
>         at
> org.ovirt.engine.core.bll.network.vm.ActivateDeactivateVmNicCommand.
> executeVmCommand(ActivateDeactivateVmNicCommand.java:132) [bll.jar:]
> ...snip...
> 
> Version-Release number of selected component (if applicable):
> rhevm-webadmin-portal-3.4.0-0.5.master.el6ev.noarch
> 
> How reproducible:
> 100%
> 
> Steps to Reproduce:
> 1. have a running vm
> 2. add 'Dual mode rtl8139, VirtIO' network iface type (hot-plug)
> 3.
> 
> Actual results:
> failure, traceback in engine.log
> 
> Expected results:
> ???
> 
> Additional info:
> i doubt about 'Dual mode' completely

Can you provide more information here? How did you add this network iface type? Was it from the UI?

Created attachment 881787 [details]
+ vdsm.log, supervdsm.log

Yes, I tried to hot-add that iface from Admin Portal.

Did you edit the OsInfo properties? Because by default I can't see that option on my deployment.

Of course not but this environment has long history, gets updates since first AV version.

verfied av7

Closing as part of 3.4.0