Re: using virsh and virt-manager for XEN on FreeBSD

2019-02-21 Thread Roman Bogorodskiy
  Eric Bautsch wrote:

> Hi All
> 
> 
> And one more:
> 
> root@bianca # virsh -V
> Virsh command line tool of libvirt 4.10.0
> See web site at https://libvirt.org/
> 
> Compiled with support for:
>   Hypervisors: VMware PHYP VirtualBox ESX Bhyve Test
>   Networking: Remote Network Bridging
>   Storage: Dir ZFS
>   Miscellaneous: Daemon Secrets Debug Readline
> root@bianca # virsh -c xen:///system
> error: failed to connect to the hypervisor
> error: no connection driver available for xen:///system
> 
> 
> Based on this output, I'm assuming that virsh (and virt-manager, too) wasn't 
> compiled with XEN support on FreeBSD.
> 
> 
> However, this page (from 2015):
> https://forums.freebsd.org/threads/libvirt-libxl-on-freebsd.51862/
> 
> 
> Would seem to suggest that it should work.
> 
> 
> Should I just stop trying and compile my own virsh and virt-manager?
> 
> 
> Sorry, this seems like a stupid question again.
> 
> Eric

Hi Eric,

virsh comes from the devel/libvirt port (or respectful package). On
amd64, it has XEN option available which adds Xen support through libxl.
However, it's not enabled by default (therefore if you're installing
libvirt from an official repo, it won't be enabled), so you'll have to
build your own version with this option enabled.

