search for: kazak

Displaying 10 results from an estimated 10 matches for "kazak".

Did you mean: kanak
2012 Mar 10
3
xenpm hypercalls support in latest kernels?
...one know what is the latest version of dom0-kernel, that supports fully xenpm hypercalls? I tried from 3.0 to 3.3 with xen-4.1.3, but none of them has xenpm working. On the other hand native kernel cpufreq is OK with all of them. My CPU is Xeon family 6 on PowerEdge 1950 III box. Regards, Dimitar Kazakov
2012 Mar 10
3
xenpm hypercalls support in latest kernels?
...one know what is the latest version of dom0-kernel, that supports fully xenpm hypercalls? I tried from 3.0 to 3.3 with xen-4.1.3, but none of them has xenpm working. On the other hand native kernel cpufreq is OK with all of them. My CPU is Xeon family 6 on PowerEdge 1950 III box. Regards, Dimitar Kazakov
2013 Oct 09
6
Processed: Re: [HVM} xen_platform_pci=0 doesn't prevent platform device creation and disk and nic take over by PV drivers.
Processing commands for xen@bugs.xenproject.org: > create ^ Created new bug #20 rooted at `<1571692646.20131009000945@eikelenboom.it>'' Title: `Re: [HVM} xen_platform_pci=0 doesn''t prevent platform device creation and disk and nic take over by PV drivers.'' > title it xen_platform_pci=0 doesn''t work with qemu-xen Set title for #20 to
2014 Sep 05
3
Bug#760563: xen-hypervisor-4.4-amd64: Xen >=4.1 not booting on IBM HS20
Package: xen-hypervisor-4.4-amd64 Version: 4.4.0-4 Severity: normal -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash
2013 Nov 05
20
Xen 4.3.1 / Linux 3.12 panic
Hej folks, I''ve been trying to get a new machine up and running with the latest Xen for a while on a Slackware64 (current) machine. After installing Xen from source and building a new kernel with all xen options enabled I haven''t been able to get the machine to behave. The machine is a brand new dual opteron 6212 on a Supermicro H8DGi board with 64G ECC memory. Running a stock
2013 Nov 05
20
Xen 4.3.1 / Linux 3.12 panic
Hej folks, I''ve been trying to get a new machine up and running with the latest Xen for a while on a Slackware64 (current) machine. After installing Xen from source and building a new kernel with all xen options enabled I haven''t been able to get the machine to behave. The machine is a brand new dual opteron 6212 on a Supermicro H8DGi board with 64G ECC memory. Running a stock
2013 Jul 12
14
[PATCH] xen: arm: make zImage the default target which we install
From: Ian Campbell <ian.campbell@citrix.com> The zImage compatible binary is the useful one on real hardware. The relocated ELF thing is only really useful when booting directly on Fast Models. The customary suffix for that case is .axf so provide that as a target. Signed-off-by: Ian Campbell <ian.campbell@citrix.com> Cc: Wookey <wookey@linaro.org> --- xen/arch/arm/Makefile |
2013 Jul 31
29
[PATCH 0/9] tools: remove or disable old/useless/unused/unmainted stuff
depends on "autoconf: regenerate configure scripts with 4.4 version" This series removes some of the really old deadwood from the tools build and makes some other things which are on their way out configurable at build time with a default depending on how far down the slope I judge them to be. * nuke in tree copy of libaio * nuke obsolete tools: xsview, miniterm, lomount & sv *
2012 Apr 05
0
xe vdi-create failure ot local SR type=file and type=ext
Hi, have permanent failure when try to create VDI on local SR type=file or type=ext. On both types it failed with the same error: SR_BACKEND_FAILURE_78 VDI Creation failed [opterr=error 127] I am on Debian box with kernel 3.3.0-rc7, Xen version 4.1.2 (Debian 4.1.2-2.1), Xen-API Version: 1.3.2-4 (Kronos) Is it a bug, or am I missing something? Anybody managed to workaround this problem? Here is
2012 Apr 05
0
Re: [Xen-API] (solved) xe vdi-create failure ot local SR type=file and type=ext
.../lock/sm/4137dc90-4ad7-ecc6-dd2f-6f05ac280fc2/sr On 04/05/2012 01:08 PM, Jonathan Ludlam wrote: > The log snippet doesn''t have the detail in it - have a look in /var/log/SMlog - you might find something more useful in there. > > Jon > > On 5 Apr 2012, at 10:23, Dimitar Kazakov wrote: > >> Hi, >> have permanent failure when try to create VDI on local SR type=file or >> type=ext. On both types it failed with the same error: >> SR_BACKEND_FAILURE_78 >> VDI Creation failed [opterr=error 127] >> >> I am on Debian box with kernel...