It is currently Sat Dec 07, 2019 5:26 am


All times are UTC




Post new topic Reply to topic  [ 24 posts ]  Go to page Previous  1, 2, 3  Next
Author Message
 Post subject: Re: More interfaces for Qemu image
PostPosted: Sat Jul 31, 2010 11:01 pm 
Offline

Joined: Mon Nov 10, 2008 10:31 am
Posts: 555
Location: Slovakia
Hi,

Quote:
There is one line to change in net.h => :#define MAX_NICS 8


I will try it.

I notice message "/usr/local/bin/qemu: invalid option -- '-kernel-kqemu'" when i use patched 0.12.5 qemu. According to text bellow it is not a good news for owners of old proccessor.

Quote:
http://en.wikipedia.org/wiki/QEMU#KQEMU


Cheers,



_________________
Brezular

All my tutorials can be found here:
http://brezular.com


Top
 Profile  
 
 Post subject: Re: More interfaces for Qemu image
PostPosted: Sat Jul 31, 2010 11:48 pm 
Offline

Joined: Mon Nov 10, 2008 10:31 am
Posts: 555
Location: Slovakia
Hi,
Quote:
I changed the number to 16 and after that I can boot microcore linux with 10 interfaces but apparently this is the maximum for microcore?!.


Yes, I got same result - max. 10 eth cards presented in Microcore.

I am testing JUNOS now ;-)

_________________
Brezular

All my tutorials can be found here:
http://brezular.com


Top
 Profile  
 
 Post subject: Re: More interfaces for Qemu image
PostPosted: Sun Aug 01, 2010 12:05 am 
Offline

Joined: Mon Nov 10, 2008 10:31 am
Posts: 555
Location: Slovakia
Hi,

I got this nice error message when I run Junos on Qemu 0.12.5. My base image runs OK with qemu 0.11.0 I suspect newer version qemu. Too tired to find workaround now, good night Jeremy ;-)

Trying ::1...
telnet: connect to address ::1: Connection refused
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
/kernel text=0x711c68 data=0x41ce0+0x79d74 syms=[0x4+0x7c0f0+0x4+0xac0ee]
/boot/modules/if_bge.ko text=0xa98c data=0x364+0xc syms=[0x4+0xd50+0x4+0xd18]
/boot/modules/mpt_core.ko text=0x18dbc data=0x488+0x358
/boot/modules/if_bce.ko text=0xcf9c data=0x16db0+0x24e4 syms=[0x4+0x14c0+0x4+0x1783]
/boot/modules/acb.ko text=0x3d78 data=0x284+0x80 syms=[0x4+0xa70+0x4+0x9a4]
/boot/modules/mcs.ko text=0x4dc0 data=0x391+0xeb syms=[0x4+0xc40+0x4+0xbc2]
/boot/modules/scs.ko text=0x7c08 data=0x564+0x164 syms=[0x4+0x1110+0x4+0x1179]
/boot/modules/rcb.ko text=0x29c8 data=0x184+0x2c syms=[0x4+0x7e0+0x4+0x704]
/boot/modules/cb.ko text=0x639c data=0x3b8+0x11c syms=[0x4+0xf20+0x4+0xe69]
/boot/modules/mesw.ko text=0x630c data=0x344+0x58 syms=[0x4+0xba0+0x4+0xe7a]
/boot/modules/cbd.ko text=0x1fcc data=0x9c+0xc syms=[0x4+0x540+0x4+0x445]
/boot/modules/sfccb.ko text=0xe30 data=0x1b0+0x14 syms=[0x4+0x540+0x4+0x4a4]


Hit [Enter] to boot immediately, or space bar for command prompt.
Booting [/kernel]...
platform_early_bootinit: M/T Series Early Boot Initialization
kernel trap 12 with interrupts disabled


