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

[Xen-users] Re: [Xen-devel] Error: Device 0 (vif) could not be connected. Hotplug scripts not working


  • To: Michal Novotny <minovotn@xxxxxxxxxx>
  • From: Ananth <cbananth@xxxxxxxxx>
  • Date: Thu, 26 Mar 2009 18:10:35 +0530
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Thu, 26 Mar 2009 05:41:38 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=UW9Xs6532/XAWzB5bYtwdcslBLFjk7IB1G4cpB2k0VRvUfJqfQGQTHtjcWCxWj3vGa 3ShEnKM3UzjdpTrtHd924ZVRKN6siJZOV6I6ANy1PwjgIMWMyWQHWzy6yFonp6g+bWn1 rAfikQgMEH01cHZtF+6gNU5TW9naDYZIWYu0c=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hi,
Got missed when i shifted the thread from xen-devel to xen-users list.

I tried commenting as well as specifying vif=[]. I got the below response.

linux-ka07:/home/cbananth/xen_Guests/Ubuntu8.04_xen # xm create /home/cbananth/x
en_Guests/Ubuntu8.04_xen/ubuntu.8-04.xen3.cfg -c
Using config file "/home/cbananth/xen_Guests/Ubuntu8.04_xen/ubuntu.8-04.xen3.cfg
".
Started domain ubuntu.8-04
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 5, 131072 bytes)
TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 16384 bind 8192)
TCP reno registered
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
BUG: unable to handle kernel NULL pointer dereference at virtual address 0000000
0
 printing eip:
