@@ -2742,7 +2742,6 @@ static const VMStateDescription vmstate_vmbus_bridge = {
static Property vmbus_bridge_props[] = {
DEFINE_PROP_UINT8("irq0", VMBusBridge, irq0, 7),
- DEFINE_PROP_UINT8("irq1", VMBusBridge, irq1, 13),
DEFINE_PROP_END_OF_LIST()
};
@@ -1083,8 +1083,6 @@ static Aml *build_vmbus_device_aml(VMBusBridge *vmbus_bridge)
crs = aml_resource_template();
aml_append(crs, aml_irq_no_flags(vmbus_bridge->irq0));
- /* FIXME: newer HyperV gets by with only one IRQ */
- aml_append(crs, aml_irq_no_flags(vmbus_bridge->irq1));
aml_append(dev, aml_name_decl("_CRS", crs));
return dev;
@@ -20,7 +20,6 @@ typedef struct VMBusBridge {
SysBusDevice parent_obj;
uint8_t irq0;
- uint8_t irq1;
VMBus *bus;
} VMBusBridge;
It seems like Windows does not really require 2 IRQs to have a functioning VMBus. Signed-off-by: Jon Doron <arilou@gmail.com> --- hw/hyperv/vmbus.c | 1 - hw/i386/acpi-build.c | 2 -- include/hw/hyperv/vmbus-bridge.h | 1 - 3 files changed, 4 deletions(-)