Fatal trap 30: reserved (unknown) fault while in kernel mode
instruction pointer = 0x20:0xc0991c01
stack pointer = 0x28:0xc1021c6c
frame pointer = 0x28:0xc1021ca4
code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags = interrupt enabled, IOPL = 0
current process = 0 ()
trap number = 30
dog: ERROR - reset of uninitialized watchdog
panic: reserved (unknown) fault
(null)(c0b5bac0,c0b5bac0,c0b0d5e3,c1021bb4,5) at 0xc097d247
(null)(c0b0d5e3,1e,c1021c2c,1,1) at 0xc058a798
(null)(c0ae3132,0,c1021d14,c05aa990,a) at 0xc0991217
(null)(c1021c2c) at 0xc0992101
(null)(c1021cb0) at 0xc097e87f
(null)(c1021d44,c0a73999,c0b0f138,c1021d34,c1021d30) at 0xc097e87f
(null)(c0b0f138,c1021d34,c1021d30,a,c1021d54) at 0xc0977b1e
(null)(c0aeddb4,c0aa6358,c1021d84,c09873fe,80) at 0xc0a73999
(null)(80,c097e8c0,f,3,20) at 0xc0a73f7e
(null)(1026000) at 0xc09873fe
(null)() at 0xc04963dd
kernel trap 12 with interrupts disabled


Fatal trap 12: page fault while in kernel mode
fault virtual address = 0xf000ff53
fault code = supervisor write, page not present
instruction pointer = 0x20:0xc05b2b31
stack pointer = 0x28:0xc1021920
frame pointer = 0x28:0xc1021940
code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags = IOPL = 0
current process = 0 ()
trap number = 12
dog: ERROR - reset of uninitialized watchdog
panic: page fault
XXXXX: ERROR platform_boot_mastership_relinquish not defined:XXXXXdog: ERROR - reset of uninitialized watchdog
dog: ERROR - reset of uninitialized watchdog
Uptime: 1s


Cheers,

_________________
Brezular

All my tutorials can be found here:
http://brezular.com


Top
 Profile  
 
 Post subject: Re: More interfaces for Qemu image
PostPosted: Sun Aug 01, 2010 3:42 am 
If i select 8 interfaces for JUNOS than it works fine for me....

thanks


Top
  
 
 Post subject: Re: More interfaces for Qemu image
PostPosted: Sun Aug 01, 2010 1:42 pm 
Offline

Joined: Mon Nov 10, 2008 10:31 am
Posts: 555
Location: Slovakia
Hi,

there are two problems when we use qemu 0.12.5.

1. QEMU versions starting with 0.12.0 no longer support KQEMU

When kqemu is enabled there is an error message "/usr/local/bin/qemu: invalid option -- '-kernel-kqemu'" in the output of qemuwrapper and device doesn't start.

I suggest to show warning message after enabling Kqemu when Qemu 0.12.5 is used:

"Your qemu version 0.12.5 and no longer support Kqemu, please disable Kqemu"

This should help us to avoid many problems :-)

2. Olive problem with qemu 0.12.5

There is a bug that prevents you to run Olive with qemu 0.12.5. During first Olive boots you get this error message and Olive hangs up.

Quote:
Trying ::1...
telnet: connect to address ::1: Connection refused
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
Loading /boot/defaults/loader.conf
/kernel text=0x76a2cc data=0x43340+0x937b4 syms=[0x4+0x80df0+0x4+0xb3a9b]
/boot/modules/if_bge.ko text=0xa98c data=0x364+0xc syms=[0x4+0xd50+0x4+0xd18]
/boot/modules/if_em.ko text=0x13088 data=0x6d8+0x18 syms=[0x4+0x15e0+0x4+0x18e5]
/boot/modules/mpt_core.ko text=0x18dbc data=0x488+0x358
/boot/modules/if_bce.ko text=0xd07c data=0x16d94+0x24e4 syms=[0x4+0x14d0+0x4+0x1787]
/boot/modules/acb.ko text=0x3ffc data=0x284+0x80 syms=[0x4+0xad0+0x4+0xa19]
/boot/modules/mcs.ko text=0x4dc0 data=0x391+0xeb syms=[0x4+0xc40+0x4+0xbc2]
/boot/modules/scs.ko text=0x7c08 data=0x564+0x164 syms=[0x4+0x1110+0x4+0x1179]
/boot/modules/rcb.ko text=0x29c8 data=0x184+0x2c syms=[0x4+0x7e0+0x4+0x704]
/boot/modules/cb.ko text=0x63fc data=0x3b8+0x11c syms=[0x4+0xf20+0x4+0xe69]
/boot/modules/mesw.ko text=0x630c data=0x344+0x58 syms=[0x4+0xba0+0x4+0xe7a]
/boot/modules/cbd.ko text=0x1fcc data=0x9c+0xc syms=[0x4+0x540+0x4+0x445]
/boot/modules/sfccb.ko text=0xe30 data=0x1b0+0x14 syms=[0x4+0x540+0x4+0x4a5]
/boot/modules/mac_runasnonroot.ko text=0x7b4 data=0x4d0 syms=[0x4+0x310+0x4+0x39d]


