- 21 5月, 2014 2 次提交
-
-
由 Roman Bogorodskiy 提交于
In a number of places in the bhyve driver, virObjectUnlock() is called with an arg without check if the arg is non-NULL, which could result in passing NULL value and a warning like: virObjectUnlock:340 : Object 0x0 ((unknown)) is not a virObjectLockable instance * src/bhyve/bhyve_driver.c (bhyveDomainGetInfo) (bhyveDomainGetState, bhyveDomainGetAutostart) (bhyveDomainSetAutostart, bhyveDomainIsActive) (bhyveDomainIsPersistent, bhyveDomainGetXMLDesc) (bhyveDomainUndefine, bhyveDomainLookupByUUID) (bhyveDomainLookupByName, bhyveDomainLookupByID) (bhyveDomainCreateWithFlags, bhyveDomainOpenConsole): Check if arg is not NULL before calling virObjectUnlock on it.
-
由 Roman Bogorodskiy 提交于
Support events for these functions: - domainDefineXML - domainUndefine - domainCreate{WithFlags,XML} - domainDestroy
-
- 12 5月, 2014 1 次提交
-
-
由 Roman Bogorodskiy 提交于
-
- 05 5月, 2014 1 次提交
-
-
由 Roman Bogorodskiy 提交于
Add a helper function virBhyveGetDomainTotalCpuStats() to obtain process CPU time using kvm (kernel memory interface) and use it to set cpuTime field of the virDomainInfo struct in bhyveDomainGetInfo().
-
- 04 5月, 2014 1 次提交
-
-
由 Roman Bogorodskiy 提交于
The only accepted format for now is 'bhyve-argv' which prints out a bhyve command corresponding to the given domain definition.
-
- 23 4月, 2014 1 次提交
-
-
由 Roman Bogorodskiy 提交于
- do not lose new definition for an active domain - do not leak oldDef - do not set dom->id if virDomainSaveConfig() fails - do not call virObjectUnlock(vm) if vm is NULL
-
- 20 4月, 2014 1 次提交
-
-
由 Wojciech Macek 提交于
Implement bhyveDomainCreateXML function. Signed-off-by: NDaniel P. Berrange <berrange@redhat.com> Signed-off-by: NRoman Bogorodskiy <bogorodskiy@gmail.com>
-
- 12 4月, 2014 1 次提交
-
-
由 Wojciech Macek 提交于
When domain is not persistent, it should be forgotten upon destroying.
-
- 09 4月, 2014 2 次提交
-
-
由 Roman Bogorodskiy 提交于
Implement domainSetMetadata and domainGetMetadata driver calls.
-
由 Roman Bogorodskiy 提交于
Fix incorrect ATTRIBUTE_NONNULL usage introduced in 17b17565 which caused build failure: bhyve/bhyve_driver.c:127:48: error: expected ')' bhyveDriverGetCapabilities(bhyveConnPtr driver ATTRIBUTE_NONNULL) ^ bhyve/bhyve_driver.c:127:27: note: to match this '(' bhyveDriverGetCapabilities(bhyveConnPtr driver ATTRIBUTE_NONNULL) Pushed under the build breaker rule.
-
- 08 4月, 2014 2 次提交
-
-
由 Michal Privoznik 提交于
At the beginning of the function we gain a reference to the driver capabilities. Then, we call format function (*) which if failed, unref over caps is called. Then, at the end another unref occurs. * - Moreover, the format was not called over gained caps, but over privconn->caps directly which is not allowed anymore. Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>
-
由 Michal Privoznik 提交于
The driver passed as the only argument to the function should never be NULL so there's no need to check it. After removing it, the whole function collapses to a single line doing ref over driver capabilities. Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>
-
- 07 4月, 2014 3 次提交
-
-
由 Wojciech Macek 提交于
Implement support for connectCompareCPU.
-
由 Wojciech Macek 提交于
- Move all capabilities functions to separate file - Add initCPU
-
由 Wojciech Macek 提交于
Implement bhyveConnectBaselineCPU to support OpenStack/Nova
-
- 05 4月, 2014 2 次提交
-
-
由 Roman Bogorodskiy 提交于
nmdm is a FreeBSD driver which allows to create a pair of tty devices one of which is passed to the guest and second is used by the client. This patch adds new 'nmdm' character device type. Its definition looks this way: <serial type='nmdm'> <source master='/dev/nmdm0A' slave='/dev/nmdm0B'/> </serial> Master is passed to the hypervisior and slave is used for client connection. Also implement domainOpenConsole() for bhyve driver based on that.
-
由 David Shane Holden 提交于
Signed-off-by: NRoman Bogorodskiy <bogorodskiy@gmail.com>
-
- 27 3月, 2014 1 次提交
-
-
由 Wojciech Macek 提交于
Implement domain lookup by its ID.
-
- 25 3月, 2014 1 次提交
-
-
由 Ján Tomko 提交于
-
- 23 3月, 2014 1 次提交
-
-
由 Roman Bogorodskiy 提交于
The only supported flag for now is 'autodestroy'. In order to support 'autodestroy', add support for close callbacks.
-
- 21 3月, 2014 1 次提交
-
-
由 Martin Kletzander 提交于
Signed-off-by: NMartin Kletzander <mkletzan@redhat.com>
-
- 20 3月, 2014 1 次提交
-
-
由 Wojciech Macek 提交于
New functionalities: - connectGetMaxVcpus - on bhyve hardcode this value to 16 - nodeGetFreeMemory - do not use physmem_get on FreeBSD, since it might get wrong value on systems with more than 100GB of RAM - nodeGetCPUMap - wrapper only for mapping function, currently not supported by FreeBSD - nodeSet/GetMemoryParameters - wrapper only for future improvements, currently not supported by FreeBSD
-
- 18 3月, 2014 3 次提交
-
-
由 Daniel P. Berrange 提交于
Any source file which calls the logging APIs now needs to have a VIR_LOG_INIT("source.name") declaration at the start of the file. This provides a static variable of the virLogSource type. Signed-off-by: NDaniel P. Berrange <berrange@redhat.com>
-
由 Roman Bogorodskiy 提交于
Add a check that domain is active before attempting to destroy it.
-
由 Roman Bogorodskiy 提交于
Add bhyveNodeGetInfo() which is a simple wrapper around nodeGetInfo() from src/nodeinfo.c.
-
- 17 3月, 2014 1 次提交
-
-
由 Pavel Hrdina 提交于
Coverity found an issue in lxc_driver and uml_driver that we don't check the return value of register functions. I've also updated all other places and unify the way we check the return value. Signed-off-by: NPavel Hrdina <phrdina@redhat.com>
-
- 01 3月, 2014 2 次提交
-
-
由 Roman Bogorodskiy 提交于
-
由 Roman Bogorodskiy 提交于
Implement domainUndefine and required helper functions: - domainIsActive - domainIsPersistent
-
- 24 2月, 2014 1 次提交
-
-
由 Roman Bogorodskiy 提交于
- Implement nodeGetCPUStats using nodeGetCPUStats() - Implement nodeGetMemoryStats using nodeGetMemoryStats()
-
- 19 2月, 2014 1 次提交
-
-
由 Roman Bogorodskiy 提交于
At this point it has a limited functionality and is highly experimental. Supported domain operations are: * define * start * destroy * dumpxml * dominfo It's only possible to have only one disk device and only one network, which should be of type bridge.
-