search for: capabi

...;> >> The VMs are not visible because the XML cannot be parsed if the binaries >> are not on the system (the XML contains the whole path). Also, I think >> this works because libvirt doesn't look into /usr/local/bin, but I might >> be wrong. Check whether 'virsh capabilities' tells you something about >> any emulator. >> >> You can try installing from source, but putting it in /usr/bin, > > >I put qemu-system-x86_64 and qemu-x86_64 in /usr/bin as requested. No >luck. It seems /usr/local/bin/qemu-xxx is found (see CGroup: output)...

Hi, I use Asterisk at home to filter the annoying people before they get a real voice. So basically if you don't know the extension of one of the occupants you have no choice but leave a message. Works well... perhaps I miss some improtant calls, but if you leave no message it must not be important! Anyhow, I would like to be able to make the phone ring distinctively depending on who the

...All have >root:root owner:group: > The VMs are not visible because the XML cannot be parsed if the binaries are not on the system (the XML contains the whole path). Also, I think this works because libvirt doesn't look into /usr/local/bin, but I might be wrong. Check whether 'virsh capabilities' tells you something about any emulator. You can try installing from source, but putting it in /usr/bin, you can also remove that installation, put back the one from the package and try running: { for i in qmp_capabilities query-commands quit; do echo "{'execute':'$...

...ing [s at macro-transfer:36] NoOp("SIP/joostkuif-00000003", "dial= ") in new stack -- Executing [s at macro-transfer:37] Dial("SIP/joostkuif-00000003", "DAHD= I/g1/003164616****,10") in new stack -- Making new call for cref 32772 -- Requested transfer capability: 0x00 - SPEECH > Protocol Discriminator: Q.931 (8) len=3D45 > TEI=3D0 Call Ref: len=3D 2 (reference 4/0x4) (Sent from originator) > Message Type: SETUP (5) > [04 03 80 90 a3] > Bearer Capability (len=3D 5) [ Ext: 1 Q.931 Std: 0 Info transfer capabi= lity: Speech (0) >...

...ing [s at macro-transfer:36] NoOp("SIP/joostkuif-00000003", "dial= ") in new stack -- Executing [s at macro-transfer:37] Dial("SIP/joostkuif-00000003", "DAHD= I/g1/003164616****,10") in new stack -- Making new call for cref 32772 -- Requested transfer capability: 0x00 - SPEECH > Protocol Discriminator: Q.931 (8) len=3D45 > TEI=3D0 Call Ref: len=3D 2 (reference 4/0x4) (Sent from originator) > Message Type: SETUP (5) > [04 03 80 90 a3] > Bearer Capability (len=3D 5) [ Ext: 1 Q.931 Std: 0 Info transfer capabi= lity: Speech (0) >...

...:group: >> > > The VMs are not visible because the XML cannot be parsed if the binaries > are not on the system (the XML contains the whole path). Also, I think > this works because libvirt doesn't look into /usr/local/bin, but I might > be wrong. Check whether 'virsh capabilities' tells you something about > any emulator. > > You can try installing from source, but putting it in /usr/bin, I put qemu-system-x86_64 and qemu-x86_64 in /usr/bin as requested. No luck. It seems /usr/local/bin/qemu-xxx is found (see CGroup: output) $ sudo systemctl status...

...because the XML cannot be parsed if the >>> binaries >>> are not on the system (the XML contains the whole path). Also, I think >>> this works because libvirt doesn't look into /usr/local/bin, but I >>> might >>> be wrong. Check whether 'virsh capabilities' tells you something about >>> any emulator. >>> >>> You can try installing from source, but putting it in /usr/bin, >> >> >> I put qemu-system-x86_64 and qemu-x86_64 in /usr/bin as requested. No >> luck. It seems /usr/local/bin/qemu-xxx...

...ot be parsed if the >>>> binaries >>>> are not on the system (the XML contains the whole path). Also, I think >>>> this works because libvirt doesn't look into /usr/local/bin, but I >>>> might >>>> be wrong. Check whether 'virsh capabilities' tells you something >>>> about >>>> any emulator. >>>> >>>> You can try installing from source, but putting it in /usr/bin, >>> >>> >>> I put qemu-system-x86_64 and qemu-x86_64 in /usr/bin as requested. No >&g...

I build a DomU kernel on RHEL AS5.1. But when I boot this Guest DomU with the kernel, it gives me error message: Error: (2, ''Invalid kernel'', ''xc_dom_compat_check: guest type xen-3.0-x86_32 not supported by xen kernel, sorry\n'') Can someone give me any suggestion about this problem? Thank you! Joe _______________________________________________ Xen-users