On 24 Dec 2009, at 8:59pm, Alxen4 wrote:
> Brand new IBM x3650,16G RAM,
> Totally fresh installation of Nevada,b129,no modifications done,only enabled 
> XVM and created couple of DomU

Did you do any stability testing of the system before enabling xVM?

> Dom0 network and DomU network sit on dedicated interfaces,

Please describe this more. Do you have multiple network interfaces and only one 
of them fails?

> Dom0 network crashes(becomes unresponsive) every 30 min ,the only way to fix 
> it is to reboot the server.

Unresponsive in what way? If you have existing connection (ssh, for example), 
does it stop working, or is it only new connections?

> 
> The funny thing is DomU network stays on,no problem,so I can access all 
> guests...
> 
> /var/adm/messages shows bunch of messages at the very moment of crash,but I 
> can't relate any of them to the issue(even after googling)
> 
> 
> ------------------------------------
> 
> Dec 24 13:06:46 storage0 gnome-session[1153]: [ID 702911 daemon.warning] 
> WARNING: IceListenForConnections returned 2 non-local listeners: 
> inet/storage0:43894,
> inet6/storage0:36702
> Dec 24 13:06:46 storage0 gnome-session[1153]: [ID 702911 daemon.warning] 
> WARNING: Could not connect to ConsoleKit: Could not get owner of name 
> 'org.freedeskto
> p.ConsoleKit': no such name
> Dec 24 13:06:46 storage0 last message repeated 1 time
> Dec 24 13:06:51 storage0 pseudo: [ID 129642 kern.info] pseudo-device: pm0
> Dec 24 13:06:51 storage0 genunix: [ID 936769 kern.info] pm0 is /pseudo/p...@0
> Dec 24 13:06:51 storage0 genunix: [ID 127566 kern.info] device 
> pciclass,030...@0(display#0) keeps up device s...@0,0(sd#0), but the former 
> is not power managed
> Dec 24 13:11:59 storage0 mac: [ID 469746 kern.info] NOTICE: e1000g1 registered
> Dec 24 13:11:59 storage0 e1000g: [ID 766679 kern.info] Intel(R) PRO/1000 
> Network Connection, Driver Ver. 5.3.18
> 
> 
> Please HELP !
> 
> Thanks a lot.
> -- 
> This message posted from opensolaris.org
> _______________________________________________
> xen-discuss mailing list
> [email protected]

_______________________________________________
xen-discuss mailing list
[email protected]

Reply via email to