Re: xen 4.5.0 packages available

[Patrick Welche <prlw1%cam.ac.uk@localhost>]

On Tue, Jan 27, 2015 at 05:12:32PM +0100, Manuel Bouyer wrote:
> From ktrace, xl without argument doens't seem to rely on xen-specific
> kernel services, or other userland daemons.
> Can you get a kernel stack trace of the hung process ?

This is getting messy... Reboot, and

xl with no arguments prints usage
ls /kern/xen works

Now try
# cat nbsd.cfg 
kernel = "/netbsd-XEN_DOMU"
name = "netbsd"
vcpus = 2
memory = 512
# ktrace xl -v create -c nbsd.cfg 
Parsing config from nbsd.cfg

and

  PID USERNAME PRI NICE   SIZE   RES STATE      TIME   WCPU    CPU COMMAND
 1391 root     117    0    32M 2408K tstile     0:00  0.00%  0.00% xl

the end of kdump pasted at the end of this email.

Now trying:
# ls /kern/xen
privcmd  xenbus   xsd_port
# ls -l /kern/xen

hangs. (This time xl without arguments doesn't hang)

So my conf file and -current/amd64 DOMU kernel may yet be at fault...

Cheers,

Patrick

  1391      1 xl       NAMI  "/usr/pkg/libexec/xen/bin/qemu-system-i386"
  1391      1 xl       RET   access 0
  1391      1 xl       CALL  ioctl(5,_IOWR('P',0,0x38),0x7f7fffffced0)
  1391      1 xl       GIO   fd 5 wrote 56 bytes
       "#\0\0\0\0\0\0\0\^D\M-@\M-1\M-w\^?\^?\0\0\0\M-,\M^?\M-w\^?\^?\0\0\0\M-(\M^?\M-w\^?\^?\0\0\M^C\^A\0\0\0\0\0\0\^A\
        \0\0\0\0\0\0\0\M-0\M-Q\M^?\M^?\^?\^?\0\0"
  1391      1 xl       GIO   fd 5 read 56 bytes
       "#\0\0\0\0\0\0\0\^D\M-@\M-1\M-w\^?\^?\0\0\0\M-,\M^?\M-w\^?\^?\0\0\0\M-(\M^?\M-w\^?\^?\0\0\M^C\^A\0\0\0\0\0\0\^A\
        \0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"
  1391      1 xl       RET   ioctl 0
  1391      1 xl       CALL  ioctl(5,_IOWR('P',0,0x38),0x7f7fffffcf50)
  1391      1 xl       GIO   fd 5 wrote 56 bytes
       "\f\0\0\0\0\0\0\0\^R\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\M^P\M-O\M^?\M^?\^?\^?\0\0\^D\M-@\M-1\M-w\^?\^?\0\0\0\M-X\M-0\
        \M-w\^?\^?\0\0\^R\0\0\0\0\0\0\0"
  1391      1 xl       GIO   fd 5 read 56 bytes
       "\f\0\0\0\0\0\0\0\^R\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\M^P\M-O\M^?\M^?\^?\^?\0\0\^D\M-@\M-1\M-w\^?\^?\0\0\0\M-X\M-0\
        \M-w\^?\^?\0\0\0\0\0\0\0\0\0\0"
  1391      1 xl       RET   ioctl 0
  1391      1 xl       CALL  ioctl(5,_IOWR('P',0,0x38),0x7f7fffffcf50)
  1391      1 xl       GIO   fd 5 wrote 56 bytes
       "\f\0\0\0\0\0\0\0\^S\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\^F\^B\0\0\0\0\0\0\0\0\0\0\0\0\0\0\M^P\M-O\M^?\M^?\^?\^?\0\0\
        \^D\M-@\M-1\M-w\^?\^?\0\0"
  1391      1 xl       GIO   fd 5 read 56 bytes
       "\f\0\0\0\0\0\0\0\^S\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\^F\^B\0\0\0\0\0\0\0\0\0\0\0\0\0\0\M^P\M-O\M^?\M^?\^?\^?\0\0\
        \0\0\0\0\0\0\0\0"
  1391      1 xl       RET   ioctl 0
  1391      1 xl       CALL  __sigaction_sigtramp(SIGPIPE,0x7f7fffffcf40,0x7f7fffffcf20,0x7f7ff60a0250,2)
  1391      1 xl       RET   __sigaction_sigtramp 0
  1391      1 xl       CALL  write(6,0x7f7fffffcf60,0x10)
  1391      1 xl       GIO   fd 6 wrote 16 bytes
       "\^B\0\0\0\0\0\0\0\0\0\0\0%\0\0\0"
  1391      1 xl       RET   write 16/0x10
  1391      1 xl       CALL  write(6,0x7f7ff7460758,0x25)