Xen project Mailing List

Re: [Xen-users] What is pygrub status in Xen 3.2.1 ? (just a minor fix is required)

From: Boris Derzhavets <bderzhavets@xxxxxxxxx>

Date: Sun, 1 Jun 2008 10:57:09 -0700 (PDT)

Delivery-date: Sun, 01 Jun 2008 10:57:44 -0700

Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Received:X-Mailer:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Message-ID; b=u3LKmpeHzjBU2wDS382e+xfSNcL2UUnyurd+/wmYgw5FQ+Fj/pkA8K/g7P1YebviZ4ylOUcxhTPivYalEeK5+8Z/cXfrew5YbRpXyfiUIPpd9gJ61bfLNhHoUdP9AdO+F5LstaocPo6KGxpeQ3frGcOp7BUGuH49C/fpNOJdgg0=;

List-id: Xen user discussion <xen-users.lists.xensource.com>

Ok. I got it done due to :-

http://lists.xensource.com/archives/html/xen-bugs/2008-04/msg00051.html

1. Install F8 xen disabled
2.yum install python_libvirt
3.Install Xen 3.2.1 from source on F8 instance.
4. Perform virt-install PV CentOS 5.1 DomU
The way i did ( just the first try)
DomU hanged at reboot
# xm destroy <Domain>
# xm delete <Domain>
5. Fixed /usr/bin/pygrub.
6. Cretated RHLPV:-
[root@dhcppc0 xen]# cat RHELPV
name = "RHELPV"
maxmem = 1024
memory = 1024
vcpus = 1
bootloader = "/usr/bin/pygrub"

# vfb = [ ]
disk = [ "phy:/dev/sdb12,xvda,w" ]
vif = [ "bridge=eth2" ]

7. Started up DomU:-
# xm create -c RHLPV
Domain started fine.

Now , I believe there wouldn't be any need destroy and delete Domain.
It should work with fixed pygrub through :-
xm start/shutdown/reboot <Domain>

--- On Sun, 6/1/08, Boris Derzhavets <bderzhavets@xxxxxxxxx> wrote:

From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
Subject: [Xen-users] What is pygrub status in Xen 3.2.1 ?
To: xen-users@xxxxxxxxxxxxxxxxxxx
Date: Sunday, June 1, 2008, 1:23 PM

Looking at http://strugglers.net/~andy/blog/2008/01/20/red-hat-based-linux-under-xen-from-debian-etch/
I found following statement.
Quote:-
Andy Says:
March 29th, 2008 at 2:42 am
Hi,

The broken pygrub is not a security bug so not going to be fixed at least until the next stable release I suppose.

Do you have the details of the pygrub exploit? I thought I saw it fixed, which is what I would expect as a security issue.

If youʼre just here to bash Debian then Iʼm not really interested however.
My concern is failure to manage with "xm" CentOS 5.1 DomU at Xen 3.2.1 F8 Dom0 after successful DomU creating by virt-install obtained as a result of "yum install python_libvirt" on xen-disabled F8 instance (64-bit)
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

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