Re: Kernel Panic on FreeBSD guests with libvirt 1.2.2 and qemu 1.7.91

2014-05-02 Thread Andre Goree

On 05/02/2014 3:42 pm, Andre Goree wrote:

On 05/02/2014 2:18 pm, Juergen Lock wrote:
In article <201405021800.s42i0tie094...@enceladus10.kn-bremen.de> you 
write:
In article 
 
you write:

On 05/01/2014 11:00 am, Andre Goree wrote:

Hello,

I'm running libvirt 1.2.2 and QEMU 1.7.91 on an Ubuntu 12.04LTS 
host.
Prior to a recent upgrade, I've been able to run FreeBSD guests 
(both

10.0 and 9.2) perfectly fine without issue.  Now, this the
aforementioned versions, I'm running into a kernel panic almost
immediately after booting, same message with both 10.0 & 9.2:  
"Fatal

trap 12: page fault while in kernel mode".

To ensure that it had nothing to do with my configuration [of the
guest OS] I've tried installing the guest from guest using
virt-install, however I still run into the same kernel panic.  
It'll
be hard for me to post the output of the panic, so I'll try to show 
as

much info as possible via images[1].

Upon researching, I've come across a few threads (e.g., this 
one[2])
that appear to be related, but none have helped.  Any information 
that

you can provide to help me get to the root of this issue would be
greatly appreciated!

[1]http://www.drenet.net/images/panic1.png
http://www.drenet.net/images/panic2.png
http://www.drenet.net/images/panic_noacpi1.png
http://www.drenet.net/images/panic_noacpi2.png

[2]http://forums.freebsd.org/viewtopic.php?t=36761



After using my noggin a bit, I've determine the culprit to be atkbd. 
 If
I disable it via the bootloader with "set hint.atkbd.0.disabled=1", 
the
vm will boot fine.  HOWEVER, my problem then is that I cannot use 
the
keyboard via VNC.  I'm trying to figure out ways around this...any 
help
would be much appreciated.  I've already tried setting different 
flags

for atkbd, but no matter which flag I set, I get the kernel panic --
ostensibly because atkbd is enabled (as it must be for a flag to be 
set

for it).


I think you have hit this issue for which the workaround is a patch
to seabios:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug


Hm for some reason that link got truncated, try this one:

https://bugs.debian.org/737142



http://git.qemu.org/?p=seabios.git;a=commit;h=8032b8a0fec550de5cb2f7d37aa031cebc2200c3

References:

http://article.gmane.org/gmane.comp.emulators.qemu/254414/

https://lists.gnu.org/archive/html/qemu-stable/2013-03/msg00037.html



Juergen
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to
"freebsd-virtualization-unsubscr...@freebsd.org"


Lol, yeah, I was gonna say...but thanks!  Not sure if I'm into
implementing a patch vs. finding a way around this, and I'm wondering
why it reared it's head after an update to libvirt & qemu vs. earlier
in my testing -- makes me think it may be an unrelated, albeit similar
bug.  Thanks again Juergen.


Btw, from the link you posted:

"From: Michael Tokarev 
To: 737142-cl...@bugs.debian.org
Subject: Bug#737142: fixed in seabios 1.7.4-4
Source: seabios
Source-Version: 1.7.4-4

We believe that the bug you reported is fixed in the latest version of
seabios, which is due to be installed in the Debian FTP archive."

and on my host server having the issue:
"# dpkg -l |grep seabio
ii  seabios  1.7.4-4~cloud0  
   Legacy BIOS implementation"


I'll try to determine which version of seabios I had running initially 
before the issue, however from what I can tell, an upgrade to the 
version that _should_ have fixed this appears be what caused my issue in 
the first place, heh.



--
Andre Goree
-=-=-=-=-=-
Email - andre at drenet.net
Website   - http://www.drenet.net
PGP key   - http://www.drenet.net/pubkey.txt
-=-=-=-=-=-
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"


Re: Kernel Panic on FreeBSD guests with libvirt 1.2.2 and qemu 1.7.91

2014-05-02 Thread Andre Goree

On 05/02/2014 2:18 pm, Juergen Lock wrote:
In article <201405021800.s42i0tie094...@enceladus10.kn-bremen.de> you 
write:
In article 
 
you write:

On 05/01/2014 11:00 am, Andre Goree wrote:

Hello,

