[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-users] Re: XEN 3.1: critical bug: vif init failure after creating 15-17 VMs (XENBUS: Timeout connecting to device: device/vif)
- To: Keir Fraser <keir@xxxxxxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
- From: Eric Tessler <maiden1134@xxxxxxxxx>
- Date: Sat, 14 Jul 2007 23:15:10 -0700 (PDT)
- Cc: "mark.williamson@xxxxxxxxxxxx" <mark.williamson@xxxxxxxxxxxx>
- Delivery-date: Sat, 14 Jul 2007 23:13:05 -0700
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=WsKPxZSMsTzarDDUWOwGvMAEmocDL8R0hWOW3os/SWZZ48vV0FeQZx+l5KhlJeyFdaWmO2mXNw7jHKoy74QZrUFwEMNOtgK5UbYhWW6c2xSoNucdWG+hHbU8CyVNgXBekTOigpYxKAEecheDh9NZQxX2o9OARmSYaLZq18ulgPc=;
- List-id: Xen user discussion <xen-users.lists.xensource.com>
I applied the patch and rebuilt XEN - this did indeed resolve the problem. My test now can create 40 VMs w/o any failures. I will leave the test running for a few days to make sure. Thanks for the help, Eric
Keir Fraser <keir@xxxxxxxxxxxxx> wrote: Now fixed in the staging tree. The patch (for your dom0 kernel) is also attached to this email.
Thanks for your help in tracking this one down!
-- Keir
On 14/7/07 07:43, "Keir Fraser" <keir@xxxxxxxxxxxxx> wrote:
What dom0 kernel image are you running? It looks like vmalloc_sync_all(), called from alloc_vm_area() has not caused
the pte that will map the rx ring to be made present in the currently-running page tables. The code looks okay on inspection though.
-- Keir
On 14/7/07 03:32, "Eric Tessler" <maiden1134@xxxxxxxxx> wrote:
Also, by suggestion of Keir, I tried the XEN 3.0.4 kernel in my 16th VM (2.6.16.33), it failed the same way. The only difference is that instead of extending the grant table from 4 to 5 frames, it was extended from 4 to 16 frames:
(XEN) grant_table.c:557:d18 Expanding dom (18) grant table from (4) to (16) frames.
(XEN) mm.c:2605:d0 Could not find L1 PTE for address d1400000
I believe the following stack trace represents the trace of the failure (starting from within XenBus, traced by hand):
connect_rings
linux-2.6-xen-sparse/drivers/xen/netback/xenbus.c
netif_map linux-2.6-xen-sparse/drivers/xen/netback/interface.c
map_frontend_pages linux-2.6-xen-sparse/drivers/xen/netback/interface.c
__gnttab_map_grant_ref (hypercall) xen/common/grant_table.c
create_grant_host_mapping xen/arch/x86/mm.c
create_grant_va_mapping xen/arch/x86/mm.c
guest_map_l1e
xen/arch/x86/mm.c
(this is the function that is ultimately failing)
Any clue as to what is causing this failure or how to fix it? Is there any other debug info I can provide here that would be of any help in resolving this issue? I have some free time tomorrow to debug this issue, but need some direction; this is in an area of XEN I don't understand very well.
Bored stiff? Loosen up...
Download and play hundreds of games for free on Yahoo! Games._______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
