Port-xen archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Reboot on *DOM0* while/after installing GPLPV drivers



I'm having a very strange issue with a netbsd Dom0...

I have a FreeBSD guest which gives me 0 problems, and Windows7 (x64) and
Windows Server 2012 (x64) that I'm testing with.

On both Widows versions while I was installing the GPLPV drivers the
domu crashed... But the odd part is that the Dom0 simply rebooted (I
don't even see a panic), its just like someone unplugged the AC cable!

After that I can't really boot any of the windows servers because I get
the same problem while booting... I was able to revert Windows 7 and try
again, but again while installing GPLPV drivers I get this same problem!

I'm not sure how to debug this further since there no error message in
the NetBSD box...

(/var/log/messages)
--
Oct  3 21:06:40 yoda /netbsd: xvif2i0: Ethernet address 00:16:3e:19:ca:8e
Oct  3 21:06:42 yoda /netbsd: xbd backend: attach device vgXen-plexLV
(size 62914560) for domain 3
Oct  3 21:06:42 yoda /netbsd: xbd backend: attach device wd2d (size
1953525168) for domain 3
Oct  3 21:06:42 yoda /netbsd: xbd backend: attach device wd4d (size
1953525168) for domain 3
Oct  3 21:06:42 yoda /netbsd: tap1: Ethernet address f2:0b:a4:57:1d:09
Oct  3 21:06:43 yoda /netbsd: xvif3i0: Ethernet address 00:16:3e:53:3e:cf
Oct  3 21:07:18 yoda /netbsd: tap1: detached
Oct  3 21:07:27 yoda /netbsd: xbd backend domain 3 handle 0x300 (768)
using event channel 33, protocol x86_64-abi
Oct  3 21:07:27 yoda /netbsd: xbd backend domain 3 handle 0x340 (832)
using event channel 34, protocol x86_64-abi
-----> Oct  3 21:07:27 yoda /netbsd: xbd backend domain 3 handle 0x1600
(5632) using event channel 35, protocol x86_64-abi
-----> Oct  3 21:09:12 yoda syslogd[175]: restart

(xl domu log)
yoda# cat /var/log/xen/xl-w2k12.hvm.log 
Waiting for domain w2k12.hvm (domid 2) to die [pid 271]
yoda# cat /var/log/xen/xl-w2k12.hvm.log.1
Waiting for domain w2k12.hvm (domid 2) to die [pid 1013]
Domain 2 has shut down, reason code 1 0x1
Action for shutdown reason code 1 is restart
Domain 2 needs to be cleaned up: destroying the domain
Done. Rebooting now
xc: info: VIRTUAL MEMORY ARRANGEMENT:
  Loader:        0000000000100000->000000000019bbc4
  TOTAL:         0000000000000000->000000003f800000
  ENTRY ADDRESS: 0000000000100000
xc: info: PHYSICAL MEMORY ALLOCATION:
  4KB PAGES: 0x0000000000000200
  2MB PAGES: 0x00000000000001fb
  1GB PAGES: 0x0000000000000000
Waiting for domain w2k12.hvm (domid 3) to die [pid 1013]
Domain 3 has shut down, reason code 1 0x1
Action for shutdown reason code 1 is restart
Domain 3 needs to be cleaned up: destroying the domain
Done. Rebooting now
xc: info: VIRTUAL MEMORY ARRANGEMENT:
  Loader:        0000000000100000->000000000019bbc4
  TOTAL:         0000000000000000->000000003f800000
  ENTRY ADDRESS: 0000000000100000
xc: info: PHYSICAL MEMORY ALLOCATION:
  4KB PAGES: 0x0000000000000200
  2MB PAGES: 0x00000000000001fb
  1GB PAGES: 0x0000000000000000
Waiting for domain w2k12.hvm (domid 4) to die [pid 1013]
Domain 4 has shut down, reason code 1 0x1
Action for shutdown reason code 1 is restart
Domain 4 needs to be cleaned up: destroying the domain
Done. Rebooting now
xc: info: VIRTUAL MEMORY ARRANGEMENT:
  Loader:        0000000000100000->000000000019bbc4
  TOTAL:         0000000000000000->000000003f800000
  ENTRY ADDRESS: 0000000000100000
xc: info: PHYSICAL MEMORY ALLOCATION:
  4KB PAGES: 0x0000000000000200
  2MB PAGES: 0x00000000000001fb
  1GB PAGES: 0x0000000000000000
Waiting for domain w2k12.hvm (domid 5) to die [pid 1013]



Thanks!

Mike





Home | Main Index | Thread Index | Old Index