Xen project Mailing List

Re: [Xen-users] Can not init netfront

From: Nodir Kodirov <nodir.qodirov@xxxxxxxxx>

Date: Wed, 2 Jul 2014 20:42:19 -0700

Delivery-date: Thu, 03 Jul 2014 03:44:54 +0000

List-id: Xen user discussion <xen-users.lists.xen.org>

I was using xl only and bridge was up. Since I did not know how to retrieve log messages without xend, I kept it on. But now I turned xend off by 'service xend stop' and re-run the 'xl create minios.cfg'. It still fails to start. 'xl list' shows only dom0. $cat minios.cfg kernel = "/home/knodir/devel/mini-os/mini-os.gz" builder = 'pvm' vcpus = 1 memory = 1024 name = "Mini-OS-custom" vif = [ 'bridge=xenbr0' ] serial = 'pty' on_poweroff = 'destroy' on_reboot = 'destroy' on_crash = 'destroy' I don't know where to check xl log, but here is what I got by 'cat /var/log/xen/Mini-OS-custom.log' Waiting for domain Mini-OS-custom (domid 35) to die [pid 30809] Domain 35 has shut down, reason code 3 0x3 Action for shutdown reason code 3 is destroy Domain 35 needs to be cleaned up: destroying the domain Done. Exiting now $ brctl show bridge name bridge id STP enabled interfaces xenbr0 8000.001cc03757b2 no eth0 $ ifconfig xenbr0 xenbr0 Link encap:Ethernet HWaddr 00:1C:C0:37:57:B2 inet addr: [...] Bcast:[...] Mask:255.255.255.0 inet6 addr: [...] Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:659103 errors:0 dropped:0 overruns:0 frame:0 TX packets:30125 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:40783911 (38.8 MiB) TX bytes:3287602 (3.1 MiB) Thanks for the help, Nodir. On 2 July 2014 00:00, Joost Roeleveld <joost@xxxxxxxxxxxx> wrote: > On Tuesday 01 July 2014 14:14:47 Nodir Kodirov wrote: >> Hello, >> >> I'm a graduate student, trying to run Mini-OS for my project. >> >> When I create mini-os instance, netfront fails to initialize. I get >> following output from 'xl console <domid>' >> >> Xen Minimal OS! >> start_info: 000000000028f000(VA) >> nr_pages: 0x40000 >> shared_inf: 0xc05e1000(MA) >> pt_base: 0000000000292000(VA) >> nr_pt_frames: 0x5 >> mfn_list: 000000000008f000(VA) >> mod_start: 0x0(VA) >> mod_len: 0 >> flags: 0x0 >> cmd_line: >> stack: 000000000004e7a0-000000000006e7a0 >> MM: Init >> _text: 0000000000000000(VA) >> _etext: 00000000000303c2(VA) >> _erodata: 0000000000038000(VA) >> _edata: 0000000000038540(VA) >> stack start: 000000000004e7a0(VA) >> _end: 000000000008efa0(VA) >> start_pfn: 29a >> max_pfn: 40000 >> Mapping memory range 0x400000 - 0x40000000 >> setting 0000000000000000-0000000000038000 readonly >> skipped 0000000000001000 >> MM: Initialise page allocator for 498000(498000)-40000000(40000000) >> MM: done >> Demand map pfns at 40001000-2040001000. >> Initialising timer interface >> Initialising console ... done. >> gnttab_table mapped at 0000000040001000. >> Initialising scheduler >> Thread "Idle": pointer: 0x4a2070, stack: 0x4b0000 >> Thread "xenstore": pointer: 0x4a20d0, stack: 0x4c0000 >> xenbus initialised on irq 1 mfn 0xbe5f5 >> Thread "shutdown": pointer: 0x4a2130, stack: 0x4d0000 >> Thread "server": pointer: 0x4a2190, stack: 0x4e0000 >> [server] Waiting for network. >> Failed to read device/vif/0/backend-id. >> _init_netfront: backend/mac failed >> >> VM's state is 'b' (for blocked) and that's a last line of output before VM >> gets frozen. My host environment is x86_64 CentOS 6.5 with Linux 3.10.34-11 >> kernel. I configured a bridged network with eth0 and xenbr0 configured as >> following: >> >> /etc/sysconfig/network-scripts/ifcfg-xenbr0 >> DEVICE=xenbr0 >> TYPE=Bridge >> BOOTPROTO=dhcp >> ONBOOT=yes >> DELAY=0 >> NM_CONTROLLED=no >> >> /etc/sysconfig/network-scripts/ifcfg-eth0 >> DEVICE="eth0" >> NM_CONTROLLED="no" >> ONBOOT="yes" >> HWADDR=00:1C:C0:37:57:B2 >> BRIDGE=xenbr0 >> >> Xen VM configuration file is as follows: >> >> kernel = "/home/knodir/devel/mini-os/mini-os.gz" >> builder = 'pvm' >> vcpus = 1 >> memory = 1024 >> name = "Mini-OS-custom" >> serial = 'pty' >> on_poweroff = 'destroy' >> on_reboot = 'destroy' >> on_crash = 'destroy' >> >> My custom mini-os kernel is built from https://github.com/cnplab/mini-os >> since I'm planning to use it for ClickOS https://github.com/cnplab/clickos >> I believe this modified Mini-OS to have the same networking source code as >> an original one (I did not apply xennet https://github.com/cnplab/xennet >> patch). >> >> I wonder if I'm missing something in my Xen VM configuration file. When I >> add a new line vif=[ 'mac=00:16:3e:01:01:01,bridge=xenbr0' ] to it, VM is >> not created at all. These are the VM creation corresponding lines from >> /var/log/xen/xend.log >> >> [2014-07-01 14:11:11 20157] DEBUG (XendDomainInfo:151) >> XendDomainInfo.recreate({'max_vcpu_id': 0, 'cpu_time': 0L, 'ssidref': 0, >> 'hvm': 0, 'shutdown_reason': 255, 'dying': 0, 'online_vcpus': 1, 'domid': >> 33, 'paused': 1, 'crashed': 0, 'running': 0, 'maxmem_kb': 1049600L, >> 'shutdown': 0, 'mem_kb': 1048576L, 'handle': [121, 198, 174, 221, 11, 118, >> 72, 231, 172, 230, 168, 102, 169, 14, 221, 123], 'blocked': 0, 'cpupool': >> 0}) >> [2014-07-01 14:11:11 20157] INFO (XendDomainInfo:169) Recreating domain 33, >> UUID 79c6aedd-0b76-48e7-ace6-a866a90edd7b. at /local/domain/33 >> [2014-07-01 14:11:11 20157] DEBUG (XendDomain:476) Adding Domain: 33 >> [2014-07-01 14:11:11 20157] DEBUG (XendDomainInfo:1882) >> XendDomainInfo.handleShutdownWatch >> [2014-07-01 14:11:11 20157] DEBUG (DevController:95) DevController: writing >> {'state': '1', 'backend-id': '0', 'backend': >> '/local/domain/0/backend/console/33/0'} to >> /local/domain/33/device/console/0. >> [2014-07-01 14:11:11 20157] DEBUG (DevController:97) DevController: writing >> {'domain': 'Mini-OS-custom', 'frontend': >> '/local/domain/33/device/console/0', 'uuid': >> '12b56995-0349-8bf3-93ee-92c6a9ec75e7', 'frontend-id': '33', 'state': '1', >> 'location': '2', 'online': '1', 'protocol': 'vt100'} to >> /local/domain/0/backend/console/33/0. >> [2014-07-01 14:11:11 20157] WARNING (XendDomainInfo:2062) Domain has >> crashed: name=Mini-OS-custom id=33. >> [2014-07-01 14:11:11 20157] ERROR (XendDomainInfo:2196) VM Mini-OS-custom >> restarting too fast (Elapsed time: 0.400618 seconds). Refusing to restart >> to avoid loops. >> [2014-07-01 14:11:11 20157] DEBUG (XendDomainInfo:3077) >> XendDomainInfo.destroy: domid=33 >> [2014-07-01 14:11:12 20157] DEBUG (XendDomainInfo:2402) Destroying device >> model >> [2014-07-01 14:11:12 20157] DEBUG (XendDomainInfo:2409) Releasing devices >> [2014-07-01 14:11:12 20157] DEBUG (XendDomainInfo:2407) No device model >> [2014-07-01 14:11:12 20157] DEBUG (XendDomainInfo:2409) Releasing devices >> >> Any help is appreciated. >> >> Nodir. > > > Few quick questions: > > You use the XL-toolkit AND xend? > Please only use one of these. > Eg. stop xend and use XL to stop/start the domains. > > Additionally, is the bridge actually up when trying to start the domain with > the vif.... line? > Check with (and provide the output): > # brctl show > > -- > Joost > > _______________________________________________ > Xen-users mailing list > Xen-users@xxxxxxxxxxxxx > http://lists.xen.org/xen-users _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxx http://lists.xen.org/xen-users

©2013 Xen Project, A Linux Foundation Collaborative Project. All Rights Reserved.
Linux Foundation is a registered trademark of The Linux Foundation.
Xen Project is a trademark of The Linux Foundation.