I'm running libvirt 1.2.2 and QEMU 1.7.91 on an Ubuntu 12.04LTS 
host.
Prior to a recent upgrade, I've been able to run FreeBSD guests 
(both

10.0 and 9.2) perfectly fine without issue.  Now, this the
aforementioned versions, I'm running into a kernel panic almost
immediately after booting, same message with both 10.0 & 9.2:  
"Fatal

trap 12: page fault while in kernel mode".

To ensure that it had nothing to do with my configuration [of the
guest OS] I've tried installing the guest from guest using
virt-install, however I still run into the same kernel panic.  It'll
be hard for me to post the output of the panic, so I'll try to show 
as

much info as possible via images[1].

Upon researching, I've come across a few threads (e.g., this one[2])
that appear to be related, but none have helped.  Any information 
that

you can provide to help me get to the root of this issue would be
greatly appreciated!

[1]http://www.drenet.net/images/panic1.png
http://www.drenet.net/images/panic2.png
http://www.drenet.net/images/panic_noacpi1.png
http://www.drenet.net/images/panic_noacpi2.png

[2]http://forums.freebsd.org/viewtopic.php?t=36761



After using my noggin a bit, I've determine the culprit to be atkbd.  
If
I disable it via the bootloader with "set hint.atkbd.0.disabled=1", 
the

vm will boot fine.  HOWEVER, my problem then is that I cannot use the
keyboard via VNC.  I'm trying to figure out ways around this...any 
help
would be much appreciated.  I've already tried setting different 
flags

for atkbd, but no matter which flag I set, I get the kernel panic --
ostensibly because atkbd is enabled (as it must be for a flag to be 
set

for it).


I think you have hit this issue for which the workaround is a patch
to seabios:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug


Hm for some reason that link got truncated, try this one:

https://bugs.debian.org/737142



http://git.qemu.org/?p=seabios.git;a=commit;h=8032b8a0fec550de5cb2f7d37aa031cebc2200c3

References:

http://article.gmane.org/gmane.comp.emulators.qemu/254414/

https://lists.gnu.org/archive/html/qemu-stable/2013-03/msg00037.html



Juergen
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to
"freebsd-virtualization-unsubscr...@freebsd.org"


Lol, yeah, I was gonna say...but thanks!  Not sure if I'm into 
implementing a patch vs. finding a way around this, and I'm wondering 
why it reared it's head after an update to libvirt & qemu vs. earlier in 
my testing -- makes me think it may be an unrelated, albeit similar bug. 
 Thanks again Juergen.



--
Andre Goree
-=-=-=-=-=-
Email - andre at drenet.net
Website   - http://www.drenet.net
PGP key   - http://www.drenet.net/pubkey.txt
-=-=-=-=-=-
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"


Problems with bhyve's kgdb support and loadable modules

2014-05-02 Thread Kurt Lidl

Is there any reasonable tutorial for using kgdb with the
bvmdebug kernel option?

A couple of folks I know have run into issues trying to
debug a FreeBSD stable/9 kernel from their bhyve
hosting machine (running stable/10).

In particular, the loadable modules that are in use in
the stable/9 kernel are being "troublesome" to get to
the point where source-level debugging actually works.

Even a pointer to a couple of "worked" examples might be
useful.

I've read this:
http://people.freebsd.org/~jhb/papers/bsdcan/2008/article/node4.html
but not all the techniques in there appear to work properly.

-Kurt
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"


Re: Kernel Panic on FreeBSD guests with libvirt 1.2.2 and qemu 1.7.91

