[Top] [All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Virt-install not working

  • To: amazab@xxxxxxxx, xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
  • Date: Thu, 29 May 2008 09:32:42 -0700 (PDT)
  • Delivery-date: Thu, 29 May 2008 09:33:28 -0700
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Message-ID; b=2m8frutXQMRnqZUquirJSDA0gmxd2jADKAf5XkF67zYLar4DHAGdx+4NKdkQPPqoyEF2FRpQTwwEbHh0LhRMeAV6eSssRPBIAKTGJQRYR7d8IlGefxTKwRoT8I3rwBwszPTzIlK0KN/dSkjKToITnnYlizTEzGKCOq7m+44dXXg=;
  • List-id: Xen user discussion <xen-users.lists.xensource.com>
Ahmed,

 I've just checked my own F8(64-bit) instance been installed xen-disabled
with Xen 3.2.1 compiled from source on top of it. No virt-install python
executable script on the system.
As far as to my knowledge (regarding Xen 3.2.X Linux Dom0s) only Ubuntu 8.04 pretend to have virt-install ready to go in it's Repositories at mean time. I've just filed a bug on mentioned case.
What about your stuff ...
1. Perform F8 clean install (xen-disabled) (better CentOS 5.1)
2. Build Xen
# cd /usr/src/
# hg clone http://xenbits.xensource.com/xen-3.2-testing.hg
# cd xen-3.2-testing.hg
# make world
# make install
and etc.

No mess and no virt-install :-)
I guess the best case scenario Ubuntu 8.04.01 , hopefully with
working virt-install.

Thank you.
Boris

----- Original Message ----
From: "amazab@xxxxxxxx" <amazab@xxxxxxxx>
To: xen-users@xxxxxxxxxxxxxxxxxxx
Cc: Boris Derzhavets <bderzhavets@xxxxxxxxx>
Sent: Thursday, May 29, 2008 12:05:23 PM
Subject: Re: [Xen-users] Virt-install not working

That is absolutely right! When I installed Xen from the source, there were
no virt-install associated with it. That is why I built mine from the FC8
repository!!

How can I reorganize this mess?

Ahmed

