WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Changeset 19594 for Xen 3.4 build on Ubuntu Server 9.04

To: 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
From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
Date: Tue, 12 May 2009 11:14:10 -0700 (PDT)
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Keir Fraser <Keir.Fraser@xxxxxxxxxxxxx>
Delivery-date: Tue, 12 May 2009 11:14:42 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1242152050; bh=UrYQCjZy6oG8QLediG7su4/2vcr8BhITzq6r4A9xtCM=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=IqsygwY3trMLj3G7KSQ10Pki/qg0NwiIpMwOQ2Ik67NHD0YP3T0aqHTsxk+rA0bYCJYYnbBwih4iqAW1hSkz3x1FDeqfnJkX1G/RLKe7+UbVm70wlFeENAY7LZK0kCwxPA70ntMGO/MIyjKNUoN2NmzPV/XCpPqYuoGNujyCx+g=
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=aFj/QcqCpn0bJ3X8bmjkEoGms4cpqbSuk6pIN+n5HEUd+KdF12QREUOL8wo8BDlW61DkGl9AO353jJr1mefoOGbvCyvT0nwft6xgbTYtO4S0q8PFkolJMrXHWkcfJ/PjGCRYdLOCQVpz1RBc4IMZoNEa+F1Xs8fI+7yphW0HaXc=;
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <18953.44765.986437.108694@xxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bderzhavets@xxxxxxxxx
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx


--- 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