Re: kldload vmm partial lockup
Hey Neel,
I compiled 11-CURRENT and it works now I can kldload vmm with no problems.
Thanks.
Joe Maloney
On Jan 21, 2014, at 9:01 PM, Neel Natu neeln...@gmail.com wrote:
Hi Joe,
On Tue, Jan 21, 2014 at 6:53 PM, Joe Maloney jpm...@gmail.com wrote:
Neel,
sorry it took me a day or two to get to test this. The patch compiles
cleanly however it fails now trying to build the vmm module.
No worries.
I committed the patch as r260972:
http://svnweb.freebsd.org/base?view=revisionrevision=260972
Could you get the latest HEAD and see how it works for you?
best
Neel
p.s. not sure why the patch is not compiling - perhaps ppt.h did not
get patched properly?
Joe Maloney
/usr/src/sys/modules/vmm/../../amd64/vmm/vmm.c:232:7: error: implicit
declaration of function 'ppt_avail_devices' is invalid in C99
[-Werror,-Wimplicit-function-declaration]
if (ppt_avail_devices() 0)
^
/usr/src/sys/modules/vmm/../../amd64/vmm/vmm.c:565:6: error: implicit
declaration of function 'ppt_assigned_devices' is invalid in C99
[-Werror,-Wimplicit-function-declaration]
if (ppt_assigned_devices(vm) == 0) {
^
/usr/src/sys/modules/vmm/../../amd64/vmm/vmm.c:565:6: note: did you mean
'ppt_assign_device'?
if (ppt_assigned_devices(vm) == 0) {
^~~~
ppt_assign_device
/usr/src/sys/modules/vmm/../../amd64/vmm/io/ppt.h:46:5: note:
'ppt_assign_device' declared here
int ppt_assign_device(struct vm *vm, int bus, int slot, int func);
^
2 errors generated.
*** Error code 1
Stop.
make[4]: stopped in /usr/src/sys/modules/vmm
*** Error code 1
Stop.
make[3]: stopped in /usr/src/sys/modules
*** Error code 1
Stop.
make[2]: stopped in /usr/obj/usr/src/sys/GENERIC
*** Error code 1
Stop.
make[1]: stopped in /usr/src
*** Error code 1
Stop.
make: stopped in /usr/src
root@jmhome-pc:/usr/src #
On Jan 19, 2014, at 8:43 PM, Neel Natu neeln...@gmail.com wrote:
Hi Joe,
On Sun, Jan 19, 2014 at 2:21 PM, Joe Maloney jpm...@gmail.com wrote:
I’ve been trying to get bhyve to work on a system with the following specs:
FreeBSD 10.0 64 bit
ASUS P6T Deluxe
Intel i7 920
According to what I’ve researched my cpu should have the VT-D extensions.
However many users of this motherboard have complained about ASUS not
properly supporting VT-D with Xen and something about a problem with tables
getting corrupt due to a problem with the bios. On the third link below
which is the Xen wiki it even states that this motherboard needs a bios
update which is not available to the public.
https://communities.intel.com/thread/28389
http://vip.asus.com/forum/view.aspx?id=20090402224408018SLanguage=en-usboard_id=1
http://wiki.xen.org/wiki/VTd_HowTo
I am curious though if this would be what would be causing my problem with
bhyve? I suppose I am willing to just by a new motherboard if so.
I can run kldload vmm and I see a bunch of text fly by and then something
about uhci interrupt problem. As soon as that happens the messages repeats
my network drops and no keyboard input. However the message repeats and it
doesn’t appear that the system has fully locked up otherwise. However on
another system that works I notice that kldload VMM does not show this
information it just loads the module.
Is there a way I can gather more logs somehow so that I can determine what
text is appearing before the uhci errors? Perhaps some kind of dump
procedure? Or is there a way I can confirm that freebsd can properly see
and utilize the VT-D extensions. VirtualBox runs fine with the VT
extensions enabled. I also made sure VirtualBox wasn’t installed or loaded
before I tried bhyve. I’ve tried to research for a week or two before
posting here.
I have a patch to not initialize the iommu unless there are passthru
devices explicitly configured for bhyve to use.
It is available here:
http://people.freebsd.org/~neel/patches/bhyve_iommu_init.patch
Could you give it a spin and see if it helps with the ASUS system?
best
Neel
Joe Maloney
___
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
___
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: kldload vmm partial lockup
Hi Joe,
On Tue, Jan 21, 2014 at 6:53 PM, Joe Maloney jpm...@gmail.com wrote:
Neel,
sorry it took me a day or two to get to test this. The patch compiles
cleanly however it fails now trying to build the vmm module.
No worries.
I committed the patch as r260972:
http://svnweb.freebsd.org/base?view=revisionrevision=260972
Could you get the latest HEAD and see how it works for you?
best
Neel
p.s. not sure why the patch is not compiling - perhaps ppt.h did not
get patched properly?
Joe Maloney
/usr/src/sys/modules/vmm/../../amd64/vmm/vmm.c:232:7: error: implicit
declaration of function 'ppt_avail_devices' is invalid in C99
[-Werror,-Wimplicit-function-declaration]
if (ppt_avail_devices() 0)
^
/usr/src/sys/modules/vmm/../../amd64/vmm/vmm.c:565:6: error: implicit
declaration of function 'ppt_assigned_devices' is invalid in C99
[-Werror,-Wimplicit-function-declaration]
if (ppt_assigned_devices(vm) == 0) {
^
/usr/src/sys/modules/vmm/../../amd64/vmm/vmm.c:565:6: note: did you mean
'ppt_assign_device'?
if (ppt_assigned_devices(vm) == 0) {
^~~~
ppt_assign_device
/usr/src/sys/modules/vmm/../../amd64/vmm/io/ppt.h:46:5: note:
'ppt_assign_device' declared here
int ppt_assign_device(struct vm *vm, int bus, int slot, int func);
^
2 errors generated.
*** Error code 1
Stop.
make[4]: stopped in /usr/src/sys/modules/vmm
*** Error code 1
Stop.
make[3]: stopped in /usr/src/sys/modules
*** Error code 1
Stop.
make[2]: stopped in /usr/obj/usr/src/sys/GENERIC
*** Error code 1
Stop.
make[1]: stopped in /usr/src
*** Error code 1
Stop.
make: stopped in /usr/src
root@jmhome-pc:/usr/src #
On Jan 19, 2014, at 8:43 PM, Neel Natu neeln...@gmail.com wrote:
Hi Joe,
On Sun, Jan 19, 2014 at 2:21 PM, Joe Maloney jpm...@gmail.com wrote:
I’ve been trying to get bhyve to work on a system with the following specs:
FreeBSD 10.0 64 bit
ASUS P6T Deluxe
Intel i7 920
According to what I’ve researched my cpu should have the VT-D extensions.
However many users of this motherboard have complained about ASUS not
properly supporting VT-D with Xen and something about a problem with tables
getting corrupt due to a problem with the bios. On the third link below
which is the Xen wiki it even states that this motherboard needs a bios
update which is not available to the public.
https://communities.intel.com/thread/28389
http://vip.asus.com/forum/view.aspx?id=20090402224408018SLanguage=en-usboard_id=1
http://wiki.xen.org/wiki/VTd_HowTo
I am curious though if this would be what would be causing my problem with
bhyve? I suppose I am willing to just by a new motherboard if so.
I can run kldload vmm and I see a bunch of text fly by and then something
about uhci interrupt problem. As soon as that happens the messages repeats
my network drops and no keyboard input. However the message repeats and it
doesn’t appear that the system has fully locked up otherwise. However on
another system that works I notice that kldload VMM does not show this
information it just loads the module.
Is there a way I can gather more logs somehow so that I can determine what
text is appearing before the uhci errors? Perhaps some kind of dump
procedure? Or is there a way I can confirm that freebsd can properly see
and utilize the VT-D extensions. VirtualBox runs fine with the VT
extensions enabled. I also made sure VirtualBox wasn’t installed or loaded
before I tried bhyve. I’ve tried to research for a week or two before
posting here.
I have a patch to not initialize the iommu unless there are passthru
devices explicitly configured for bhyve to use.
It is available here:
http://people.freebsd.org/~neel/patches/bhyve_iommu_init.patch
Could you give it a spin and see if it helps with the ASUS system?
best
Neel
Joe Maloney
___
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
___
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
kldload vmm partial lockup
I’ve been trying to get bhyve to work on a system with the following specs: FreeBSD 10.0 64 bit ASUS P6T Deluxe Intel i7 920 According to what I’ve researched my cpu should have the VT-D extensions. However many users of this motherboard have complained about ASUS not properly supporting VT-D with Xen and something about a problem with tables getting corrupt due to a problem with the bios. On the third link below which is the Xen wiki it even states that this motherboard needs a bios update which is not available to the public. https://communities.intel.com/thread/28389 http://vip.asus.com/forum/view.aspx?id=20090402224408018SLanguage=en-usboard_id=1 http://wiki.xen.org/wiki/VTd_HowTo I am curious though if this would be what would be causing my problem with bhyve? I suppose I am willing to just by a new motherboard if so. I can run kldload vmm and I see a bunch of text fly by and then something about uhci interrupt problem. As soon as that happens the messages repeats my network drops and no keyboard input. However the message repeats and it doesn’t appear that the system has fully locked up otherwise. However on another system that works I notice that kldload VMM does not show this information it just loads the module. Is there a way I can gather more logs somehow so that I can determine what text is appearing before the uhci errors? Perhaps some kind of dump procedure? Or is there a way I can confirm that freebsd can properly see and utilize the VT-D extensions. VirtualBox runs fine with the VT extensions enabled. I also made sure VirtualBox wasn’t installed or loaded before I tried bhyve. I’ve tried to research for a week or two before posting here. Joe Maloney ___ 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: kldload vmm partial lockup
On Sun, Jan 19, 2014 at 5:21 PM, Joe Maloney jpm...@gmail.com wrote: I’ve been trying to get bhyve to work on a system with the following specs: FreeBSD 10.0 64 bit ASUS P6T Deluxe Intel i7 920 According to what I’ve researched my cpu should have the VT-D extensions. However many users of this motherboard have complained about ASUS not properly supporting VT-D with Xen and something about a problem with tables getting corrupt due to a problem with the bios. On the third link below which is the Xen wiki it even states that this motherboard needs a bios update which is not available to the public. https://communities.intel.com/thread/28389 http://vip.asus.com/forum/view.aspx?id=20090402224408018SLanguage=en-usboard_id=1 http://wiki.xen.org/wiki/VTd_HowTo I am curious though if this would be what would be causing my problem with bhyve? I suppose I am willing to just by a new motherboard if so. I can run kldload vmm and I see a bunch of text fly by and then something about uhci interrupt problem. As soon as that happens the messages repeats my network drops and no keyboard input. However the message repeats and it doesn’t appear that the system has fully locked up otherwise. However on another system that works I notice that kldload VMM does not show this information it just loads the module. Is there a way I can gather more logs somehow so that I can determine what text is appearing before the uhci errors? Perhaps some kind of dump procedure? Or is there a way I can confirm that freebsd can properly see and utilize the VT-D extensions. VirtualBox runs fine with the VT extensions enabled. I also made sure VirtualBox wasn’t installed or loaded before I tried bhyve. I’ve tried to research for a week or two before posting here. Joe Maloney According to this, your processor supports VT-x, but not VT-d ; http://ark.intel.com/products/37147/Intel-Core-i7-920-Processor-8M-Cache-2_66-ghz-4_80-gts-Intel-qpi -Tom ___ 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: kldload vmm partial lockup
On Sun, Jan 19, 2014 at 5:34 PM, Thomas Hoffmann trh...@gmail.com wrote: On Sun, Jan 19, 2014 at 5:21 PM, Joe Maloney jpm...@gmail.com wrote: I’ve been trying to get bhyve to work on a system with the following specs: FreeBSD 10.0 64 bit ASUS P6T Deluxe Intel i7 920 According to what I’ve researched my cpu should have the VT-D extensions. However many users of this motherboard have complained about ASUS not properly supporting VT-D with Xen and something about a problem with tables getting corrupt due to a problem with the bios. On the third link below which is the Xen wiki it even states that this motherboard needs a bios update which is not available to the public. https://communities.intel.com/thread/28389 http://vip.asus.com/forum/view.aspx?id=20090402224408018SLanguage=en-usboard_id=1 http://wiki.xen.org/wiki/VTd_HowTo I am curious though if this would be what would be causing my problem with bhyve? I suppose I am willing to just by a new motherboard if so. I can run kldload vmm and I see a bunch of text fly by and then something about uhci interrupt problem. As soon as that happens the messages repeats my network drops and no keyboard input. However the message repeats and it doesn’t appear that the system has fully locked up otherwise. However on another system that works I notice that kldload VMM does not show this information it just loads the module. Is there a way I can gather more logs somehow so that I can determine what text is appearing before the uhci errors? Perhaps some kind of dump procedure? Or is there a way I can confirm that freebsd can properly see and utilize the VT-D extensions. VirtualBox runs fine with the VT extensions enabled. I also made sure VirtualBox wasn’t installed or loaded before I tried bhyve. I’ve tried to research for a week or two before posting here. Joe Maloney According to this, your processor supports VT-x, but not VT-d ; http://ark.intel.com/products/37147/Intel-Core-i7-920-Processor-8M-Cache-2_66-ghz-4_80-gts-Intel-qpi -Tom But this i7-920 processor does: http://ark.intel.com/products/43126/Intel-Core-i7-920XM-Processor-Extreme-Edition-8M-Cache-2_00-GHz Not sure which you have. -Tom ___ 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
Fwd: kldload vmm partial lockup
-- Forwarded message -- From: Aryeh Friedman aryeh.fried...@gmail.com Date: Sun, Jan 19, 2014 at 6:26 PM Subject: Re: kldload vmm partial lockup To: Thomas Hoffmann trh...@gmail.com You should see the proposed handbook entry on virtualization ( http://www.petitecloud.org/handbook.jsp) for more info... note to the list Dee will be doing some additional proofing of this soon and we will submit again On Sun, Jan 19, 2014 at 5:55 PM, Thomas Hoffmann trh...@gmail.com wrote: On Sun, Jan 19, 2014 at 5:34 PM, Thomas Hoffmann trh...@gmail.com wrote: On Sun, Jan 19, 2014 at 5:21 PM, Joe Maloney jpm...@gmail.com wrote: I’ve been trying to get bhyve to work on a system with the following specs: FreeBSD 10.0 64 bit ASUS P6T Deluxe Intel i7 920 According to what I’ve researched my cpu should have the VT-D extensions. However many users of this motherboard have complained about ASUS not properly supporting VT-D with Xen and something about a problem with tables getting corrupt due to a problem with the bios. On the third link below which is the Xen wiki it even states that this motherboard needs a bios update which is not available to the public. https://communities.intel.com/thread/28389 http://vip.asus.com/forum/view.aspx?id=20090402224408018SLanguage=en-usboard_id=1 http://wiki.xen.org/wiki/VTd_HowTo I am curious though if this would be what would be causing my problem with bhyve? I suppose I am willing to just by a new motherboard if so. I can run kldload vmm and I see a bunch of text fly by and then something about uhci interrupt problem. As soon as that happens the messages repeats my network drops and no keyboard input. However the message repeats and it doesn’t appear that the system has fully locked up otherwise. However on another system that works I notice that kldload VMM does not show this information it just loads the module. Is there a way I can gather more logs somehow so that I can determine what text is appearing before the uhci errors? Perhaps some kind of dump procedure? Or is there a way I can confirm that freebsd can properly see and utilize the VT-D extensions. VirtualBox runs fine with the VT extensions enabled. I also made sure VirtualBox wasn’t installed or loaded before I tried bhyve. I’ve tried to research for a week or two before posting here. Joe Maloney According to this, your processor supports VT-x, but not VT-d ; http://ark.intel.com/products/37147/Intel-Core-i7-920-Processor-8M-Cache-2_66-ghz-4_80-gts-Intel-qpi -Tom But this i7-920 processor does: http://ark.intel.com/products/43126/Intel-Core-i7-920XM-Processor-Extreme-Edition-8M-Cache-2_00-GHz Not sure which you have. -Tom ___ 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 -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org ___ 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: kldload vmm partial lockup
Hi Joe, On Sun, Jan 19, 2014 at 2:21 PM, Joe Maloney jpm...@gmail.com wrote: I’ve been trying to get bhyve to work on a system with the following specs: FreeBSD 10.0 64 bit ASUS P6T Deluxe Intel i7 920 According to what I’ve researched my cpu should have the VT-D extensions. However many users of this motherboard have complained about ASUS not properly supporting VT-D with Xen and something about a problem with tables getting corrupt due to a problem with the bios. On the third link below which is the Xen wiki it even states that this motherboard needs a bios update which is not available to the public. https://communities.intel.com/thread/28389 http://vip.asus.com/forum/view.aspx?id=20090402224408018SLanguage=en-usboard_id=1 http://wiki.xen.org/wiki/VTd_HowTo I am curious though if this would be what would be causing my problem with bhyve? I suppose I am willing to just by a new motherboard if so. I can run kldload vmm and I see a bunch of text fly by and then something about uhci interrupt problem. As soon as that happens the messages repeats my network drops and no keyboard input. However the message repeats and it doesn’t appear that the system has fully locked up otherwise. However on another system that works I notice that kldload VMM does not show this information it just loads the module. Is there a way I can gather more logs somehow so that I can determine what text is appearing before the uhci errors? Perhaps some kind of dump procedure? Or is there a way I can confirm that freebsd can properly see and utilize the VT-D extensions. VirtualBox runs fine with the VT extensions enabled. I also made sure VirtualBox wasn’t installed or loaded before I tried bhyve. I’ve tried to research for a week or two before posting here. I have a patch to not initialize the iommu unless there are passthru devices explicitly configured for bhyve to use. It is available here: http://people.freebsd.org/~neel/patches/bhyve_iommu_init.patch Could you give it a spin and see if it helps with the ASUS system? best Neel Joe Maloney ___ 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 ___ 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
