to disable autoballoon completely.
And to answer you question - libvirt rely on libxl autoballoon.
--
Best Regards / Pozdrawiam,
Marek Marczykowski
Invisible Things Lab
signature.asc
Description: OpenPGP digital signature
--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com
On 10.04.2013 11:14, Daniel P. Berrange wrote:
On Wed, Apr 10, 2013 at 04:44:43AM +0200, Marek Marczykowski wrote:
Script to be called to prepare custom device for domain. Done with Xen
in mind, it maps to libxl_device_disk.script.
XML configuration would be:
disk type='block' device='disk
libxl uses some xenstore entries for hints in memory management
(especially when starting new domain). This includes dom0 memory limit
and Xen free memory margin, based on current system state. Entries are
created at first usage, so force such usage at daemon startup, which most
likely will be
For now only for PCI devices. Mostly copy-paste from old xen driver.
---
src/libxl/libxl_driver.c | 193 +++
1 file changed, 193 insertions(+)
diff --git a/src/libxl/libxl_driver.c b/src/libxl/libxl_driver.c
index 40a7a6b..011edf8 100644
---
This are some additional features to libxl driver. Some of them require change
in domain config structures/syntax. Details described with each patch.
The last two patches are bugfix for deadlock during daemon startup.
PS Please keep me in To/Cc - I'm not subscribed to the list.
Marek
This can be useful for route or NAT networks, or any other custom
network setup. Especially configuration example in documentation uses
script/ tag with type 'ethernet'.
---
src/libxl/libxl_conf.c | 17 +
1 file changed, 5 insertions(+), 12 deletions(-)
diff --git
This implement handling of domain name=''/ parameter introduced in previous
patch.
Lookup on domain name (to get domain ID) requires libxlDriverPrivate
object, so it must be passed down to libxlMakeDisk and libxlMakeNet from
top level callers.
---
src/libxl/libxl_conf.c | 62
While iterating with virDomainObjListForEach it is safe to remove
current element. But while iterating, 'doms' lock is already taken, so
can't use standard virDomainObjListRemove. So introduce
virDomainObjListRemoveLocked for this purpose. This is required to fix deadlock
in libxl driver.
---
Use virDomainObjListRemoveLocked instead of virDomainObjListRemove, as
driver-domains is already taken by virDomainObjListForEach.
Above deadlock can be triggered when libvirtd is started after some
domain have been started by hand (in which case driver will not find
libvirt-xml domain config).
At least Xen supports backend drivers in another domain (aka driver
domain). This patch introduces XML config option for such setting as
'domain' element with 'name' attribute. Verification its content is left
for the driver.
In the future some option will be needed for USB devices (hostdev
Xen have feature of having device model in separate domain (called stub
domain). It used to be enabled by special 'stubdom-dm' device model path.
Recent xl have separate config option for this feature
(device_model_stubdomain_override), but I'm not sure if it worth introducing
another xen-specific
Script to be called to prepare custom device for domain. Done with Xen
in mind, it maps to libxl_device_disk.script.
XML configuration would be:
disk type='block' device='disk'
source dev='/dev/mapper/custom-device'/
script path='/script/to/setup/custom-device'/
target dev='xvdc'/
Implement handling of previously introduced script/ element for disk config.
This can be used for custom backend configuration like non-standard
device-mapper nodes, or to prepare device in other domain (see the next patch).
---
src/libxl/libxl_conf.c | 5 +
1 file changed, 5 insertions(+)
Vfb entries in domain config are used only by PV drivers. Qemu parameters are
build based on b_info struct. So fill it with the same data as vfb entries
(actually the first one).
This will additionally allow graphic-less domain, when no graphics/ entries
are present in domain XML (previously VNC
This can be useful for route or NAT networks, or any other custom
network setup. Especially configuration example in documentation uses
script/ tag with type 'ethernet'.
---
src/libxl/libxl_conf.c | 17 +
1 file changed, 5 insertions(+), 12 deletions(-)
diff --git
---
src/libxl/libxl_conf.c | 72 ++
src/libxl/libxl_conf.h | 2 ++
2 files changed, 74 insertions(+)
diff --git a/src/libxl/libxl_conf.c b/src/libxl/libxl_conf.c
index ffc7bbb..7668305 100644
--- a/src/libxl/libxl_conf.c
+++
Script to be called to prepare custom device for domain. Done with Xen
in mind, it maps to libxl_device_disk.script.
XML configuration would be:
disk type='block' device='disk'
source dev='/dev/mapper/custom-device'/
script path='/script/to/setup/custom-device'/
target dev='xvdc'/
Implement handling of previously introduced script/ element for disk
config.
This can be used for custom backend configuration like non-standard
device-mapper nodes, or to prepare device in other domain (see the next
patch).
---
src/libxl/libxl_conf.c | 5 +
1 file changed, 5 insertions(+)
At least Xen supports backend drivers in another domain (aka driver
domain). This patch introduces XML config option for such setting as
'domain' element with 'name' attribute. Verification its content is left
for the driver.
In the future some option will be needed for USB devices (hostdev
Vfb entries in domain config are used only by PV drivers. Qemu
parameters are build based on b_info struct. So fill it with the same
data as vfb entries (actually the first one).
This will additionally allow graphic-less domain, when no graphics/
entries are present in domain XML (previously VNC
Xen have feature of having device model in separate domain (called stub
domain). It used to be enabled by special 'stubdom-dm' device model
path. Recent xl have separate config option for this feature
(device_model_stubdomain_override), but I'm not sure if it worth
introducing another
While iterating with virDomainObjListForEach it is safe to remove
current element. But while iterating, 'doms' lock is already taken, so
can't use standard virDomainObjListRemove. So introduce
virDomainObjListRemoveLocked for this purpose.
---
src/conf/domain_conf.c | 17 +
This are some additional features to libxl driver. Some of them require change
in domain config structures/syntax. Details described with each patch.
The last two patches are bugfix for deadlock during daemon startup.
Marek Marczykowski (12):
libxl: allow script for any network interface
For now only for PCI devices. Mostly copy-paste from old xen driver.
---
src/libxl/libxl_driver.c | 193 +++
1 file changed, 193 insertions(+)
diff --git a/src/libxl/libxl_driver.c b/src/libxl/libxl_driver.c
index 40a7a6b..011edf8 100644
---
On 10.04.2013 04:34, Eric Blake wrote:
On 04/09/2013 07:53 PM, Marek Marczykowski wrote:
This are some additional features to libxl driver. Some of them require
change
in domain config structures/syntax. Details described with each patch.
The last two patches are bugfix for deadlock during
Use virDomainObjListRemoveLocked instead of virDomainObjListRemove, as
driver-domains is already taken by virDomainObjListForEach.
Above deadlock can be triggered when libvirtd is started after some
domain have been started by hand (in which case driver will not find
libvirt-xml domain config).
of domain_conf.c? It looks like it requires connection
reference, which isn't passed to virDomain*DefParseXML.
--
Best Regards,
Marek Marczykowski
Invisible Things Lab
signature.asc
Description: OpenPGP digital signature
--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com
301 - 327 of 327 matches
Mail list logo
