similar to: [PATCH] libxl: change default HVM emulated network card to rtl8139

Displaying 20 results from an estimated 3000 matches similar to: "[PATCH] libxl: change default HVM emulated network card to rtl8139"

2011 Jan 11
0
[PATCH, v2]: xl: move domain struct init functions to libxl
Changes since v1: - Include nic,net2,vkb,vfb init functions --- This allows libxl users to get some sane default values for this complex set of structures. This is purely code movement and there are no functional changes except for a trivial error handling change in nic device init. Signed-off-by: Gianni Tedesco <gianni.tedesco@citrix.com> diff -r efe2d3ea22ae tools/libxl/libxl.c ---
2013 Apr 12
11
[PATCH v4 1/2] libxl: postpone backend name resolution
This adds a backend_domname field in libxl devices that contain a backend_domid field, allowing either a domid or a domain name to be specified in the configuration structures. The domain name is resolved into a domain ID in the _setdefault function when adding the device. This change allows the backend of the block devices to be specified (which previously required passing the libxl_ctx down
2006 Nov 15
3
qemu/rtl8139: Max transmit frame size
Hi: I noticed a bug in the realloc error checking code in the QEMU backend for RealTek8139. However, what''s worse is that there is no cap on the total size of the transmit buffer at all. So a guest can keep extending it until memory runs out. CP_TX_BUFFER_SIZE is already 64K. So it seems to me that we don''t need the while loop to extend the buffer at all since no transmitted
2002 Jun 25
1
weird rtl8139-problem
hi, have changed a ethercard, because the oldone was defect. Now I got a realtec8139 and would install it into my winbox98, but have a lot of troubles. the driver rtl8139.sys seems to be defect or has something trouble, win98 tells me, the driver couldn't be installed. Have downloaded again the drivers for rtl8139, but the same problem appears. Is anybody there, who could help here ? the
2014 Oct 03
2
sr-vio on intel while virsh chooses rtl8139 for model type
hi everybody I'd presume virsh makes the best possible choice, right? It is that just seems bit... odd having realtek in guest and Intel's VF on host, no? regards
2014 Oct 08
3
Re: sr-vio on intel while virsh chooses rtl8139 for model type
On 03/10/14 17:15, Laine Stump wrote: > On 10/03/2014 11:38 AM, lejeczek wrote: >> hi everybody >> >> I'd presume virsh makes the best possible choice, right? >> It is that just seems bit... odd having realtek in guest and Intel's >> VF on host, no? > This can safely be ignored - in the case of an SRIOV VF that is assigned > to the guest using PCI
2012 Mar 22
1
Bug#665070: xen: FTBFS: make[8]: *** No rule to make target `/usr/lib/ipxe/rtl8139.rom', needed by `eb-roms.h'. Stop.
Source: xen Version: 4.1.2-3 Severity: serious Tags: wheezy sid User: debian-qa at lists.debian.org Usertags: qa-ftbfs-20120321 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[7]: Entering directory `/?PKGBUILDDIR?/debian/build/build-utils_amd64/tools/firmware' > /usr/bin/make -C etherboot
2013 May 08
1
[PATCH] libxl: make nic 'bridge' parameter optional - do not fill default
Do not set ''bridge'' parameter - let vif-bridge script to do autodetection. Actually ''network-bridge'' never creates xenbr0 interface by default, so defaulting bridge to xenbr0 is senseless. Signed-off-by: Marek Marczykowski <marmarek@invisiblethingslab.com> --- tools/libxl/libxl.c | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff
2012 Aug 14
4
[PATCH] libxl: fix usage of backend parameter and run_hotplug_scripts
vif interfaces allows the user to specify the domain that should run the backend (also known as driver domain) using the ''backend'' parameter. This is not compatible with run_hotplug_scripts=1, since libxl can only run the hotplug scripts from the Domain 0. Signed-off-by: Roger Pau Monne <roger.pau@citrix.com> --- docs/misc/xl-network-configuration.markdown | 6 ++++--
2011 Jan 25
2
[PATCH] libxl: fix segfault on device assignement
Fix a xl/libxl segfault when assigning a device to the guest (bug http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1713). Signed-off-by: Gianni Tedesco <gianni.tedesco@citrix.com> Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com> diff -r b05892ff0fce tools/libxl/libxl_pci.c --- a/tools/libxl/libxl_pci.c Tue Jan 25 15:14:52 2011 +0000 +++
2013 Jul 05
3
[PATCH] libxl: Add qxl vga interface support for upstream qemu
Usage: vga="qxl" Reposted for xen 4.4, require SSE support on hvm domU otherwise it works only as a standard vga. Signed-off-by: Fabio Fantoni <fabio.fantoni@m2r.biz> Signed-off-by: Zhou Peng <zpengxen@gmail.com> Acked-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com> Acked-by: Ian Jackson <ian.jackson@eu.citrix.com> --- docs/man/xl.cfg.pod.5 |
2011 Jan 10
3
[PATCH] libxl: implement trigger s3resume
Implement trigger s3resume This is the equivalent of xm trigger s3resume and it is implemented the same way: using an ACPI state change. Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com> diff -r 1ae74f060a39 tools/libxl/libxl.c --- a/tools/libxl/libxl.c Mon Jan 10 10:37:53 2011 +0000 +++ b/tools/libxl/libxl.c Mon Jan 10 10:58:50 2011 +0000 @@ -2668,8 +2668,14 @@ static
2010 Jun 28
8
[PATCH] add xl ocaml bindings
Signed-off-by: Vincent Hanquez <vincent.hanquez@eu.citrix.com> --- tools/ocaml/Makefile | 2 +- tools/ocaml/common.make | 2 +- tools/ocaml/libs/xl/xl.ml | 209 ++++++++++++ tools/ocaml/libs/xl/xl.mli | 209 ++++++++++++ tools/ocaml/libs/xl/xl_stubs.c | 706 ++++++++++++++++++++++++++++++++++++++++ 5 files changed, 1126 insertions(+), 2 deletions(-)
2013 Feb 05
4
[PATCH] tools/libxl: Disable useless empty floppy drive with qemu-xen
tools/libxl: Disable useless empty floppy drive with qemu-xen Signed-off-by: Fabio Fantoni <fabio.fantoni@heliman.it> --- tools/libxl/libxl_dm.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/tools/libxl/libxl_dm.c b/tools/libxl/libxl_dm.c index 51f9914..c265618 100644 --- a/tools/libxl/libxl_dm.c +++ b/tools/libxl/libxl_dm.c @@ -406,6 +406,9 @@ static char **
2011 Feb 01
1
[PATCH] libxl: fix unsafe subtraction in libxl_set_memory_target
The current libxl_set_memory_target function subtracts a negative amount from an uint32_t variable without checking if the operation wraps around. This patch fixes this bug (that I previously believed to be an hypervisor issue): http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1729 Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com> diff -r a69965e61ae9
2011 May 25
3
libxl: setmaxmem functionality?
Hi, the function libxl_domain_setmaxmem in libxl.c doesn''t seem to do anything besides argument checking, or am I overlooking something? Cheers, Markus _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
2009 Nov 04
4
[PATCH server] Update daemons to use new QMF.
This patch updates dbomatic, taskomatic and host-register to use the new C++ wrapped ruby QMF bindings. It also fixes a couple of bugs along the way including the 0 cpu bug for host-register. This is a compilation of work done by myself and Arjun Roy. Signed-off-by: Ian Main <imain at redhat.com> --- src/db-omatic/db_omatic.rb | 111 ++++++-------
2020 Feb 03
0
Re: USB devices with same vendor:product id
Hi Maxime, Quoting Maxime Accadia (2020-02-03 14:20:47) > Hi, > > We have a VM with several USB devices attached. Everything works well, > but sometimes, after a reboot of the host, some usb device get a > different bus/device number and that prevent the reboot of the VM : > ... > Any idea on how to handle this case ? > > We were thinking about using udev, but it
2014 Oct 08
0
Re: sr-vio on intel while virsh chooses rtl8139 for model type
On 10/08/2014 03:35 AM, lejeczek wrote: > > On 03/10/14 17:15, Laine Stump wrote: >> On 10/03/2014 11:38 AM, lejeczek wrote: >>> hi everybody >>> >>> I'd presume virsh makes the best possible choice, right? >>> It is that just seems bit... odd having realtek in guest and Intel's >>> VF on host, no? >> This can safely be ignored
2020 Jun 09
2
LoopStrengthReduction generates false code
Hi. In my backend I get false code after using StrengthLoopReduction. In the generated code the loop index variable is multiplied by 8 (correct, everything is 64 bit aligned) to get an address offset, and the index variable is incremented by 1*8, which is not correct. It should be incremented by 1 only. The factor 8 appears again. I compared the debug output