Displaying 5 results from an estimated 5 matches for "libxl_bios_typ".
Did you mean:
libxl_bios_type
2012 Feb 29
5
[PATCH] [PATCH v4] Add the bios option to specify the bios to load
...12 +0000
+++ b/tools/libxl/libxl_dm.c Wed Feb 29 13:00:06 2012 +0000
@@ -66,6 +66,8 @@ const char *libxl__domain_device_model(l
static const char *libxl__domain_bios(libxl__gc *gc,
const libxl_domain_build_info *info)
{
+ if (info->u.hvm.bios)
+ return libxl_bios_type_to_string(info->u.hvm.bios);
switch (info->device_model_version) {
case 1: return "rombios";
case 2: return "seabios";
diff -r adcd6ab160fa -r 3c10ba854d37 tools/libxl/libxl_types.idl
--- a/tools/libxl/libxl_types.idl Thu Feb 23 10:29:27 2012 +0000
+++ b/to...
2012 Aug 31
2
[PATCH V2] libxl/xl: implement support for guest iooprt and irq permissions
...", Array(uint32, "num_irqs")),
+
("u", KeyedUnion(None, libxl_domain_type, "type",
[("hvm", Struct(None, [("firmware", string),
("bios", libxl_bios_type),
diff -r ccbee5bcb31b -r ddde6c2c45de tools/libxl/xl_cmdimpl.c
--- a/tools/libxl/xl_cmdimpl.c Fri Aug 31 12:03:55 2012 +0100
+++ b/tools/libxl/xl_cmdimpl.c Fri Aug 31 16:54:01 2012 +0100
@@ -573,10 +573,12 @@ static void parse_config_data(const char
long l;
XLU_Config *config;
XLU_...
2012 Apr 20
26
xl doesn't honour the parameter cpu_weight from my config file while xm does honour it
Hi,
I''ve installed xen-unstable 4.2 from actual git (last commit was
4dc7dbef5400f0608321d579aebb57f933e8f707).
When I start a domU with xm all is fine include the cpu_weight I
configured in my domU config.
When I start the domU with xl then all my domU have the default
cpu_weight of 256 instead of the configured one.
Was the name of cpu_weight being changed for xl command ?
My domU
2012 Apr 20
26
xl doesn't honour the parameter cpu_weight from my config file while xm does honour it
Hi,
I''ve installed xen-unstable 4.2 from actual git (last commit was
4dc7dbef5400f0608321d579aebb57f933e8f707).
When I start a domU with xm all is fine include the cpu_weight I
configured in my domU config.
When I start the domU with xl then all my domU have the default
cpu_weight of 256 instead of the configured one.
Was the name of cpu_weight being changed for xl command ?
My domU
2013 Jul 23
73
Bug: Limitation of <=2GB RAM in domU persists with 4.3.0
I just built 4.3.0 in order to get > 2GB of RAM in domU with GPU
passthrough without crashes. Unfortunately, the same crashes still
happen. Massive frame buffer corruption on domU before it locks up
solid. It seems the PCI memory stomp is still happening.
I am using qemu-dm, as I did on Xen 4.2.x.
So whatever fix for this went into 4.3.0 didn''t fix it for me.
Passing less than 2GB