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

Re: [Xen-users] xen 3.2.0 problems with DomU freezing... ubuntu 7.10

To: Casper <kl@xxxxx>
Subject: Re: [Xen-users] xen 3.2.0 problems with DomU freezing... ubuntu 7.10
From: "Todd Deshane" <deshantm@xxxxxxxxx>
Date: Sat, 26 Jan 2008 00:40:59 -0500
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 25 Jan 2008 21:41:34 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:references; bh=GiNYR2Qf4tsXrhxOrt33K7QwVZ8SH3EMs/mJV0WV6I8=; b=diYLJmbSeVTO1Bxsphi6JmQzEGhqOwafFCQrFh4+c3CYa/G52OzYSG/p2A1ihbrJSdhBrd9mr5wdw46UjWFdOpbotBKZZvDppF1brEPVHOaxxz1pDJakJdBNGK9Fxg7JshH3Htt3kyoi33BQkYfyhWAgxnz77FnHptc/tIoWc7E=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:references; b=C0x9RmZBBQ0uEoGehYjfa3SuC4CZWku4uNTzgJtfBhJ5ET/K48E7l5GBUCocXbMV3c78ykpVS4eeo3/WPnkurOzXRDT1DOlrdkhuBVrRsquaO3hoNCKGFi6xmWjP19ZBS1V3ZBIvZnT+1pXAwF57qZiOK1/jpusTO2kwXT74AvQ=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <4798F838.50304@xxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <47988B08.1010905@xxxxx> <1e16a9ed0801240946u5732ef1ao337beeab5e2c9397@xxxxxxxxxxxxxx> <4798F838.50304@xxxxx>
Reply-to: deshantm@xxxxxxxxx
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx


On Jan 24, 2008 3:42 PM, Casper <kl@xxxxx> wrote:

You mean about bridge or DomU starting?

For bridge with xen 3.1.x from source Ubuntu was problem with
/etc/xen/scripts/network-bridge script (line #62):
-vifnum=${vifnum:-$(ip route list | awk '/^default / { print $NF }' |
sed 's/^[^0-9]*//')}
+vifnum=${vifnum:-$(netstat -arn | awk '/^0.0.0.0 / { print $NF }' | sed
's/^[^0-9]*//')}

In 3.2 didn`t find this line... there is something wrong with it?

I can try to search about DomU starting, if you will point me what the
problem in Ubuntu, or give some urls...

This is the specific bug I was referring to:
https://bugs.launchpad.net/ubuntu/+source/xen-3.1/+bug/144631

I don't think it has been solved. I will need to test myself, but based on what I have read recently on this list it hasn't been.

Zoran's reply (earlier) is basically one of the workarounds.

Regards,
Todd
 

thank you Todd,

K.

Todd Deshane wrote:
> There are Ubuntu bugs related to this already with work arounds. Let me
> know if you have trouble finding them and I can try to did them up.
>
> Best regards,
> Todd
>
> On Jan 24, 2008 7:56 AM, Casper < kl@xxxxx <mailto:kl@xxxxx>> wrote:
>
>
>      Hello,
>
>      First of all, I wanted to thank all project members for great free
>     open source project... playing already with it more then year...
>
>      I wanted to test new xen 3.2.0 from src, compiled it just fine with
>     tips from mailing lists etc... Dom0 and DomU are fresh ubuntu 7.10...
>
>     I have problem DomU starting... xm list output seems ok:
>     Name            ID   Mem VCPUs      State   Time(s)
>     Domain-0        0   128     4     r-----     41.9
>     wiki            3   128     1     -b----      5.3
>
>     logs shows:
>     tail xend.log
>     [2008-01-24 14:22:20 4424] DEBUG (__init__:1094) Waiting for 0.
>     [2008-01-24 14:22:20 4424] DEBUG (__init__:1094) Waiting for devices
>     pci.
>     [2008-01-24 14:22:20 4424] DEBUG (__init__:1094) Waiting for devices
>     ioports.
>     [2008-01-24 14:22:20 4424] DEBUG (__init__:1094) Waiting for devices
>     tap.
>     [2008-01-24 14:22:20 4424] DEBUG (__init__:1094) Waiting for devices
>     vtpm.
>     [2008-01-24 14:22:20 4424] INFO (__init__:1094) Domain wiki (3)
>     unpaused.
>
>     tail domain-builder-ng.log
>           anon mmap          : 0 bytes
>        mapped
>           file mmap          : 8232 kB
>           domU mmap          : 20348 kB
>     arch_setup_bootlate: shared_info: pfn 0x0, mfn 0x1ae
>     shared_info_x86_32: called
>     vcpu_x86_32: called
>     vcpu_x86_32: cr3: pfn 0x14d3 mfn 0x11d54c
>     launch_vm: called, ctxt=0x86f1704
>     xc_dom_release: called
>
>
>     in cosole ubuntu 7.10 server kernel output stops at:
>
>     EDD information not available.
>     Freeing unused kernel memory: 196k freed
>     fuse init (API version 7.7)
>     EXT3-fs: INFO: recovery required on readonly filesystem.
>     EXT3-fs: write access will be enabled during recovery.
>     kjournald starting.  Commit interval 5 seconds
>     EXT3-fs: recovery complete.
>     EXT3-fs: mounted filesystem with ordered data mode.
>     lp: driver loaded but no devices found
>
>     and nothing more...
>     Couldn`t find any error msg to debug it...
>
>
>     Another question is about network bridges in Ubuntu, xen 3.1.x brctl
>     shows xenbr* but xen 3.2.0:
>     # brctl show
>     bridge name     bridge id               STP enabled     interfaces
>     eth0            8000.001d0900ab21       no              peth0
>
>     Now I must use vif = ['bridge=eth0'] network bridge?
>
>     Any ideas to put me in right direction?
>
>     thanks to all,
>
>     Casper
>
>     _______________________________________________
>     Xen-users mailing list
>     Xen-users@xxxxxxxxxxxxxxxxxxx <mailto:Xen-users@xxxxxxxxxxxxxxxxxxx>

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>