WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-bugs

[Xen-bugs] [Bug 1612] New: x86-64 : Can't start VM when vif set

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 1612] New: x86-64 : Can't start VM when vif set
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Sat, 15 May 2010 13:32:52 -0700
Delivery-date: Sat, 15 May 2010 13:33:07 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1612

           Summary: x86-64 : Can't start VM when vif set
           Product: Xen
           Version: unstable
          Platform: x86-64
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Linux-pv_ops dom0
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: silversens@xxxxxxxxx


I've been using Xen on different x86 platforms without any troubles.
I'm trying it for the first time on a pure x86_64 system.

Everything went well for xen compilation, same for compiling dom0 kernel, and
booting on it.
But when I tryed to start my first VM, a kernel panic appeared, I've been
trying upgrading to a newer dom0 kernel and the 4.0 release of xen, nothing
helped, still the same behavior.

I realised that when i was commenting the line concerning the vif interface I
had no more problems.

Here's what I get (and see attached my dom0 .config file for kernel 2.6.32) :

$ xm create /etc/xen/first_vm

[  123.670637]   alloc irq_desc for 745 on node 0
[  123.670641]   alloc kstat_irqs on node 0
[  123.729203] BUG: unable to handle kernel NULL pointer dereference at
0000000000000008
[  123.729569] IP: [<ffffffff81321416>] netback_uevent+0x1e/0xb6
[  123.729771] PGD 72afb067 PUD 72aa3067 PMD 0 
[  123.730003] Oops: 0000 [#1] SMP 
[  123.730003] last sysfs file: /sys/devices/vif-1-0/uevent
[  123.730003] CPU 0 
[  123.730003] Modules linked in:
[  123.730003] Pid: 934, comm: udevd Not tainted 2.6.32.12 #2         
[  123.730003] RIP: e030:[<ffffffff81321416>]  [<ffffffff81321416>]
netback_uevent+0x1e/0xb6
[  123.730003] RSP: e02b:ffff880072b25da8  EFLAGS: 00010246
[  123.730003] RAX: 0000000000000000 RBX: ffff880072ae1800 RCX:
0000000000000000
[  123.730003] RDX: 0000000000000037 RSI: ffff8800720cc000 RDI:
0000000000000000
[  123.730003] RBP: ffff880072b25dc8 R08: 0000000000000002 R09:
0000000000000073
[  123.730003] R10: 00000000000006a5 R11: 000000000002d1af R12:
ffff8800720cc000
[  123.730003] R13: ffff880072ae1800 R14: ffffffff8192c9f8 R15:
ffff880034b85000
[  123.730003] FS:  00007f2cea4126f0(0000) GS:ffff880001fa1000(0000)
knlGS:0000000000000000
[  123.730003] CS:  e033 DS: 0000 ES: 0000 CR0: 000000008005003b
[  123.730003] CR2: 0000000000000008 CR3: 0000000072b03000 CR4:
0000000000002660
[  123.730003] DR0: 0000000000000000 DR1: 0000000000000000 DR2:
0000000000000000
[  123.730003] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7:
0000000000000400
[  123.730003] Process udevd (pid: 934, threadinfo ffff880072b24000, task
ffff88007283adc0)
[  123.730003] Stack:
[  123.730003]  ffff880072ae1840 ffff8800720cc000 ffff880072ae1800
ffffffff8192c9f8
[  123.730003] <0> ffff880072b25df8 ffffffff81312e2c ffff880072ae1840
ffff8800720cc000
[  123.730003] <0> ffff88007401d480 ffff880072ae1850 ffff880072b25e28
ffffffff8138ce3b
[  123.730003] Call Trace:
[  123.730003]  [<ffffffff81312e2c>] xenbus_uevent_backend+0x90/0xab
[  123.730003]  [<ffffffff8138ce3b>] dev_uevent+0x102/0x146
[  123.730003]  [<ffffffff8138db22>] show_uevent+0x81/0xd7
[  123.730003]  [<ffffffff8138cafd>] dev_attr_show+0x22/0x49
[  123.730003]  [<ffffffff810ba1b2>] ? __get_free_pages+0x9/0x46
[  123.730003]  [<ffffffff8113df56>] sysfs_read_file+0xac/0x12e
[  123.730003]  [<ffffffff810ed94a>] vfs_read+0xa6/0x103
[  123.730003]  [<ffffffff810eda5d>] sys_read+0x45/0x69
[  123.730003]  [<ffffffff81011a82>] system_call_fastpath+0x16/0x1b
[  123.730003] Code: 00 00 0f 86 78 fe ff ff e9 e4 fb ff ff 55 48 89 e5 41 56
41 55 41 54 49 89 f4 53 48 89 fb 48 8d 7f 40 e8 84 e0 06 00 31 c9 31 ff <4c> 8b
68 08 48 8b 73 08 48 c7 c2 d6 1c 84 81 e8 e9 05 ff ff 49 
[  123.730003] RIP  [<ffffffff81321416>] netback_uevent+0x1e/0xb6
[  123.730003]  RSP <ffff880072b25da8>
[  123.730003] CR2: 0000000000000008
[  123.730003] ---[ end trace e62360ceb21167c0 ]---


Here's my VM config :

kernel = "/usr/lib/xen/boot/hvmloader"
builder='hvm'

name="test"
boot='c'
vnc = 1
sdl = 0
memory = 1024   # Memory size  
swap   = 128    # Swap size  
disk = [ 'phy:vg00/win2008_x64,ioemu:hda,w' ]
vif = [ 'type=ioemu, bridge=xenbr0' ]
keyboard='fr'


-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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