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

RE: [Xen-ia64-devel] IA64 using Redhat 5.1: xm create fails: Hotplugscri

To: "Kayvan Sylvan" <kayvan@xxxxxxxxx>, "Tristan Gingold" <tgingold@xxxxxxx>
Subject: RE: [Xen-ia64-devel] IA64 using Redhat 5.1: xm create fails: Hotplugscripts not working.
From: "Zhang, Xing Z" <xing.z.zhang@xxxxxxxxx>
Date: Wed, 14 Nov 2007 10:06:12 +0800
Cc: xen-ia64-devel <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 13 Nov 2007 18:07:17 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C2E6BA7FD3442A4C916735460ABB064F02E92ADC@xxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
References: <FF386CB4AE0E4648B0A96060EC00F36C4ECF94@xxxxxxxxxxxxxxxxxxxxxxxxxxxx><C2E6BA7FD3442A4C916735460ABB064F02BB273F@xxxxxxxxxxxxxxxxxxxx><20071113193405.GA2495@saphi> <C2E6BA7FD3442A4C916735460ABB064F02E92ADC@xxxxxxxxxxxxxxxxxxxx>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcgmKz6HT/36edU9S+KWyFo7yrHfogAK5QGwAAJ4DNA=
Thread-topic: [Xen-ia64-devel] IA64 using Redhat 5.1: xm create fails: Hotplugscripts not working.
Do you check your "disk" parameter is right? 
"Error: Device 768 (vbd) could not be connected. Hotplug scripts
not working." often has relation to un-correct disk image path or you mount the 
image somewhere but forget unmount it.
In the newest XEN/IA64 changeset, the error info is more readable, you can 
update to a new one.
If you want to debug it, see /var/log/xen/xend.log and search key word "Error". 
Then you can get a series of python error info.
The python code of Xend is at /usr/lib/python/xen. Good luck.

Good good study,day day up ! ^_^
-Wing(zhang xin)

OTC,Intel Corporation
>-----Original Message-----
>From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
>[mailto:xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx] On
>Behalf Of Kayvan Sylvan
>Sent: 2007?11?14? 8:43
>To: Tristan Gingold
>Cc: xen-ia64-devel
>Subject: RE: [Xen-ia64-devel] IA64 using Redhat 5.1: xm create
>fails: Hotplugscripts not working.
>
>I tried commenting the vif= line out and I get:
>
>Error: Device 768 (vbd) could not be connected. Hotplug scripts
>not
>working.
>
>I'm also not getting a console or anything else that I can
>interact
>with.
>
>I'm not sure how to proceed to try to debug this.
>
>Thanks for any suggestions!
>
>---Kayvan
>
>-----Original Message-----
>From: Tristan Gingold [mailto:tgingold@xxxxxxx]
>Sent: Tuesday, November 13, 2007 11:34 AM
>To: Kayvan Sylvan
>Cc: xen-ia64-devel
>Subject: Re: [Xen-ia64-devel] IA64 using Redhat 5.1: xm create
>fails:
>Hotplug scripts not working.
>
>On Tue, Nov 13, 2007 at 07:06:13AM -0800, Kayvan Sylvan wrote:
>> Hi everyone,
>>
>> I'm trying to bring up an hvm guest on a Redhat Enterprise
>Linux 5.1
>on an IA64 host machine.
>>
>[...]
>> vif = [ 'type=ioemu, mac=00:16:3e:00:dd:11, bridge=xenbr0' ]
>[...]
>> Error: Device 0 (vif) could not be connected. Hotplug scripts
>not
>working.
>
>Try to disable vif as vif fails to connect.
>
>Did you setup the ethernet bridge ?
>
>Tristan.
>
>_______________________________________________
>Xen-ia64-devel mailing list
>Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>http://lists.xensource.com/xen-ia64-devel

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

<Prev in Thread] Current Thread [Next in Thread>