Is there a way that I can monitor all xenstore activity? The sort of thing I am after is output like: D2045: /local/domain/2045/device/vbd/state set to "4" D0: /local/domain/2045/device/vbd/state watch fired D0: /local/domain/2045/device/vbd/state read value "4" etc OpenSolaris Dom0 doesn''t appear to want to talk to the Windows GPLPV drivers and I suspect that I''m doing something wrong in the xenbus arena... monitoring exactly what I do vs what a Linux PV DomU does would be educational! Thanks James _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Am Freitag, 7. November 2008 schrieb James Harper:> Is there a way that I can monitor all xenstore activity? > > The sort of thing I am after is output like: > > D2045: /local/domain/2045/device/vbd/state set to "4" > D0: /local/domain/2045/device/vbd/state watch fired > D0: /local/domain/2045/device/vbd/state read value "4"You must set export XENSTORED_TRACE=1 before starting xend. You can search for XENSTORED_TRACE in /usr/bin/xend. Then a trace file /var/log/xen/xenstored-trace.log is written. You will see such lines: IN 0x516a70 20081010 08:20:33 GET_DOMAIN_PATH (1 ) OUT 0x516a70 20081010 08:20:33 GET_DOMAIN_PATH (/local/domain/1 ) IN 0x5373e0 20081010 08:20:33 READ (/local/domain/1/serial/0/ring-ref ) OUT 0x5373e0 20081010 08:20:33 ERROR (ENOENT ) Dietmar.> > etc > > OpenSolaris Dom0 doesn''t appear to want to talk to the Windows GPLPV > drivers and I suspect that I''m doing something wrong in the xenbus > arena... monitoring exactly what I do vs what a Linux PV DomU does would > be educational! > > Thanks > > James > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
> > You must set > export XENSTORED_TRACE=1 > before starting xend. You can search for XENSTORED_TRACE in/usr/bin/xend.> Then a trace file /var/log/xen/xenstored-trace.log is written. > You will see such lines: > IN 0x516a70 20081010 08:20:33 GET_DOMAIN_PATH (1 ) > OUT 0x516a70 20081010 08:20:33 GET_DOMAIN_PATH (/local/domain/1 ) > IN 0x5373e0 20081010 08:20:33 READ (/local/domain/1/serial/0/ring-ref)> OUT 0x5373e0 20081010 08:20:33 ERROR (ENOENT ) >Should xend restart without any problems? After restarting xend, xenstore-ls just says: " tool = "" xenstored = "" vm = "" Segmentation fault Message from syslogd@bitvs2 at Fri Nov 7 21:33:34 2008 ... bitvs2 kernel: invalid opcode: 0000 [3] SMP " And this is in dmesg: " ----------- [cut here ] --------- [please bite here ] --------- Kernel BUG at drivers/xen/xenbus/xenbus_dev.c:112 invalid opcode: 0000 [4] SMP CPU 0 Modules linked in: iptable_filter ip_tables ipmi_poweroff ipmi_si ipmi_devintf ipmi_msghandler tun tcp_diag inet_diag mptctl mptbase xt_physdev x_tables ppdev parport_pc lp parport button ac battery ipv6 bridge fuse xen_scsibk eeprom sg 8021q netloop loop shpchp pci_hotplug serial_core pcspkr i2c_nforce2 i2c_core st tsdev evdev xfs dm_mirror dm_snapshot dm_mod raid1 md_mod ide_generic ide_cd cdrom sata_nv libata usbhid cciss tg3 generic aic7xxx scsi_transport_spi scsi_mod amd74xx ohci_hcd ehci_hcd ide_core fan Pid: 17077, comm: xenstore-ls Not tainted 2.6.18-6-xen-amd64 #1 RIP: e030:[<ffffffff80369201>] [<ffffffff80369201>] queue_reply+0x61/0x93 RSP: e02b:ffff88000c9e9e88 EFLAGS: 00010206 RAX: 0000000000001248 RBX: ffff880035abc000 RCX: 0000000000001238 RDX: 0000000000001200 RSI: ffff880035abd239 RDI: ffff880018152048 RBP: ffff880018150000 R08: ffff880018152038 R09: 0000000000000000 R10: ffff880018150024 R11: ffff88003a218770 R12: ffff880018152048 R13: 0000000000001238 R14: ffff880018150024 R15: 0000000000602100 FS: 00002adefe772af0(0000) GS:ffffffff804c3000(0000) knlGS:0000000000000000 CS: e033 DS: 0000 ES: 0000 Process xenstore-ls (pid: 17077, threadinfo ffff88000c9e8000, task ffff88003a218770) Stack: 0000000000000001 0000000000000000 ffff880018150000 0000000000000001 ffff880035abc000 ffffffff803695c5 ffff88003a218770 0000000000000004 0000000000000000 0000000200000000 Call Trace: [<ffffffff803695c5>] xenbus_dev_write+0x18a/0x33f [<ffffffff80216ac9>] vfs_write+0xce/0x174 [<ffffffff802172ec>] sys_write+0x45/0x6e [<ffffffff8025be4a>] system_call+0x86/0x8b [<ffffffff8025bdc4>] system_call+0x0/0x8b Code: 0f 0b 68 2e e8 41 80 c2 70 00 4c 89 e7 e8 db 5c ef ff 41 58 RIP [<ffffffff80369201>] queue_reply+0x61/0x93 RSP <ffff88000c9e9e88> " Good thing I''m using my dev machine :) Thanks James _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On 7/11/08 10:35, "James Harper" <james.harper@bendigoit.com.au> wrote:> > Should xend restart without any problems? > After restarting xend, xenstore-ls just says: > > " > tool = "" > xenstored = "" > vm = "" > Segmentation fault > > Message from syslogd@bitvs2 at Fri Nov 7 21:33:34 2008 ... > bitvs2 kernel: invalid opcode: 0000 [3] SMP > "Restarting xenstored is a bad idea. ;-) That said, ''xend restart'' shouldn''t restart xenstored. -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
> On 7/11/08 10:35, "James Harper" <james.harper@bendigoit.com.au>wrote:> > > > > Should xend restart without any problems? > > After restarting xend, xenstore-ls just says: > > > > " > > tool = "" > > xenstored = "" > > vm = "" > > Segmentation fault > > > > Message from syslogd@bitvs2 at Fri Nov 7 21:33:34 2008 ... > > bitvs2 kernel: invalid opcode: 0000 [3] SMP > > " > > Restarting xenstored is a bad idea. ;-) > > That said, ''xend restart'' shouldn''t restart xenstored. >It didn''t. ''xm list'' still worked, but ''xenstore-ls'' gave the above error. I have seen that before under 3.1.2 when domid reached a few thousand, but just thought it was because it was full. I did, however, restart xenstore manually after I saw that error, and found out for myself what a bad idea that was :) Thanks James _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On 7/11/08 10:53, "James Harper" <james.harper@bendigoit.com.au> wrote:> It didn''t. ''xm list'' still worked, but ''xenstore-ls'' gave the above > error. I have seen that before under 3.1.2 when domid reached a few > thousand, but just thought it was because it was full.Okay. Then I might guess that the xenbus driver in your dom0 kernel has got upset that one of its clients went away in the middle of some operation? The BUG() that triggered in your backtrace doesn''t exist in our current 2.6.18 tree. Perhaps some bug or limitation got fixed some time ago? -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
> On 7/11/08 10:53, "James Harper" <james.harper@bendigoit.com.au>wrote:> > > It didn''t. ''xm list'' still worked, but ''xenstore-ls'' gave the above > > error. I have seen that before under 3.1.2 when domid reached a few > > thousand, but just thought it was because it was full. > > Okay. Then I might guess that the xenbus driver in your dom0 kernelhas> got > upset that one of its clients went away in the middle of someoperation?> The > BUG() that triggered in your backtrace doesn''t exist in our current2.6.18> tree. Perhaps some bug or limitation got fixed some time ago? >Very possibly. This is all running on Debian and the kernel is from 3.0.x vintage. I''ll ignore the error :) Thanks James _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Fri, Nov 07, 2008 at 09:12:04PM +1100, James Harper wrote:> The sort of thing I am after is output like: > > D2045: /local/domain/2045/device/vbd/state set to "4" > D0: /local/domain/2045/device/vbd/state watch fired > D0: /local/domain/2045/device/vbd/state read value "4" > > etc > > OpenSolaris Dom0 doesn''t appear to want to talk to the Windows GPLPV > drivers and I suspect that I''m doing something wrong in the xenbus > arena... monitoring exactly what I do vs what a Linux PV DomU does would > be educational!If you''re interested in fixing this and have a spare space for actually trying OpenSolaris dom0, you might like /usr/lib/xen/bin/xenstore-snoop: interpol:~ # /usr/lib/xen/bin/xenstore-snoop DOM PID TX OP 0 103781 0 XS_GET_DOMAIN_PATH: 0 -> /local/domain/0 0 103781 0 XS_TRANSACTION_START: -> 154491 0 103781 154491 [ERROR] XS_DIRECTORY: /local/domain/0/backend/vtpm/31 -> ENOENT 0 103781 154491 XS_TRANSACTION_END: T -> OK 0 103781 0 XS_TRANSACTION_START: -> 154492 0 103781 154492 XS_READ: /local/domain/31/console/port -> 2 0 103781 154492 XS_TRANSACTION_END: T -> OK 0 103781 0 XS_TRANSACTION_START: -> 154493 0 103781 154493 [ERROR] XS_READ: /local/domain/31/console/vnc-port -> ENOENT (You can do this without restarting xenstored too.) regards john _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel