On 28.09.2017 16:03, Konrad Rzeszutek Wilk wrote:
> On Thu, Sep 28, 2017 at 02:45:38PM +, Hongjiang Zhang wrote:
(XEN) ACPI Error (tbxfroot-0218): A valid RSDP was not found
[20070126]
>>>
>>> Uuh, that is rather bad, I guess.
>
> I am going to assume this is due to not having:
>
>
On 13.03.2017 11:29, Andrew Cooper wrote:
> On 13/03/17 09:24, Jan Beulich wrote:
> On 10.03.17 at 18:22, wrote:
>>> On 08.03.2017 13:54, Jan Beulich wrote:
All,
I am pleased to announce the release of Xen 4.6.5. This is
available immediately
On 08.03.2017 13:54, Jan Beulich wrote:
> All,
>
> I am pleased to announce the release of Xen 4.6.5. This is
> available immediately from its git repository
> http://xenbits.xen.org/gitweb/?p=xen.git;a=shortlog;h=refs/heads/stable-4.6
> (tag RELEASE-4.6.5) or from the XenProject download page
>
On 26.08.2016 13:53, Juergen Gross wrote:
> On 26/08/16 12:52, Stefan Bader wrote:
>> On 25.08.2016 19:31, Juergen Gross wrote:
>>> On 25/08/16 17:48, Stefan Bader wrote:
>>>> When I try to save a PV guest with 4G of memory using xen-4.7 I get the
>>>> f
On 25.08.2016 19:31, Juergen Gross wrote:
> On 25/08/16 17:48, Stefan Bader wrote:
>> When I try to save a PV guest with 4G of memory using xen-4.7 I get the
>> following error:
>>
>> II: Guest memory 4096 MB
>> II: Saving guest state to file...
>> Saving t
Sorry for the incomplete subject. Got interrupted while writing the email and
then forgot to complete it... :/
On 25.08.2016 17:48, Stefan Bader wrote:
> When I try to save a PV guest with 4G of memory using xen-4.7 I get the
> following error:
>
> II: Guest memory 4096 MB
> I
When I try to save a PV guest with 4G of memory using xen-4.7 I get the
following error:
II: Guest memory 4096 MB
II: Saving guest state to file...
Saving to /tmp/pvguest.save new xl format (info 0x3/0x0/1131)
xc: info: Saving domain 23, type x86 PV
xc: error: Bad mfn in p2m_frame_list[0]:
be making a proper fix
>>> in-tree (since it will never be released).
>>
>> I know that 4.1 is EOL.
>> I'm aware of Ubuntu still having xen-4.1 in one of their LTS versions
>> (Precise) and its also in Debian-oldstable, which a lot people (us
>> included) still
On 02.05.2016 16:24, Stefan Bader wrote:
> On 02.05.2016 13:41, Juergen Gross wrote:
>> On 02/05/16 12:47, Stefan Bader wrote:
>>> I recently tried to boot 32bit dom0 on 64bit Xen host which I configured to
>>> run
>>> with a limited, fix amount of memo
I recently tried to boot 32bit dom0 on 64bit Xen host which I configured to run
with a limited, fix amount of memory for dom0. It seems that somewhere between
kernel versions 3.19 and 4.2 (sorry that is still a wide range) the Linux kernel
would report bad page flags for a range of pages (which
On 26.01.2016 11:58, Stefan Bader wrote:
> Hi,
>
> while playing around with xen-4.6 I stumbled over an odd problem and am
> wondering whether anybody has seen the same. A method to relatively quickly
> reproduce this for me seems to:
>
> - Start one domU (PV or HVM do
On 28.01.2016 10:39, Ian Campbell wrote:
> On Thu, 2016-01-28 at 09:50 +0100, Stefan Bader wrote:
>> On 26.01.2016 11:58, Stefan Bader wrote:
>>> Hi,
>>>
>>> while playing around with xen-4.6 I stumbled over an odd problem and am
>>> wonderin
Hi,
while playing around with xen-4.6 I stumbled over an odd problem and am
wondering whether anybody has seen the same. A method to relatively quickly
reproduce this for me seems to:
- Start one domU (PV or HVM does not seem to matter)
- Repeatedly call xenstore-ls a few times
I think I never
On 23.11.2015 08:51, Jan Beulich wrote:
On 23.11.15 at 08:37, wrote:
>> Actually there's no problem with ICEBP - just like INTnn it isn't itself
>> interceptable (and the injection of vector 0x01 from the x86
>> emulator path can't fully distinguish between ICEBP and INT
Hi Jan, hi Andrew,
I am currently trying to backport the changes of XSA156 back to Xen-4.1.x and I
am struggling with the VMX side. I did see the backports made for 4.2 and 3.4 on
the security mailing list but I am not sure the 3.4 backport is not having the
same issues (or similar ones).
On 20.11.2015 17:10, Stefan Bader wrote:
> On 20.11.2015 16:59, Jan Beulich wrote:
>>>>> On 20.11.15 at 16:03, <stefan.ba...@canonical.com> wrote:
>>> I am currently trying to backport the changes of XSA156 back to Xen-4.1.x
>>> and I
>>> am st
On 20.11.2015 16:59, Jan Beulich wrote:
On 20.11.15 at 16:03, wrote:
>> I am currently trying to backport the changes of XSA156 back to Xen-4.1.x
>> and I
>> am struggling with the VMX side. I did see the backports made for 4.2 and
>> 3.4 on
>> the security
On 20.11.2015 17:54, Jan Beulich wrote:
On 20.11.15 at 17:15, wrote:
>> So this is a quick hack I just tried and that keeps the HVM alive:
>>
>> @@ -1294,7 +1288,6 @@ void vmx_inject_hw_exception(int trap, i
>> switch ( trap )
>> {
>> case
On 02.06.2015 09:40, Sanjeev Pandita wrote:
All,
I am pretty new to xen . I am trying to boot DOMU with qemu qcow AARCH64
Ubuntu 15.04 disk on Xen but I am getting the errors which link to
/usr/local/lib/xen/bin/qemu-system-i386.
Since I am working on aarch64 system the
On 02.06.2015 12:35, Stefano Stabellini wrote:
On Tue, 2 Jun 2015, Stefano Stabellini wrote:
On Tue, 2 Jun 2015, Stefan Bader wrote:
On 02.06.2015 09:40, Sanjeev Pandita wrote:
All,
I am pretty new to xen . I am trying to boot DOMU with qemu qcow AARCH64
Ubuntu 15.04 disk on Xen but I am
On 02.06.2015 14:09, Sanjeev Pandita wrote:
Hi,
-Original Message-
From: Stefan Bader [mailto:stefan.ba...@canonical.com]
Sent: Tuesday, June 02, 2015 1:52 PM
To: Sanjeev Pandita; xen-devel@lists.xen.org
Cc: ian.campb...@citrix.com; Pranavkumar Sawargaonkar;
stefano.stabell
After being asked about this I started to play around with Xen-4.4.1/4.5
together with HVM Linux guest running 3.13/3.16/3.19. With mixed success.
Usually rather failing.
From a bit of research most activity to enable things were back in 2011. There
was a bit of a throwback around Linux 3.2[1]
On 05.02.2015 15:33, Stefan Bader wrote:
While experimenting/testing various kernel versions I discovered that trying
to
boot a Haswell based hosts will always crash when booting as Xen dom0
(Xen-4.4.1). The same crash happens since v3.19-rc1 and still does happen with
v3.19-rc7. A bare
...@google.com
Link: http://lkml.kernel.org/r/1421720467-7709-2-git-send-email-jiang@linux.intel.com
Signed-off-by: Thomas Gleixner t...@linutronix.de
Signed-off-by: Stefan Bader stefan.ba...@canonical.com
---
arch/x86/kernel/acpi/boot.c | 23 +++---
arch/x86/pci/xen.c | 47
On 09.02.2015 14:07, Stefan Bader wrote:
On 05.02.2015 20:36, Konrad Rzeszutek Wilk wrote:
On Thu, Feb 05, 2015 at 03:33:02PM +0100, Stefan Bader wrote:
While experimenting/testing various kernel versions I discovered that
trying to
boot a Haswell based hosts will always crash when booting
On 05.02.2015 20:36, Konrad Rzeszutek Wilk wrote:
On Thu, Feb 05, 2015 at 03:33:02PM +0100, Stefan Bader wrote:
While experimenting/testing various kernel versions I discovered that trying
to
boot a Haswell based hosts will always crash when booting as Xen dom0
(Xen-4.4.1). The same crash
While experimenting/testing various kernel versions I discovered that trying to
boot a Haswell based hosts will always crash when booting as Xen dom0
(Xen-4.4.1). The same crash happens since v3.19-rc1 and still does happen with
v3.19-rc7. A bare metal boot is having no issues and also an Opteron
Hey David,
after just being in that pain, I thought I might as well give a summary to
you/the list. Maybe helpful to not forget which piece should go to which
stable...
So:
v3.16...v3.17.8: Somewhen in between those, the acpi irq seems to have broken.
I have not yet verified
On 08.12.2014 12:11, David Vrabel wrote:
On 08/12/14 10:19, Luis Henriques wrote:
On Mon, Dec 01, 2014 at 09:55:24AM +0100, Stefan Bader wrote:
On 11.08.2014 19:32, Zoltan Kiss wrote:
There is a long known problem with the netfront/netback interface: if the
guest
tries to send a packet
On 08.12.2014 12:31, David Vrabel wrote:
On 08/12/14 11:21, Stefan Bader wrote:
On 08.12.2014 12:11, David Vrabel wrote:
On 08/12/14 10:19, Luis Henriques wrote:
On Mon, Dec 01, 2014 at 09:55:24AM +0100, Stefan Bader wrote:
On 11.08.2014 19:32, Zoltan Kiss wrote:
There is a long known
On 11.08.2014 19:32, Zoltan Kiss wrote:
There is a long known problem with the netfront/netback interface: if the
guest
tries to send a packet which constitues more than MAX_SKB_FRAGS + 1 ring
slots,
it gets dropped. The reason is that netback maps these slots to a frag in the
frags array,
31 matches
Mail list logo