c03b98a4
00445000 -> *pde = 00000000:00000000
Oops: 0000 [#1]
SMP
Modules linked in:
CPU:    0
EIP:    0061:[<c03b98a4>]    Not tainted VLI
EFLAGS: 00010282   (2.6.18.8-xenU #1)
EIP is at hgafb_probe+0xc4/0x390
eax: c13c5940   ebx: 00000000   ecx: c13c5940   edx: 00000000
esi: c03697a8   edi: c03696e0   ebp: c12afe88   esp: c12afe5c
ds: 007b   es: 007b   ss: e021
Process swapper (pid: 1, ti=c12ae000 task=c12aaa70 task.ti=c12ae000)
Stack: c035ed00 000003bf 00000000 00000001 00000000 c034026e 00000000 00000000
       00000000 c03697a8 c03696e0 c12afeac c0279a3a c03697a8 c03696e0 00000000
       c036974c 00000000 c12afed0 c0279b40 c12afebc c0279b58 c03696e0 c03697a8
Call Trace:
 [<c0105d59>] show_stack_log_lvl+0xa9/0xe0
 [<c010615f>] show_registers+0x1bf/0x250
 [<c0106618>] die+0x158/0x2f0
 [<c0115d19>] do_page_fault+0x6c9/0xc43
 [<c010581f>] error_code+0x2b/0x30
 [<c0279a3a>] driver_probe_device+0x4a/0xc0
 [<c0279b58>] __device_attach+0x18/0x1a
 [<c027909e>] bus_for_each_drv+0x5e/0x80
 [<c02799ea>] device_attach+0x7a/0x80
 [<c0278cb1>] bus_attach_device+0x21/0x40
 [<c0277dc3>] device_add+0x2a3/0x350
 [<c027baab>] platform_device_add+0x14b/0x1a0
 [<c027bb1d>] platform_device_register+0x1d/0x30
 [<c03b97be>] hgafb_init+0x4e/0x70
 [<c0102180>] init+0x140/0x4a0
 [<c0102c35>] kernel_thread_helper+0x5/0x10
Code: 08 00 00 00 00 c7 04 24 00 ed 35 c0 e8 76 0e d7 ff ba 01 00 00 00 85 c0 0f                                                            44 15 d0 f0 3e c0 89 15 d0 f0 3e c0 8b 15 d4 f0 3e c0 <0f> b7 0a 0f b7 82 00 10                                                            00

When I tried the same once again, few more lines were added to the output. They are,

Code: 08 00 00 00 00 c7 04 24 00 ed 35 c0 e8 76 0e d7 ff ba 01 00 00 00 85 c0 0f 44 15 d0 f0 3e c0 89 15 d0 f0 3e c0 8b 15 d4 f0 3e c0 <0f> b7 0a 0f b7 82 00 10 00 00 66 c7 02 55 aa 0f b7 1a 66 c7 02
EIP: [<c03b98a4>] hgafb_probe+0xc4/0x390 SS:ESP e021:c12afe5c
 <0>Kernel panic - not syncing: Attempted to kill init!


Regards
Ananth

On Thu, Mar 26, 2009 at 5:23 PM, Michal Novotny <minovotn@xxxxxxxxxx> wrote:
Hi,
could you please send it to all the Xen-Devel list with attachments (xminfo.txt and xend.log) and not just me? To get more replies... Anyway I tried to look at the log and I found nothing relevant. Could you please tell me what it's doing now and/or disable vif=[] like by commenting it (adding # sign before the line, change it to #vif=[]) and try again?

Michal

Ananth wrote:
Hi
Please find the attachments.

Regards
Ananth

On Thu, Mar 26, 2009 at 3:39 PM, Michal Novotny <minovotn@xxxxxxxxxx <mailto:minovotn@xxxxxxxxxx>> wrote:

   Hi Ananth,
   could you please send xend.log file containing more information
   about test running? This looks like the hotplug script issue which
   are shipped with Xen itself.

   Michal

   Ananth wrote:

       Hi
       Thanks for the quick response. brctl show returned bridge name
       eth0 .
       I still get the same error after I modified the config file as
       you had mentioned.

       Regards
       Ananth

       On Thu, Mar 26, 2009 at 3:26 PM, Boris Derzhavets
       <bderzhavets@xxxxxxxxx <mailto:bderzhavets@xxxxxxxxx>
       <mailto:bderzhavets@xxxxxxxxx <mailto:bderzhavets@xxxxxxxxx>>>

       wrote:

          Try:-
          # brctl show
          It will report your xen-bridge. Say eth0.
          Fix vif= [ 'bridge=eth0']
          See what happens.

          --- On *Thu, 3/26/09, Ananth /<cbananth@xxxxxxxxx
       <mailto:cbananth@xxxxxxxxx>
          <mailto:cbananth@xxxxxxxxx <mailto:cbananth@xxxxxxxxx>>>/*

       wrote:

              From: Ananth <cbananth@xxxxxxxxx
       <mailto:cbananth@xxxxxxxxx> <mailto:cbananth@xxxxxxxxx

       <mailto:cbananth@xxxxxxxxx>>>

              Subject: [Xen-devel] Error: Device 0 (vif) could not be
              connected. Hotplug scripts not working
              To: "xen-devel@xxxxxxxxxxxxxxxxxxx
       <mailto:xen-devel@xxxxxxxxxxxxxxxxxxx>
              <mailto:xen-devel@xxxxxxxxxxxxxxxxxxx
       <mailto:xen-devel@xxxxxxxxxxxxxxxxxxx>>"

              <xen-devel@xxxxxxxxxxxxxxxxxxx
       <mailto:xen-devel@xxxxxxxxxxxxxxxxxxx>
              <mailto:xen-devel@xxxxxxxxxxxxxxxxxxx
       <mailto:xen-devel@xxxxxxxxxxxxxxxxxxx>>>

              Date: Thursday, March 26, 2009, 5:32 AM


              Hello,
              When I install guest OS on xen using "xm create
              /path/of/file/ubuntu.cfg -c" , I am getting an error
       message
              *"Error*: Device 0 (*vif*) could not be connected. Hotplug
              scripts not working
              <http://markmail.org/message/24aj3qs6ddrtwdks>" . I
       also saw

              that hotplugs and udev are prerequisites to be installed
              before compiling xen. I could not find hotplugs in Yast.
              However i installed udev.
              My vif value in the config file is set to [' '].

              Please guide me through this.

              Thank you.

              Warm Regards
              Ananth

              _______________________________________________
              Xen-devel mailing list
              Xen-devel@xxxxxxxxxxxxxxxxxxx
       <mailto:Xen-devel@xxxxxxxxxxxxxxxxxxx>
       <mailto:Xen-devel@xxxxxxxxxxxxxxxxxxx
       <mailto:Xen-devel@xxxxxxxxxxxxxxxxxxx>>

              http://lists.xensource.com/xen-devel

                         

       ------------------------------------------------------------------------



       _______________________________________________
       Xen-devel mailing list
       Xen-devel@xxxxxxxxxxxxxxxxxxx
       <mailto:Xen-devel@xxxxxxxxxxxxxxxxxxx>
       http://lists.xensource.com/xen-devel
       




_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

 


Rackspace

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