search for: xend_debug

...n/xend/server/ > SrvDaemon.py > --- a/tools/python/xen/xend/server/SrvDaemon.py Wed Oct 25 10:25:18 > 2006 +0100 > +++ b/tools/python/xen/xend/server/SrvDaemon.py Wed Oct 25 10:27:03 > 2006 +0100 > @@ -106,12 +106,12 @@ class Daemon: > os.close(2) > if XEND_DEBUG: > os.open(''/dev/null'', os.O_RDONLY) > - os.open(XEND_DEBUG_LOG, os.O_WRONLY|os.O_CREAT) > + os.open(XEND_DEBUG_LOG, os.O_WRONLY|os.O_CREAT| > os.O_APPEND) > os.dup(1) > else: > os.open(...

...cpus = 1 + memory = 512 + name = "rhel5" + disk = [ 'file:/root/rhel5.img,xvda1,w' ] + root = "/dev/xvda1 ro" + extra= "rhgb console=hvc0" + + 2. After boot xen and dom0, start xend + # /etc/init.d/xend start + ( In the debugging case, # XEND_DEBUG=1 xend trace_start ) + + 3. start domU + # xm create -c rhel5 + +========= +Reference +========= +- Wiki of Xen/IA64 upstream merge + http://wiki.xensource.com/xenwiki/XenIA64/UpstreamMerge + +Written by Akio Takebe <takebe_akio at jp.fujitsu.com> on 28 May 2008 -- 1.6.0.2 On Thu, Oct...

...cpus = 1 + memory = 512 + name = "rhel5" + disk = [ 'file:/root/rhel5.img,xvda1,w' ] + root = "/dev/xvda1 ro" + extra= "rhgb console=hvc0" + + 2. After boot xen and dom0, start xend + # /etc/init.d/xend start + ( In the debugging case, # XEND_DEBUG=1 xend trace_start ) + + 3. start domU + # xm create -c rhel5 + +========= +Reference +========= +- Wiki of Xen/IA64 upstream merge + http://wiki.xensource.com/xenwiki/XenIA64/UpstreamMerge + +Written by Akio Takebe <takebe_akio at jp.fujitsu.com> on 28 May 2008 -- 1.6.0.2 On Thu, Oct...

...irq) ) > 415 return -EPERM; > 416 > > And I wonder if the XEN_DOMCTL_irq_permission aka, xc_domain_irq_permission > had been called. I remember that at some point we missed it for Xend.. > > Could you enable Xend debugging (if you are using that): > > export XEND_DEBUG=1 > /etc/init.d/xend start > > And try starting the guest. Then grep in /var/log/xen/xend.log for > "pci: enabling irq " > > You should see 18, 17 and 21. > > Also if you do 'xl debug-keys i && xl dmesg' > > You should see that the IRQ 17,...

...And I wonder if the XEN_DOMCTL_irq_permission aka, xc_domain_irq_permission > had been called. I remember that at some point we missed it for Xend.. > > Could you enable Xend debugging (if you are using that): > I'm using xl. Is there a similar setting for that? > > export XEND_DEBUG=1 > /etc/init.d/xend start > > And try starting the guest. Then grep in /var/log/xen/xend.log for > "pci: enabling irq " > > You should see 18, 17 and 21. > > Also if you do 'xl debug-keys i && xl dmesg' > > You should see that the IRQ 17, 18,...

Hi. This patchset implements ia64/xen domU support based on ia64/pv_ops frame work which was already merged to linux ia64 test branch. This patch is for linux ia64 test branch. This patchset does the followings. - Some preparation work. Mainly importing header files to define related structures. - Then, define functions related to hypercall which is the way to communicate with Xen hypervisor.

Hi. This patchset implements ia64/xen domU support based on ia64/pv_ops frame work which was already merged to linux ia64 test branch. This patch is for linux ia64 test branch. This patchset does the followings. - Some preparation work. Mainly importing header files to define related structures. - Then, define functions related to hypercall which is the way to communicate with Xen hypervisor.

Hi. This patchset is ia64/xen domU patch take 8 which was updated following Tony's review. (Thank you very much, Tony.) This patchset implements ia64/xen domU support based on ia64/pv_ops frame work which was sent as another patchest. This patchset is for linux ia64 test branch and depends on some patches for xen common part I'll send separately. To compile, the changesets in x86/xen

Hi. This patchset is ia64/xen domU patch take 8 which was updated following Tony's review. (Thank you very much, Tony.) This patchset implements ia64/xen domU support based on ia64/pv_ops frame work which was sent as another patchest. This patchset is for linux ia64 test branch and depends on some patches for xen common part I'll send separately. To compile, the changesets in x86/xen

This patchset is ia64/xen domU patch take 9 which is rebased to 2.6.26 This patchset implements ia64/xen domU support based on ia64/pv_ops frame work which was sent as another patchest. This patchset does the followings. - Some preparation work. Mainly importing header files to define related structures. - Then, define functions related to hypercall which is the way to communicate with Xen

This patchset is ia64/xen domU patch take 9 which is rebased to 2.6.26 This patchset implements ia64/xen domU support based on ia64/pv_ops frame work which was sent as another patchest. This patchset does the followings. - Some preparation work. Mainly importing header files to define related structures. - Then, define functions related to hypercall which is the way to communicate with Xen

This patchset is ia64/xen domU patch take 10 which is rebased to 2.6.27-rc4. This patchset implements ia64/xen domU support based on ia64/pv_ops frame work which was sent as another patchest. This patchset does the followings. - Some preparation work. Mainly importing header files to define related structures. - Then, define functions related to hypercall which is the way to communicate with

This patchset is ia64/xen domU patch take 10 which is rebased to 2.6.27-rc4. This patchset implements ia64/xen domU support based on ia64/pv_ops frame work which was sent as another patchest. This patchset does the followings. - Some preparation work. Mainly importing header files to define related structures. - Then, define functions related to hypercall which is the way to communicate with

This patchset is ia64/xen domU patch take 11. Tony, please commit those patches. They are ready to commit because all the issues which were pointed out had been addressed and got enough reviews. This patchset does the followings. - Some preparation work. Mainly importing header files to define related structures. - Then, define functions related to hypercall which is the way to communicate

This patchset is ia64/xen domU patch take 11. Tony, please commit those patches. They are ready to commit because all the issues which were pointed out had been addressed and got enough reviews. This patchset does the followings. - Some preparation work. Mainly importing header files to define related structures. - Then, define functions related to hypercall which is the way to communicate

This patchset is ia64/xen domU patch take 12. Tony, please commit those patches. They are ready to commit because all the issues which were pointed out had been addressed and got enough reviews. This patchset does the followings. - Some preparation work. Mainly importing header files to define related structures. - Then, define functions related to hypercall which is the way to communicate

This patchset is ia64/xen domU patch take 12. Tony, please commit those patches. They are ready to commit because all the issues which were pointed out had been addressed and got enough reviews. This patchset does the followings. - Some preparation work. Mainly importing header files to define related structures. - Then, define functions related to hypercall which is the way to communicate