[c-nsp] IOS XRv in a virtual environment
Aaron
aaron1 at gvtc.com
Wed Feb 18 11:30:02 EST 2015
Memory was 1914 MB…
Changed to 2048 MB Still crashes
Changed to 3092 MB Still crashes
Changed to 4096 MB won’t start at all when trying to start it in gns3….. when I try to start it in virtual box console, I get
“virtualbox error…. Failed to open a session for the virtual machine xrv5.3-vm-name … AMD-V is not available (VERR_SVM_NO_SVM)
Details….
Result Code:
E_FAIL (0x80004005)
Component:
Console
Interface:
IConsole {8ab7c520-2442-4b66-8d74-4ff1e195d2b6}
Aaron
From: Scott Miller [mailto:fordlove at gmail.com]
Sent: Wednesday, February 18, 2015 10:07 AM
To: Aaron
Cc: Harold Ritter (hritter); cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] IOS XRv in a virtual environment
Try to increase the amount of memory allocated to the VBox XR. I had the same error a while back, the bumped it up to 2gig and away it went.
Scott
On Wed, Feb 18, 2015 at 8:50 AM, 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/
More information about the cisco-nsp
mailing list