I downloaded a prebuilt slackware domu from jailtime.org, extracted and tried to install it and keep getting this error: error: (11, ''Resource temporarily unavailable'') Whatever assistance you can give would be appreciated. Thanks.
Royce Stute wrote:> I downloaded a prebuilt slackware domu from jailtime.org, extracted > and tried to install it and keep getting this error: > > error: (11, ''Resource temporarily unavailable'') >Double check the entries in your config file (image files, etc). And make sure that both Domains (Dom0 and DomU) are either 32 Bit or 64 Bit but not mixed. regards Bernd> Whatever assistance you can give would be appreciated. > > Thanks. > > > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.org > >-- Bernd Schemmer, Frankfurt am Main, Germany http://home.arcor.de/bnsmb/index.html Más temprano que tarde el mundo cambiará. Fidel Castro
I''ve doublechecked the cfg entries and verified it''s 32 bit all across. Anything else I should check?>From: Bernd Schemmer <Bernd.Schemmer@gmx.de> >To: Royce Stute <rjstute@hotmail.com>, xen-discuss@opensolaris.org >Subject: Re: [xen-discuss] error message >Date: Mon, 23 Oct 2006 21:51:40 +0000 > >Royce Stute wrote: >>I downloaded a prebuilt slackware domu from jailtime.org, extracted and >>tried to install it and keep getting this error: >> >>error: (11, ''Resource temporarily unavailable'') >> >Double check the entries in your config file (image files, etc). > >And make sure that both Domains (Dom0 and DomU) are either 32 Bit or 64 Bit >but not mixed. > >regards > >Bernd > >>Whatever assistance you can give would be appreciated. >> >>Thanks. >> >> >>_______________________________________________ >>xen-discuss mailing list >>xen-discuss@opensolaris.org >> >> > > >-- >Bernd Schemmer, Frankfurt am Main, Germany >http://home.arcor.de/bnsmb/index.html > >Más temprano que tarde el mundo cambiará. > Fidel Castro >
I too am seeing the same thing trying to get centos and debian running. I only have a 32 bit machine (dell poweredge w/Xeon), 32 bit dom0 and 32 bit domU''s. I''m using the vmlinuz image from the demo CD. I can only boot solaris snv_44. Royce Stute wrote:> I''ve doublechecked the cfg entries and verified it''s 32 bit all across. > > Anything else I should check? > >> From: Bernd Schemmer <Bernd.Schemmer@gmx.de> >> To: Royce Stute <rjstute@hotmail.com>, xen-discuss@opensolaris.org >> Subject: Re: [xen-discuss] error message >> Date: Mon, 23 Oct 2006 21:51:40 +0000 >> >> Royce Stute wrote: >> >>> I downloaded a prebuilt slackware domu from jailtime.org, extracted >>> and tried to install it and keep getting this error: >>> >>> error: (11, ''Resource temporarily unavailable'') >>> >> Double check the entries in your config file (image files, etc). >> >> And make sure that both Domains (Dom0 and DomU) are either 32 Bit or >> 64 Bit but not mixed. >> >> regards >> >> Bernd >> >>> Whatever assistance you can give would be appreciated. >>> >>> Thanks. >>> >>> >>> _______________________________________________ >>> xen-discuss mailing list >>> xen-discuss@opensolaris.org >>> >>> >> >> >> -- >> Bernd Schemmer, Frankfurt am Main, Germany >> http://home.arcor.de/bnsmb/index.html >> >> Más temprano que tarde el mundo cambiará. >> Fidel Castro >> > > > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.org
Royce Stute wrote:> I''ve doublechecked the cfg entries and verified it''s 32 bit all across. > > Anything else I should check? >Hmm, I tested the slackware 10.2 image from jailtime.org sucessfull - so it should work. Let''s see: 1. Are the xen daemons running? svcs -a | grep xen ps -ef | grep xen (I don''t have a machine running with Xen right now and I don''t know the correct FRMIs for the daemons from memory) If one of the xen daemons is not online please post the logfile of the daemon (svcs -x ) 2. Can you start "xentop"? Does "xm list" work? 3. Can you start other DomUs? If yes, which ones? In general I suggest always try the Xen DomUs from the Xen Demo Disk first. If these images work, you can start to test other DomU Images. 4. Please post the messages from the logfiles (/var/log/xen*) that are generated when you try to start the DomU. 5. Please post your config file for the slackware image; it should look like: kernel = "/export/xen-images/centos1/vmlinuz-2.6.16.13-xen" memory = 128 name = "slackware" disk = [''file:/export/xen-images/slackware/slackware.10-2.img,sda1,w'', ''file:/export/xen-images/slackware/slackware.swap,sda2,w''] vif = [ ''mac=00:16:3E:00:00:21'' ] root = "/dev/sda1 ro" 6. What kernel image do you use? Please post the output of the command "file <your_kernel_image>" and "ls -l <your_kernel_image>" 7. In addition, execute "gzip -t <your_kernel_image>" and "ls -l <your_kernel_image>" 8. How big is your disk image file (do a "ls -l <your_disk_image>")? 9. Does "lofiadm -a <your_disk_image>" work? 10. If you have installed the "Miscellaneous filesystem support for OpenSolaris x86" from Moniak Gosh (http://belenix.sarovar.org/) you could try to mount your disk image, e.g (replace "/export/xen-images/slackware/slackware.10-2.img" with your image file) (bash):root@ferrari:/export/xen-images/slackware # LOFIDEVICE=$( lofiadm -a /export/xen-images/slackware/slackware.10-2.img ) (bash):root@ferrari:/export/xen-images/slackware # echo $LOFIDEVICE /dev/lofi/5 (bash):root@ferrari:/export/xen-images/slackware # mount -F ext2fs $LOFIDEVICE /mnt (bash):root@ferrari:/export/xen-images/slackware # df -k /mnt Filesystem kbytes used avail capacity Mounted on 127.0.0.1:/ 1048576 369700 626448 38% /mnt 11. How much free memory shows xentop? Is it less than the memory you configured for the DomU in the config file? 12. Try to increase the memory for your DomU in the config file regards Bernd>> From: Bernd Schemmer <Bernd.Schemmer@gmx.de> >> To: Royce Stute <rjstute@hotmail.com>, xen-discuss@opensolaris.org >> Subject: Re: [xen-discuss] error message >> Date: Mon, 23 Oct 2006 21:51:40 +0000 >> >> Royce Stute wrote: >>> I downloaded a prebuilt slackware domu from jailtime.org, extracted and tried to install it and keep getting this error: >>> >>> error: (11, ''Resource temporarily unavailable'') >>> >> Double check the entries in your config file (image files, etc). >> >> And make sure that both Domains (Dom0 and DomU) are either 32 Bit or 64 Bit but not mixed. >> >> regards >> >> Bernd >> >>> Whatever assistance you can give would be appreciated. >>> >>> Thanks. >>> >>> >>> _______________________________________________ >>> xen-discuss mailing list >>> xen-discuss@opensolaris.org >>> >>> >> >> >> -- >> Bernd Schemmer, Frankfurt am Main, Germany >> http://home.arcor.de/bnsmb/index.html >> >> Más temprano que tarde el mundo cambiará. >> Fidel Castro >> > >This message posted from opensolaris.org
Bernd Schemmer wrote:> Brian Kolaci wrote: > >> I too am seeing the same thing trying to get centos and debian running. >> I only have a 32 bit machine (dell poweredge w/Xeon), 32 bit dom0 and >> 32 bit domU''s. >> I''m using the vmlinuz image from the demo CD. >> >> I can only boot solaris snv_44. >> > Brian, > > see my response to Royce in the forum > (http://www.opensolaris.org/jive/thread.jspa?threadID=15972&tstart=0) > > > And please cc your emails regarding Xen to the Xen forum - thanks > > Bernd >Hi, Actually, I did cc the xen-discuss forum (and Royce too). The xen daemons are running. xentop shows Domain-0 and solaris-b44 domains, so I can start a solaris domU. I''ve attached the logs as requested. I did notice that in xend-debug.log there''s multiple errors like: + ifconfig -a netdev=e1000g0 brctl=/sbin/brctl + /sbin/brctl addbr xenbr0 /sbin/brctl: Can''t create bridge xenbr0: File exists + /sbin/brctl addif xenbr0 e1000g0 /sbin/brctl: adding e1000g0 failed: SIOCSLIFNAME: File exists It looks like it attempts to create it 4 times. The first one succeeds, but the other 3 attempts fail. I see in xentop that an empty entry is created momentarily and goes away, then the error comes up: Error: (11, ''Resource temporarily unavailable'') I''ve attached my config: demo.py Here''s my directory listing: -rw-rw-rw- 1 root root 1024001024 Oct 26 13:46 centos.img -rw-r--r-- 1 root root 246 Oct 26 13:53 demo.py -rw-rw-rw- 1 root root 1073741824 Oct 26 13:51 demo.swap I''m using the kernel off the xen-demo disk. orion-hw:root==>file /export/xen-demo/boot/vmlinuz-2.6.16.29-xen /export/xen-demo/boot/vmlinuz-2.6.16.29-xen: gzip compressed data - deflate method , max compression orion-hw:root==>ls -l /export/xen-demo/boot/vmlinuz-2.6.16.29-xen -r--r--r-- 1 root root 1439981 Oct 16 07:11 /export/xen-demo/boot/vmlinuz-2.6.16.29-xen orion-hw:root==>gzip -t /export/xen-demo/boot/vmlinuz-2.6.16.29-xen orion-hw:root==> (no output from the ''gzip -t'') xentop shows 3Gig free, I''m trying to get 400 Meg. I''ve also tried 512 Meg and 1024 Meg. Can the brctl error be the culprit?
Bernd Schemmer wrote:> Brian Kolaci wrote: > > Brian, > >> Actually, I did cc the xen-discuss forum (and Royce too). >> > Ooops, yes I did not see it. Sorry, my fault. > > There''s an error message in your xend-debug.log that I''ve never seen > before: > > ERROR: PAE-kernel on non-PAE host. > ERROR: Error constructing guest OS > > I think the kernel you''re using does not work in a Solaris Dom0 (I > remember that I also coud not use the kernel from Ubuntu wich was also > something like version 2.6.16-something) > > Looks like the Xen people did an update of the Xen Demo Disk > > Please try again with the 2.6.13 kernel from the Xen Demo Disk; I''ve > uploaded it to my Web site. > > http://home.arcor.de/bnsmb/public/solaris/vmlinuz-2.6.16.13-xen > > BTW: You''re using the last Xen bfu drop for Solaris, right? > > > regards > > Bernd >Good eye, Not sure how I missed that error message... Yes, got the latest demo disk. I''m using the exact version in the "How To" from snv_44. I just tried with the kernel you''ve uploaded and it worked fine, Thanks !!!
Brian Kolaci wrote:> I too am seeing the same thing trying to get centos and debian running. > I only have a 32 bit machine (dell poweredge w/Xeon), 32 bit dom0 and > 32 bit domU''s. > I''m using the vmlinuz image from the demo CD. > > I can only boot solaris snv_44. >Brian, see my response to Royce in the forum (http://www.opensolaris.org/jive/thread.jspa?threadID=15972&tstart=0) And please cc your emails regarding Xen to the Xen forum - thanks Bernd -- Bernd Schemmer, Frankfurt am Main, Germany http://home.arcor.de/bnsmb/index.html Más temprano que tarde el mundo cambiará. Fidel Castro
Brian Kolaci wrote: Brian,> Actually, I did cc the xen-discuss forum (and Royce too). >Ooops, yes I did not see it. Sorry, my fault. There''s an error message in your xend-debug.log that I''ve never seen before: ERROR: PAE-kernel on non-PAE host. ERROR: Error constructing guest OS I think the kernel you''re using does not work in a Solaris Dom0 (I remember that I also coud not use the kernel from Ubuntu wich was also something like version 2.6.16-something) Looks like the Xen people did an update of the Xen Demo Disk Please try again with the 2.6.13 kernel from the Xen Demo Disk; I''ve uploaded it to my Web site. http://home.arcor.de/bnsmb/public/solaris/vmlinuz-2.6.16.13-xen BTW: You''re using the last Xen bfu drop for Solaris, right? regards Bernd> The xen daemons are running. > xentop shows Domain-0 and solaris-b44 domains, so I can start a > solaris domU. > I''ve attached the logs as requested. I did notice that in > xend-debug.log there''s > multiple errors like: > > + ifconfig -a > netdev=e1000g0 > brctl=/sbin/brctl > + /sbin/brctl addbr xenbr0 > /sbin/brctl: Can''t create bridge xenbr0: File exists > + /sbin/brctl addif xenbr0 e1000g0 > /sbin/brctl: adding e1000g0 failed: SIOCSLIFNAME: File exists > > It looks like it attempts to create it 4 times. The first one succeeds, > but the other 3 attempts fail. > > I see in xentop that an empty entry is created momentarily and goes away, > then the error comes up: > > Error: (11, ''Resource temporarily unavailable'') > > I''ve attached my config: demo.py > > Here''s my directory listing: > > -rw-rw-rw- 1 root root 1024001024 Oct 26 13:46 centos.img > -rw-r--r-- 1 root root 246 Oct 26 13:53 demo.py > -rw-rw-rw- 1 root root 1073741824 Oct 26 13:51 demo.swap > > I''m using the kernel off the xen-demo disk. > > orion-hw:root==>file /export/xen-demo/boot/vmlinuz-2.6.16.29-xen > /export/xen-demo/boot/vmlinuz-2.6.16.29-xen: gzip compressed data - > deflate method , max compression > orion-hw:root==>ls -l /export/xen-demo/boot/vmlinuz-2.6.16.29-xen > -r--r--r-- 1 root root 1439981 Oct 16 07:11 > /export/xen-demo/boot/vmlinuz-2.6.16.29-xen > orion-hw:root==>gzip -t /export/xen-demo/boot/vmlinuz-2.6.16.29-xen > orion-hw:root==> > (no output from the ''gzip -t'') > > xentop shows 3Gig free, I''m trying to get 400 Meg. I''ve also tried > 512 Meg and 1024 Meg. > > Can the brctl error be the culprit? > > > > > ------------------------------------------------------------------------ > > [2006-10-26 14:14:38 xend.XendDomainInfo] DEBUG (XendDomainInfo:178) XendDomainInfo.create([''vm'', [''name'', ''centos''], [''memory'', 400], [''vcpus'', 1], [''image'', [''linux'', [''kernel'', ''/export/xen-demo/boot/vmlinuz-2.6.16.29-xen''], [''root'', ''/dev/sda1 ro'']]], [''device'', [''vbd'', [''uname'', ''file:/export/xc/xvm/demo/centos.img''], [''dev'', ''sda1''], [''mode'', ''w'']]], [''device'', [''vbd'', [''uname'', ''file:/export/xc/xvm/demo/demo.swap''], [''dev'', ''sda2''], [''mode'', ''w'']]], [''device'', [''vif'', [''mac'', ''00:16:3E:00:00:21'']]]]) > [2006-10-26 14:14:38 xend.XendDomainInfo] DEBUG (XendDomainInfo:284) parseConfig: config is [''vm'', [''name'', ''centos''], [''memory'', 400], [''vcpus'', 1], [''image'', [''linux'', [''kernel'', ''/export/xen-demo/boot/vmlinuz-2.6.16.29-xen''], [''root'', ''/dev/sda1 ro'']]], [''device'', [''vbd'', [''uname'', ''file:/export/xc/xvm/demo/centos.img''], [''dev'', ''sda1''], [''mode'', ''w'']]], [''device'', [''vbd'', [''uname'', ''file:/export/xc/xvm/demo/demo.swap''], [''dev'', ''sda2''], [''mode'', ''w'']]], [''device'', [''vif'', [''mac'', ''00:16:3E:00:00:21'']]]] > [2006-10-26 14:14:38 xend.XendDomainInfo] DEBUG (XendDomainInfo:380) parseConfig: result is {''ssidref'': None, ''uuid'': None, ''on_crash'': None, ''on_reboot'': None, ''image'': [''linux'', [''kernel'', ''/export/xen-demo/boot/vmlinuz-2.6.16.29-xen''], [''root'', ''/dev/sda1 ro'']], ''on_poweroff'': None, ''cpus'': None, ''name'': ''centos'', ''backend'': [], ''vcpus'': 1, ''cpu_weight'': None, ''vcpu_avail'': None, ''memory'': 400, ''device'': [(''vbd'', [''vbd'', [''uname'', ''file:/export/xc/xvm/demo/centos.img''], [''dev'', ''sda1''], [''mode'', ''w'']]), (''vbd'', [''vbd'', [''uname'', ''file:/export/xc/xvm/demo/demo.swap''], [''dev'', ''sda2''], [''mode'', ''w'']]), (''vif'', [''vif'', [''mac'', ''00:16:3E:00:00:21'']])], ''bootloader'': None, ''cpu'': None, ''maxmem'': None} > [2006-10-26 14:14:38 xend.XendDomainInfo] DEBUG (XendDomainInfo:1163) XendDomainInfo.construct: None 0 > [2006-10-26 14:14:38 xend.XendDomainInfo] DEBUG (XendDomainInfo:1195) XendDomainInfo.initDomain: 29 1.0 > [2006-10-26 14:14:38 xend] DEBUG (balloon:126) Balloon: free 3018; need 401; done. > [2006-10-26 14:14:38 xend] INFO (image:135) buildDomain os=linux dom=29 vcpus=1 > [2006-10-26 14:14:38 xend] DEBUG (image:173) dom = 29 > [2006-10-26 14:14:38 xend] DEBUG (image:174) image = /export/xen-demo/boot/vmlinuz-2.6.16.29-xen > [2006-10-26 14:14:38 xend] DEBUG (image:175) store_evtchn = 1 > [2006-10-26 14:14:38 xend] DEBUG (image:176) console_evtchn = 2 > [2006-10-26 14:14:38 xend] DEBUG (image:177) cmdline = root=/dev/sda1 ro > [2006-10-26 14:14:38 xend] DEBUG (image:178) ramdisk = > [2006-10-26 14:14:38 xend] DEBUG (image:179) vcpus = 1 > [2006-10-26 14:14:38 xend] DEBUG (image:180) features = > [2006-10-26 14:14:38 xend.XendDomainInfo] ERROR (XendDomainInfo:190) Domain construction failed > Traceback (most recent call last): > File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 183, in create > vm.initDomain() > File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 1224, in initDomain > channel_details = self.image.createImage() > File "/usr/lib/python/xen/xend/image.py", line 118, in createImage > return self.createDomain() > File "/usr/lib/python/xen/xend/image.py", line 137, in createDomain > result = self.buildDomain() > File "/usr/lib/python/xen/xend/image.py", line 188, in buildDomain > features = self.features) > error: (11, ''Resource temporarily unavailable'') > [2006-10-26 14:14:38 xend.XendDomainInfo] DEBUG (XendDomainInfo:1326) XendDomainInfo.destroy: domid=29 > [2006-10-26 14:14:38 xend.XendDomainInfo] DEBUG (XendDomainInfo:1334) XendDomainInfo.destroyDomain(29) > [2006-10-26 14:14:38 xend] ERROR (xmlrpclib2:124) (11, ''Resource temporarily unavailable'') > Traceback (most recent call last): > File "/usr/lib/python/xen/util/xmlrpclib2.py", line 103, in _marshaled_dispatch > response = self._dispatch(method, params) > File "/usr/lib/python2.4/SimpleXMLRPCServer.py", line 406, in _dispatch > return func(*params) > File "/usr/lib/python/xen/xend/server/XMLRPCServer.py", line 63, in domain_create > info = XendDomain.instance().domain_create(config) > File "/usr/lib/python/xen/xend/XendDomain.py", line 227, in domain_create > dominfo = XendDomainInfo.create(config) > File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 183, in create > vm.initDomain() > File "/usr/lib/python/xen/xend/XendDomainInfo.py", line 1224, in initDomain > channel_details = self.image.createImage() > File "/usr/lib/python/xen/xend/image.py", line 118, in createImage > return self.createDomain() > File "/usr/lib/python/xen/xend/image.py", line 137, in createDomain > result = self.buildDomain() > File "/usr/lib/python/xen/xend/image.py", line 188, in buildDomain > features = self.features) > error: (11, ''Resource temporarily unavailable'') > > ------------------------------------------------------------------------ > > kernel = "/export/xen-demo/boot/vmlinuz-2.6.16.29-xen" > memory = 400 > name = "centos" > disk = [''file:/export/xc/xvm/demo/centos.img,sda1,w'', > ''file:/export/xc/xvm/demo/demo.swap,sda2,w'' ] > vif = [''mac=00:16:3E:00:00:21''] > root = "/dev/sda1 ro" >-- Bernd Schemmer, Frankfurt am Main, Germany http://home.arcor.de/bnsmb/index.html Más temprano que tarde el mundo cambiará. Fidel Castro
Brian Kolaci wrote:> > > Bernd Schemmer wrote: > >> Brian Kolaci wrote: >> >> Brian, >> >>> Actually, I did cc the xen-discuss forum (and Royce too). >>> >> Ooops, yes I did not see it. Sorry, my fault. >> >> There''s an error message in your xend-debug.log that I''ve never seen >> before: >> >> ERROR: PAE-kernel on non-PAE host. >> ERROR: Error constructing guest OS >> >> I think the kernel you''re using does not work in a Solaris Dom0 (I >> remember that I also coud not use the kernel from Ubuntu wich was >> also something like version 2.6.16-something) >> >> Looks like the Xen people did an update of the Xen Demo Disk >> >> Please try again with the 2.6.13 kernel from the Xen Demo Disk; I''ve >> uploaded it to my Web site. >> >> http://home.arcor.de/bnsmb/public/solaris/vmlinuz-2.6.16.13-xen >> >> BTW: You''re using the last Xen bfu drop for Solaris, right? >> >> >> regards >> >> Bernd >> > Good eye, Not sure how I missed that error message... > Yes, got the latest demo disk. > I''m using the exact version in the "How To" from snv_44. > > I just tried with the kernel you''ve uploaded and it worked fine, > Thanks !!! >Good to hear! @Dave, can you confirm that the Xen Linux Kernel 2.6.16-something is not working for DomUs on Solaris Dom0 and update your blog entry http://www.dme.org/log/2006/07/17/solaris-on-xen-a-linux-domu-without-installing-linux/? regards Bernd> > >-- Bernd Schemmer, Frankfurt am Main, Germany http://home.arcor.de/bnsmb/index.html Más temprano que tarde el mundo cambiará. Fidel Castro
* Bernd.Schemmer@gmx.de [2006-10-27 07:02:00]> @Dave, can you confirm that the Xen Linux Kernel 2.6.16-something is > not working for DomUs on Solaris Dom0 and update your blog entry > http://www.dme.org/log/2006/07/17/solaris-on-xen-a-linux-domu-without-installing-linux/?I can confirm that a PAE kernel will not work - we don''t have 32 bit PAE implemented. I''m pushed for time to go and check the latest demo CD now, but I updated the blog entry to report your findings. dme. -- David Edmondson, Sun Microsystems, http://www.dme.org