similar to: Xen 4.18 Release Schedule?

On 19.11.2015 11:00, Ian Campbell wrote: > On Wed, 2015-11-18 at 23:07 +0000, Thomas Jepp wrote: >> >> [...] >> xc: error: Could not open kernel image '/usr/lib/xen/boot/hvmloader' (2 = No such file or directory): Internal error > > This is the wrong path, in the Debian packages it should be /usr/lib/xen- > 4.6/boot/hvmloader (and this should be arranged by

On Thu, Mar 17, 2016 at 6:58 PM, Martin Michlmayr <tbm at hpe.com> wrote: > Package: xen > Version: 4.6.0-1+nmu2 > Severity: serious > > This package fails to build in unstable: > >> sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux > ... >> mkdir -p compat >> grep -v 'DEFINE_XEN_GUEST_HANDLE(long)' public/grant_table.h | \

On Fri, 2013-08-16 at 15:12 +0100, Ian Campbell wrote: > waldi, > > I reckon you can close at least the following with the new release. > > Ian. > > diff --git a/xen/debian/changelog b/xen/debian/changelog > index e5b25ef..fc3f161 100644 > --- a/xen/debian/changelog > +++ b/xen/debian/changelog > @@ -2,14 +2,15 @@ xen (4.3.0-1) UNRELEASED; urgency=low >

Attached are the most recent boot logs. All tests have been on the same system, an Intel S1200BTL motherboard. I did 2 boots, both with kernel 3.13. First one into xen 4.3 and the 2nd into xen 4.1. The keyboard works on xen 4.1, not on 4.3. Cheers, Mike -------------- next part -------------- An HTML attachment was scrubbed... URL:

Package: xen-utils-4.0 Version: 4.0.1~rc6-1 Severity: important Issue confirmed with xen-utils-4.0 (4.0.1~rc6-1) in Debian Squeeze AMD64. Trace of error while using xm-debian.cfg (attached): [2010-09-02 00:53:21 1407] ERROR (xmlrpclib2:178) Internal error handling xend.domain.create Traceback (most recent call last): File "/usr/lib/xen-4.0/lib/python/xen/util/xmlrpclib2.py",

Package: ftp.debian.org Severity: normal Hello, Please consider removing xen. New xen-3.0 splited packages are upcoming, making this one obsolete. Cheers, -- Julien Danjou // <julien@danjou.info> http://julien.danjou.info // 9A0D 5FD9 EB42 22F6 8974 C95C A462 B51E C2FE E5CD // The more we fly, the more we climb, the more we know that heaven is a lie. -------------- next part

Your message dated Fri, 06 Sep 2013 09:09:48 +0100 with message-id <1378454988.3057.2.camel at dagon.hellion.org.uk> and subject line Re: [Pkg-xen-devel] Bug#710522: Problem found has caused the Debian Bug report #710522, regarding xen-hypervisor-4.1-amd64: Boot hang with Linux 3.2+Xen, works with linux 2.6.32+Xen or 3.2 raw to be marked as done. This means that you claim that the problem

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-2 I have a similar problem. Hardware configuration: - IBM x3850 server - 6GB DDR2 RAM - IBM ServeRAID 8i configured to RAID0 - 2x DualCore Xeon processors with HyperThreading. The following options available for CPU: - HyperThreading - Processor Adjacent Selector Prefetch - Processor Hardware Prefetcher - Processor Execute

I thought people on this list might be interested in the Xen Developer Summit in Edinburgh in October (alongside LinuxCon EU and a bunch of other confs). Lars tells me that they are going to be advertising more widely next week so if you are interested now would be a good time to sign up. Ian. -------- Forwarded Message -------- Dear Community member, the schedule for the Xen Project

Hello, my latest try : X11 starts up and freeze with a black screen. I've updated the nvidia package to 195.36.31-5. ii nvidia-glx 195.36.31-5 ii nvidia-kernel-2.6-xen-amd64 195.36.31+1 ii nvidia-kernel-2.6.32-5-amd64 195.36.31+2+4+2.6.32-24 ii nvidia-kernel-2.6.32-5-xen-am 195.36.31+1+2+2.6.32-21 ii nvidia-kernel-common 20100522+1 ii nvidia-kernel-dkms

After working a few more days with the Xen 3.1 packages build with my patches I've found two bugs. The attached diff contain the fixes - it's a full diff against xen-3.0 rev 391 and xen-common rev 388; they are not yet synced with Guido Trotter's patches for Xen 3.0.4 now in trunk. The bugs fixed: Pygrub did not work due to some well known issues and Python library pathes.

On Tue, 2016-01-19 at 10:39 +0000, Ian Campbell wrote: > On Thu, 2015-11-26 at 15:16 +0000, Ian Campbell wrote: > > anything better would need to be arranged upstream. > > http://xenbits.xen.org/gitweb/?p=xen.git;a=commit;h=de858271c16851d662b26 > 13 > 699401df6ecec8ef8 has now landed upstream, which allows the leaf dir to > be > set at configure time and therefore

Dear Debian-Bugteam Unfortunately this problem still exists. I want to use the server in production environment, but can't by reason of this error. Installed XEN-Versions: ii xen-hypervisor-4.4-amd64 4.4.1-9+deb8u5 amd64 Xen Hypervisor on AMD64 ii xen-linux-system-3.16.0-4-amd64 3.16.7-ckt25-2 amd64

package grub-pc tag 505517 patch upstream thanks Le jeudi 13 novembre 2008 09:36:03, vous avez ?crit?: > Hi, > > Willing to try Xen, I installed "xen-linux-system-2.6.26-1-xen-amd64", > which came with a bunch of packages? > > When I tried to boot the corresponding image, I got an error in Grub. > > AFAIK and from what I gathered on the web, the entry

On Mon, Nov 11, 2024 at 06:03:22PM +0100, Alexandre GRIVEAUX wrote: > Hello, > > Some time ago I created some merge request on salsa for debian-xen: > > https://salsa.debian.org/xen-team/debian-xen/-/merge_requests?scope=all&state=opened These looks like you want to send them upstream instead. -- WBR, wRAR -------------- next part -------------- A non-text attachment was

I think I remember some discussion of something in this area not too long ago on xen-devel. CC-s added. Konrad, do you know of any issues with ucode=scan in 4.4? On Wed, 2015-05-13 at 10:27 +0200, Stephan Seitz wrote: > Package: xen-hypervisor-4.5-amd64 > Version: 4.5.0-1 > Severity: normal > > Dear Maintainer, > > according to the documentation the option ucode=scan

On Sat, 2015-05-09 at 14:07 +0200, Romain Mourier wrote: > On 09/05/2015 13:25, Ian Campbell wrote: > > On Sat, 2015-05-09 at 03:41 +0200, Romain Mourier wrote: > > [...] > >> xen-create-image --hostname=test0 --lvm=raid10 --fs=ext4 > >> --bridge=br-lan --dhcp --dist=jessie > > [...] > >> root at hv0:~# xl create /etc/xen/test0.cfg && xl

Hi, attached (hopefully ;-)) you'll find patches against the current SVN for xen-3.0 and xen-common to support Xen 3.1. Packages I've build with them run fine under Debian Etch for a couple of days now (with the official 2.6.18-4-xen kernel). But I am sure there will be some issues. I did not do any modifications regarding versioning - something that changes with Xen 3.1.

Your message dated Sat, 14 Apr 2012 19:24:04 +0200 with message-id <20120414172403.GA25566 at wavehammer.waldi.eu.org> and subject line meta-packages available has caused the Debian Bug report #606589, regarding xen-linux-system-2.6.32-5-xen-amd64 doesn't upgrade from xen-linux-system-2.6.26-2-xen-amd64 to be marked as done. This means that you claim that the problem has been dealt

On Wed, 2015-09-16 at 01:52 +0200, Arne Klein wrote: > [...] > At the moment when the network in the domU completely stops working, > there is the error message > [2178752.854380] vif vif-33-0 vif33.0: Guest Rx stalled > visible in dmesg in the dom0. This will therefore be a kernel issue not a hypervisor one. It sounds like a backend one given the issue is with both new and