Re: [Xen-devel] Changeset 19594 for Xen 3.4 build on Ubuntu Server 9.04 causes pygrub doesn't return any data anymore

[Boris Derzhavets <bderzhavets@xxxxxxxxx>]

--- On Tue, 5/12/09, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx> wrote:

From: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Changeset 19594 for Xen 3.4 build on Ubuntu Server 9.04 causes pygrub doesn't return any data anymore
To: "bderzhavets@xxxxxxxxx" <bderzhavets@xxxxxxxxx>
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxxx>
Date: Tuesday, May 12, 2009, 1:16 PM

Boris Derzhavets writes ("Re: [Xen-devel] Changeset 19594 for Xen 3.4 build
on Ubuntu Server 9.04 causes pygrub doesn't return any data anymore"):
> Yes, now
> # make install-xen
> # make install-tools
> commit
 builds

Good.

> Pygrub doesn't work ( i believe default path is incorrect ) and
> hotplug scripts don't work as well . The last problem makes Xen Host
> dead.

But xm create now appears to work ?  It's possible that the fix didn't
take properly for pygrub.  Or perhaps that you are running a version
leftover from a previous attempt ?
*******************************************************
No "xm create -f DomU.cfg" doesn't appear to work
( *.cfg profile has kernel,ramdisk,root,extra no pygrub
involvment). It's not leftover due to :-

# make clean
# make uninstall
# make install-xen
# make install-tools
# reboot
******************************************************

> I've tested Suse's 2.6.27.5 kernel under Xen 3.4 .
> It shows same behavior as 2.6.30-rc3-tip. Problem seems to be on Xen side.
> Otherwise,  backend drivers in both xen-ified and pvops kernel
 refuse to
repond

What errors are in the hotplug logfile ?
***************************************
No hotplug.log at all. 
DomU gets paused. Then it may be unpaused
or no , but some time later console reports
"(0) vif couldn't be connected. Hotplug scripts
not working"

root@ServerJaunty:/var/log/xen# ls -l

total 636
-rw-r--r-- 1 root root 148858 2009-05-12 12:58 domain-builder-ng.log
-rw-r--r-- 1 root root 125338 2009-05-12 12:55 xend-debug.log
-rw-r--r-- 1 root root 357212 2009-05-12 12:59 xend.log

xend.log:-

[2009-05-12 12:58:09 3993] DEBUG (XendDomainInfo:1708) XendDomainInfo.handleShutdownWatch
[2009-05-12 12:58:09 3993] DEBUG (DevController:139) Waiting for devices vif.
[2009-05-12 12:58:09 3993] DEBUG (DevController:144) Waiting for 0.
[2009-05-12 12:58:09 3993] DEBUG (DevController:629) hotplugStatusCallback /local/domain/0/backend/vif/2/0/hotplug-status.
[2009-05-12
 12:58:58 3993] INFO (XendDomain:1180) Domain FedoraPV (2) unpaused.
[2009-05-12 12:59:49 3993] DEBUG (XendDomainInfo:2723) XendDomainInfo.destroy: domid=2
[2009-05-12 12:59:49 3993] DEBUG (XendDomainInfo:2198) Destroying device model
[2009-05-12 12:59:49 3993] DEBUG (XendDomainInfo:2205) Releasing devices
[2009-05-12 12:59:49 3993] DEBUG (XendDomainInfo:2218) Removing vif/0
[2009-05-12 12:59:49 3993] DEBUG (XendDomainInfo:1133) XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0
[2009-05-12 12:59:49 3993] DEBUG (XendDomainInfo:2218) Removing vbd/51712
[2009-05-12 12:59:49 3993] DEBUG (XendDomainInfo:1133) XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/51712
[2009-05-12 12:59:49 3993] DEBUG (XendDomainInfo:2218) Removing console/0

Udev is in place:-

root@ServerJaunty:/var/log/xen# ps -ef|grep udev
root      1239     1  0 12:54 ?        00:00:00 /sbin/udevd --daemon

Bridge is
 correct.

Boris
*****************************************************************************************************************************

Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel