On Wed, 22 Jun 2005, Stefan Berger wrote:
Changing the following line makes a temporary fix:
tools/python/xen/xm/create.py
--
gopts.var('ssidref', val='SSIDREF',
- fn=set_u32, default=0xfffffff,
use="Security Identifier.")
++
gopts.var('ssidref', val='SSIDREF',
+ fn=set_u32, default=0xffff,
use="Security Identifier.")
[snip]
I am using version 2.3.4 and do not encounter this problem. Did you put
any ssidref line into the VM configuration file?
No -- I just used the config file that worked before the update. :-)
I've attached it for reference. Consider me as testing backwards
compatibility and/or useful failure messages. :-)
-George
+-------------------+----------------------------------------
| dunlapg@xxxxxxxxx | http://www-personal.umich.edu/~dunlapg
+-------------------+----------------------------------------
| Who could move a mountain, who could love their enemy?
| Who could rejoice in pain, and turn the other cheek?
| - Rich Mullins, "Surely God is With Us"
+------------------------------------------------------------
| Outlaw Junk Email! Support HR 1748 (www.cauce.org)
xmr-not
Description: Text document
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home