search for: slotnum

...d_binary: phdr 0 at 0x0x7f7375ca2000 -> 0x0x7f7375d36d95 libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend: Disk vdev=hda spec.backend=phy libxl: debug: libxl_event.c:512:libxl__ev_xswatch_register: watch w=0x9cf248 wpath=/local/domain/0/backend/vbd/10/768/state token=3/0: register slotnum=3 libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend: Disk vdev=hdc spec.backend=qdisk libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend: Disk vdev=hdc spec.backend=qdisk libxl: debug: libxl_create.c:1186:do_domain_create: ao 0x9cc890: inprogress: poller=0x9cc920, flags=i...

Hi, Here is a little patch that attempt to fix the issue regarding xen_platform_pci=0 not been handled. There is one patch left from the previous version. The patch that was adding qemu_machine_override have been removed as it is unnecessary. If someone wants to change the -machine, it can always add it to device_model_args_hvm, as QEMU appear to use the last one. Regards, Anthony PERARD (1):

Does anyone know what program can be used to query the RAID status from the OS for an on-board LSI SAS 2308-4i? On this page: http://docs.avagotech.com/docs/12351997 there is a curious note on the left that reads: "Integrated MegaRAID support available upon request" After one mostly fruitless round of chatting with LSI/Avago/Broadcom and one completely fruitless round of chatting

It looks like the AsmWriter is generating the local variables (SlotNum)s on the fly in that file (AsmWriter.cpp), so is there any way at all to get this information from the operation itself, via Instruction, Value or Type? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20111021/...

On 1/30/2015 1:53 AM, Gordon Messmer wrote: > On 01/29/2015 05:07 AM, Jatin Davey wrote: >> Yes , it is a SATA disk. I am not sure of the speed. Can you tell me >> how to find out this information ? Additionally we are using RAID 10 >> configuration with 4 disks. > > What RAID controller are you using? > > # lspci | grep RAID [Jatin] [root at localhost ~]# lspci |

...; + str(units) return [id,type,size,state,inprogress] def returnDiskInfo(output,controllerid,currentarrayid): arrayid = False oldarrayid = False olddiskid = False table = [] state = 'Offline' model = 'Unknown' enclnum = 'Unknown' slotnum = 'Unknown' enclsl = 'Unknown' firstDisk = True for line in output: if re.match(r'Firmware state: .*$',line.strip()): state = line.split(':')[1].strip() if re.match(r'Rebuild',state): cmd2 =...

...; + str(units) return [id,type,size,state,inprogress] def returnDiskInfo(output,controllerid,currentarrayid): arrayid = False oldarrayid = False olddiskid = False table = [] state = 'Offline' model = 'Unknown' enclnum = 'Unknown' slotnum = 'Unknown' enclsl = 'Unknown' firstDisk = True for line in output: if re.match(r'Firmware state: .*$',line.strip()): state = line.split(':')[1].strip() if re.match(r'Rebuild',state): cmd2 =...

...state,inprogress] > > def returnDiskInfo(output,controllerid,currentarrayid): > arrayid = False > oldarrayid = False > olddiskid = False > table = [] > state = 'Offline' > model = 'Unknown' > enclnum = 'Unknown' > slotnum = 'Unknown' > enclsl = 'Unknown' > > firstDisk = True > for line in output: > if re.match(r'Firmware state: .*$',line.strip()): > state = line.split(':')[1].strip() > if re.match(r'Rebuild',stat...

...reating (or basically copying) the API from AsmWriter (seems very dedundant to me)? This seems like a large failing? On Fri, Oct 21, 2011 at 7:03 PM, Nick Lewycky <nicholas at mxc.ca> wrote: > Ryan Taylor wrote: > >> It looks like the AsmWriter is generating the local variables (SlotNum)s >> on the fly in that file (AsmWriter.cpp), so is there any way at all to >> get this information from the operation itself, via Instruction, Value >> or Type? >> > > Nope! As you noticed, they're created on the fly... > > ...when the Value or Type is anony...

On Thursday 02 November 2017 14:10:25 Bowie Bailey wrote: > If you want raid 5 or 6, then you should get a hardware controller. For > raid 1, mdadm should work just fine.? I would suggest trying it before > buying a raid controller.? If it works for you, you save a few hundred > dollars and you have one less piece of hardware to worry about. > > I haven't looked at them in

I just had an IBM in a remote location with a hardware raid1 have both drives go bad. With local machines I probably would have caught it from the drive light before the 2nd one died... What is the state of the art in linux software monitoring for this? Long ago when that box was set up I think the best I could have done was a Java GUI tool that IBM had for their servers - and that seemed like

Ryan Taylor wrote: > It looks like the AsmWriter is generating the local variables (SlotNum)s > on the fly in that file (AsmWriter.cpp), so is there any way at all to > get this information from the operation itself, via Instruction, Value > or Type? Nope! As you noticed, they're created on the fly... ...when the Value or Type is anonymous. If you want them to be persisten...

...to:nicholas at mxc.ca>> wrote: >>> >>> Ryan Taylor wrote: >>> >>> Nick, >>> >>> Also, I forgot to mention I had no luck with instnamer, it >>> still left >>> the local variables as "%slotNum", it didn't name them, unless I >>> used >>> -instnamer wrong: >>> >>> opt -instnamer <file.bc> file2.bc >>> >>> >>> Almost, use -o to specify output: opt -instnamer file.bc -o file2.bc >>&gt...

Package: xen-utils-common Version: 4.4.1-6 Severity: normal Dear Maintainer, (There appear to be several reports on the BTS with concerns relating to this report. Some unarchiving/merging may be necessary. Reassignment may be needed as well since I'm not sure which package this problem would fall under. Ultimately decided to file with xen-utils-common with 'xl' being the frontend

...refer to a value, we use the Value*. Nick > > On Fri, Oct 21, 2011 at 7:03 PM, Nick Lewycky <nicholas at mxc.ca > <mailto:nicholas at mxc.ca>> wrote: > > Ryan Taylor wrote: > > It looks like the AsmWriter is generating the local variables > (SlotNum)s > on the fly in that file (AsmWriter.cpp), so is there any way at > all to > get this information from the operation itself, via Instruction, > Value > or Type? > > > Nope! As you noticed, they're created on the fly... > &...

I''m unable to start xl console on latest xen-unstable (build with commit 8e0da8c07f4f80e14314977a11f738bd74a5b62b). > xl -vvv console sid > xenconsole: Could not read tty from store: No such file or directory I also tried "xl create -c", and it shows console from pygrub but when the "xl create" reaches the end I got the same error: > xenconsole: Could not

Ryan Taylor wrote: > Nick, > > Also, I forgot to mention I had no luck with instnamer, it still left > the local variables as "%slotNum", it didn't name them, unless I used > -instnamer wrong: > > opt -instnamer <file.bc> file2.bc Almost, use -o to specify output: opt -instnamer file.bc -o file2.bc > Those are the ones I am refering to. The description for instnamer says that it names unnamed instructio...

...1:21 PM, Nick Lewycky <nicholas at mxc.ca > <mailto:nicholas at mxc.ca>> wrote: > > Ryan Taylor wrote: > > Nick, > > Also, I forgot to mention I had no luck with instnamer, it > still left > the local variables as "%slotNum", it didn't name them, unless I > used > -instnamer wrong: > > opt -instnamer <file.bc> file2.bc > > > Almost, use -o to specify output: opt -instnamer file.bc -o file2.bc > > > Those are the ones I am refering to. The...

...aylor wrote: >>>>>> >>>>>> Nick, >>>>>> >>>>>> Also, I forgot to mention I had no luck with instnamer, it >>>>>> still left >>>>>> the local variables as "%slotNum", it didn't name them, unless >>>>>> I >>>>>> used >>>>>> -instnamer wrong: >>>>>> >>>>>> opt -instnamer <file.bc> file2.bc >>>>>> >>>>>>...

...t;>>>>>>> Nick, >>>>>>>> >>>>>>>> Also, I forgot to mention I had no luck with instnamer, it >>>>>>>> still left >>>>>>>> the local variables as "%slotNum", it didn't name them, >>>>>>>> unless I >>>>>>>> used >>>>>>>> -instnamer wrong: >>>>>>>> >>>>>>>> opt -instnamer <file.bc> file2.bc >>&...