2014-05-02 Thread Juergen Lock
In article <201405021800.s42i0tie094...@enceladus10.kn-bremen.de> you write:
>In article 
> you 
>write:
>>On 05/01/2014 11:00 am, Andre Goree wrote:
>>> Hello,
>>> 
>>> I'm running libvirt 1.2.2 and QEMU 1.7.91 on an Ubuntu 12.04LTS host.
>>> Prior to a recent upgrade, I've been able to run FreeBSD guests (both
>>> 10.0 and 9.2) perfectly fine without issue.  Now, this the
>>> aforementioned versions, I'm running into a kernel panic almost
>>> immediately after booting, same message with both 10.0 & 9.2:  "Fatal
>>> trap 12: page fault while in kernel mode".
>>> 
>>> To ensure that it had nothing to do with my configuration [of the
>>> guest OS] I've tried installing the guest from guest using
>>> virt-install, however I still run into the same kernel panic.  It'll
>>> be hard for me to post the output of the panic, so I'll try to show as
>>> much info as possible via images[1].
>>> 
>>> Upon researching, I've come across a few threads (e.g., this one[2])
>>> that appear to be related, but none have helped.  Any information that
>>> you can provide to help me get to the root of this issue would be
>>> greatly appreciated!
>>> 
>>> [1]http://www.drenet.net/images/panic1.png
>>> http://www.drenet.net/images/panic2.png
>>> http://www.drenet.net/images/panic_noacpi1.png
>>> http://www.drenet.net/images/panic_noacpi2.png
>>> 
>>> [2]http://forums.freebsd.org/viewtopic.php?t=36761
>>
>>
>>After using my noggin a bit, I've determine the culprit to be atkbd.  If 
>>I disable it via the bootloader with "set hint.atkbd.0.disabled=1", the 
>>vm will boot fine.  HOWEVER, my problem then is that I cannot use the 
>>keyboard via VNC.  I'm trying to figure out ways around this...any help 
>>would be much appreciated.  I've already tried setting different flags 
>>for atkbd, but no matter which flag I set, I get the kernel panic -- 
>>ostensibly because atkbd is enabled (as it must be for a flag to be set 
>>for it).
>>
>I think you have hit this issue for which the workaround is a patch
>to seabios:
>
>   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug
>
Hm for some reason that link got truncated, try this one:

https://bugs.debian.org/737142

>   
> http://git.qemu.org/?p=seabios.git;a=commit;h=8032b8a0fec550de5cb2f7d37aa031cebc2200c3
>
> References:
>
>   http://article.gmane.org/gmane.comp.emulators.qemu/254414/
>
>   https://lists.gnu.org/archive/html/qemu-stable/2013-03/msg00037.html
>

Juergen
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"


Re: Kernel Panic on FreeBSD guests with libvirt 1.2.2 and qemu 1.7.91

2014-05-02 Thread Juergen Lock
In article  you write:
>On 05/01/2014 11:00 am, Andre Goree wrote:
>> Hello,
>> 
>> I'm running libvirt 1.2.2 and QEMU 1.7.91 on an Ubuntu 12.04LTS host.
>> Prior to a recent upgrade, I've been able to run FreeBSD guests (both
>> 10.0 and 9.2) perfectly fine without issue.  Now, this the
>> aforementioned versions, I'm running into a kernel panic almost
>> immediately after booting, same message with both 10.0 & 9.2:  "Fatal
>> trap 12: page fault while in kernel mode".
>> 
>> To ensure that it had nothing to do with my configuration [of the
>> guest OS] I've tried installing the guest from guest using
>> virt-install, however I still run into the same kernel panic.  It'll
>> be hard for me to post the output of the panic, so I'll try to show as
>> much info as possible via images[1].
>> 
>> Upon researching, I've come across a few threads (e.g., this one[2])
>> that appear to be related, but none have helped.  Any information that
>> you can provide to help me get to the root of this issue would be
>> greatly appreciated!
>> 
>> [1]http://www.drenet.net/images/panic1.png
>> http://www.drenet.net/images/panic2.png
>> http://www.drenet.net/images/panic_noacpi1.png
>> http://www.drenet.net/images/panic_noacpi2.png
>> 
>> [2]http://forums.freebsd.org/viewtopic.php?t=36761
>
>
>After using my noggin a bit, I've determine the culprit to be atkbd.  If 
>I disable it via the bootloader with "set hint.atkbd.0.disabled=1", the 
>vm will boot fine.  HOWEVER, my problem then is that I cannot use the 
>keyboard via VNC.  I'm trying to figure out ways around this...any help 
>would be much appreciated.  I've already tried setting different flags 
>for atkbd, but no matter which flag I set, I get the kernel panic -- 
>ostensibly because atkbd is enabled (as it must be for a flag to be set 
>for it).
>
I think you have hit this issue for which the workaround is a patch
to seabios:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug


http://git.qemu.org/?p=seabios.git;a=commit;h=8032b8a0fec550de5cb2f7d37aa031cebc2200c3

 References:

http://article.gmane.org/gmane.comp.emulators.qemu/254414/

https://lists.gnu.org/archive/html/qemu-stable/2013-03/msg00037.html

 HTH, :)
Juergen
___
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"