Re: Running `sysctl -a` causes crash (Hyper-V)
On 11 November 2013 16:38, Pavel Timofeev tim...@gmail.com wrote: Hi! Can anybody confirm the subject? Every time when I run `sysctl -a` get this http://pastebin.com/Chf9qQTD Can you show 'p vm_guest' from core file? -- wbr, pluknet ___ 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: Running `sysctl -a` causes crash (Hyper-V)
On 11 November 2013 18:13, Pavel Timofeev tim...@gmail.com wrote: [...] (kgdb) p vm_guest $1 = 3 Current language: auto; currently minimal (kgdb) What if you try this change? Index: sys/kern/subr_param.c === --- sys/kern/subr_param.c(revision 257695) +++ sys/kern/subr_param.c(working copy) @@ -153,6 +153,7 @@ none, generic, xen, +hv, NULL }; ___ 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: Running `sysctl -a` causes crash (Hyper-V)
On 11 November 2013 20:00, Roger Pau Monné roger@citrix.com wrote:
On 11/11/13 15:31, Sergey Kandaurov wrote:
On 11 November 2013 18:13, Pavel Timofeev tim...@gmail.com wrote:
[...]
(kgdb) p vm_guest
$1 = 3
Current language: auto; currently minimal
(kgdb)
What if you try this change?
Index: sys/kern/subr_param.c
===
--- sys/kern/subr_param.c(revision 257695)
+++ sys/kern/subr_param.c(working copy)
@@ -153,6 +153,7 @@
none,
generic,
xen,
+hv,
NULL
};
This is my fault, I've added VM_GUEST_HV to the guest type enum without
knowing there was another array in a completely different file that
contained a description for those values.
Ok, I committed the fix in r257996.
If you (or someone else) are going to commit this change, I would
recommend adding a BIG comment in sys/systm.h above the declaration of
VM_GUEST explaining that if you add a new guest type there you also need
to add a description in subr_param.c, this will probably prevent
something like this happening again.
What about this change?
Index: sys/sys/systm.h
===
--- sys/sys/systm.h(revision 257695)
+++ sys/sys/systm.h(working copy)
@@ -70,6 +70,7 @@
* Detected virtual machine guest types. The intention is to expand
* and/or add to the VM_GUEST_VM type if specific VM functionality is
* ever implemented (e.g. vendor-specific paravirtualization features).
+ * Keep in sync with vm_guest_sysctl_names[].
*/
enum VM_GUEST { VM_GUEST_NO = 0, VM_GUEST_VM, VM_GUEST_XEN, VM_GUEST_HV };
--
wbr,
pluknet
___
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: FreeBSD PVHVM call for testing
On 23 May 2013 20:30, Outback Dingo outbackdi...@gmail.com wrote: On Thu, May 23, 2013 at 9:33 AM, Roger Pau Monné roger@citrix.comwrote: On 23/05/13 14:57, Jeroen van der Ham wrote: Hi, On 13 May 2013, at 20:32, Roger Pau Monné roger@citrix.com wrote: Right now the code is in a state where it can be tested by users, so we would like to encourage FreeBSD and Xen users to test it and provide feedback. I've just been able to install it on a VPS using the latest pvhvm_v9 branch. The branch pvhvm_v9 contains an initial implementation of PV IPIs for amd64. I've now finished it and I'm going to port it to i386 also, and push a new branch to the repository. This is good news, because the system I had before actually had trouble with the HVM kernel from 9.1 [0]. I'm going to leave this running for a while and do some more tests on it. Jeroen. [0]: http://www.freebsd.org/cgi/query-pr.cgi?pr=175822 I built the rev_9 branch on a XCP host and rebooted, however I am seeing on boot after ugen0.2: QEMU 0.10.2 at usbus0 run_interrupt_driven_hooks: still waiting after 60 seconds for xenbus_nop_confighook_cb run_interrupt_driven_hooks: still waiting after 120 seconds for xenbus_nop_confighook_cb run_interrupt_driven_hooks: still waiting after 180 seconds for xenbus_nop_confighook_cb run_interrupt_driven_hooks: still waiting after 240 seconds for xenbus_nop_confighook_cb run_interrupt_driven_hooks: still waiting after 300 seconds for xenbus_nop_confighook_cb panic: run_interrupt_driven_confighooks: waited too long cpuid = 0 KDB: enter: panic [ thread pid 0 tid 10 ] Stropped at kdb_enter +0x3b: movq $0,0xad6522(%rip) db Can you recheck this on stock HEAD? From your description this looks like a rather old bug seen with 8.2 or above and XCP (referenced in PR kern/164630). You can trigger it when e.g. booting with empty cdrom. -- wbr, pluknet ___ 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