> Ahmed,
> Building Xen 3.2.1 from source via cloning Mercurial
> Repository@xxxxxxxxxxxxx
> to CentOS 5.1 instance (been installed as xen-disabled) doesn't creaty new
> "virt-install"
> file at all. Please , make sure that virt-install you fire up ,
> hasn't been installed with F8's files and is newly generated file during
> Xen 3.2.1 building from source.
> Thank you.
> Boris"Boris Derzhavets" <bderzhavets@xxxxxxxxx>
>
>
> ----- Original Message ----
> From: "amazab@xxxxxxxx" <amazab@xxxxxxxx>
> To: xen-users@xxxxxxxxxxxxxxxxxxx
> Cc: Cliff Pratt <enkiduonthenet@xxxxxxxxx>
> Sent: Thursday, May 29, 2008 11:17:28 AM
> Subject: Re: [Xen-users] Virt-install not working
>
>> On Thu, May 29, 2008 at 10:43 AM,  <amazab@xxxxxxxx> wrote:
>>> 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
>>>
>> Hi, Are you booted off the correct kernel?
>
> Yeah sure, it is 2.6.18.8-Xen, I got it through mercurial after I totally
> failed to convince the Xen source to use the downloaded tarball. However,
> I feel that i have a problem with Xend, as I got the following errors in
> the Xend log.
>
> [2008-05-29 10:56:14 3622] INFO (SrvDaemon:331) Xend Daemon started
> [2008-05-29 10:56:14 3622] INFO (SrvDaemon:335) Xend changeset:
> unavailable.
> [2008-05-29 10:56:14 3622] INFO (SrvDaemon:342) Xend version: Unknown.
> [2008-05-29 10:56:14 3622] INFO (XendNetwork:114) Not recreating missing
> unmanaged network tmpbridge
> [2008-05-29 10:56:14 3622] DEBUG (XendDomainInfo:132)
> XendDomainInfo.recreate({'max_vcpu_id': 1, 'cpu_time': 46531729537L,
> 'ssidref': 120, 'hvm': 0, 'shutdown_reason': 0, 'dying': 0,
> 'online_vcpus': 2, 'domid': 0, 'paused': 0, 'crashed': 0, 'running': 1,
> 'maxmem_kb': 4294967292L, 'shutdown': 0, 'mem_kb': 1048576L, 'handle': [0,
> 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], 'blocked': 0, 'name':
> 'Domain-0'})
> [2008-05-29 10:56:14 3622] INFO (XendDomainInfo:149) Recreating domain 0,
> UUID 00000000-0000-0000-0000-000000000000. at /local/domain/0
> [2008-05-29 10:56:14 3622] DEBUG (XendDomainInfo:2195) Storing VM details:
> {'on_xend_stop': 'ignore', 'shadow_memory': '0', 'uuid':
> '00000000-0000-0000-0000-000000000000', 'on_reboot': 'restart', 'image':
> '(linux (kernel ))', 'on_poweroff': 'destroy', 'on_xend_start': 'ignore',
> 'on_crash': 'restart', 'xend/restart_count': '0', 'vcpus': '2',
> 'vcpu_avail': '3', 'name': 'Domain-0'}
> [2008-05-29 10:56:14 3622] DEBUG (XendDomainInfo:1008) Storing domain
> details: {'name': 'Domain-0', 'console/limit': '1048576', 'memory/target':
> '1048576', 'vm': '/vm/00000000-0000-0000-0000-000000000000', 'domid': '0',
> 'security_label': '', 'cpu/0/availability': 'online',
> 'cpu/1/availability': 'online',
> 'control/platform-feature-multiprocessor-suspend': '1', 'console/type':
> 'xenconsoled'}
> [2008-05-29 10:56:14 3622] DEBUG (XendDomain:443) Adding Domain: 0
> [2008-05-29 10:56:14 3622] DEBUG (XendDomain:379) number of vcpus to use
> is 0
> [2008-05-29 10:56:14 3622] DEBUG (XendDomainInfo:1092)
> XendDomainInfo.handleShutdownWatch
> [2008-05-29 10:56:14 3622] WARNING (XendAPI:678) API call: VBD.set_device
> not found
> [2008-05-29 10:56:14 3622] WARNING (XendAPI:678) API call: VBD.set_type
> not found
> [2008-05-29 10:56:14 3622] WARNING (XendAPI:678) API call:
> session.get_all_records not found
> [2008-05-29 10:56:14 3622] WARNING (XendAPI:678) API call:
> event.get_record not found
> [2008-05-29 10:56:14 3622] WARNING (XendAPI:678) API call: event.get_all
> not found
> [2008-05-29 10:56:15 3622] WARNING (XendAPI:678) API call:
> VM.get_auto_power_on not found
> [2008-05-29 10:56:15 3622] WARNING (XendAPI:678) API call:
> VM.set_auto_power_on not found
> [2008-05-29 10:56:15 3622] WARNING (XendAPI:678) API call: VIF.get_network
> not found
> [2008-05-29 10:56:15 3622] WARNING (XendAPI:678) API call: VIF.set_device
> not found
> [2008-05-29 10:56:15 3622] WARNING (XendAPI:678) API call: VIF.set_MAC not
> found
> [2008-05-29 10:56:15 3622] WARNING (XendAPI:678) API call: VIF.set_MTU not
> found
> [2008-05-29 10:56:15 3622] WARNING (XendAPI:678) API call: debug.get_all
> not found
> [2008-05-29 10:56:15 3622] INFO (XMLRPCServer:149) Opening Unix domain
> socket XML-RPC server on /var/run/xend/xen-api.sock; authentication has
> been disabled for this server.
> [2008-05-29 10:56:15 3622] INFO (XMLRPCServer:149) Opening Unix domain
> socket XML-RPC server on /var/run/xend/xmlrpc.sock.
>
>
>>
>> Cheers,
>>
>> Cliff
>>
>
>
> _______________________________________________
> 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

 

©2013 Xen Project, A Linux Foundation Collaborative Project. All Rights Reserved.
Linux Foundation is a registered trademark of The Linux Foundation.
Xen Project is a trademark of The Linux Foundation.

Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.