thr3ads.net - Xen users - [Xen-users] Please help, I get a kernel panic on all DomUs when setting vif in VM config file [May 2010]

If this information is useful, please help other people find it:
Share via:

Pierre CHAUSSEE

2010-May-17 16:43 UTC

[Xen-users] Please help, I get a kernel panic on all DomUs when setting vif in VM config file

I just don''t get it.
I''ve been using Xen for quite a long time, never had any trouble on
x86, so
I''m trying to move on an x86_64 platform.

Everything went well (building, booting on Dom0, ...) except that I can only
start my VMs when vif parameter is not filled !
When I remove the comment on my "vif  = [ ''type=ioemu,
bridge=xenbr0'' ]"
then I get a kernel panic.

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


And here''s the kernel panic output :

$ xm create /etc/xen/first_vm

[  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 ]---


Please help ! I''ve been trying this for days...


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

Fajar A. Nugraha

2010-May-18 03:33 UTC

head link

Re: [Xen-users] Please help, I get a kernel panic on all DomUs when setting vif in VM config file

On Mon, May 17, 2010 at 11:43 PM, Pierre CHAUSSEE <silversens@gmail.com>
wrote:> I just don''t get it.
> I''ve been using Xen for quite a long time, never had any trouble
on x86, so
> I''m trying to move on an x86_64 platform.
>
> Everything went well (building, booting on Dom0, ...) except that I can
only
> start my VMs when vif parameter is not filled !
> When I remove the comment on my "vif  = [ ''type=ioemu,
bridge=xenbr0'' ]"
> then I get a kernel panic.
>
> Here''s my VM config :
>
> kernel = "/usr/lib/xen/boot/hvmloader"
Usually I put this as well:
device_model = ''/usr/lib64/xen/bin/qemu-dm''
>
> builder=''hvm''
>
> name="test"
> boot=''c''
> vnc = 1
> sdl = 0
> memory = 1024   # Memory size
> swap   = 128    # Swap size
where did you get instruction to use "swap" from?
> disk = [ ''phy:vg00/win2008_x64,ioemu:hda,w'' ]
for x64 windows, I think you also need to specify
acpi=1
apic=1
pae=1
>
> vif = [ ''type=ioemu, bridge=xenbr0'' ]
try removing "type=ioemu"
> keyboard=''fr''
>
> And here''s the kernel panic output :
>
> $ xm create /etc/xen/first_vm
>
> [  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
What dom0 kernel are you using? It''s often best to start with
known-good setup first. Centos or Opensuse with their bundled Xen
version is a good start.

-- 
Fajar

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

Pierre CHAUSSEE

2010-May-18 05:45 UTC

head link

Re: [Xen-users] Please help, I get a kernel panic on all DomUs when setting vif in VM config file

>> I just don''t get it.
>> I''ve been using Xen for quite a long time, never had any
trouble on x86, so
>> I''m trying to move on an x86_64 platform.
>> 
>> Everything went well (building, booting on Dom0, ...) except that I can
only
>> start my VMs when vif parameter is not filled !
>> When I remove the comment on my "vif  = [ ''type=ioemu,
bridge=xenbr0'' ]"
>> then I get a kernel panic.
>> 
>> Here''s my VM config :
>> 
>> kernel = "/usr/lib/xen/boot/hvmloader"
> 
> Usually I put this as well:
> device_model = ''/usr/lib64/xen/bin/qemu-dm''
> 
>> 
>> builder=''hvm''
>> 
>> name="test"
>> boot=''c''
>> vnc = 1
>> sdl = 0
>> memory = 1024   # Memory size
>> swap   = 128    # Swap size
> 
> where did you get instruction to use "swap" from?
> 
>> disk = [ ''phy:vg00/win2008_x64,ioemu:hda,w'' ]
> 
> for x64 windows, I think you also need to specify
> acpi=1
> apic=1
> pae=1
> 
>> 
>> vif = [ ''type=ioemu, bridge=xenbr0'' ]
> 
> try removing "type=ioemu"
I just tried all of those. It didn''t help I still get my kernel panic.

> 
>> keyboard=''fr''
>> 
>> And here''s the kernel panic output :
>> 
>> $ xm create /etc/xen/first_vm
>> 
>> [  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
> 
> What dom0 kernel are you using? It''s often best to start with
> known-good setup first. Centos or Opensuse with their bundled Xen
> version is a good start.
Well I''ve been trying 2.6.27, 2.6.31 and this one is 2.6.32.
Yeah thank you for the tip with known good setups, but the thing is
it''s not my first Xen setup, and I''m trying to port it to
Crux.
I already did that for x86, but for x86_64 I get those problems...

Thank you very much for trying to help !
> 
> -- 
> Fajar

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

Fajar A. Nugraha

2010-May-18 05:57 UTC

head link

Re: [Xen-users] Please help, I get a kernel panic on all DomUs when setting vif in VM config file

On Tue, May 18, 2010 at 12:45 PM, Pierre CHAUSSEE <silversens@gmail.com>
wrote:>>> And here''s the kernel panic output :
>>>
>>> $ xm create /etc/xen/first_vm
>>>
>>> [  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
>>
>> What dom0 kernel are you using? It''s often best to start with
>> known-good setup first. Centos or Opensuse with their bundled Xen
>> version is a good start.
>
> Well I''ve been trying 2.6.27, 2.6.31 and this one is 2.6.32.
> Yeah thank you for the tip with known good setups, but the thing is
> it''s not my first Xen setup, and I''m trying to port it to
Crux.
> I already did that for x86, but for x86_64 I get those problems...
FWIW, I use 2.6.32.13  +
http://code.google.com/p/gentoo-xen-kernel/downloads/detail?name=xen-patches-2.6.32-2.tar.bz2&can=1&qon
top of RHEL5, and it works fine with regards to vif. There''s a
problem with blktap/blktap2, but that''s another story. So if all
fails, you might want to try that one.

-- 
Fajar

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

Xen users - May 2010 - Please help, I get a kernel panic on all DomUs when setting vif in VM config file

[Xen-users] Please help, I get a kernel panic on all DomUs when setting vif in VM config file

Re: [Xen-users] Please help, I get a kernel panic on all DomUs when setting vif in VM config file

Re: [Xen-users] Please help, I get a kernel panic on all DomUs when setting vif in VM config file

Re: [Xen-users] Please help, I get a kernel panic on all DomUs when setting vif in VM config file