similar to: [xenconsoled] Add syslog (v2)

flight 10458 xen-4.1-testing real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/10458/ Failures and problems with tests :-( Tests which did not succeed and are blocking: test-amd64-i386-xl-credit2 3 host-install(3) broken test-amd64-amd64-xl-sedf 3 host-install(3) broken test-amd64-amd64-xl-winxpsp3 3 host-install(3) broken

flight 12043 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/12043/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-rhel6hvm-amd 7 redhat-install fail REGR. vs. 12031 test-amd64-i386-rhel6hvm-intel 7 redhat-install fail REGR. vs. 12031 test-amd64-i386-xl-winxpsp3-vcpus1 7

Expose more host bridge config space value to make the driver happy for all the different revisions of the device. Signed-off-by: Jean Guyader <jean.guyader@eu.citrix.com> --- hw/pt-graphics.c | 3 +++ 1 files changed, 3 insertions(+), 0 deletions(-) _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

The GGC field have moved from 0x52 to 0x50 on Sandy Bridge. Signed-off-by: Jean Guyader <jean.guyader@eu.citrix.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

The OpRegion shouldn''t be mapped 1:1 because the address in the host can''t be used in the guest directly. This patch traps read and write access to the opregion of the Intel GPU config space (offset 0xfc). To work correctly this patch needs a change in hvmloader. HVMloader will allocate 2 pages for the OpRegion and write this address on the config space of the Intel GPU. Qemu

Grant references for the xenstore and xenconsole shared pages exist, but currently only xenstore uses these references. Change the xenconsole daemon to prefer using the grant reference over map_foreign_range when mapping the shared console ring. This allows xenconsoled to be run in a domain other than dom0 if set up correctly - for libxl, the xenstore path /tool/xenconsoled/domid specifies the

I''m trying to get XCI running on a Lenovo T61 with Intel-based graphics following the steps in the HOWTO in the build directory. I was able to get to the GRUB screen but never get to the "Welcome to XenClient" prompt. When I boot with the full console output, the system hangs indefinitely after "Starting XenConsoled". I''m well trained in the XenServer

Grant references for the xenstore and xenconsole shared pages exist, but currently only xenstore uses these references. Change the xenconsole daemon to prefer using the grant reference over map_foreign_range when mapping the shared console ring. This allows xenconsoled to be run in a domain other than dom0 if set up correctly - for libxl, the xenstore path /tool/xenconsoled/domid specifies the

These values are already defined by the libpci heders in the version 3.1.7. PCI_STATUS_66MHZ PCI_STATUS_RESERVED2 PCI_STATUS_FAST_BACK PCI_MSIX_TABSIZE Signed-off-by: Jean Guyader <jean.guyader@eu.citrix.com> --- hw/pci.h | 6 ++++++ hw/pt-msi.h | 2 ++ 2 files changed, 8 insertions(+), 0 deletions(-) _______________________________________________ Xen-devel mailing list

flight 12090 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/12090/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-rhel6hvm-amd 7 redhat-install fail REGR. vs. 12031 test-amd64-i386-rhel6hvm-intel 7 redhat-install fail REGR. vs. 12031 test-i386-i386-xl-win 7

xenconsoled: do not write the pty under serial in xenstore if xenconsoled is handling a consolepath. The idea is that pv consoles use the "console" prefix in xenstore and emulated serials use the "serial" prefix in xenstore. There is no need to write the pty for a pv console under "serial", considering that xenconsoled is already writing the pty under

The memory permutation cause a slow down in case of a save/restore (bug 1143). It works better when the mixing is done with 2MB chunks. Signed-off-by: Jean Guyader <jean.guyader@eu.citrix.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

ioemu-remote: Enable pci pass-through by default. -- Jean Guyader _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

The OpRegion shouldn''t be mapped 1:1 because the address in the host can''t be used in the guest directly. This patch traps read and write access to the opregion of the Intel GPU config space (offset 0xfc). To work correctly this patch needs a change in hvmloader. HVMloader will allocate 2 pages for the OpRegion and write this address on the config space of the Intel GPU. Qemu

Hi Ian, On Tue, Jan 17, 2017 at 10:58 +0000, Ian Jackson wrote: > Wolodja Wentland writes ("Bug#851654: Prerm maintainer script unconditionally > stops xend/xenconsoled"): > We triggered a xen stop by removing obsolete > xen-utils-4.1 packages while already using xen-utils-4.4. > I think a xenconsoled restart should be harmless, so I think it is > probably right that

Hi everyone, I know this process is started by xend with no command parameters , if I want xenconsoled''s log facility , I must pass the --log parameter . So I change the following line from: os.execvp(''xenconsoled'', [''xenconsoled'']) to os.execvp(''xenconsoled'', [''xenconsoled'',''--log=all'']) but this

Hello, Is there any documention on "xenconsoled" ? (I have installed xen from source) /usr/sbin/xenconsoled --help Usage: /usr/sbin/xenconsoled [-h] [-V] [-v] [-i] What do the different options mean? Should xenconsoled always be running, even when no "xm console" commands are active? I killed it in error, but now need to know how to start it with it''s default

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: wishlist Hi, this morning I spend some time to find out how to log console output of Xen guest domains into a file in dom0. I ended up using a quick 'n dirty solution: mario:/usr/lib/xen-3.2-1/bin 0-# diff -u xend.orig xend --- xend.orig 2009-03-02 16:49:49.000000000 +0100 +++ xend 2009-03-02 16:16:03.000000000 +0100 @@ -100,7 +100,8 @@

Hi, I am trying to make the vt-d and pci pass-through work and I have some problems. I just try to give a NIC to an HVM guest. When I create the vm the hypervisor goes to an infinite loop, it displays in loop the message enclosed (console_on_xm_create). I use xen x86_64, debian etch dom0 with linux-2.6.18.8-xen 32. The hvm guest is a debian etch 64. Cheers, -- Jean Guyader

# HG changeset patch # User Olaf Hering <olaf@aepfle.de> # Date 1336153082 -7200 # Node ID 9a430b7e2df2893f7f4f75d10e66d52bdffa7efa # Parent 113fd57259b91af06a5352404dd94b484a98d2bc tools/hotplug: remove 4 from default runlevel in xen-watchdog, xend and xendomains Similar to what changeset 24847:0900b1c905f1 does in xencommons, remove runlevel 4 from the other runlevel scripts. LSB defines