[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Xen-users] Virt-install and pygrub (bootloader)
- To: Alain Barthe <ab266061@xxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx, amazab@xxxxxxxx
- From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
- Date: Sun, 1 Jun 2008 03:20:42 -0700 (PDT)
- Delivery-date: Sun, 01 Jun 2008 03:21:18 -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=uJhi15Y7VTppjFQskxHWI5Xlg55hLdi5KApsALDIeq4VeOVBsf2J64OgOyCIkQEMqcKbu4cP+5rtcYYRz3aWMjOICrB/xjASv8s2MnoQlcq5tV80Z8lye8r4u9NuAbDDiK7FkKXZpspSuzYi+grINvuddCmmfm1Fg3W5/2g0gds=;
- List-id: Xen user discussion <xen-users.lists.xensource.com>
Creating same PV DomU at Xen 3.1 F8 Dom0 works fine. "xm list -l" reports that bootloader for PVM is /usr/bin/pygrub. Native pygrub on F8 Dom0 and pygrub compiled from source at Xen 3.2.1 F8 Dom0 have different lengths.I didn't run "diff" to get details. My guess is:- Virt-install creates image specific for "pygrub" bootloader - that is a root cause of issue. DomU create by virt-install from "python_libvirt" (F8 repos) is expecting native pygrub bootloader to be managed properly by "xm" When you try to do that at Xeb 3.2.1 Dom0 another ( not native) pygrub appears to be invoked as bootloader and it doesn't work. I also don't know how many python executables scripts might be invoked when " xm
start <Domain>" is issued. That is my inderstanding of the mess you've got after install "python_libvirt" from F8 repos. Actually, for hard core xen developer it shouldn't be a mess , but virt-install at Ubuntu 8.04 Dom0 (2-6.24-17-xen) is comletely useless at mean time. --- On Fri, 5/30/08, Boris Derzhavets <bderzhavets@xxxxxxxxx> wrote:
From: Boris Derzhavets <bderzhavets@xxxxxxxxx> Subject: Re: [Xen-users] Virt-install not working To: "Alain Barthe" <ab266061@xxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx, amazab@xxxxxxxx Date: Friday, May 30, 2008, 1:14 PM
--- On Thu, 5/29/08, amazab@xxxxxxxx <amazab@xxxxxxxx> wrote:
From: amazab@xxxxxxxx <amazab@xxxxxxxx> Subject: Re: [Xen-users] Virt-install not working To: "Alain Barthe" <ab266061@xxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx Date: Thursday, May 29, 2008, 12:39 PM
It worked, Thanks Alain.
However, I still have further problems:
1- I still cannot get "Virtual Machine Manager" to work, I feel it is another configurations problem ***************************************************** Actually, one doesn't need virt-manager to manipulate with Domains created by virt-install (like on
Nevada) xm start <Domain> xm shutdown <Domain> xm console <Domain> xm reboot <Domain> All this commands hangs with PV CentOS 5.1 DomU at Xen 3.2.1 F8 Dom0 (64-bit). DomU has been successfully created with virt-install installed from F8 repositories ************************************************ 2- I created a domain using the "xm create <domain name>" then I just shut it down. When I do "xm start <domain name>" it says "<domain name> does not exist". How can I get xm to recognize previously created domains.
3- How can I see the Xen logs from Dom-0. Where are they saved? Is there a specific toold to see events that occur in the hypervisor during the real time?
Ahmed
> With xen 3.0, the parameter "xend-unix-server" must be set to "yes" in > the > /etc/xen/xend-config.sxp configuration file for virt-manager and >
virt-install to work. It is set to "no" by default. Maybe it is the same > with xen 3.2. > > Hope this helps. > > Alain Barthe > > 2008/5/29 <amazab@xxxxxxxx>: > >> Hi all, >> >> I installed Xen 3.2.1 on FC8 from the source, It is working fine and I >> even created a virtual machine, however I cannot use the "Virtual >> Machine >> Manager" it does not even respond and when I try to use virt-install, I >> get the message: >> >> Traceback (most recent call last): >> File "/usr/sbin/virt-install", line 502, in <module> >> main() >> File "/usr/sbin/virt-install", line 345, in main >> conn = cli.getConnection(options.connect) >> File "/usr/lib/python2.5/site-packages/virtinst/cli.py", line 76, in >> getConnection >> return
libvirt.open(connect) >> File "/usr/lib/python2.5/site-packages/libvirt.py", line 135, in open >> if ret is None:raise libvirtError('virConnectOpen() failed') >> libvirtError: virConnectOpen() failed >> >> >> Thanks In Advance, >> Ahmed >> >> _______________________________________________ >> 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 |
_______________________________________________ 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
|