IIRC, virt-manager supports Xen by default and does not need any
additional configuration.
> 
> 
> -- 
>   
>
>   /  .   Eric A. Bautsch
>  /--   __   _________
> /     //   /  /
>(_/(___(__/   email: eric.baut...@pobox.com
> 



Roman Bogorodskiy


signature.asc
Description: PGP signature


Re: Xen dom0 crash

2015-05-22 Thread Roman Bogorodskiy
  Roger Pau Monné wrote:

 El 18/05/15 a les 15.04, Eggert, Lars ha escrit:
  Hi,
  
  I'm trying to boot a Xen dom0 on another machine (Fujitsu RX308) and Xen 
  crashes when starting the kernel. Log below; any ideas?
  
  Thanks,
  Lars
  (XEN) [ Xen-4.6-unstable  x86_64  debug=y  Not tainted ]
  (XEN) CPU:0
  (XEN) RIP::[80854000]
  (XEN) RFLAGS: 0200   CONTEXT: hvm guest (d0v0)
  (XEN) rax:    rbx: 82d0802e8000   rcx: 82d0802eff80
  (XEN) rdx: 82d0801e1500   rsi:    rdi: 82d0801ed77c
  (XEN) rbp: 82d0801061d2   rsp: 81bb5000   r8:  83103ff0
  (XEN) r9:  82d08010623f   r10: 82d0802eff70   r11: 
  (XEN) r12: 82d0802eff50   r13: 831033ae7000   r14: 83103ff0
  (XEN) r15: 82d08018eae3   cr0: 8011   cr4: 0020
  (XEN) cr3: 01ba1000   cr2: 
  (XEN) ds:    es:    fs:    gs:    ss:    cs: 
  (XEN) Guest stack trace from rsp=81bb5000:
  (XEN)   Fault while accessing guest memory.
  (XEN) Hardware Dom0 crashed: rebooting machine in 5 seconds.
  (XEN) Resetting with ACPI MEMORY or I/O RESET_REG.
 
 Hello,
 
 This looks very similar to the crash reported at:
 
 https://lists.freebsd.org/pipermail/freebsd-xen/2015-April/002315.html
 
 Which was also reported at xen-devel, but nobody seems to have looked
 into it.
 
 Could you send a bug report to xen-devel with the following trace
 (please make sure to mention PVH in the subject line) CCing the Intel
 VT-X maintainers? (the emails are in the MAINTAINERS file in the Xen
 source tree).

H,

I'm observing a crash that looks similar to me:

(XEN) [ Xen-4.5.0  x86_64  debug=n  Not tainted ]
(XEN) CPU:0
(XEN) RIP:0020:[8034a2f3]
(XEN) RFLAGS: 00010246   CONTEXT: hvm guest
(XEN) rax: f800d887c1b0   rbx: f8000ed85100   rcx: 
(XEN) rdx: 81788560   rsi: 0008   rdi: f8000ed85100
(XEN) rbp: fe023956a850   rsp: fe023956a850   r8:  815056f8
(XEN) r9:  8178857c   r10: f8000ea9e0f0   r11: 81664200
(XEN) r12: 0004   r13: 80ee832b   r14: f8000ed85118
(XEN) r15: f8000ed85100   cr0: 8005003b   cr4: 000406e0
(XEN) cr3: 02cca000   cr2: 00080a8da140
(XEN) ds: 003b   es: 003b   fs: 0013   gs: 001b   ss: 0028   cs: 0020
(XEN) Guest stack trace from rsp=fe023956a850:
(XEN)   Fault while accessing guest memory.
(XEN) Domain 0 crashed: rebooting machine in 5 seconds.
(XEN) Resetting with ACPI MEMORY or I/O RESET_REG.

I'm wondering if it's related to the same issue?

It's triggered only when I try to reboot/poweroff the guest.

Roman Bogorodskiy



pgpMB7f3P5A43.pgp
Description: PGP signature


Re: Xen dom0 crash

2015-05-22 Thread Roman Bogorodskiy
  Roman Bogorodskiy wrote:

   Roger Pau Monné wrote:
 
  El 18/05/15 a les 15.04, Eggert, Lars ha escrit:
   Hi,
   
   I'm trying to boot a Xen dom0 on another machine (Fujitsu RX308) and Xen 
   crashes when starting the kernel. Log below; any ideas?
   
   Thanks,
   Lars
   (XEN) [ Xen-4.6-unstable  x86_64  debug=y  Not tainted ]
   (XEN) CPU:0
   (XEN) RIP::[80854000]
   (XEN) RFLAGS: 0200   CONTEXT: hvm guest (d0v0)
   (XEN) rax:    rbx: 82d0802e8000   rcx: 
   82d0802eff80
   (XEN) rdx: 82d0801e1500   rsi:    rdi: 
   82d0801ed77c
   (XEN) rbp: 82d0801061d2   rsp: 81bb5000   r8:  
   83103ff0
   (XEN) r9:  82d08010623f   r10: 82d0802eff70   r11: 
   
   (XEN) r12: 82d0802eff50   r13: 831033ae7000   r14: 
   83103ff0
   (XEN) r15: 82d08018eae3   cr0: 8011   cr4: 
   0020
   (XEN) cr3: 01ba1000   cr2: 
   (XEN) ds:    es:    fs:    gs:    ss:    cs: 
   (XEN) Guest stack trace from rsp=81bb5000:
   (XEN)   Fault while accessing guest memory.
   (XEN) Hardware Dom0 crashed: rebooting machine in 5 seconds.
   (XEN) Resetting with ACPI MEMORY or I/O RESET_REG.
  
  Hello,
  
  This looks very similar to the crash reported at:
  
  https://lists.freebsd.org/pipermail/freebsd-xen/2015-April/002315.html
  
  Which was also reported at xen-devel, but nobody seems to have looked
  into it.
  
  Could you send a bug report to xen-devel with the following trace
  (please make sure to mention PVH in the subject line) CCing the Intel
  VT-X maintainers? (the emails are in the MAINTAINERS file in the Xen
  source tree).
 
 H,
 
 I'm observing a crash that looks similar to me:
 
 (XEN) [ Xen-4.5.0  x86_64  debug=n  Not tainted ]
 (XEN) CPU:0
 (XEN) RIP:0020:[8034a2f3]
 (XEN) RFLAGS: 00010246   CONTEXT: hvm guest
 (XEN) rax: f800d887c1b0   rbx: f8000ed85100   rcx: 
 (XEN) rdx: 81788560   rsi: 0008   rdi: f8000ed85100
 (XEN) rbp: fe023956a850   rsp: fe023956a850   r8:  815056f8
 (XEN) r9:  8178857c   r10: f8000ea9e0f0   r11: 81664200
 (XEN) r12: 0004   r13: 80ee832b   r14: f8000ed85118
 (XEN) r15: f8000ed85100   cr0: 8005003b   cr4: 000406e0
 (XEN) cr3: 02cca000   cr2: 00080a8da140
 (XEN) ds: 003b   es: 003b   fs: 0013   gs: 001b   ss: 0028   cs: 0020
 (XEN) Guest stack trace from rsp=fe023956a850:
 (XEN)   Fault while accessing guest memory.
 (XEN) Domain 0 crashed: rebooting machine in 5 seconds.
 (XEN) Resetting with ACPI MEMORY or I/O RESET_REG.
 
 I'm wondering if it's related to the same issue?
 
 It's triggered only when I try to reboot/poweroff the guest.
 
 Roman Bogorodskiy

And the full log from guest start to crash:

https://dpaste.de/mWNu


Roman Bogorodskiy


pgpX3J5D6I0Rq.pgp
Description: PGP signature


Re: Xen dom0 crash

2015-05-22 Thread Roman Bogorodskiy
  Roger Pau Monné wrote:

 El 22/05/15 a les 18.40, Roman Bogorodskiy ha escrit:
  No, the guest is:
  
  FreeBSD 10.0-RELEASE amd64.
  
  Here's dmesg.boot from dom0:
  
  https://dpaste.de/ey7Q
 
 I think I know what's going on, you are using a rather old kernel (from
 27/04/15) which doesn't contain r282634. Could you update your Dom0
 kernel to recent HEAD and try again?

That worked, thanks!

Roman Bogorodskiy


pgptElbXey3Lc.pgp
Description: PGP signature