[c-nsp] IOS XRv in a virtual environment

[James Bensley]

Hi Aaron,

How much RAM has been assigned to this Virtual Machine by your Linux engineer?

On my laptop with 4GB RAM, if I assign 2GB to an IOS-XRv VM it will
run but has periodic memory dumps. On my desktop with many GBs of RAM
(can't remember how much I have assigned to the IOS-XRv VM on their)
it doesn't.

Cheers,
James.



On 18 February 2015 at 15:50, Aaron <aaron1 at gvtc.com> wrote:
> Harold, et al, I have XRv running nicely on a laptop Windows 7.  I imported
> XRv into VirtualBox which then created the virtual XR instance.  I then see
> it in GNS3 Jungle and it runs nicely in GNS3 Jungle. (nevermind that it's a
> memory hog)
>
>
>
> Now, question is, I tried to recreate this in a data center where my linux
> engineer created me a virtual pc machine running windows 7.  I did all the
> same stuff, except now XRv crashes when trying to boot up.
>
>
>
> Any ideas?
>
>
>
> Last bootup messages prior to crash are shown below. I will provide more
> info if you need it to tell why this is occurring.
>
>
>
> Aaron
>
>
>
> This is XRv 5.3
>
>
>
> 2015-02-17 16:00:46.000
>
> Crash Reason: Kernel Crash
>
>
>
> Exception at 0xfe6ac39a signal 5 c=2 f=0
>
>
>
> Active process(s):
>
>         <No kdebug_info information available>
>
>
>
>        REGISTER INFO
>
>        EDI       ESI       EBP       EXX
>
>   R0   fe6eb969  00000000  fe6f2120  fdfc40ec
>
>        EBX       EDX       ECX       EAX
>
>   R4   00000674  fe255240  00000025  00000024
>
>        EIP        CS       EFL       ESP
>
>   R8   fe6ac39a  0000001c  00001092  fe6eba29
>
>        SS
>
>   R12  00000000
>
>
>
>               Control Registers
>
>                  CR0 #         0x8005003b
>
>                  CR2 #                  0
>
>                  CR3 #            0x10fc0
>
>                  CR4 #              0x2f0
>
>
>
>
>
>               Debug Registers
>
>                  DR0 #                  0
>
>                  DR1 #                  0
>
>                  DR2 #                  0
>
>                  DR3 #                  0
>
>                  DR6 #         0xffff0ff0
>
>                  DR7 #              0x400
>
>
>
>
>
>           GDTR limit #              0x13f
>
>    GDTR base address #         0xfed18474
>
>                 LDTR #               0xa0
>
>           IDTR limit #              0x70f
>
>    IDTR base address #         0xfed165b4
>
>                   TR #              0x100
>
>
>
> STACK TRACE
>
> #0 0xfdf30d70
>
> #1 0xfdf33ff8
>
>
>
>
>
> Local Syslog Messages:
>
>
>
>
>
> Dumping local syslog messages
>
>
>
> Dumping kernel printf messages
>
>
>
>
>
> Kernel Printf Messages:
>
>
>
> Crash[0,0] at nano_alloc line 1652.
>
>
>
> System reload. Waiting for pending output..........
>
>
>
>   Cause code : 0x00000000
>
>   Reboot code: 0x00000000, "Unknown"
>
>   Dump type  : 0x00000000, "No kernel dump needed"
>
>   Proc name  : ""
>
>   (Kernel dump not required)
>
> Missing reboot reason information. Reboot reason will be derived from Kernel
> signal code !!!
>
> Writing crashinfo
>
> Crash Reason: Kernel Crash
>
>
>
> Exception at 0xfe6ac39a signal 5 c=2 f=0
>
>
>
> Active process(s):
>
>         <No kdebug_info information available>
>
>
>
>        REGISTER INFO
>
>        EDI       ESI       EBP       EXX
>
>   R0   fe6eb969  00000000  fe6f2120  fdfc40ec
>
>        EBX       EDX       ECX       EAX
>
>   R4   00000674  fe255240  00000025  00000024
>
>        EIP        CS       EFL       ESP
>
>   R8   fe6ac39a  0000001c  00001092  fe6eba29
>
>        SS
>
>   R12  00000000
>
>                  CR0 #         0x8005003b
>
>                  CR2 #                  0
>
>                  CR3 #            0x10fc0
>
>                  CR4 #              0x2f0
>
>                  DR0 #                  0
>
>                  DR1 #                  0
>
>                  DR2 #                  0
>
>                  DR3 #                  0
>
>                  DR6 #         0xffff0ff0
>
>                  DR7 #              0x400
>
>
>
>
>
>           GDTR limit #              0x13f
>
>    GDTR base address #         0xfed18474
>
>                 LDTR #               0xa0
>
>           IDTR limit #              0x70f
>
>    IDTR base address #         0xfed165b4
>
>                   TR #              0x100
>
>
>
> STACK TRACE
>
> #0 0xfdf30d70
>
> #1 0xfdf33ff8
>
> 2015-02-17 16:00:46.000
>
> Crash Reason: Kernel Crash
>
>
>
> Exception at 0xfe6ac39a signal 5 c=2 f=0
>
>
>
> Active process(s):
>
>         <No kdebug_info information available>
>
>
>
>        REGISTER INFO
>
>        EDI       ESI       EBP       EXX
>
>   R0   fe6eb969  00000000  fe6f2120  fdfc40ec
>
>        EBX       EDX       ECX       EAX
>
>   R4   00000674  fe255240  00000025  00000024
>
>        EIP        CS       EFL       ESP
>
>   R8   fe6ac39a  0000001c  00001092  fe6eba29
>
>        SS
>
>   R12  00000000
>
>
>
>               Control Registers
>
>                  CR0 #         0x8005003b
>
>                  CR2 #                  0
>
>                  CR3 #            0x10fc0
>
>                  CR4 #              0x2f0
>
>
>
>
>
>               Debug Registers
>
>                  DR0 #                  0
>
>                  DR1 #                  0
>
>                  DR2 #                  0
>
>                  DR3 #                  0
>
>                  DR6 #         0xffff0ff0
>
>                  DR7 #              0x400
>
>
>
>
>
>           GDTR limit #              0x13f
>
>    GDTR base address #         0xf
>
> Writing crashinfo done!
>
>
>
> Writing x86 kernel core file
>
>
>
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/