Skip to contentSkip to conversation

Fix TypeError when starting VMX domains

PATCH Applied Arun Sharma 3 participants 5 messages Aug 8, 2005 – Aug 10, 2005

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 Fix TypeError when starting VMX domains

The attached patch fixes this traceback:

Traceback (most recent call last):
File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 510, in construct
self.construct_image()
File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 574, in
construct_image
self.store_channel)
File "/usr/lib/python/xen/xend/xenstore/xsobj.py", line 310, in
introduceDomain
log.info("DBMap>introduceDomain> %d %d %s %s" %(dom, page, evtchn,
path))
TypeError: int argument required

tools/python/xen/xend/XendDomainInfo.py Mon Aug 8 15:00:19 2005 renamed from tools/python/xen/xend/XendDomainInfo.py Mon Aug 8 20:22:16 2005 +1 -1
@@ -239,7 +239,7 @@
 
         self.channel = None
         self.store_channel = None
-        self.store_mfn = None
+        self.store_mfn = 0
         self.controllers = {}
#1 lore raw
Quoted 2 lines · Arun Sharma

The attached patch fixes this traceback:

When does this happen? It seems that the fix will only hide the real cause of the failure and I'd rather fix the underlying bug. It's odd that we have initialized the store_channel but not figured out what the store_mfn is.

christian

Quoted 29 lines

Traceback (most recent call last):
File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 510, in construct
self.construct_image()
File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 574, in
construct_image
self.store_channel)
File "/usr/lib/python/xen/xend/xenstore/xsobj.py", line 310, in
introduceDomain
log.info("DBMap>introduceDomain> %d %d %s %s" %(dom, page, evtchn,
path))
TypeError: int argument required

tools/python/xen/xend/XendDomainInfo.py Mon Aug 8 15:00:19 2005 renamed from tools/python/xen/xend/XendDomainInfo.py Mon Aug 8 20:22:16 2005 +1 -1
@@ -239,7 +239,7 @@
 
         self.channel = None
         self.store_channel = None
-        self.store_mfn = None
+        self.store_mfn = 0
         self.controllers = {}
 
 

_______________________________________________
Xen-devel mailing list
[email protected]
http://lists.xensource.com/xen-devel

#2 lore raw
Quoted 9 lines · Christian Limpach
Quoted 1 line · Arun Sharma

The attached patch fixes this traceback:

When does this happen? It seems that the fix will only hide the real cause of the failure and I'd rather fix the underlying bug. It's odd that we have initialized the store_channel but not figured out what the store_mfn is.

The real issue is that xc_vmx_build.c was not kept upto date with the xenstore changes. Working on it now.

-Arun

#3 lore raw
Quoted 8 lines · Arun Sharma
Quoted 6 lines · Christian Limpach
Quoted 1 line · Arun Sharma

The attached patch fixes this traceback:

Quoted 8 lines
Quoted 4 lines

When does this happen? It seems that the fix will only hide the real cause of the failure and I'd rather fix the underlying bug. It's odd that we have initialized the store_channel but not figured out what the store_mfn is.

The real issue is that xc_vmx_build.c was not kept upto date with the xenstore changes. Working on it now.

It's resolved by this changeset.

http://xenbits.xensource.com/ext/xen-vt-testing.hg?cmd=changeset;node=02121365cfff9cfa8e57cc37a560df5305360b58

-Arun

#4 lore raw
Quoted 15 lines · Arun Sharma
Quoted 14 lines · Arun Sharma
Quoted 10 lines · Christian Limpach
Quoted 1 line · Arun Sharma

The attached patch fixes this traceback:

When does this happen? It seems that the fix will only hide the real cause of the failure and I'd rather fix the underlying bug. It's odd that we have initialized the store_channel but not figured out what the store_mfn is.

Quoted 7 lines
Quoted 3 lines

The real issue is that xc_vmx_build.c was not kept upto date with the xenstore changes. Working on it now.

It's resolved by this changeset.

http://xenbits.xensource.com/ext/xen-vt-testing.hg?cmd=changeset;node=02121365cfff9cfa8e57cc37a560df5305360b58

I've applied this. Thanks!

christian