Xen project Mailing List

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>
> http://lists.xensource.com/xen-users
>
>

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