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] "Bad address" when "xm create"

To: "Isaku Yamahata" <yamahata@xxxxxxxxxxxxx>
Subject: RE: [Xen-ia64-devel] "Bad address" when "xm create"
From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
Date: Thu, 20 Apr 2006 21:03:48 +0800
Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 20 Apr 2006 06:04:03 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcZkZimCROm4LyEsQNu7bVQ70MkjuAAFKBUA
Thread-topic: [Xen-ia64-devel] "Bad address" when "xm create"
Yes, same error as yours.

Thanks,
Kevin

>-----Original Message-----
>From: Isaku Yamahata [mailto:yamahata@xxxxxxxxxxxxx]
>Sent: 2006年4月20日 18:35
>To: Tian, Kevin
>Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>Subject: Re: [Xen-ia64-devel] "Bad address" when "xm create"
>
>
>Hi Kevin.
>
>On Thu, Apr 20, 2006 at 05:22:17PM +0800, Tian, Kevin wrote:
>>      Only observed once that "Bad address" returned when "xm
>> create" and thus failed to create domU on top of latest p2m tree.
>> However I can't reproduce it and just reported here for you
>> reference. Possibly the cause is from hypercall parameter copy,
>> but not sure. Next time if I see it, I'll try to capture more info.
>
>Thank you for your report.
>Is there any message in xend.log?
>
>I found "bad address" from the xend.log of my test environtment.
>I don't remember it clearly, but I guess this was caused by hypercall
>parameter copy.
>xc_linux_build() has work around, but xc_memory_op() doesn't
>so that xc_memory_op() might result in EFAULT.
>
>
>xc_domain_memory_increase_reservation()
>  => xc_memory_op(xc_handle, XENMEM_increase_reservation,
>&reservation);
>
>[2006-03-23 15:05:04 xend.XendDomainInfo] DEBUG
>(XendDomainInfo:177) XendDomainInfo.create(['vm', ['name',
>'dom0vp-domU'], ['memory', '128'], ['vcpus', '1'], ['image', ['linux', 
>['kernel',
>'/home/yamahata/xen/hg/ia64/xen-config/dom0vp/domU/vmlinux-xenU'],
>['ramdisk', '/boot/efi/efi/people/yamahata/cross3/initrd-2.6.12'], ['root',
>'/dev/sda6 ro'], ['args', '4']]], ['device', ['vbd', ['uname', 'phy:sda6'], 
>['dev',
>'sda6'], ['mode', 'w']]], ['
>device', ['vif', ['bridge', 'xenbr0']]]])
>[2006-03-23 15:05:04 xend.XendDomainInfo] DEBUG
>(XendDomainInfo:283) parseConfig: config is ['vm', ['name',
>'dom0vp-domU'], ['memory', '128'], ['vcpus', '1'], ['image', ['linux', 
>['kernel',
>'/home/yamahata/xen/hg/ia64/xen-config/dom0vp/domU/vmlinux-xenU'],
>['ramdisk', '/boot/efi/efi/people/yamah
>ata/cross3/initrd-2.6.12'], ['root', '/dev/sda6 ro'], ['args', '4']]], 
>['device',
>['vbd', ['uname', 'phy:sda6'], ['dev', 'sda6'], ['mode', 'w']]], ['device', 
>['vif',
>['bridge', 'xenbr0']]]]
>[2006-03-23 15:05:04 xend.XendDomainInfo] DEBUG
>(XendDomainInfo:379) parseConfig: result is {'ssidref': None, 'uuid':
>None, 'on_crash': None, 'on_reboot': None, 'image': ['linux', ['kernel',
>'/home/yamahata/xen/hg/ia64/xen-config/dom0vp/domU/vmlinux-xenU'],
>['ramdisk', '/boot/efi/efi/people/yama
>hata/cross3/initrd-2.6.12'], ['root', '/dev/sda6 ro'], ['args', '4']],
>'on_poweroff': None, 'cpus': None, 'name': 'dom0vp-domU', 'backend': [],
>'vcpus': 1, 'cpu_weight': None, 'vcpu_avail': None, 'memory': 128,
>'device': [('vbd', ['vbd', ['uname', 'phy:sda6'], ['dev', 'sda6'], ['mode', 
>'w']]), (
>'vif', ['vif', ['bridge', 'xenbr0']])], 'bootloader': None, 'cpu': None, 
>'maxmem':
>None}
>[2006-03-23 15:05:04 xend.XendDomainInfo] DEBUG
>(XendDomainInfo:1163) XendDomainInfo.construct: None 0
>[2006-03-23 15:05:04 xend.XendDomainInfo] DEBUG
>(XendDomainInfo:1195) XendDomainInfo.initDomain: 1 1.0
>[2006-03-23 15:05:04 xend] DEBUG (balloon:126) Balloon: free 1777;
>need 129; done.
>[2006-03-23 15:05:04 xend.XendDomainInfo] ERROR
>(XendDomainInfo:189) Domain construction failed
>Traceback (most recent call last):
>  File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 182, in create
>    vm.initDomain()
>  File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 1220, in
>initDomain
>    xc.domain_memory_increase_reservation(self.domid, m, 0, 0)
>error: (14, 'Bad address')
>[2006-03-23 15:05:04 xend.XendDomainInfo] DEBUG
>(XendDomainInfo:1321) XendDomainInfo.destroy: domid=1
>[2006-03-23 15:05:04 xend.XendDomainInfo] DEBUG
>(XendDomainInfo:1329) XendDomainInfo.destroyDomain(1)
>[2006-03-23 15:05:04 xend] ERROR (SrvBase:87) Request create
>failed.
>Traceback (most recent call last):
>  File "/usr/lib/python/xen/web/SrvBase.py", line 85, in perform
>    return op_method(op, req)
>  File "/usr/lib/python/xen/xend/server/SrvDomainDir.py", line 82, in
>op_create
>    raise XendError("Error creating domain: " + str(ex))
>XendError: Error creating domain: (14, 'Bad address')
>
>--
>yamahata

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

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