On Tue, Oct 25, 2016 at 07:25:06PM +0200, Sander Eikelenboom wrote:
> On 2016-10-25 16:49, Wei Liu wrote:
> >On Tue, Oct 25, 2016 at 01:37:45PM +0200, Sander Eikelenboom wrote:
> >>
> >>Tuesday, October 25, 2016, 1:24:12 PM, you wrote:
> >>
> >>> On Tue, Oct 18, 2016 at 01:48:23PM +0100, Wei Liu
On 2016-10-25 16:49, Wei Liu wrote:
On Tue, Oct 25, 2016 at 01:37:45PM +0200, Sander Eikelenboom wrote:
Tuesday, October 25, 2016, 1:24:12 PM, you wrote:
> On Tue, Oct 18, 2016 at 01:48:23PM +0100, Wei Liu wrote:
>> On Mon, Oct 17, 2016 at 05:28:17PM +0200, Sander Eikelenboom wrote:
>> >
On Tue, Oct 25, 2016 at 03:49:59PM +0100, Wei Liu wrote:
> On Tue, Oct 25, 2016 at 01:37:45PM +0200, Sander Eikelenboom wrote:
> >
> > Tuesday, October 25, 2016, 1:24:12 PM, you wrote:
> >
> > > On Tue, Oct 18, 2016 at 01:48:23PM +0100, Wei Liu wrote:
> > >> On Mon, Oct 17, 2016 at 05:28:17PM
On Tue, Oct 25, 2016 at 01:37:45PM +0200, Sander Eikelenboom wrote:
>
> Tuesday, October 25, 2016, 1:24:12 PM, you wrote:
>
> > On Tue, Oct 18, 2016 at 01:48:23PM +0100, Wei Liu wrote:
> >> On Mon, Oct 17, 2016 at 05:28:17PM +0200, Sander Eikelenboom wrote:
> >> > Thursday, October 13, 2016,
Tuesday, October 25, 2016, 1:24:12 PM, you wrote:
> On Tue, Oct 18, 2016 at 01:48:23PM +0100, Wei Liu wrote:
>> On Mon, Oct 17, 2016 at 05:28:17PM +0200, Sander Eikelenboom wrote:
>> > Thursday, October 13, 2016, 4:43:31 PM, you wrote:
>> >
>> > > Hi Jan / Wei,
>> >
>> > > Took a while before
On Tue, Oct 18, 2016 at 01:48:23PM +0100, Wei Liu wrote:
> On Mon, Oct 17, 2016 at 05:28:17PM +0200, Sander Eikelenboom wrote:
> > Thursday, October 13, 2016, 4:43:31 PM, you wrote:
> >
> > > Hi Jan / Wei,
> >
> > > Took a while before i had the chance to fiddle some more to find the
> > >
Den 18. okt. 2016 14:48, skrev Wei Liu:
> On Mon, Oct 17, 2016 at 05:28:17PM +0200, Sander Eikelenboom wrote:
>> Thursday, October 13, 2016, 4:43:31 PM, you wrote:
>>
>>> Hi Jan / Wei,
>>> Took a while before i had the chance to fiddle some more to find the actual
>>> culprit.
>>> After analyzing
On Mon, Oct 17, 2016 at 05:28:17PM +0200, Sander Eikelenboom wrote:
> Thursday, October 13, 2016, 4:43:31 PM, you wrote:
>
> > Hi Jan / Wei,
>
> > Took a while before i had the chance to fiddle some more to find the actual
> > culprit.
> > After analyzing the output of xl -v create somewhat
Thursday, October 13, 2016, 4:43:31 PM, you wrote:
> Hi Jan / Wei,
> Took a while before i had the chance to fiddle some more to find the actual
> culprit.
> After analyzing the output of xl -v create somewhat more i came to the
> insight it was probably Qemu and not Xen causing the fault.
Hi Jan / Wei,
Took a while before i had the chance to fiddle some more to find the actual
culprit.
After analyzing the output of xl -v create somewhat more i came to the
insight it was probably Qemu and not Xen causing the fault.
As a test I just used a qemu-xen binary build with xen-4.6.0
On 2016-09-05 13:43, Jan Beulich wrote:
On 05.09.16 at 13:19, wrote:
On 2016-09-05 12:25, Jan Beulich wrote:
Anyway - with you quite clearly having used HAP before, I can't
see how this commit would matter for you at all. In case you want
to double check you could try
>>> On 05.09.16 at 13:19, wrote:
> On 2016-09-05 12:25, Jan Beulich wrote:
>> Anyway - with you quite clearly having used HAP before, I can't
>> see how this commit would matter for you at all. In case you want
>> to double check you could try with a hypervisor built without
On 2016-09-05 12:25, Jan Beulich wrote:
On 05.09.16 at 12:02, wrote:
On 2016-09-05 11:46, Jan Beulich wrote:
On 05.09.16 at 11:20, wrote:
Hmm it seems my thread was kind of hijacked and i was dropped from
the
CC.
I had some time and bisected the
>>> On 05.09.16 at 12:02, wrote:
> On 2016-09-05 11:46, Jan Beulich wrote:
> On 05.09.16 at 11:20, wrote:
>>> Hmm it seems my thread was kind of hijacked and i was dropped from the
>>> CC.
>>>
>>> I had some time and bisected the issue and it
On 2016-09-05 11:46, Jan Beulich wrote:
On 05.09.16 at 11:20, wrote:
Hmm it seems my thread was kind of hijacked and i was dropped from the
CC.
I had some time and bisected the issue and it resulted in:
5a3ce8f85e7e7bdd339d259daa19f6bc5cb4735f is the first bad commit
>>> On 05.09.16 at 11:20, wrote:
> Hmm it seems my thread was kind of hijacked and i was dropped from the
> CC.
>
> I had some time and bisected the issue and it resulted in:
>
> 5a3ce8f85e7e7bdd339d259daa19f6bc5cb4735f is the first bad commit
> commit
On Mon, Sep 05, 2016 at 11:20:30AM +0200, li...@eikelenboom.it wrote:
> On 2016-08-25 23:18, li...@eikelenboom.it wrote:
> >On 2016-08-25 22:34, Doug Goldstein wrote:
> >>On 8/25/16 4:21 PM, li...@eikelenboom.it wrote:
> >>>Today i tried to switch some of my HVM guests (qemu-xen) from booting
>
On 2016-08-25 23:18, li...@eikelenboom.it wrote:
On 2016-08-25 22:34, Doug Goldstein wrote:
On 8/25/16 4:21 PM, li...@eikelenboom.it wrote:
Today i tried to switch some of my HVM guests (qemu-xen) from booting
of
a kernel *inside* the guest, to a dom0 supplied kernel, which is
described as
Could you please use xl -vvv create to create the guest and collect the
output?
Wei.
___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
Den 25. aug. 2016 23:18, skrev li...@eikelenboom.it:
> On 2016-08-25 22:34, Doug Goldstein wrote:
>> On 8/25/16 4:21 PM, li...@eikelenboom.it wrote:
>>> Today i tried to switch some of my HVM guests (qemu-xen) from
>>> booting of
>>> a kernel *inside* the guest, to a dom0 supplied kernel, which is
On 2016-08-25 22:34, Doug Goldstein wrote:
On 8/25/16 4:21 PM, li...@eikelenboom.it wrote:
Today i tried to switch some of my HVM guests (qemu-xen) from booting
of
a kernel *inside* the guest, to a dom0 supplied kernel, which is
described as "Direct Kernel Boot" here:
On 8/25/16 4:21 PM, li...@eikelenboom.it wrote:
> Today i tried to switch some of my HVM guests (qemu-xen) from booting of
> a kernel *inside* the guest, to a dom0 supplied kernel, which is
> described as "Direct Kernel Boot" here:
> https://xenbits.xen.org/docs/unstable/man/xl.cfg.5.html :
>
>
Today i tried to switch some of my HVM guests (qemu-xen) from booting of
a kernel *inside* the guest, to a dom0 supplied kernel, which is
described as "Direct Kernel Boot" here:
https://xenbits.xen.org/docs/unstable/man/xl.cfg.5.html :
Direct Kernel Boot
Direct kernel boot allows
23 matches
Mail list logo