domU on x86_64 xenlinux problems

domU on x86_64 xenlinux problems

[Nakajima, Jun]

Before I dig deeper to debug, I'm wondering if I'm missing some setup
things. I see some improvements with the domU side last night (I used to
get an error from xend, and xm failed), but I still see problems like:

Using config file "/root/xmexample1".
Started domain domU
xenconsole: Could not read tty from store: No such file or directory

I used the latest tree,
changeset:   6453:3bbc9384be3f
tag:         tip
user:        kaf24@firebug.cl.cam.ac.uk
date:        Fri Aug 26 10:57:09 2005 +0000
summary:     Refactor sync_lazy_execstate_cpu() into the more sensible

Jun
---
Intel Open Source Technology Center 

Re: domU on x86_64 xenlinux problems

[Keir Fraser]

On 30 Aug 2005, at 18:27, Nakajima, Jun wrote:

> Before I dig deeper to debug, I'm wondering if I'm missing some setup
> things. I see some improvements with the domU side last night (I used 
> to
> get an error from xend, and xm failed), but I still see problems like:
>
> Using config file "/root/xmexample1".
> Started domain domU
> xenconsole: Could not read tty from store: No such file or directory

I think this is a known race between xenconsoled finding a new domain, 
setting up a tty, and writing the info into xenstore, versus xm trying 
to read the tty info out of xenstore.

At the very least, xm should poll a few times (perhaps with sleep 1 in 
between) before giving up. Even better if xenconsoled could do its 
stuff in a more timely fashion, but we probably can't rely on that even 
after it's fixed up (will depend on scheduling etc).

  -- Keir

RE: domU on x86_64 xenlinux problems

[Nakajima, Jun]

Keir Fraser wrote:
> On 30 Aug 2005, at 18:27, Nakajima, Jun wrote:
> 
>> Before I dig deeper to debug, I'm wondering if I'm missing some setup
>> things. I see some improvements with the domU side last night (I
>> used to get an error from xend, and xm failed), but I still see
>> problems like: 
>> 
>> Using config file "/root/xmexample1".
>> Started domain domU
>> xenconsole: Could not read tty from store: No such file or directory
> 
> I think this is a known race between xenconsoled finding a new domain,
> setting up a tty, and writing the info into xenstore, versus xm trying
> to read the tty info out of xenstore.

That sounds correct to me, as I saw domU just once and never saw it
again after that...

> 
> At the very least, xm should poll a few times (perhaps with sleep 1 in
> between) before giving up. Even better if xenconsoled could do its
> stuff in a more timely fashion, but we probably can't rely on that
> even after it's fixed up (will depend on scheduling etc).
> 
>   -- Keir

So, who's working on it? I want to check health of (SMP) domU with the
log-dirty shadow mode, and need some quick workaround to get domU.

Jun
---
Intel Open Source Technology Center

Re: domU on x86_64 xenlinux problems

[Anthony Liguori]

Hey Jun,

Some major console changes were checked in.  I'm investigating these 
problems right now.  While we've seen this error message before, it's 
never been under these circumstances (previously, it was because 
xenconsoled wasn't running, here it seems to be a new race condition).

Regards,

Anthony Liguori

Nakajima, Jun wrote:

>Before I dig deeper to debug, I'm wondering if I'm missing some setup
>things. I see some improvements with the domU side last night (I used to
>get an error from xend, and xm failed), but I still see problems like:
>
>Using config file "/root/xmexample1".
>Started domain domU
>xenconsole: Could not read tty from store: No such file or directory
>
>I used the latest tree,
>changeset:   6453:3bbc9384be3f
>tag:         tip
>user:        kaf24@firebug.cl.cam.ac.uk
>date:        Fri Aug 26 10:57:09 2005 +0000
>summary:     Refactor sync_lazy_execstate_cpu() into the more sensible
>
>Jun
>---
>Intel Open Source Technology Center 
>
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@lists.xensource.com
>http://lists.xensource.com/xen-devel
>
>  
>

Re: domU on x86_64 xenlinux problems

[Ryan Harper]

* Nakajima, Jun <jun.nakajima@intel.com> [2005-08-30 13:37]:
> So, who's working on it? I want to check health of (SMP) domU with the
> log-dirty shadow mode, and need some quick workaround to get domU.

For what its worth, I've successfully launched SMP domU domains on
x86_64, even tested HOTPLUG_CPU.  The console even works after the
domain is created, but '-c' on the xm create command spews the error you
were seeing.

% hg tip
changeset:   6481:551870a55f240791695d30fd7fa92a1bf4e48387
tag:         tip
user:        kaf24@firebug.cl.cam.ac.uk
date:        Tue Aug 30 12:53:49 2005
summary:     Unify access to mpt using macros.

(bebop) xm-test # xm info
system                 : Linux
host                   : bebop
release                : 2.6.12-xen0-smp
version                : #1 SMP Tue Aug 30 14:53:38 CDT 2005
machine                : x86_64
cores_per_socket       : 1
threads_per_core       : 1
cpu_mhz                : 2193
memory                 : 3583
free_memory            : 2989
(bebop) xm-test # xm list
Name              Id  Mem(MB)  CPU VCPU(s)  State  Time(s)
Domain-0           0      507    -      2   r----     30.6
default            1       32    -      4   -----     12.2
(bebop) xm-test # xm list -v
Name              Id  VCPU  CPU  CPUMAP
Domain-0           0     0    0  0x3
Domain-0           0     1    1  0x3
default            1     0    1  0xf
default            1     1    0  0xf
default            1     2    1  0xf
default            1     3    0  0xf

-- 
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
(512) 838-9253   T/L: 678-9253
ryanh@us.ibm.com

Re: domU on x86_64 xenlinux problems

[Keir Fraser]

On 30 Aug 2005, at 19:36, Nakajima, Jun wrote:

> So, who's working on it? I want to check health of (SMP) domU with the
> log-dirty shadow mode, and need some quick workaround to get domU.

Just run xm console manually.

  -- Keir