Re: Fwd: Re: Unable to boot with the dom0 xen kernel
On 14/04/2015 11:51, Roger Pau Monné wrote: > Thanks, could you add ioapic_ack=old to your xen_cmdline and try again? Adding ioapic_ack=old seems to prevent the problem with the interruptions. Anything else you want me to test? Best ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
Re: Fwd: Re: Unable to boot with the dom0 xen kernel
Hello, Re-adding freebsd-xen ;). El 14/04/15 a les 11.33, Gustau Pérez ha escrit: > > > On 14/04/2015 10:36, Roger Pau Monné wrote: >>> >>>Hello, >>> >>>I've tried the IN/OUT patch (I haven't tested the acpi shutdown patch >>> yet) but the problem remains the same. In the serial console I can see >>> different interruption problems (USB_ERR_TIMEOUTS, mpt0, bce0, etc). >> Can you paste the full boot log (including Xen and FreeBSD)? Also, can >> you switch to the Xen console when all those time outs start happening >> and paste the output of the 'i' debug key? >> > >Sure, it is here: > > http://dpaste.com/30VTA0B > >sorry about the mangled parts, it happens when capturing from the > serial console. It is the boot of a patched kernel in verbose mode, at > the end you'll find the interruption information provided by xen itself. Thanks, could you add ioapic_ack=old to your xen_cmdline and try again? I have a similar system (two IO-APICs, Nehalem series), and without this option I also see interrupt timeouts (although mine only happen on heavy load). Roger. ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
Fwd: Re: Fwd: Re: Unable to boot with the dom0 xen kernel
On 14/04/2015 10:36, Roger Pau Monné wrote: >> >>Hello, >> >>I've tried the IN/OUT patch (I haven't tested the acpi shutdown patch >> yet) but the problem remains the same. In the serial console I can see >> different interruption problems (USB_ERR_TIMEOUTS, mpt0, bce0, etc). > Can you paste the full boot log (including Xen and FreeBSD)? Also, can > you switch to the Xen console when all those time outs start happening > and paste the output of the 'i' debug key? > Sure, it is here: http://dpaste.com/30VTA0B sorry about the mangled parts, it happens when capturing from the serial console. It is the boot of a patched kernel in verbose mode, at the end you'll find the interruption information provided by xen itself. Best, G. ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
Re: Fwd: Re: Unable to boot with the dom0 xen kernel
Hello, El 14/04/15 a les 9.40, Gustau Pérez ha escrit: > > >> The interrupt timeouts are probably related to the IOMMU errata, the >> ACPI poweroff problem is because we need to negotiate the shutdown with >> the hypervisor, which we currently don't do. I have a very hacky patch >> for FreeBSD that should fix it, but I haven't found time to properly >> integrate it: >> >> http://xenbits.xen.org/gitweb/?p=people/royger/freebsd.git;a=patch;h=612509976d5d2af7633547e0279aae08a6508d7c >> >> Leaving this aside, I have a patch for Xen I would like you to try on >> this box, it *should* fix the INS/OUTS problem (not the poweroff). I've >> pushed it to a branch on my git repo, you can find it at: >> >> http://xenbits.xen.org/gitweb/?p=people/royger/xen.git;a=shortlog;h=refs/heads/pvh_io_ports.v1 >> >> > >Hello, > >I've tried the IN/OUT patch (I haven't tested the acpi shutdown patch > yet) but the problem remains the same. In the serial console I can see > different interruption problems (USB_ERR_TIMEOUTS, mpt0, bce0, etc). Can you paste the full boot log (including Xen and FreeBSD)? Also, can you switch to the Xen console when all those time outs start happening and paste the output of the 'i' debug key? Thanks, Roger. ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
Re: Fwd: Re: Unable to boot with the dom0 xen kernel
> The interrupt timeouts are probably related to the IOMMU errata, the > ACPI poweroff problem is because we need to negotiate the shutdown with > the hypervisor, which we currently don't do. I have a very hacky patch > for FreeBSD that should fix it, but I haven't found time to properly > integrate it: > > http://xenbits.xen.org/gitweb/?p=people/royger/freebsd.git;a=patch;h=612509976d5d2af7633547e0279aae08a6508d7c > > Leaving this aside, I have a patch for Xen I would like you to try on > this box, it *should* fix the INS/OUTS problem (not the poweroff). I've > pushed it to a branch on my git repo, you can find it at: > > http://xenbits.xen.org/gitweb/?p=people/royger/xen.git;a=shortlog;h=refs/heads/pvh_io_ports.v1 > > Hello, I've tried the IN/OUT patch (I haven't tested the acpi shutdown patch yet) but the problem remains the same. In the serial console I can see different interruption problems (USB_ERR_TIMEOUTS, mpt0, bce0, etc). Best, G. ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
Re: Fwd: Re: Unable to boot with the dom0 xen kernel
> The interrupt timeouts are probably related to the IOMMU errata, the > ACPI poweroff problem is because we need to negotiate the shutdown with > the hypervisor, which we currently don't do. I have a very hacky patch > for FreeBSD that should fix it, but I haven't found time to properly > integrate it: > > http://xenbits.xen.org/gitweb/?p=people/royger/freebsd.git;a=patch;h=612509976d5d2af7633547e0279aae08a6508d7c > > Leaving this aside, I have a patch for Xen I would like you to try on > this box, it *should* fix the INS/OUTS problem (not the poweroff). I've > pushed it to a branch on my git repo, you can find it at: > > http://xenbits.xen.org/gitweb/?p=people/royger/xen.git;a=shortlog;h=refs/heads/pvh_io_ports.v1 > > or > > git://xenbits.xen.org/people/royger/xen.git branch pvh_io_ports.v1 > > If you still get the timeouts please post the full boot log and we can > try to figure out if there's any workaround. > Hi Roger, tomorrow I'll try to give them a try with that box, I have it busy building packages. If not then friday I'll let you know. Thank you, G. -- --- Prou top-posting :http://ca.wikipedia.org/wiki/Top-posting Stop top-posting :http://en.wikipedia.org/wiki/Posting_style O O O Gustau Pérez i Querol O O O Unitat de Gestió dels departaments O O O Matemàtica Aplicada IV i Enginyeria Telemàtica Universitat Politècnica de Catalunya Edifici C3 - Despatx S101-B UPC Campus Nord UPC C/ Jordi Girona, 1-3 08034 - Barcelona ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
Re: Fwd: Re: Unable to boot with the dom0 xen kernel
Hello, El 07/04/15 a les 17.51, Gustau Pérez ha escrit: >Removing the assert prevents the panic and thus the machine boots. > However I believe the assert was there for a reason, wouldn't it break > somewhere else? > >OTOH, I see the machine has problems handling the interruption from > all devices. I see watchdog timeouts from the mpt controller, usb, and > network. Even shutting down the machine via ACPI fails (I had to unplug > the two PS to shut it down). Probably related with the iommu=no-intremap > in the xen_cmdline, isn't it? The interrupt timeouts are probably related to the IOMMU errata, the ACPI poweroff problem is because we need to negotiate the shutdown with the hypervisor, which we currently don't do. I have a very hacky patch for FreeBSD that should fix it, but I haven't found time to properly integrate it: http://xenbits.xen.org/gitweb/?p=people/royger/freebsd.git;a=patch;h=612509976d5d2af7633547e0279aae08a6508d7c Leaving this aside, I have a patch for Xen I would like you to try on this box, it *should* fix the INS/OUTS problem (not the poweroff). I've pushed it to a branch on my git repo, you can find it at: http://xenbits.xen.org/gitweb/?p=people/royger/xen.git;a=shortlog;h=refs/heads/pvh_io_ports.v1 or git://xenbits.xen.org/people/royger/xen.git branch pvh_io_ports.v1 If you still get the timeouts please post the full boot log and we can try to figure out if there's any workaround. Thanks, Roger. ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
Re: Fwd: Re: Unable to boot with the dom0 xen kernel
On 07/04/2015 16:46, Roger Pau Monné wrote:
>
> Ah, I've forgot about the ASSERT in handle_mmio. It looks like at least
> one of the drivers for your hardware uses the INS or OUTS instruction
> which is not yet correctly handled by PVH guests. You can try the
> following patch, which removes the assert you hit before (again
> this is for the Xen source tree):
>
> diff --git a/xen/arch/x86/hvm/io.c b/xen/arch/x86/hvm/io.c
> index 68fb890..b2f1ce4 100644
> --- a/xen/arch/x86/hvm/io.c
> +++ b/xen/arch/x86/hvm/io.c
> @@ -84,8 +84,6 @@ int handle_mmio(void)
> struct hvm_vcpu_io *vio = &curr->arch.hvm_vcpu.hvm_io;
> int rc;
>
> -ASSERT(!is_pvh_vcpu(curr));
> -
> hvm_emulate_prepare(&ctxt, guest_cpu_user_regs());
>
> rc = hvm_emulate_one(&ctxt);
> diff --git a/xen/arch/x86/hvm/vmx/vmx.c b/xen/arch/x86/hvm/vmx/vmx.c
> index e1c55ce..fc3c45b 100644
> --- a/xen/arch/x86/hvm/vmx/vmx.c
> +++ b/xen/arch/x86/hvm/vmx/vmx.c
> @@ -3102,8 +3102,7 @@ void vmx_vmexit_handler(struct cpu_user_regs *regs)
> if ( exit_qualification & 0x10 )
> {
> /* INS, OUTS */
> -if ( unlikely(is_pvh_vcpu(v)) /* PVH fixme */ ||
> - !handle_mmio() )
> +if ( !handle_mmio() )
> hvm_inject_hw_exception(TRAP_gp_fault, 0);
> }
> else
>
Removing the assert prevents the panic and thus the machine boots.
However I believe the assert was there for a reason, wouldn't it break
somewhere else?
OTOH, I see the machine has problems handling the interruption from
all devices. I see watchdog timeouts from the mpt controller, usb, and
network. Even shutting down the machine via ACPI fails (I had to unplug
the two PS to shut it down). Probably related with the iommu=no-intremap
in the xen_cmdline, isn't it?
Btw, the laptop dom0 domain now boots just fine with xen. It was a
pekbac (sorry for the noise on that).
> The Xen console is only available over the serial, pressing Ctrl-A
> tree times should bring it up (the keystroke sequence is the same
> that's used to change windows on screen).
Oh, the problem was minicom in the middle. With cu it does work.
Thank you.
Gustau
--
---
Prou top-posting :http://ca.wikipedia.org/wiki/Top-posting
Stop top-posting :http://en.wikipedia.org/wiki/Posting_style
O O O Gustau Pérez i Querol
O O O Unitat de Gestió dels departaments
O O O Matemàtica Aplicada IV i Enginyeria Telemàtica
Universitat Politècnica de Catalunya
Edifici C3 - Despatx S101-B
UPC Campus Nord UPC
C/ Jordi Girona, 1-3
08034 - Barcelona
___
freebsd-xen@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
Re: Fwd: Re: Unable to boot with the dom0 xen kernel
Hello,
El 07/04/15 a les 15.03, Gustau Pérez ha escrit:
>Hi there,
>> can you apply the
>> following patch to the Xen source tree and recompile the Xen kernel,
>> (there's no need to recompile the tools):
>>
>> diff --git a/xen/arch/x86/hvm/vmx/vmx.c b/xen/arch/x86/hvm/vmx/vmx.c
>> index e1c55ce..fc3c45b 100644
>> --- a/xen/arch/x86/hvm/vmx/vmx.c
>> +++ b/xen/arch/x86/hvm/vmx/vmx.c
>> @@ -3102,8 +3102,7 @@ void vmx_vmexit_handler(struct cpu_user_regs *regs)
>> if ( exit_qualification & 0x10 )
>> {
>> /* INS, OUTS */
>> -if ( unlikely(is_pvh_vcpu(v)) /* PVH fixme */ ||
>> - !handle_mmio() )
>> +if ( !handle_mmio() )
>> hvm_inject_hw_exception(TRAP_gp_fault, 0);
>> }
>> else
>>
>
>Sure. I applied the patch, recompiled the xen kernel, and copied it
> to /boot (as usual). I also raised the iommu debug level. Now the crash
> is different:
>
>http://dpaste.com/1H4XBY5
Ah, I've forgot about the ASSERT in handle_mmio. It looks like at least
one of the drivers for your hardware uses the INS or OUTS instruction
which is not yet correctly handled by PVH guests. You can try the
following patch, which removes the assert you hit before (again
this is for the Xen source tree):
diff --git a/xen/arch/x86/hvm/io.c b/xen/arch/x86/hvm/io.c
index 68fb890..b2f1ce4 100644
--- a/xen/arch/x86/hvm/io.c
+++ b/xen/arch/x86/hvm/io.c
@@ -84,8 +84,6 @@ int handle_mmio(void)
struct hvm_vcpu_io *vio = &curr->arch.hvm_vcpu.hvm_io;
int rc;
-ASSERT(!is_pvh_vcpu(curr));
-
hvm_emulate_prepare(&ctxt, guest_cpu_user_regs());
rc = hvm_emulate_one(&ctxt);
diff --git a/xen/arch/x86/hvm/vmx/vmx.c b/xen/arch/x86/hvm/vmx/vmx.c
index e1c55ce..fc3c45b 100644
--- a/xen/arch/x86/hvm/vmx/vmx.c
+++ b/xen/arch/x86/hvm/vmx/vmx.c
@@ -3102,8 +3102,7 @@ void vmx_vmexit_handler(struct cpu_user_regs *regs)
if ( exit_qualification & 0x10 )
{
/* INS, OUTS */
-if ( unlikely(is_pvh_vcpu(v)) /* PVH fixme */ ||
- !handle_mmio() )
+if ( !handle_mmio() )
hvm_inject_hw_exception(TRAP_gp_fault, 0);
}
else
>
> I don't if it has to do with the dom0_max_vcpus xen_cmdline option.
> I lowered it to 2 (the machine has 1 package(s) x 4 core(s) x 2 SMT
> threads) just in case.
No, I don't think it's related to the dom0_max_vcpus option.
>> .
>>
>> Yes, this is possible from the serial console. Press Ctrl-A tree times
>> (to switch to the Xen console), and then 'R' (note the caps).
>>
>PS: Thanks. I'm unable to bring in the xen console, perhaps because
> I'm using the serial console, I don't know. I'll try the physical
> console, just in case.
The Xen console is only available over the serial, pressing Ctrl-A tree
times should bring it up (the keystroke sequence is the same that's
used to change windows on screen).
Roger.
___
freebsd-xen@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
Fwd: Re: Unable to boot with the dom0 xen kernel
Resending it to the mailing list, just in case.
Hi there,
> can you apply the
> following patch to the Xen source tree and recompile the Xen kernel,
> (there's no need to recompile the tools):
>
> diff --git a/xen/arch/x86/hvm/vmx/vmx.c b/xen/arch/x86/hvm/vmx/vmx.c
> index e1c55ce..fc3c45b 100644
> --- a/xen/arch/x86/hvm/vmx/vmx.c
> +++ b/xen/arch/x86/hvm/vmx/vmx.c
> @@ -3102,8 +3102,7 @@ void vmx_vmexit_handler(struct cpu_user_regs *regs)
> if ( exit_qualification & 0x10 )
> {
> /* INS, OUTS */
> -if ( unlikely(is_pvh_vcpu(v)) /* PVH fixme */ ||
> - !handle_mmio() )
> +if ( !handle_mmio() )
> hvm_inject_hw_exception(TRAP_gp_fault, 0);
> }
> else
>
Sure. I applied the patch, recompiled the xen kernel, and copied it
to /boot (as usual). I also raised the iommu debug level. Now the crash
is different:
http://dpaste.com/1H4XBY5
I don't if it has to do with the dom0_max_vcpus xen_cmdline option.
I lowered it to 2 (the machine has 1 package(s) x 4 core(s) x 2 SMT
threads) just in case.
Any other thing you'd like me to check, let me know.
Best,
Gustau
> .
>
> Yes, this is possible from the serial console. Press Ctrl-A tree times
> (to switch to the Xen console), and then 'R' (note the caps).
>
PS: Thanks. I'm unable to bring in the xen console, perhaps because
I'm using the serial console, I don't know. I'll try the physical
console, just in case.
--
---
Prou top-posting :http://ca.wikipedia.org/wiki/Top-posting
Stop top-posting :http://en.wikipedia.org/wiki/Posting_style
O O O Gustau Pérez i Querol
O O O Unitat de Gestió dels departaments
O O O Matemàtica Aplicada IV i Enginyeria Telemàtica
Universitat Politècnica de Catalunya
Edifici C3 - Despatx S101-B
UPC Campus Nord UPC
C/ Jordi Girona, 1-3
08034 - Barcelona
___
freebsd-xen@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
Re: Unable to boot with the dom0 xen kernel
Hello,
El 07/04/15 a les 13.11, Gustau Pérez ha escrit:
>
>Hi Roger,
If you don't have a serial console you
should use console=vga in your xen_cmdline. Additionally if you have a
usb debug port you could use that as console with console=dbgp [1].
>>>Thank you. I did not have a console at $home (the laptop has no
>>> physical serial port) but at $work my laptop dockstation provides me
>>> with a physical serial port. I'll try to use it.
>
>Well, my current laptop (Dell latitude E6430) and the previous one
> (Fujitsu Lifebook) have that. I'd say that even an old D630 laptop had
> that option. It is quite useful.
>> I didn't know there were dock stations that provided serial ports even
>> when the laptop didn't have them, that's something worth a try. If not
>> just setting console=vga ought to provide some output. If that also
>> fails please write back and I will provide a patch for the bootloader in
>> order to try to figure out what's going on.
>>
>> Roger.
>
>I added a new test machine. I'll show my results with this one (I'll
> report my laptop results later).
>
>The new machine is
>
> Intel(R) Xeon(R) CPU L5520 @ 2.27GHz
>
>EPT and IOMMU are there:
>
>[root@hast16 ~/xen]# dmesg|grep EPT
> VT-x: PAT,HLT,MTF,PAUSE,EPT,VPID
> [root@hast16 ~/xen]# acpidump -t | grep DMAR
>DMAR: Length=432, Revision=1, Checksum=213,
>
>First I tried xen and xen-tools from ports (version 4.5, hoping those
> were enought). The boot failed, he error says iommu is not enabled. The
> complete log is here:
>
> http://dpaste.com/0KCGGW7
Yup, there's an errata with that specific chipset :(.
>
>so I switched to git version instead. The error was the same. I
> suspect this is the reason:
>
> (XEN) [VT-D]Disabling IOMMU due to Intel 5500/5520/X58 Chipset
> errata #47, #53
>
>According to the article [1] it is possible to prevent interruption
> remapping. I added iommu=no-intremap (it is listed in [2]), it appears
> the xen kernel is happy with that, but then the domain0 FreeBSD kernel
> panics:
>
> http://dpaste.com/3TJYYDQ
Could you add iommu=no-intremap,debug? That will make the IOMMU code a
little bit more verbose. Also the full boot log and a backtrace of
FreeBSD might be helpful.
I think I have an idea of what might cause this GP, can you apply the
following patch to the Xen source tree and recompile the Xen kernel,
(there's no need to recompile the tools):
diff --git a/xen/arch/x86/hvm/vmx/vmx.c b/xen/arch/x86/hvm/vmx/vmx.c
index e1c55ce..fc3c45b 100644
--- a/xen/arch/x86/hvm/vmx/vmx.c
+++ b/xen/arch/x86/hvm/vmx/vmx.c
@@ -3102,8 +3102,7 @@ void vmx_vmexit_handler(struct cpu_user_regs *regs)
if ( exit_qualification & 0x10 )
{
/* INS, OUTS */
-if ( unlikely(is_pvh_vcpu(v)) /* PVH fixme */ ||
- !handle_mmio() )
+if ( !handle_mmio() )
hvm_inject_hw_exception(TRAP_gp_fault, 0);
}
else
>
>Gustau
>
>[1] http://support.citrix.com/article/CTX136517
>[2]
> http://xenbits.xenproject.org/docs/unstable/misc/xen-command-line.html
>
>PS: I'd like to talk about the behavior of the xen_cmdline reboot
> option. Setting it "no" causes the machine to stop (which is fine) but
> the machine remains there. Perhaps it'd be good to allow to reboot the
> machine by pressing a key when in panic. Otherwise you have physically
> reboot the machine.
Yes, this is possible from the serial console. Press Ctrl-A tree times
(to switch to the Xen console), and then 'R' (note the caps).
Roger.
___
freebsd-xen@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
Re: Unable to boot with the dom0 xen kernel
Hi Roger, >>> If you don't have a serial console you >>> should use console=vga in your xen_cmdline. Additionally if you have a >>> usb debug port you could use that as console with console=dbgp [1]. >>Thank you. I did not have a console at $home (the laptop has no >> physical serial port) but at $work my laptop dockstation provides me >> with a physical serial port. I'll try to use it. Well, my current laptop (Dell latitude E6430) and the previous one (Fujitsu Lifebook) have that. I'd say that even an old D630 laptop had that option. It is quite useful. > I didn't know there were dock stations that provided serial ports even > when the laptop didn't have them, that's something worth a try. If not > just setting console=vga ought to provide some output. If that also > fails please write back and I will provide a patch for the bootloader in > order to try to figure out what's going on. > > Roger. I added a new test machine. I'll show my results with this one (I'll report my laptop results later). The new machine is Intel(R) Xeon(R) CPU L5520 @ 2.27GHz EPT and IOMMU are there: [root@hast16 ~/xen]# dmesg|grep EPT VT-x: PAT,HLT,MTF,PAUSE,EPT,VPID [root@hast16 ~/xen]# acpidump -t | grep DMAR DMAR: Length=432, Revision=1, Checksum=213, First I tried xen and xen-tools from ports (version 4.5, hoping those were enought). The boot failed, he error says iommu is not enabled. The complete log is here: http://dpaste.com/0KCGGW7 so I switched to git version instead. The error was the same. I suspect this is the reason: (XEN) [VT-D]Disabling IOMMU due to Intel 5500/5520/X58 Chipset errata #47, #53 According to the article [1] it is possible to prevent interruption remapping. I added iommu=no-intremap (it is listed in [2]), it appears the xen kernel is happy with that, but then the domain0 FreeBSD kernel panics: http://dpaste.com/3TJYYDQ Gustau [1] http://support.citrix.com/article/CTX136517 [2] http://xenbits.xenproject.org/docs/unstable/misc/xen-command-line.html PS: I'd like to talk about the behavior of the xen_cmdline reboot option. Setting it "no" causes the machine to stop (which is fine) but the machine remains there. Perhaps it'd be good to allow to reboot the machine by pressing a key when in panic. Otherwise you have physically reboot the machine. -- --- Prou top-posting :http://ca.wikipedia.org/wiki/Top-posting Stop top-posting :http://en.wikipedia.org/wiki/Posting_style O O O Gustau Pérez i Querol O O O Unitat de Gestió dels departaments O O O Matemàtica Aplicada IV i Enginyeria Telemàtica Universitat Politècnica de Catalunya Edifici C3 - Despatx S101-B UPC Campus Nord UPC C/ Jordi Girona, 1-3 08034 - Barcelona ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
Re: Unable to boot with the dom0 xen kernel
Hello, El 07/04/15 a les 10.25, Gustau Pérez ha escrit: >I'm using the cmdline in the xen wiki. No special tweaking yet. I've just realized the xen_cmdline on the wiki page has the output set to serial only, I've now updated it to send output to both com1 and VGA. > >> If you don't have a serial console you >> should use console=vga in your xen_cmdline. Additionally if you have a >> usb debug port you could use that as console with console=dbgp [1]. > >Thank you. I did not have a console at $home (the laptop has no > physical serial port) but at $work my laptop dockstation provides me > with a physical serial port. I'll try to use it. I didn't know there were dock stations that provided serial ports even when the laptop didn't have them, that's something worth a try. If not just setting console=vga ought to provide some output. If that also fails please write back and I will provide a patch for the bootloader in order to try to figure out what's going on. Roger. ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
Re: Unable to boot with the dom0 xen kernel
Hi, On 07/04/2015 09:28, Roger Pau Monné wrote: >this morning I updated my sources to r281106, recompiled just the > bootloader, installed it under /boot, installed the bootloader with: > >gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada0 > In order to update the loader you should do: > > cd /usr/src/sys/boot && make clean && make -j4 && make install Thanks, this is basically what I did. Just to clarify, I'd say (please someone correct me if I'm wrong) that at the end the bootloader has to be installed in the disk (the make install phase just copies the bootcode under /boot) with gpart. One example is when you upgrade your sources and new zfs attributes appear; if any of those new attributes are enabled in the boot disk, the loader has to be installed with gpart bootcode or the boot process would fail. >>but the results were the same. >> >>When the bootloader starts, I see it loading both the kernel and the >> xen_kernel and some modules, then it shows me the menu and when it >> starts booting I see a blinking cursor and then the machine reboots. > Can you paste your xen_cmdline? I'm using the cmdline in the xen wiki. No special tweaking yet. > If you don't have a serial console you > should use console=vga in your xen_cmdline. Additionally if you have a > usb debug port you could use that as console with console=dbgp [1]. Thank you. I did not have a console at $home (the laptop has no physical serial port) but at $work my laptop dockstation provides me with a physical serial port. I'll try to use it. > >> Does the xen kernel show some debug when booting? Can I send that debug >> to the console (how?) instead to ttyu1? > Yes, Xen will print debug info while booting to the console specified in > the "console" option, which can be the serial, VGA or USB debug port. > They are not exclusive, you can send output to several different > destinations at once. I'll try with an non-vital (it is used for package building) Xen EPT-enabled server I have around and also with my laptop. I'll try sending the debug to vga console and the com1, if it fails I'll try to capture the output with the com1 console. I'll check the options for the xen_commandline Thanks for your help, Gustau -- --- Prou top-posting :http://ca.wikipedia.org/wiki/Top-posting Stop top-posting :http://en.wikipedia.org/wiki/Posting_style O O O Gustau Pérez i Querol O O O Unitat de Gestió dels departaments O O O Matemàtica Aplicada IV i Enginyeria Telemàtica Universitat Politècnica de Catalunya Edifici C3 - Despatx S101-B UPC Campus Nord UPC C/ Jordi Girona, 1-3 08034 - Barcelona ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
Re: Unable to boot with the dom0 xen kernel
Hello, El 06/04/15 a les 10.00, Gustau Pérez ha escrit: > >> Could you update your boot loader to r280954 (or any later version) >> and try again? I've recently committed some small bug fixes for it. > >Hi, > >this morning I updated my sources to r281106, recompiled just the > bootloader, installed it under /boot, installed the bootloader with: > >gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada0 In order to update the loader you should do: cd /usr/src/sys/boot && make clean && make -j4 && make install > >but the results were the same. > >When the bootloader starts, I see it loading both the kernel and the > xen_kernel and some modules, then it shows me the menu and when it > starts booting I see a blinking cursor and then the machine reboots. Can you paste your xen_cmdline? If you don't have a serial console you should use console=vga in your xen_cmdline. Additionally if you have a usb debug port you could use that as console with console=dbgp [1]. > Does the xen kernel show some debug when booting? Can I send that debug > to the console (how?) instead to ttyu1? Yes, Xen will print debug info while booting to the console specified in the "console" option, which can be the serial, VGA or USB debug port. They are not exclusive, you can send output to several different destinations at once. Roger. [1] http://xenbits.xenproject.org/docs/unstable/misc/xen-command-line.html ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
Re: Unable to boot with the dom0 xen kernel
> Could you update your boot loader to r280954 (or any later version) > and try again? I've recently committed some small bug fixes for it. Hi, this morning I updated my sources to r281106, recompiled just the bootloader, installed it under /boot, installed the bootloader with: gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada0 but the results were the same. When the bootloader starts, I see it loading both the kernel and the xen_kernel and some modules, then it shows me the menu and when it starts booting I see a blinking cursor and then the machine reboots. Does the xen kernel show some debug when booting? Can I send that debug to the console (how?) instead to ttyu1? Thanks, Gustau -- --- Prou top-posting :http://ca.wikipedia.org/wiki/Top-posting Stop top-posting :http://en.wikipedia.org/wiki/Posting_style O O O Gustau Pérez i Querol O O O Unitat de Gestió dels departaments O O O Matemàtica Aplicada IV i Enginyeria Telemàtica Universitat Politècnica de Catalunya Edifici C3 - Despatx S101-B UPC Campus Nord UPC C/ Jordi Girona, 1-3 08034 - Barcelona ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
Re: Unable to boot with the dom0 xen kernel
, > I'm replying from my phone, sorry for the format\brevity. > > El dia 03/04/2015 23:37, "Gustau Pérez" < > > Could you update your boot loader to r280954 (or any later version) and try > > again? I've recently committed some small bug fixes for it. > > Thanks, Roger. > Hi, I'll try building and installing the new bootloader and report back. Thank to you, Gus ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
Re: Unable to boot with the dom0 xen kernel
Hello, I'm replying from my phone, sorry for the format\brevity. El dia 03/04/2015 23:37, "Gustau Pérez" va escriure: > > >Hi, > >I'm trying to test xen but after following the instructions here: > >http://wiki.xen.org/wiki/FreeBSD_Dom0 > >the machine is unable to boot. I see the FreeBSD loader, giving me > the traditional options, after the timeout I see it loads the kernel and > modules (basically opensolaris.ko and zfs.ko) and then, instead of > showing the me boot info as usual, the machine shows me a cursor for a > while and then reboots. Could you update your boot loader to r280954 (or any later version) and try again? I've recently committed some small bug fixes for it. Thanks, Roger. ___ freebsd-xen@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
