search for: ready

...t created for this LUN Pleas see below. The last 4 should be active and I think this is the problem Kernel: 2.6.18-164.11.1.el5xen , EL 5.5 -- [root at cvprd3 lvm]# multipathd -k multipathd> show paths hcil dev dev_t pri dm_st chk_st next_check 5:0:0:0 sdb 8:16 1 [active][ready] XXX....... 7/20 5:0:0:1 sdc 8:32 1 [active][ready] XXX....... 7/20 5:0:0:16384 sdd 8:48 1 [active][ready] XXX....... 7/20 5:0:0:16385 sde 8:64 1 [active][ready] XXX....... 7/20 5:0:0:32768 sdf 8:80 1 [active][ready] XXX....... 7/20 5:0:0:32769 sdg 8:96 1 [active][ready...

...sr/lib/xen/bin/qemu-dm'' qemu-dm log: domid: 10 qemu: the number of cpus is 10 Watching /local/domain/10/logdirty/next-active qemu_map_cache_init nr_buckets = 4000 shared page at pfn 3ffff buffered io page at pfn 3fffd Time offset set 0 char device redirected to /dev/pts/1 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 Triggered log-dirty buffer switch I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O req...

Hi All; We know that agents can login and logout from the phone handset. But if we need the login, logout, ready and not ready to be from an application and to be integrated with the CRM, how to acheive this? Normally in Cisco and AVAYA, they use CTI integration and the CTI client (which is embded in the CRM application) will receive the the caller id or information via that CTI client. How this to be done...

...n Charlie. - Lang. On Thu, Jan 15, 2015 at 4:34 PM, Lang Hames <lhames at gmail.com> wrote: > Hi Charlie, > > Thanks for working on this. Sorry it took me so long to get around to > looking at it. > > I've just tested the patch out on Top-of-tree and I see: > > ready> def foo(x y) x+y; > ready> Read function definition: > define double @foo(double %x, double %y) { > entry: > %addtmp = fadd double %x, %y > ret double %addtmp > } > > ready> foo(1,2); > ready> Evaluated to 3.000000 > ready> foo(3,4); > ready>...

Hi all, Starting from Chapter 4 of the Kaleidoscope tutorial (where the JIT support is added), there's some strange behaviour, ready> def foo(x y) x+y; ready> Read function definition: define double @foo(double %x, double %y) { entry: %addtmp = fadd double %x, %y ret double %addtmp } ready> foo(1, 2); ready> Evaluated to 3.000000 ready> foo(3, 4); ready> Evaluated to 3.000000 You can see that foo(3, 4) is...

...2J Rev: SB00 Type: CD-ROM ANSI SCSI revision: 05 sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray Uniform CD-ROM driver Revision: 3.20 sr 6:0:0:0: Attached scsi CD-ROM sr0 cdrom: This disc doesn't have any tracks I recognize! sr0: CDROM not ready. Make sure there is a disc in the drive. sr0: CDROM not ready. Make sure there is a disc in the drive. sr0: CDROM not ready. Make sure there is a disc in the drive. sr0: CDROM not ready. Make sure there is a disc in the drive. sr0: CDROM not ready. Make sure there is a disc in the drive. sr0:...

...s scsi: [ID 107833 kern.notice] Requested Block: 17672154 Error Block: 17672154 Jul 8 20:12:59 fortress scsi: [ID 107833 kern.notice] Vendor: SEAGATE Serial Number: 9946626576 Jul 8 20:12:59 fortress scsi: [ID 107833 kern.notice] Sense Key: Not Ready Jul 8 20:12:59 fortress scsi: [ID 107833 kern.notice] ASC: 0x4 (LUN is becoming ready), ASCQ: 0x1, FRU: 0x2 Jul 8 20:13:04 fortress scsi: [ID 107833 kern.warning] WARNING: / sbus at 1f,0/SUNW,fas at 2,8800000/sd at 6,0 (sd19): Jul 8 20:13:04 fortress Error for Command: write(10)...

...2J Rev: SB00 Type: CD-ROM ANSI SCSI revision: 05 sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray Uniform CD-ROM driver Revision: 3.20 sr 6:0:0:0: Attached scsi CD-ROM sr0 cdrom: This disc doesn't have any tracks I recognize! sr0: CDROM not ready. Make sure there is a disc in the drive. sr0: CDROM not ready. Make sure there is a disc in the drive. sr0: CDROM not ready. Make sure there is a disc in the drive. sr0: CDROM not ready. Make sure there is a disc in the drive. sr0: CDROM not ready. Make sure there is a disc in the drive. sr0:...

...I no longer have the problem with the home directory. That's fine now. Thanks a lot! But the other problem remains, that very soon after startup I can't log into the GUI. I think the remaining problem doesn't has to do something with Samba/Autofs. It looks as if the network becomes ready very late (after autofs started), which perhaps would explain my problem. In the /var/log/boot.log I see: ... Schnittstelle eth0 hochfahren: IP-Informationen f?r eth0 werden bestimmt ... fehlgeschlagen; keine Verbindung vorhanden. Kabel pr?fen? FEHLGESCHLAGEN ... Netzwerkparameter einstellen...

I understand that libvirt provides async events that are triggered once the block job reaches ready state and successfully pivots as it is reported by qemu. Whats the event that is triggered and what's the handler that we have to implement? To be more specific, I am looking for the onEVENT callback method that is invoked when the event is fired. On Tue, Jan 3, 2017 at 6:28 PM, Kashyap Chamar...

