2014-04-12 19:37:53 +00:00
|
|
|
/*
|
|
|
|
* bhyve_domain.c: bhyve domain private state
|
|
|
|
*
|
|
|
|
* Copyright (C) 2014 Roman Bogorodskiy
|
|
|
|
*
|
|
|
|
* This library is free software; you can redistribute it and/or
|
|
|
|
* modify it under the terms of the GNU Lesser General Public
|
|
|
|
* License as published by the Free Software Foundation; either
|
|
|
|
* version 2.1 of the License, or (at your option) any later version.
|
|
|
|
*
|
|
|
|
* This library is distributed in the hope that it will be useful,
|
|
|
|
* but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
|
|
|
|
* Lesser General Public License for more details.
|
|
|
|
*
|
|
|
|
* You should have received a copy of the GNU Lesser General Public
|
|
|
|
* License along with this library. If not, see
|
|
|
|
* <http://www.gnu.org/licenses/>.
|
|
|
|
*
|
|
|
|
* Author: Roman Bogorodskiy
|
|
|
|
*/
|
|
|
|
|
|
|
|
#include <config.h>
|
|
|
|
|
|
|
|
#include "bhyve_device.h"
|
|
|
|
#include "bhyve_domain.h"
|
bhyve: fix SATA address allocation
As bhyve for a long time didn't have a notion of the explicit SATA
controller and created a controller for each drive, the bhyve driver
in libvirt acted in a similar way and didn't care about the SATA
controllers and assigned PCI addresses to drives directly, as
the generated command will look like this anyway:
2:0,ahci-hd,somedisk.img
This no longer makes sense because:
1. After commit c07d1c1c4f it's not possible to assign
PCI addresses to disks
2. Bhyve now supports multiple disk drives for a controller,
so it's going away from 1:1 controller:disk mapping, so
the controller object starts to make more sense now
So, this patch does the following:
- Assign PCI address to SATA controllers (previously we didn't do this)
- Assign disk addresses instead of PCI addresses for disks. Now, when
building a bhyve command, we take PCI address not from the disk
itself but from its controller
- Assign addresses at XML parsing time using the
assignAddressesCallback. This is done mainly for being able to
verify address allocation via xml2xml tests
- Adjust existing bhyvexml2{xml,argv} tests to chase the new
address allocation
This patch is largely based on work of Fabian Freyer.
2017-01-05 12:51:25 +00:00
|
|
|
#include "bhyve_capabilities.h"
|
2014-04-12 19:37:53 +00:00
|
|
|
#include "viralloc.h"
|
|
|
|
#include "virlog.h"
|
|
|
|
|
|
|
|
#define VIR_FROM_THIS VIR_FROM_BHYVE
|
|
|
|
|
|
|
|
VIR_LOG_INIT("bhyve.bhyve_domain");
|
|
|
|
|
|
|
|
static void *
|
|
|
|
bhyveDomainObjPrivateAlloc(void)
|
|
|
|
{
|
|
|
|
bhyveDomainObjPrivatePtr priv;
|
|
|
|
|
|
|
|
if (VIR_ALLOC(priv) < 0)
|
|
|
|
return NULL;
|
|
|
|
|
|
|
|
return priv;
|
|
|
|
}
|
|
|
|
|
|
|
|
static void
|
|
|
|
bhyveDomainObjPrivateFree(void *data)
|
|
|
|
{
|
|
|
|
bhyveDomainObjPrivatePtr priv = data;
|
|
|
|
|
|
|
|
virDomainPCIAddressSetFree(priv->pciaddrs);
|
|
|
|
|
|
|
|
VIR_FREE(priv);
|
|
|
|
}
|
|
|
|
|
|
|
|
virDomainXMLPrivateDataCallbacks virBhyveDriverPrivateDataCallbacks = {
|
|
|
|
.alloc = bhyveDomainObjPrivateAlloc,
|
|
|
|
.free = bhyveDomainObjPrivateFree,
|
|
|
|
};
|
|
|
|
|
|
|
|
static int
|
|
|
|
bhyveDomainDefPostParse(virDomainDefPtr def,
|
|
|
|
virCapsPtr caps ATTRIBUTE_UNUSED,
|
2016-01-08 13:00:56 +00:00
|
|
|
unsigned int parseFlags ATTRIBUTE_UNUSED,
|
2016-09-22 14:41:33 +00:00
|
|
|
void *opaque ATTRIBUTE_UNUSED,
|
|
|
|
void *parseOpaque ATTRIBUTE_UNUSED)
|
2014-04-12 19:37:53 +00:00
|
|
|
{
|
|
|
|
/* Add an implicit PCI root controller */
|
|
|
|
if (virDomainDefMaybeAddController(def, VIR_DOMAIN_CONTROLLER_TYPE_PCI, 0,
|
|
|
|
VIR_DOMAIN_CONTROLLER_MODEL_PCI_ROOT) < 0)
|
|
|
|
return -1;
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2014-10-06 15:28:46 +00:00
|
|
|
static int
|
bhyve: fix SATA address allocation
As bhyve for a long time didn't have a notion of the explicit SATA
controller and created a controller for each drive, the bhyve driver
in libvirt acted in a similar way and didn't care about the SATA
controllers and assigned PCI addresses to drives directly, as
the generated command will look like this anyway:
2:0,ahci-hd,somedisk.img
This no longer makes sense because:
1. After commit c07d1c1c4f it's not possible to assign
PCI addresses to disks
2. Bhyve now supports multiple disk drives for a controller,
so it's going away from 1:1 controller:disk mapping, so
the controller object starts to make more sense now
So, this patch does the following:
- Assign PCI address to SATA controllers (previously we didn't do this)
- Assign disk addresses instead of PCI addresses for disks. Now, when
building a bhyve command, we take PCI address not from the disk
itself but from its controller
- Assign addresses at XML parsing time using the
assignAddressesCallback. This is done mainly for being able to
verify address allocation via xml2xml tests
- Adjust existing bhyvexml2{xml,argv} tests to chase the new
address allocation
This patch is largely based on work of Fabian Freyer.
2017-01-05 12:51:25 +00:00
|
|
|
bhyveDomainDiskDefAssignAddress(bhyveConnPtr driver,
|
|
|
|
virDomainDiskDefPtr def,
|
|
|
|
const virDomainDef *vmdef ATTRIBUTE_UNUSED)
|
|
|
|
{
|
|
|
|
int idx = virDiskNameToIndex(def->dst);
|
|
|
|
|
|
|
|
if (idx < 0) {
|
|
|
|
virReportError(VIR_ERR_XML_ERROR,
|
|
|
|
_("Unknown disk name '%s' and no address specified"),
|
|
|
|
def->dst);
|
|
|
|
return -1;
|
|
|
|
}
|
|
|
|
|
|
|
|
switch (def->bus) {
|
|
|
|
case VIR_DOMAIN_DISK_BUS_SATA:
|
|
|
|
def->info.type = VIR_DOMAIN_DEVICE_ADDRESS_TYPE_DRIVE;
|
|
|
|
|
|
|
|
if ((driver->bhyvecaps & BHYVE_CAP_AHCI32SLOT) != 0) {
|
|
|
|
def->info.addr.drive.controller = idx / 32;
|
|
|
|
def->info.addr.drive.unit = idx % 32;
|
|
|
|
} else {
|
|
|
|
def->info.addr.drive.controller = idx;
|
|
|
|
def->info.addr.drive.unit = 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
def->info.addr.drive.bus = 0;
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int
|
|
|
|
bhyveDomainDeviceDefPostParse(virDomainDeviceDefPtr dev,
|
|
|
|
const virDomainDef *def,
|
|
|
|
virCapsPtr caps ATTRIBUTE_UNUSED,
|
|
|
|
unsigned int parseFlags ATTRIBUTE_UNUSED,
|
|
|
|
void *opaque,
|
|
|
|
void *parseOpaque ATTRIBUTE_UNUSED)
|
|
|
|
{
|
|
|
|
bhyveConnPtr driver = opaque;
|
|
|
|
|
|
|
|
if (dev->type == VIR_DOMAIN_DEVICE_DISK) {
|
|
|
|
virDomainDiskDefPtr disk = dev->data.disk;
|
|
|
|
|
|
|
|
if (disk->info.type == VIR_DOMAIN_DEVICE_ADDRESS_TYPE_NONE &&
|
|
|
|
bhyveDomainDiskDefAssignAddress(driver, disk, def) < 0)
|
|
|
|
return -1;
|
|
|
|
}
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int
|
|
|
|
bhyveDomainDefAssignAddresses(virDomainDef *def,
|
2014-10-06 15:28:46 +00:00
|
|
|
virCapsPtr caps ATTRIBUTE_UNUSED,
|
2016-01-08 13:00:56 +00:00
|
|
|
unsigned int parseFlags ATTRIBUTE_UNUSED,
|
2016-09-23 08:53:38 +00:00
|
|
|
void *opaque ATTRIBUTE_UNUSED,
|
|
|
|
void *parseOpaque ATTRIBUTE_UNUSED)
|
2014-10-06 15:28:46 +00:00
|
|
|
{
|
bhyve: fix SATA address allocation
As bhyve for a long time didn't have a notion of the explicit SATA
controller and created a controller for each drive, the bhyve driver
in libvirt acted in a similar way and didn't care about the SATA
controllers and assigned PCI addresses to drives directly, as
the generated command will look like this anyway:
2:0,ahci-hd,somedisk.img
This no longer makes sense because:
1. After commit c07d1c1c4f it's not possible to assign
PCI addresses to disks
2. Bhyve now supports multiple disk drives for a controller,
so it's going away from 1:1 controller:disk mapping, so
the controller object starts to make more sense now
So, this patch does the following:
- Assign PCI address to SATA controllers (previously we didn't do this)
- Assign disk addresses instead of PCI addresses for disks. Now, when
building a bhyve command, we take PCI address not from the disk
itself but from its controller
- Assign addresses at XML parsing time using the
assignAddressesCallback. This is done mainly for being able to
verify address allocation via xml2xml tests
- Adjust existing bhyvexml2{xml,argv} tests to chase the new
address allocation
This patch is largely based on work of Fabian Freyer.
2017-01-05 12:51:25 +00:00
|
|
|
if (bhyveDomainAssignAddresses(def, NULL) < 0)
|
|
|
|
return -1;
|
|
|
|
|
2014-10-06 15:28:46 +00:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2017-01-05 12:31:35 +00:00
|
|
|
virDomainXMLOptionPtr
|
|
|
|
virBhyveDriverCreateXMLConf(bhyveConnPtr driver)
|
|
|
|
{
|
|
|
|
virBhyveDriverDomainDefParserConfig.priv = driver;
|
|
|
|
return virDomainXMLOptionNew(&virBhyveDriverDomainDefParserConfig,
|
|
|
|
&virBhyveDriverPrivateDataCallbacks,
|
|
|
|
NULL);
|
|
|
|
}
|
|
|
|
|
2014-04-12 19:37:53 +00:00
|
|
|
virDomainDefParserConfig virBhyveDriverDomainDefParserConfig = {
|
2014-10-06 15:28:46 +00:00
|
|
|
.devicesPostParseCallback = bhyveDomainDeviceDefPostParse,
|
2014-04-12 19:37:53 +00:00
|
|
|
.domainPostParseCallback = bhyveDomainDefPostParse,
|
bhyve: fix SATA address allocation
As bhyve for a long time didn't have a notion of the explicit SATA
controller and created a controller for each drive, the bhyve driver
in libvirt acted in a similar way and didn't care about the SATA
controllers and assigned PCI addresses to drives directly, as
the generated command will look like this anyway:
2:0,ahci-hd,somedisk.img
This no longer makes sense because:
1. After commit c07d1c1c4f it's not possible to assign
PCI addresses to disks
2. Bhyve now supports multiple disk drives for a controller,
so it's going away from 1:1 controller:disk mapping, so
the controller object starts to make more sense now
So, this patch does the following:
- Assign PCI address to SATA controllers (previously we didn't do this)
- Assign disk addresses instead of PCI addresses for disks. Now, when
building a bhyve command, we take PCI address not from the disk
itself but from its controller
- Assign addresses at XML parsing time using the
assignAddressesCallback. This is done mainly for being able to
verify address allocation via xml2xml tests
- Adjust existing bhyvexml2{xml,argv} tests to chase the new
address allocation
This patch is largely based on work of Fabian Freyer.
2017-01-05 12:51:25 +00:00
|
|
|
.assignAddressesCallback = bhyveDomainDefAssignAddresses,
|
2014-04-12 19:37:53 +00:00
|
|
|
};
|