Re: z/VM bug, Linux bug, or operator error?
Hi Mark, good point, I am going to address the documentation side. with kind regards Carsten Otte IBM Linux Technology Center / Boeblingen lab -- omnis enim res, quae dando non deficit, dum habetur et non datur, nondum habetur, quomodo habenda est Mark Post To Sent by: Linux on LINUX-390@vm.marist.edu 390 Port cc Subject Re: z/VM bug, Linux bug, or operator error? 27.05.2011 16:17 Please respond to Linux on 390 Port >>> On 5/26/2011 at 05:14 AM, Carsten Otte wrote: > Hi Mark, > > could you please trace diag x64 and send the output? You see this message > due to a diag call failing, > and the trace would enable the hypervisor people to comment on why that is. Hi, Carsten, Thanks for the offer to help, but the fix was Kris Buelens' comment that a DCSS must start and end on megabyte boundaries. That means the "end page" value should end in x'FF', or at least the subsequent DCSS needs to have a "start page" value ending in x'00' to avoid overlaps. That fact should probably explicitly be called out in the XIP documentation. (In a blatant attempt to deflect blame for my shallow z/VM skills. :) Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: z/VM bug, Linux bug, or operator error?
>>> On 5/26/2011 at 05:14 AM, Carsten Otte wrote: > Hi Mark, > > could you please trace diag x64 and send the output? You see this message > due to a diag call failing, > and the trace would enable the hypervisor people to comment on why that is. Hi, Carsten, Thanks for the offer to help, but the fix was Kris Buelens' comment that a DCSS must start and end on megabyte boundaries. That means the "end page" value should end in x'FF', or at least the subsequent DCSS needs to have a "start page" value ending in x'00' to avoid overlaps. That fact should probably explicitly be called out in the XIP documentation. (In a blatant attempt to deflect blame for my shallow z/VM skills. :) Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: z/VM bug, Linux bug, or operator error?
Hi Mark, could you please trace diag x64 and send the output? You see this message due to a diag call failing, and the trace would enable the hypervisor people to comment on why that is. with kind regards Carsten Otte IBM Linux Technology Center / Boeblingen lab -- omnis enim res, quae dando non deficit, dum habetur et non datur, nondum habetur, quomodo habenda est Mark Post To Sent by: Linux on LINUX-390@vm.marist.edu 390 Port cc Subject z/VM bug, Linux bug, or operator error? 25.05.2011 02:49 Please respond to Linux on 390 Port Cross-posted to IBMVM and Linux-390 I'm working on a project where I want an xip2 file system that is larger than 2GB. So, I'm trying to use the support built into z/VM and Linux to logically concatenate multiple DCSS into one. But, I can't seem to get it to work. I can load one segment or the other, but not both. The message that comes out on the console is extmem.cb0afe: ITMV1B needs used memory resources and cannot be loaded or queried "man extmem.cb0afe" says "You cannot load or query the DCSS because it overlaps with an already loaded DCSS or with the memory of the z/VM guest virtual machine (guest storage)." I don't believe any of those apply, but I need someone to tell me what to do differently, or to whom I should be complaining. The segments are defined as this: FILE FILENAME FILETYPE BEGPAG ENDPAG TYPE CL #USERS 0054 ITMV1A DCSSG00028 0002FFE00 SR A 0 0055 ITMV1B DCSSG0002FFE01 00037FD00 SR A 0 The guest virtual storage is 1GB: #CP Q V STOR STORAGE = 1G The kernel was booted with a mem= value sufficient to contain the highest address of the ITMV1B DCSS: # cat /proc/cmdline root=/dev/disk/by-path/ccw-0.0.9300-part1 TERM=dumb mem=16384M BOOT_IMAGE=0 The command to allocate the two DCSS is: echo itmv1a:itmv1b > /sys/devices/dcssblk/add And that's where I get my error (after 2 minutes). As I said previously, if I try to load them individually, I can do one or the other, but not both. This is an up to date SLES11 SP1 system, running on z/VM 6.1 RSU 1003. Does anyone see the problem? Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
z/VM bug, Linux bug, or operator error?
Mark, Memory segments begin on megabyte boundaries, in other words a page address ending in 00. You defined your ITMV1A segment from page 28 through 2FFE00. I think it should be 2FFDFF. Then, your ITMV1B segment should start at page 2FFE00, through page 37FCFF. -Bill -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
z/VM bug, Linux bug, or operator error?
Cross-posted to IBMVM and Linux-390 I'm working on a project where I want an xip2 file system that is larger than 2GB. So, I'm trying to use the support built into z/VM and Linux to logically concatenate multiple DCSS into one. But, I can't seem to get it to work. I can load one segment or the other, but not both. The message that comes out on the console is extmem.cb0afe: ITMV1B needs used memory resources and cannot be loaded or queried "man extmem.cb0afe" says "You cannot load or query the DCSS because it overlaps with an already loaded DCSS or with the memory of the z/VM guest virtual machine (guest storage)." I don't believe any of those apply, but I need someone to tell me what to do differently, or to whom I should be complaining. The segments are defined as this: FILE FILENAME FILETYPE BEGPAG ENDPAG TYPE CL #USERS 0054 ITMV1A DCSSG00028 0002FFE00 SR A 0 0055 ITMV1B DCSSG0002FFE01 00037FD00 SR A 0 The guest virtual storage is 1GB: #CP Q V STOR STORAGE = 1G The kernel was booted with a mem= value sufficient to contain the highest address of the ITMV1B DCSS: # cat /proc/cmdline root=/dev/disk/by-path/ccw-0.0.9300-part1 TERM=dumb mem=16384M BOOT_IMAGE=0 The command to allocate the two DCSS is: echo itmv1a:itmv1b > /sys/devices/dcssblk/add And that's where I get my error (after 2 minutes). As I said previously, if I try to load them individually, I can do one or the other, but not both. This is an up to date SLES11 SP1 system, running on z/VM 6.1 RSU 1003. Does anyone see the problem? Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