...evices: sda and sdf are different paths to the same LUN. dm-0 is the multipath as stated by the following command: multipath -ll ASM_DISK_4 (360060e80056583000000658300004064) dm-3 HITACHI,OPEN-V [size=9.0G][features=0][hwhandler=0] \_ round-robin 0 [prio=2][active] \_ 0:0:1:4 sde 8:64 [active][ready] \_ 1:0:1:4 sdj 8:144 [active][ready] ASM_DISK_3 (360060e80056583000000658300004063) dm-2 HITACHI,OPEN-V [size=9.0G][features=0][hwhandler=0] \_ round-robin 0 [prio=2][active] \_ 0:0:1:3 sdd 8:48 [active][ready] \_ 1:0:1:3 sdi 8:128 [active][ready] ASM_DISK_2 (360060e80056583000000658300004062)...

...13, in wrapper return func(inst, *args, **kwargs) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 733, in blockJobAbort if ret == -1: raise libvirtError ('virDomainBlockJobAbort() failed', dom=self) libvirtError: block copy still active: disk 'vdb' not ready for pivot yet That exception observed in following BZs: https://bugzilla.redhat.com/1376580 https://bugzilla.redhat.com/1397122 I am trying to understand what this exception indicates in order to handle it appropriately when thrown by libvirt. Thanks, Ala

....com. I installed Quicken 2007 without event. I wanted to restore a file from my Windows version of Quicken. I hit the radio button saying I'm not a new user and want to restore a file from the computer. I browse to the file and select it. Then I get a dailogue box saying: "The Disk is not ready" I can use Notepad to create and save a file in drive_c. I tried chmod 777 /home/tootlet/.wine/Quicken thinking it was a permissions issue. Didn't work. Still "Disk is not ready". How do I get the disk ready? Tried googling and reading some entries in winehq forums but didn'...

...s of hdc errors here's an excerpt from /var/log/messages: ide: failed opcode was: unknown Oct 19 20:34:46 rbmain1 kernel: end_request: I/O error, dev hdc, sector 552 Oct 19 20:34:46 rbmain1 kernel: Buffer I/O error on device hdc, logical block 69 Oct 19 20:34:46 rbmain1 kernel: hdc: drive not ready for command Oct 19 20:34:46 rbmain1 kernel: hdc: status error: status=0x10 { SeekComplete } Oct 19 20:34:46 rbmain1 kernel: Oct 19 20:34:46 rbmain1 kernel: ide: failed opcode was: unknown Oct 19 20:34:46 rbmain1 kernel: hdc: drive not ready for command Oct 19 20:34:46 rbmain1 kernel: hdc: status e...

...fine so far except for local externs (as opposed to things like the math functions, which are working). Note that I have seen this bug with the reference code listing, as well as my own code. link to code: https://llvm.org/docs/tutorial/LangImpl05.html#full-code-listing [c34n10 kaleidoscope] ./toy ready> extern sin(x); sin(1); ready> Read extern: declare double @sin(double) ready> ready> Evaluated to 0.841471 ready> extern putchard(x); putchard(120); ready> Read extern: declare double @putchard(double) ready> ready> Failure value returned from cantFail wrapped call UNREAC...

Hi, In kubevirt, we discovered [1] that whenever e1000 is used for vNIC, link on the interface becomes ready several seconds after 'ifup' is executed, which for some buggy images like cirros may slow down boot process for up to 1 minute [2]. If we switch from e1000 to virtio, the link is brought up and ready almost immediately. For the record, I am using the following versions: - L0 kernel: 4.16....

...>> Hi all, >> >> Probably won't read mail. Linus, I'll have pull requests early >> next week; if there's anything needed I'm sure Michael Tsirkin can >> handle it. > > Sure. > Rusty, there's a small chance virtio 1.0 bits will be ready in time. > I started working on them based on your virtio-pci-new-layout branch. > > If ready before the merge window, are you ok with me merging this > support (without you having the opportunity to review first)? Sorry, absolutely not. I *really* want to review this in depth; if we...

Skipped content of type multipart/alternative-------------- next part -------------- A non-text attachment was scrubbed... Name: dovecot.conf Type: application/octet-stream Size: 20440 bytes Desc: not available Url : http://dovecot.org/pipermail/dovecot/attachments/20051214/c3493d0b/dovecot-0001.obj

...>> Hi all, >> >> Probably won't read mail. Linus, I'll have pull requests early >> next week; if there's anything needed I'm sure Michael Tsirkin can >> handle it. > > Sure. > Rusty, there's a small chance virtio 1.0 bits will be ready in time. > I started working on them based on your virtio-pci-new-layout branch. > > If ready before the merge window, are you ok with me merging this > support (without you having the opportunity to review first)? Sorry, absolutely not. I *really* want to review this in depth; if we...

On Wed, Dec 28, 2016 at 01:26:12PM +0200, Ala Hino wrote: > Hi guys, > > When performing live merge, in few cases, we see the following exception: [...] > libvirtError: block copy still active: disk 'vdb' not ready for pivot yet You can see if the block operation is still in progress or not by doing: `sudo virsh blockjob vm1 vdb --info`. > That exception observed in following BZs: > > https://bugzilla.redhat.com/1376580 > https://bugzilla.redhat.com/1397122 [I see, that the above are oVirt bug...