[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-users] Minios behaves strangely after startup
Looking at your post again, if dom0 does not show the vm started (no command "xx started" line after xm starting) and dom0 is on 0.0 it's not good. Show us your logs. Regards, Mark Simply, b means "blocked" which is just that that domU doesn't have anything to do so dom0 is not giving it any resources.
If you are trying to access a running PV domU from your dom0 you should try -c when booting or use Ctrl-] Regards, Mark Ok,
I got it "xm create -c domain_config" is the way. Still do not completely understand what is "b" state then.
Date: Sun, 12 Sep 2010 13:37:42 -0400
From: Grigory Makarevich <grigorymakarevich@xxxxxxxxx>
Subject: [Xen-users] Minios behaves strangely after startup
To: xen-users@xxxxxxxxxxxxxxxxxxx
Message-ID:
<AANLkTi=QYNy4L-Wk9+ZcF9HHVHj8rM0LkFXebdWTUR02@xxxxxxxxxxxxxx>
Content-Type: text/plain; charset="iso-8859-1"
Dear All,
I am quite new to xen. I have got and installed mercurial repository of xen.
I was able successfully run FC13 and Windows under the xen installation.
I have successfully compiled minios. When I run "xm create domain_config"
it prints
Using config file "./domain_config".
Started domain Mini-OS (id=12)
However, I do not see any promised printings.
The result of xm list command also shows that domain is blocked -
# xm list
XEND_DEBUG = 1
Name ID Mem VCPUs State
Time(s)
Domain-0 0 3068 8 r-----
2980.6
Mini-OS 12 32 1 -b----
0.0
wintest 2048 1
183.0
xenfirst 2048 1
87.6
Any idea/suggestion how to debug would be appreciated.
Thanks,
Best regards,
Grigory
|
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