Hit [Enter] to boot immediately, or space bar for command prompt.
Booting [/kernel]...
platform_early_bootinit: M/T Series Early Boot Initialization
kernel trap 12 with interrupts disabled


Fatal trap 30: reserved (unknown) fault while in kernel mode
instruction pointer = 0x20:0xc09d3a01
stack pointer = 0x28:0xc1021c6c
frame pointer = 0x28:0xc1021ca4
code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags = interrupt enabled, IOPL = 0
current process = 0 ()
trap number = 30
dog: ERROR - reset of uninitialized watchdog
panic: reserved (unknown) fault
(null)(c0bce740,c0bce740,c0b6599a,c1021bb4,c1021bb4) at 0xc09bf437
(null)(c0b6599a,1e,c1021c2c,1,1) at 0xc0596178
(null)(c0b43132,0,c1021d14,c05b6b10,a) at 0xc09d3017
(null)(c1021c2c) at 0xc09d3f01
(null)(c1021cb0) at 0xc09c0a4b
(null)(c1021d44,c0ac6439,c0b6764e,c1021d34,c1021d30) at 0xc09c0a4b
(null)(c0b6764e,c1021d34,c1021d30,a,c1021d54) at 0xc09b9cfe
(null)(c0b44f60,c0afad98,c1021d84,c09c917e,80) at 0xc0ac6439
(null)(80,c09c0a90,f,3,20) at 0xc0ac6a2e
(null)(1026000) at 0xc09c917e
(null)() at 0xc049e07d
dog: ERROR - reset of uninitialized watchdog
dog: ERROR - reset of uninitialized watchdog
Uptime: 1s


There is a workaround here (in Troubleshooting section):

Quote:
http://www.internetworkpro.org/wiki/Using_QEMU_with_Olive_to_emulate_Juniper_Routers#Watchdog_panic_immediately_after_boot


These are the steps:
a) First download the lastest copy of the source code

$ git clone git://git.linuxtogo.org/home/kevin/seabios.git seabios
$ cd seabios

Edit the src/config.h file and set the CONFIG_SMBIOS to 0 like below

// Support generation of SM BIOS tables (for emulators)
#define CONFIG_SMBIOS 0

b)
$make

