Hi, I''m new to the xen business and tried the latest Xen drop code. The system install was ok, but I could not get the xend running, when I booted Solaris dom0. /var/log/xen/xend.log said: [2007-07-27 01:12:06 xend 684] WARNING (XendAuthSessions:27) python-pam is required for XenAPI support. [2007-07-27 01:12:18 xend 685] WARNING (XendAuthSessions:27) python-pam is required for XenAPI support. [2007-07-27 01:12:18 xend 687] INFO (SrvDaemon:322) Xend Daemon started [2007-07-27 01:12:18 xend 687] ERROR (SrvDaemon:344) Exception starting xend ((79, ''Value too large for defined data type'')) Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/xen/xend/server/SrvDaemon.py", line 325, in run Error: (79, ''Value too large for defined data type'') Thanks in adcance for any hint. Greetings Robert
On Fri, Jul 27, 2007 at 01:26:42AM +0200, Robert Schien wrote:> I''m new to the xen business and tried the latest Xen drop code. The > system install was ok, but I could not get the xend running, when I > booted Solaris dom0. > /var/log/xen/xend.log said: > > [2007-07-27 01:12:06 xend 684] WARNING (XendAuthSessions:27) python-pam is required for XenAPI support. > [2007-07-27 01:12:18 xend 685] WARNING (XendAuthSessions:27) python-pam is required for XenAPI support. > [2007-07-27 01:12:18 xend 687] INFO (SrvDaemon:322) Xend Daemon started > [2007-07-27 01:12:18 xend 687] ERROR (SrvDaemon:344) Exception starting xend ((79, ''Value too large for defined data type'')) > Traceback (most recent call last): > File "/usr/lib/python2.4/site-packages/xen/xend/server/SrvDaemon.py", line 325, in run > Error: (79, ''Value too large for defined data type'')This is curious. Is this a 64-bit system (run "isainfo -b") ? Do you install a-new from the ISO we make available? People used to get this error when the wrong Python version was being run. In this case it looks like you''re trying to run a 32-bit Python against a 64-bit kernel, though it''s hard to see how that would happen if you started from our ISO. regards john
On Fri, Jul 27, 2007 at 01:33:15AM +0100, John Levon wrote:> On Fri, Jul 27, 2007 at 01:26:42AM +0200, Robert Schien wrote: > > > I''m new to the xen business and tried the latest Xen drop code. The > > system install was ok, but I could not get the xend running, when I > > booted Solaris dom0. > > /var/log/xen/xend.log said: > > > > [2007-07-27 01:12:06 xend 684] WARNING (XendAuthSessions:27) python-pam is required for XenAPI support. > > [2007-07-27 01:12:18 xend 685] WARNING (XendAuthSessions:27) python-pam is required for XenAPI support. > > [2007-07-27 01:12:18 xend 687] INFO (SrvDaemon:322) Xend Daemon started > > [2007-07-27 01:12:18 xend 687] ERROR (SrvDaemon:344) Exception starting xend ((79, ''Value too large for defined data type'')) > > Traceback (most recent call last): > > File "/usr/lib/python2.4/site-packages/xen/xend/server/SrvDaemon.py", line 325, in run > > Error: (79, ''Value too large for defined data type'') > > This is curious. Is this a 64-bit system (run "isainfo -b") ? > > Do you install a-new from the ISO we make available? > > People used to get this error when the wrong Python version was being run. In > this case it looks like you''re trying to run a 32-bit Python against a 64-bit > kernel, though it''s hard to see how that would happen if you started from our > ISO. > > regards > johnisainfo -b replies 64. uname -a delivers SunOS robk1 5.11 xen-nv66-2007-06-24 i86pc i386 i86xpv Is this the correct version? Of course, I can install a-new, but I don''t know what I could change. BTW, during install the first grub entry (Solaris Express Developer Edition) delivers an error message that it can''t be installed. Therefore I used the enty "Solaris Express". Also, during install in used a 32 bit kernel, after reboot a 64 the systen changed to 64 bit. Is this a normal behaviour? I have two 64 bit machines with AMD processors, one is a X2 without Pacifica extensions, the other an AM2 (non X2), but with Pacifica extensions. I can''t imagine that my systems are so strange: the X2 has an ASUS mainboard, the AM2 a cheap Asrock. Thnaks again for your help. Greetings Robert
On Fri, Jul 27, 2007 at 04:26:47PM +0200, Robert Schien wrote:> Also, during install in used a 32 bit kernel, after reboot a 64 the > systen changed to 64 bit. Is this a normal behaviour?Yes, that''s normal. I''m utterly confused now. Can you verify that /usr/bin/amd64/python exists on your system? john
Robert Schien wrote:>> >> Do you install a-new from the ISO we make available? >> >> People used to get this error when the wrong Python version was being run. In >> this case it looks like you''re trying to run a 32-bit Python against a 64-bit >> kernel, though it''s hard to see how that would happen if you started from our >> ISO. >> >> regards >> john > > isainfo -b replies 64. > uname -a delivers > SunOS robk1 5.11 xen-nv66-2007-06-24 i86pc i386 i86xpv > Is this the correct version? > > Of course, I can install a-new, but I don''t know what I could change. > BTW, during install the first grub entry (Solaris Express Developer > Edition) delivers an error message that it can''t be installed. > Therefore I used the enty "Solaris Express". > > Also, during install in used a 32 bit kernel, after reboot a 64 the > systen changed to 64 bit. Is this a normal behaviour? > > I have two 64 bit machines with AMD processors, one is a X2 without > Pacifica extensions, the other an AM2 (non X2), but with Pacifica > extensions. > > I can''t imagine that my systems are so strange: the X2 has an ASUS > mainboard, the AM2 a cheap Asrock. > > Thnaks again for your help.Did you do a full install? It''s possible we have a bug when you don''t do a full install. Thanks, MRJ -- Mark Johnson <mark.johnson@sun.com> Sun Microsystems, Inc.
On Fri, Jul 27, 2007 at 03:38:49PM +0100, John Levon wrote:> On Fri, Jul 27, 2007 at 04:26:47PM +0200, Robert Schien wrote: > > > Also, during install in used a 32 bit kernel, after reboot a 64 the > > systen changed to 64 bit. Is this a normal behaviour? > > Yes, that''s normal. > > I''m utterly confused now. Can you verify that /usr/bin/amd64/python exists on > your system? > > johnyes, the file does exist. Robert
On Fri, Jul 27, 2007 at 10:40:15AM -0400, Mark Johnson wrote:> > Robert Schien wrote: > >> > >>Do you install a-new from the ISO we make available? > >> > >>People used to get this error when the wrong Python version was being > >>run. In > >>this case it looks like you''re trying to run a 32-bit Python against a > >>64-bit > >>kernel, though it''s hard to see how that would happen if you started from > >>our > >>ISO. > >> > >>regards > >>john > > > >isainfo -b replies 64. > >uname -a delivers > >SunOS robk1 5.11 xen-nv66-2007-06-24 i86pc i386 i86xpv > >Is this the correct version? > > > >Of course, I can install a-new, but I don''t know what I could change. > >BTW, during install the first grub entry (Solaris Express Developer > >Edition) delivers an error message that it can''t be installed. > >Therefore I used the enty "Solaris Express". > > > >Also, during install in used a 32 bit kernel, after reboot a 64 the > >systen changed to 64 bit. Is this a normal behaviour? > > > >I have two 64 bit machines with AMD processors, one is a X2 without > >Pacifica extensions, the other an AM2 (non X2), but with Pacifica > >extensions. > > > >I can''t imagine that my systems are so strange: the X2 has an ASUS > >mainboard, the AM2 a cheap Asrock. > > > >Thnaks again for your help. > > Did you do a full install? It''s possible we have a bug when you > don''t do a full install. > > > > Thanks, > > > MRJDuring install I selected userdefined install and selected then "complete group". Robert