[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Can not init netfront


  • To: xen-users@xxxxxxxxxxxxx
  • From: "J. Roeleveld" <joost@xxxxxxxxxxxx>
  • Date: Thu, 03 Jul 2014 08:47:53 +0200
  • Delivery-date: Thu, 03 Jul 2014 06:49:20 +0000
  • List-id: Xen user discussion <xen-users.lists.xen.org>

On Wednesday, July 02, 2014 08:42:19 PM Nodir Kodirov wrote:
> 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.

Logs, on my system, are under:
/var/log/xen
and
/var/log/xen-consoles
(but not much info there)

> 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.

Have you tried starting it with:
# xl -v create minios.cfg
and/or:
# xl create -c minios.cfg

The first one should provide more information during the creation.
(You can also add additional 'v' to the command to increase verbosity further)
The second puts you straight to the console, some info might show there.

Either of these might provide more info.

> $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 am missing a disk here.
Try adding a disk, even if it isn't used.

> 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

Reason code 3 = crash.

> $ 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)

Ok, bridge exists then, just wanted to confirm that, as config files don't 
always mean it exists :)

--
Joost

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.