$sudo cp ./out/bios.bin /usr/local/share/qemu/
cp: overwrite `/usr/local/share/qemu/bios.bin'? y

After this you should be able to run Olive with qemu 0.12.5. I test Olive with 10x e1000 NIcs and all the NIcs were presented in JunOS.

I did test with RTL8139 NICs but cards weren't presented in FreeBSD and JunOS :-(

I tested Microcore Linux and there is this warning message displayed during the boot:
PnPBIOS: dev_node_info: function non supported on this system

It delays the boot but after some time Linux Micocore is loaded (tested with 6 x NICs, e1000 type)

Conclusion:
I think that the GNS3 blog should be updated with these new information.
It should also recommend to use qemu 0.11.0 (still supports kqemu) for PCs with older CPU that don't support KVM and kqemu is only one chance to speed up virtualization.

Also information about change line ( :#define MAX_NICS 16) in net.h file (in qemu directory) before compiling Qemu if user wish to have more then 8 NIC should be on gns3 blog.

Thanks,

_________________
Brezular

All my tutorials can be found here:
http://brezular.com


Top
 Profile  
 
 Post subject: Re: More interfaces for Qemu image
PostPosted: Sun Aug 01, 2010 5:13 pm 
Offline
Site Admin

Joined: Sat Oct 11, 2008 1:41 pm
Posts: 2668
Location: Canada
Once again you did a great job, it's really helpful :) I'll update the blog but not yet because I travel until 20th of August. I won't release either so there is plenty of time to test the last changes and correctly package everthing.

_________________
Jeremy, GNS3 Programmer & Benevolent Dictator for Life.


Top
 Profile  
 
 Post subject: Re: More interfaces for Qemu image
PostPosted: Mon Aug 02, 2010 3:06 am 
Hi,
I applied the patch to qemu 0.12.5 and than copied the bios and also increased the MAX NICS value to 20.
I was able to start the JUNOS routers and did following tests:
1. using the em2 interface, it seems this bug is still there, i.e cannot send any traffic on this interface, i.e. i had directly connected link between two JUNOS routers and tried ping between each other on em2 interface and it did not work.
2. I get following error when i try to configure any interfaces in JUNOS that is em8 or above:
Code:
root# set interfaces em8 u
                     ^
device value outside range 0..7 for '8' in 'em8'.

So this looks like a limitation within JUNOS. Could be my JUNOS image....I am running 10.1R1.8
brezular are you able configure any interfaces above em7....on your JUNOS image

Thanks


Last edited by cisco006 on Tue Aug 03, 2010 2:37 am, edited 1 time in total.

Top
  
 
 Post subject: Re: More interfaces for Qemu image
PostPosted: Mon Aug 02, 2010 6:09 am 
Offline

Joined: Mon Nov 10, 2008 10:31 am
Posts: 555
Location: Slovakia
HI,
Quote:
brezular are you able configure any interfaces above em7....on your JUNOS image


Since I am busy now I will do a test and post the result later. I will test 9.x JUNOS too.
I will run LISA with 0.12.5 qemu to test how many interfaces CentOS can "see".
Thank you for your test.

Cheers,

_________________
Brezular

All my tutorials can be found here:
http://brezular.com


Top
 Profile  
 
 Post subject: Re: More interfaces for Qemu image
PostPosted: Tue Aug 03, 2010 3:25 am 
Hi,
Another observation, i left 2 JUNOS routers running overnight and both of them crashed and qemu window title says stopped.
Here is the message from from console window:
Quote:
Initial interface configuration:
rts_ifl_mput_channel_tlvs svcs_drv_apis = NULL
rts_ifl_mput_channel_tlvs svcs_drv_apis = NULL
rts_ifl_mput_channel_tlvs svcs_drv_apis = NULL
rts_ifamput: cc sent to DCD in tlv:0x0; whole cc in ifa:0x0
additional daemons:.
checking for core dump...
savecore: reboot after panic: ad_ioctl:1280744812: ad1: Standby not armed but state is invalid: state="ARMED"
savecore: writing core to vmcore.1
savecore: currently booted kernel copied
savecore: writing kernel to /var/crash/kernel.1

Please note i have left same olive img in qemu 0.11 running for days and did not come across this issue before. So it looks like more testing is required with qemu 0.12.5.

Hope this helps...

Thanks


Top
  
 
 Post subject: Re: More interfaces for Qemu image
PostPosted: Thu Aug 05, 2010 8:01 am 
Offline

Joined: Mon Nov 10, 2008 10:31 am
Posts: 555
Location: Slovakia
Hi,

I did test of connectivity between interfaces for Junos 10.1R1.8, Microcore 2.11.5, Lisa 2.0.2 with qemu 0.12.5 (seabios off).

Quote:
https://spreadsheets.google.com/ccc?key=0AqL2h6R5UKMhdGZYajA2S3l2UU84ZndkZDE5VWlPcnc&hl=en&authkey=CK_C9tcB



I can confirm that problem with eth2 interface still persists in Olive.

Cheers,



_________________
Brezular

All my tutorials can be found here:
http://brezular.com


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 24 posts ]  Go to page Previous  1, 2, 3  Next

All times are UTC


Who is online

Users browsing this forum: No registered users and 3 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group

phpBB SEO