search for: darkbasic4

Distro: debian unstable Xen version: 4.0.0-2 This is the config: #HVM #still no qemu-dm in debian #kernel = "/usr/lib/xen-4.0/boot/hvmloader" #builder = ''hvm'' #memory = 2048 #name = "webserver" #vif = [''bridge=eth0''] #disk = [''tap:tapdisk:aio:/srv/xen/webserver.img,xvda,w'',''phy:/dev/cdrom,xvdb:cdrom,r'']

Hi, I explain what I want to do.. All the operators share their phones. The number of the operator isn't constant, so it's possible that two operators share all the phones. They need to move all around, so they pick up the first phone they find. If there are only few operator is very annoying for them to ear the other phones ringing while they are at the phone! So I'dd like to limit

# dd if=/dev/zero of=/srv/xen/webserver.img oflag=direct bs=1M seek=4095 count=1 # dd if=/dev/zero of=/srv/xen/webserver.img oflag=direct bs=1M count=4096 root@debian:~# grub-install /dev/xvda Searching for GRUB installation directory ... found: /boot/grub The file /boot/grub/stage1 not read correctly. Darkbasic _______________________________________________ Xen-users mailing list

...ror. Thomas, did you try with a newer version of Rules.mk? Niccol? -------- Messaggio originale -------- Oggetto: Re: [Pkg-xen-devel] xen-qemu-dm does not build with backported xen-4.1 Data: Wed, 27 Apr 2011 13:58:30 +0100 Mittente: Ian Campbell <ijc at hellion.org.uk> A: Niccol? Belli <darkbasic4 at gmail.com> On Wed, 2011-04-27 at 14:51 +0200, Niccol? Belli wrote: > Il 27/04/2011 14:37, Ian Campbell ha scritto: > > Which specific revision of qemu-xen-4.1 are you using? > > I'm using a tarball from > http://bits.xensource.com/oss-xen/release/4.1.0/xen-4.1.0.tar.gz...

Do you know if squeeze has xen support? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Package: xen-hypervisor-4.0-amd64 Version: 4.0.0-1 Severity: grave The only thing I can read is: ERROR: Unable to locate IOAPIC for GSI 2 ERROR: Unable to locate IOAPIC for GSI 9 ERROR: Unable to locate IOAPIC for GSI 9 cannot read /etc/fstab: no such file or directory mounting [...] failed: no such file or directory I boot with: moltiboot [xen] module [kernel] root=[uuid or device] ro quiet

Hey all, I have moved 10_Linux to 50_Linux and ran update-grub which is fine. The problem I have is that there is xen-syms in /boot And that is being put first in the boot list which is incorrect. How do you make /xen.gz at the top so it is booted first? Thanks Ian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com

Does pci passthrough work with latest 2.6.26-1-xen debian kernel on both dom0 and domu? Thanks Darkbasic -- Public Key 0x3CDB2D28 @ wwwkeys.eu.pgp.net -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part. Url :

I am using Debian 6.0 "Squeeze", I applied that patch (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=591456) to xen-common because of lack of hotplugpath.sh. network-route netdev=eth1 now does work, but vif-route gives me this error: root at xen-dom0:~# xm create /srv/xen/profiles/ca.cfg Using config file "/srv/xen/profiles/ca.cfg". Error: Device 0 (vif) could not be

Isn''t the correct syntax supposed to be pci=resource_alignment=03:04.0;06:00.0;0a:06.1? I get error: unknown command `06:00.0''. error: unknown command `0a:06.1''. when booting. Thank you, Darkbasic _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hi, when I receive a call from ISDN BRI (with a Sangoma A500) and I try to playback something I get the following error: **[WOOMERA]** HW DTMF supported s1c1- -- Executing [number at from-pstn:1] Answer("WOOMERA/g1/1-7b29", "") in new stack **[WOOMERA]** +++ANSWER WOOMERA/g1/1-7b29 -- Executing [number at from-pstn:2] Playback("WOOMERA/g1/1-7b29",

Hi, I continue the discussion from https://issues.asterisk.org/view.php?id=19103 If T.38 reinvite detection should still work, why it doesn't? If I use faxdetect = t38 it does never detect the fax, even using alaw. Cheers, Darkbasic

Hi, I'd like to replace my DECT + fxs phones with some wireless phones. Main problem is: what about the roaming from one ap to another? Do someone adopted the 802.11r standard? What APs and what phones do you suggest me? I'm open to suggestions but I'd like to avoid proprietary solutions, I don't want to be bound to any hardware vendor. My switch does support spanning tree

Package: xen-utils-4.0 Version: 4.0.0-2 Severity: normal This is the config: #HVM #still no qemu-dm #kernel = "/usr/lib/xen-4.0/boot/hvmloader" #builder = 'hvm' #memory = 2048 #name = "webserver" #vif = ['bridge=eth0'] #disk = ['tap:tapdisk:aio:/srv/xen/webserver.img,xvda,w','phy:/dev/cdrom,xvdb:cdrom,r'] #device-model =

Why there is no pv-grub in debian packages? Pygrub exposes dom0.

Please apply that patch to squeeze, otherwise you will not be able to boot even a standard squeeze installation! Since there is no pv-grub in squeeze I think it's quite important to fix it. Cheers, Darkbasic

> this two patches add blktap2 functionality to xen-utils. I backported > http://xenbits.xen.org/xen-unstable.hg?rev/ca2738f258f8 to remove > license issues. Has this patch been applied? Darkbasic

Package: xen-utils-4.0 Version: 4.0.1-2 http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1699 I already reported this upstream, but I think it's debian specific. Btw xen-utils-common is still bugged (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=591456). Darkbasic

I am using Debian 6.0 "Squeeze", I applied that patch (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=591456) to xen-common because of lack of hotplugpath.sh. network-route netdev=eth1 now does work, but vif-route gives me this error: root at xen-dom0:~# xm create /srv/xen/profiles/ca.cfg Using config file "/srv/xen/profiles/ca.cfg". Error: Device 0 (vif) could not be

Hi, I set verbose to 3, but I do not see any RINGING notification in the CLI. On the contrary, when the phone goes UNREACHABLE I get: [Dec 13 21:10:06] NOTICE[9988]: chan_sip.c:25533 sip_poke_noanswer: Peer '152' is now UNREACHABLE! Last qualify: 130 == Extension Changed 152[blf] new state Unavailable for Notify User 154 [Dec 13 21:11:08] NOTICE[9988]: chan_sip.c:20196