Duplicating code from NetBSD
Hi folks, Newbie question so please excuse the naivety. If someone were to copy a few functions from NetBSD in to their FreeBSD kernel mode drivers then is it still possible to submit the code in to the FreeBSD tree under the FreeBSD license? If not then would the community accept the copied code cleanly separated out in a file and licensed under the NetBSD license? Please let me know if there is an acceptable procedure to do this or if this is a complete NONO. Thanks, Abhishek ___ 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 10.0 not work carp protocol on Hyper-v
Hi Giovanni, Sorry to come late to the thread. Have you integrated the Hyper-V drivers yet or are relying on emulated mode? Let's start from there and we shall see if the problem can be resolved. Thanks, Abhishek Gupta PM, BSD Integration Services Microsoft Corporation From: owner-freebsd-virtualizat...@freebsd.org on behalf of Maurizio Marini Sent: Tuesday, March 04, 2014 9:43 AM To: Mark Felder Cc: FreeBSD Net; freebsd-virtualization@freebsd.org; Manuel Martini; Giovanni Mattera Subject: Re: freebsd 10.0 not work carp protocol on Hyper-v On Tue, 4 Mar 2014 10:25:42 -0600 Mark Felder wrote: > That's unfortunate. If you do a packet dump do you even see the other node's > advertisements? > > CARP is really at the mercy of these half-baked virtual switc Dear sir: https://forum.pfsense.org/index.php?topic=44529.0 "But shouldn't the CARP state go to "master" anyway, even if it couldn't find a live partner due to network/Hyper-V problems?" this is the question, forget network/Hyper-V problems, CARP should go MASTER anyway -- Cordiali Saluti Maurizio Marini CoST - Computers Services and Technologies S.r.l. Via Longhi, 13 - 20137 Milano P. IVA 09585780159 Tel +39 02 45446.207 Fax +39 02 45446.333 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione. Grazie. This e-mail and any attachment are confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorized. If you are not the intended recipient, please delete this message and any attachment and advise the sender by return e-mail. Thank you ___ 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: hyperv doesn't compile on i386 with gcc
Hi Garrett, Sorry for the trouble. We shall have this fixed early next week. Thanks, Abhishek From: Garrett Cooper Sent: Sunday, January 12, 2014 12:11 AM To: virtualizat...@freebsd.org Cc: Abhishek Gupta (LIS) Subject: Fwd: hyperv doesn't compile on i386 with gcc Please see the below message. Thanks, -Garrett ___ 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: Use of Floppy Drive with FreeBSD Virtual Machines
Thanks for the insight Michael. Duly noted. Abhishek From: Michael Dexter Sent: Tuesday, November 12, 2013 5:08 PM To: Abhishek Gupta (LIS) Cc: freebsd-virtualization@freebsd.org Subject: Re: Use of Floppy Drive with FreeBSD Virtual Machines On 11/12/13 1:07 PM, Abhishek Gupta (LIS) wrote: > Thanks for the response Michael! I understand now. Just wanted to let > you know that Hyper-V Gen2 VMs do not have a virtual FDD. On the topic of passing a virtual FDD to a VM for a passed-through PCI* card BIOS update, a bhyve developer wrote: "Strictly speaking, it depends on the device: some can restart with a function-level reset, but more than likely they would require a power-cycle, and most systems don't provide the ability to power-cycle an individual card." Michael ___ 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: Use of Floppy Drive with FreeBSD Virtual Machines
Thanks for the response Michael! I understand now. Just wanted to let you know that Hyper-V Gen2 VMs do not have a virtual FDD. Not that we have FreeBSD supported on it yet but the scenarios you describe may not work on Gen2 FreeBSD virtual machines today. Thanks again for the feedback. Abhishek -Original Message- From: Michael Dexter [mailto:edi...@callfortesting.org] Sent: Monday, November 11, 2013 10:13 PM To: Abhishek Gupta (LIS); freebsd-virtualization@freebsd.org Subject: Re: Use of Floppy Drive with FreeBSD Virtual Machines Hello Abhishek, On 11/11/13 11:37 AM, Abhishek Gupta (LIS) wrote: > Thanks so much for replying. Some follow up questions: > > a) Is it not possible to use an ISO file to do the BIOS updates? I have not. > b) I did not quite understand your second comment on why PCI pass > through may promote floppy disk use. Please could you elaborate a bit > more? The scenario I see the most is a virtualized (HyperV, VMware etc.) FreeNAS guest to which you pass a PCIe storage controller card to so that ZFS is given "bare metal" access to hardware disks yet has the benefit of the fast internal backplane if you will for networking, rather than going over copper or optical network interfaces. Because the FreeNAS guest may be one among many, it would not be desirable to reboot the whole system and boot to a floppy to apply a BIOS update to a PCIe controller card. Again, I have not tried anything like this but it is a possible use case of what you describe. Also mind you I never want to see another floppy-based BIOS again but they are still out there. Michael ___ 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: Use of Floppy Drive with FreeBSD Virtual Machines
Hi Michael, Thanks so much for replying. Some follow up questions: a) Is it not possible to use an ISO file to do the BIOS updates? b) I did not quite understand your second comment on why PCI pass through may promote floppy disk use. Please could you elaborate a bit more? Thanks again for your help with this. Regards, Abhishek -Original Message- From: Michael Dexter [mailto:edi...@callfortesting.org] Sent: Monday, November 11, 2013 10:59 AM To: freebsd-virtualization@freebsd.org; Abhishek Gupta (LIS) Subject: Re: Use of Floppy Drive with FreeBSD Virtual Machines Abhishek, My single use case this last few years has been for BIOS updates and given that one could use PCI pass-through to expose say, an LSI storage controller to a virtual machine, there may indeed be a use case. Michael Dexter On 11/11/13 10:19 AM, Abhishek Gupta (LIS) wrote: > Hi everyone, > > Is anybody using floppy disk drives with virtual machines on Hyper-V or any > other hypervisor? I would be interested in knowing both common and obscure > scenarios. Please let me know if you have any thoughts in this direction. > > Thanks, > Abhishek Gupta > Program Manager, BSD Integration Services Microsoft Corporation > > ___ > 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: Use of Floppy Drive with FreeBSD Virtual Machines
Yep, completely agree but just want to know if someone has a use case. Thanks, Abhishek From: Outback Dingo [mailto:outbackdi...@gmail.com] Sent: Monday, November 11, 2013 10:22 AM To: Abhishek Gupta (LIS) Cc: freebsd-virtualization@freebsd.org Subject: Re: Use of Floppy Drive with FreeBSD Virtual Machines On Mon, Nov 11, 2013 at 1:19 PM, Abhishek Gupta (LIS) mailto:abgu...@microsoft.com>> wrote: Hi everyone, Is anybody using floppy disk drives with virtual machines on Hyper-V or any other hypervisor? I would be interested in knowing both common and obscure scenarios. Please let me know if you have any thoughts in this direction. Thanks, Abhishek Gupta Program Manager, BSD Integration Services Microsoft Corporation kinda odd, as you cant even buy a floppy disk anymore ___ freebsd-virtualization@freebsd.org<mailto: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<mailto: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"
Use of Floppy Drive with FreeBSD Virtual Machines
Hi everyone, Is anybody using floppy disk drives with virtual machines on Hyper-V or any other hypervisor? I would be interested in knowing both common and obscure scenarios. Please let me know if you have any thoughts in this direction. Thanks, Abhishek Gupta Program Manager, BSD Integration Services Microsoft Corporation ___ 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: fastide on hyper-v (pre r2)
Hi Tony, You are correct. As of now we have only tested the drivers on Server 2012. You can get them to work on Server 2008R2 but Server 2008 will have some problems. Currently we are focused on getting the drivers functional on Server 2012 for FreeBSD 10 and then we may start expanding to past versions of Windows servers if there is sufficient demand. Having said that I would be interested in hearing more about the panic that you are observing. Is it possible for you to share a stack trace? Please keep me posted on your issues. Thanks, Abhishek Gupta PM, BSD Integration Services Microsoft Corporation -Original Message- From: owner-freebsd-virtualizat...@freebsd.org [mailto:owner-freebsd-virtualizat...@freebsd.org] On Behalf Of Tony Hain Sent: Friday, October 11, 2013 10:53 AM To: freebsd-virtualization@freebsd.org Subject: fastide on hyper-v (pre r2) I am not able to get fastide working on sbs2008 with the pre-r2 version of hyper-v. Should this work? Has testing been done on older versions of hyper-v? I see there was a commit by grehan 18 hours, 30 minutes ago dealing with the cdrom, so I have a new build in process. To be honest I hadn't gotten far enough to worry about the cdrom device yet, but it is good to see that is dealt with. There is an extensive list of things I have tried in the thread http://forums.freebsd.org/showthread.php?p=236012#post236012 In short, if I leave fastide on, it will panic before it gets to error 19, but if I turn it off I can boot to ada0p2, or any label I give the device. My suspicion is that all of the dev work has been done on hyperv-r2, so there may be an oversight. In any case it is good to see all the progress. I have been running FreeBSD in VM's hobbled by the inability to reboot without manual intervention for 4 years, hoping this would happen. Even without fastide, once 10 goes to RELEASE I can move some of the production work off of dedicated hardware. Tony ___ 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"
Disabling ATA driver for IDE devices on Hyper-V
Hi folks, This may have been asked before but the solution we have currently is less than ideal. Please bear with me on the repetition and provide any suggestions you may have. One of the issues with Hyper-V is that it does not virtualize the CD device and therefore we rely on the ATA driver in the guest operating system to manage CDROMs. What we would like to do is disable the ATA driver for all device types except the CDROM in the presence of Hyper-V. Can someone help us in answering the following in this regard: a) What is the correct location in the FreeBSD ATA code where we can put in selective disabling? b) Is this a good approach? Is there something cleaner you can think of? As of now we have implemented a disengage driver that disables ATA driver permanently on Hyper-V. However this is less than desirable and we are looking for a better solution. Please let us know if you have some thoughts. Thanks, Abhishek ___ 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: Hyperv driver related error on make buildkernel on -r255933
Hi,
Is it possible for you to compile with the clang compiler instead of gcc?
It seems that you are compiling with gcc and that is why the error is showing
up:
WITHOUT_CLANG=YES
WITH_GCC=YES
Let me know if that is not acceptable and I will try to address this as soon as
possible.
Thanks,
Abhishek
From: owner-freebsd-virtualizat...@freebsd.org
on behalf of Гуляев Гоша
Sent: Sunday, September 29, 2013 11:18 AM
To: freebsd-curr...@freebsd.org; freebsd-virtualization@freebsd.org
Subject: Hyperv driver related error on make buildkernel on -r255933
I have an error when tryin to compile kernel with recent -CURRENT
sources
There is additional info uname -a, /etc/src.conf, error output and
kernel config
uname -a
FreeBSD MYBSD 10.0-CURRENT FreeBSD 10.0-CURRENT #0: Mon Aug 12 22:31:24
MSK 2013 xlr@MYBSD:/usr/obj/usr/src/sys/MYBSD amd64
/etc/src.conf
WITHOUT_ACCT=YES
#WITHOUT_AMD=YES
WITHOUT_ASSERT_DEBUG=YES
WITHOUT_ATM=YES
WITHOUT_AUDIT=YES
WITHOUT_AUTHPF=YES
WITHOUT_BIND=YES
#WITHOUT_BLUETOOTH=YES
WITHOUT_BSNMP=YES
WITHOUT_CLANG=YES
WITHOUT_CTM=YES
WITHOUT_FDT=YES
WITHOUT_FLOPPY=YES
WITHOUT_GDB=YES
WITHOUT_HTML=YES
WITH_GCC=YES
WITH_GNUCXX=YES
WITHOUT_ICONV=YES
#WITH_LIBICONV_COMPAT=YES
WITHOUT_INET6=YES
WITHOUT_INFO=YES
WITHOUT_IPFILTER=YES
WITHOUT_IPX=YES
WITHOUT_KERNEL_SYMBOLS=YES
WITHOUT_KVM=YES
WITHOUT_LPR=YES
WITHOUT_MAIL=YES
WITHOUT_NCP=YES
#WITHOUT_NDIS=YES
WITHOUT_OFED=YES
WITHOUT_PF=YES
WITHOUT_PMC=YES
WITHOUT_QUOTAS=YES
WITHOUT_RCMDS=YES
WITHOUT_RCS=YES
WITHOUT_SHAREDOCS=YES
#WITHOUT_USB=YES
#WITHOUT_WIRELESS=YES
WITHOUT_ZFS=YES
ERROR OUTPUT
awk -f /usr/src/sys/conf/kmod_syms.awk hwpmc.ko export_syms | xargs -J%
objcopy % hwpmc.ko
objcopy --strip-debug hwpmc.ko
===> hyperv (all)
===> hyperv/vmbus (all)
cc -O2 -pipe -msse -msse2 -msse3 -mmmx -m3dnow -mtune=core2
-march=core2 -fno-strict-aliasing -Wno-error -D_KERNEL -DKLD_MODULE
-nostdinc
-I/usr/src/sys/modules/hyperv/vmbus/../../../dev/hyperv/include
-I/usr/src/sys/modules/hyperv/vmbus/../../../dev/hyperv/vmbus
-I/usr/src/sys/modules/hyperv/vmbus/../../../dev/hyperv/utilities
-DHAVE_KERNEL_OPTION_HEADERS -include
/usr/obj/usr/src/sys/MYBSD/opt_global.h -I. -I@ -I@/contrib/altq
-finline-limit=8000 --param inline-unit-growth=100 --param
large-function-growth=1000 -fno-common -fno-omit-frame-pointer
-mno-omit-leaf-frame-pointer -I/usr/obj/usr/src/sys/MYBSD
-mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float
-fno-asynchronous-unwind-tables -ffreestanding -fstack-protector
-std=iso9899:1999 -fstack-protector -Wall -Wredundant-decls
-Wnested-externs -Wstrict-prototypes -Wmissing-prototypes
-Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign
-fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -c
/usr/src/sys/modules/hyperv/vmbus/../../../dev/hyperv/vmbus/hv_channel.
c
In file included from
/usr/src/sys/modules/hyperv/vmbus/../../../dev/hyperv/vmbus/hv_channel.
c:40:
/usr/src/sys/modules/hyperv/vmbus/../../../dev/hyperv/vmbus/hv_vmbus_pr
iv.h:288: warning: declaration does not declare anything
/usr/src/sys/modules/hyperv/vmbus/../../../dev/hyperv/vmbus/hv_vmbus_pr
iv.h:396: warning: declaration does not declare anything
/usr/src/sys/modules/hyperv/vmbus/../../../dev/hyperv/vmbus/hv_vmbus_pr
iv.h:410: warning: declaration does not declare anything
/usr/src/sys/modules/hyperv/vmbus/../../../dev/hyperv/vmbus/hv_vmbus_pr
iv.h:418: warning: declaration does not declare anything
/usr/src/sys/modules/hyperv/vmbus/../../../dev/hyperv/vmbus/hv_vmbus_pr
iv.h:426: warning: declaration does not declare anything
/usr/src/sys/modules/hyperv/vmbus/../../../dev/hyperv/vmbus/hv_vmbus_pr
iv.h:502: warning: declaration does not declare anything
/usr/src/sys/modules/hyperv/vmbus/../../../dev/hyperv/vmbus/hv_vmbus_pr
iv.h:514: warning: declaration does not declare anything
/usr/src/sys/modules/hyperv/vmbus/../../../dev/hyperv/vmbus/hv_vmbus_pr
iv.h:528: warning: declaration does not declare anything
/usr/src/sys/modules/hyperv/vmbus/../../../dev/hyperv/vmbus/hv_vmbus_pr
iv.h:539: warning: declaration does not declare anything
/usr/src/sys/modules/hyperv/vmbus/../../../dev/hyperv/vmbus/hv_channel.
c: In function 'vmbus_channel_set_event':
/usr/src/sys/modules/hyperv/vmbus/../../../dev/hyperv/vmbus/hv_channel.
c:73: error: 'union ' has no member named 'pending'
*** Error code 1
Stop.
make: stopped in /usr/src/sys/modules/hyperv/vmbus
*** Error code 1
Stop.
make: stopped in /usr/src/sys/modules/hyperv
*** Error code 1
Stop.
make: stopped in /usr/src/sys/modul
RE: maturity of hyperv
The drivers will work with both 32-bit and 64-bit systems. There are no known issues as of now. I am guessing that by libs you mean to ask if there is good user mode tool integration. As of now we do not have much tool integration as the drivers are pretty basic in nature and provide storage, networking, timesync, heartbeat, kvp, shutdown support only. However we intend to continue adding more features and would love to hear any requirements that you may have. I haven't looked very closely at bhyve however I suspect that the differences may be substantial. You will have to test this a bit on your own and we would be very interested in hearing your feedback. Please let me know if you have further questions. Thanks, Abhishek From: Aryeh Friedman Sent: Sunday, September 29, 2013 12:17 PM To: Abhishek Gupta (LIS) Cc: freebsd-virtualization@freebsd.org Subject: Re: maturity of hyperv If you were referencing the drivers then they are more or less ready. We have a few kinks to work out and are actively working on addressing them. This is the one I meant... the most important thing for us can it run *ANY* x86 (32 and 64 bit) OS?... if not is such support planned and when will it be available? are there any libs or any interfacing it has to be from scratch? slightly OT how close to bhyve is it in actual command and such semantics? ___ 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: maturity of hyperv
Hi Aryeh, Do you mean to ask if Hyper-V is mature as a platform or if the Hyper-V drivers for FreeBSD are mature enough? If you meant the platform then I would encourage you to give it a try. My guess is that you will be pretty blown away with the stability, feature set, usability and cost advantage. Furthermore, it is no secret that Hyper-V is gaining significant share in enterprise virtualization deployments. If you were referencing the drivers then they are more or less ready. We have a few kinks to work out and are actively working on addressing them. Please let me know if you need more information. Thanks, Abhishek From: owner-freebsd-virtualizat...@freebsd.org on behalf of Aryeh Friedman Sent: Sunday, September 29, 2013 11:38 AM To: freebsd-virtualization@freebsd.org Subject: maturity of hyperv Is HyperV mature enough that we (the petitecloud developers) consider adding support for it in petitecloud? ___ 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: [Hyper-V][camlock] storvsc driver panics during boot with patches from camlock project
Hi Oleg, Please give us some time. I shall look at it. Thanks for reporting. Regards, Abhishek -Original Message- From: owner-freebsd-virtualizat...@freebsd.org [mailto:owner-freebsd-virtualizat...@freebsd.org] On Behalf Of Oleg Sidorkin Sent: Monday, September 23, 2013 7:21 AM To: freebsd-virtualization@freebsd.org Cc: Alexander Motin Subject: [Hyper-V][camlock] storvsc driver panics during boot with patches from camlock project Hello. I'm running the latest current (amd64) under Hyper-V with hyper-v services enabled. If camlock patches are applied (http://people.freebsd.org/~mav/camlock_patches/camlock_20130906.patch), I'm hitting the following kernel panic during boot: FreeBSD 10.0-ALPHA2 #5 r255762M: Sun Sep 22 16:48:21 UTC 2013 olsi@current:/usr/obj/usr/src/sys/HYPERVKERNEL amd64 FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610 CPU: Intel(R) Core(TM) i5-2540M CPU @ 2.60GHz (1309.17-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x206a7 Family = 0x6 Model = 0x2a Stepping = 7 Timecounter "Hyper-V" frequency 1000 Hz quality 1000 ZFS NOTICE: Prefetch is disabled by default if less than 4GB of RAM is present; to enable, add "vfs.zfs.prefetch_disable=0" to /boot/loader.conf. ZFS filesystem version: 5 ZFS storage pool version: features support (5000) Timecounters tick every 10.000 msec storvsc0 on vmbus0 Netvsc initializing... SMP: AP CPU #3 Launched! SMP: AP CPU #2 Launched! SMP: AP CPU #1 Launched! kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode cpuid = 3; apic id = 03 fault virtual address = 0x20 fault code = supervisor read data, page not present instruction pointer = 0x20:0x804f444c stack pointer = 0x28:0xfe011df38610 frame pointer = 0x28:0xfe011df38640 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags= resume, IOPL = 0 current process = 0 (hv_control_1 taskq) [ thread pid 0 tid 100046 ] Stopped at turnstile_broadcast+0x8c: movq0x20(%rbx,%rax,1),%rdx db> bt Tracing pid 0 tid 100046 td 0xf80001f20490 turnstile_broadcast() at turnstile_broadcast+0x8c/frame 0xfe011df38640 __mtx_unlock_sleep() at __mtx_unlock_sleep+0x60/frame 0xfe011df38670 unlock_mtx() at unlock_mtx+0x2a/frame 0xfe011df38680 _sleep() at _sleep+0x18e/frame 0xfe011df38700 cam_periph_runccb() at cam_periph_runccb+0x9e/frame 0xfe011df38800 storvsc_attach() at storvsc_attach+0x6d4/frame 0xfe011df388a0 device_attach() at device_attach+0x396/frame 0xfe011df388f0 hv_vmbus_child_device_register() at hv_vmbus_child_device_register+0xdb/frame 0xfe011df38990 vmbus_channel_process_offer() at vmbus_channel_process_offer+0x133/frame 0xfe011df389d0 work_item_callback() at work_item_callback+0x26/frame 0xfe011df389f0 taskqueue_run_locked() at taskqueue_run_locked+0xe6/frame 0xfe011df38a40 taskqueue_thread_loop() at taskqueue_thread_loop+0xa8/frame 0xfe011df38a70 fork_exit() at fork_exit+0x9a/frame 0xfe011df38ab0 fork_trampoline() at fork_trampoline+0xe/frame 0xfe011df38ab0 --- trap 0, rip = 0, rsp = 0xfe011df38b70, rbp = 0 --- db> This patch is not commited yet (CFT thread with changes description is here: http://lists.freebsd.org/pipermail/freebsd-hackers/2013-September/04.html), but it is going to be commited till the end of the year. As far as I understand, the invocation chain is storvsc_attach->scan_for_luns->cam_periph_runccb Thanks -- Oleg Sidorkin ___ 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: turn off 220V on UPS device =} file system got corrupted Re: Hyper-V 2012 Cluster / Failover - supported? - Any known issues?
Hi Victor,
Karl is asking if high availability failover scenarios will work for FreeBSD
VMs on Hyper-V. He was specifically interested in knowing if the power plug is
pulled from the Hyper-V server then would the FreeBSD VM failover and restart
without any issues on the failover server.
My response was that yes the above scenario should work.
Thanks,
Abhishek
-Original Message-
From: Victor Miasnikov [mailto:v...@tut.by]
Sent: Wednesday, September 18, 2013 8:46 AM
To: Abhishek Gupta (LIS); Karl Pielorz; freebsd-virtualization@freebsd.org
Subject: turn off 220V on UPS device =} file system got corrupted Re: Hyper-V
2012 Cluster / Failover - supported? - Any known issues?
Hi!
K.P.> - Pulling the power on the active node hosting both VM's (i.e. Windows
K.P.> guest, and FreeBSD guest) - this showed the remaining node trying to
bring K.P.> up the VM's (of which Windows came up OK, and FreeBSD [file system]
got corrupted).
A.G.> Yes, it should work.
A.G.>My understanding is that the failover should be agnostic to the guest OS
but there could be some integration component that we might have missed.
What _exactly_ "should work" ?
1) This issue not related Hyper-V cluster itself
!) When "Pulling the power" i.e. turn off 220V in Europa ( or 110V in USA ) on
UPS device _both_ FAT on Windows and
FreeBSD [file system] got corrupted
( "Windows came up OK" look like because on this VM file system is NTFS )
K.P.> Hyper-V correctly see's the node fail, and restarts both VM's on the
K.P.> remaining node. Windows 7 boots fine (says it wasn't shut down correctly -
K.P.> which is correct) - but FreeBSD doesn't survive.
K.P.>
K.P.> At boot time we get a blank screen with "-" on it (i.e. the first part of
K.P.> the boot 'spinner') - and nothing else.
K.P.>
K.P.> Booting to a network copy of FreeBSD and looking at the underlying virtual
K.P.> disk - it appears to be trashed. You can mount it (but it understandably
K.P.> warns it's not clean) - however, any access leads to an instant panic
('bad
K.P.> dir ino 2 at offset 0: mangled entry').
K.P.>
K.P.> Trying to run fsck against the file system throws up an impressive amounts
K.P.> of 'bad magic' errors and 'rebuild cylinder group?' prompts.
To Karl: I ask You about some details . . .
Are You see related e-mail?
Best regards, Victor Miasnikov
Blog: http://vvm.blog.tut.by/
- Original Message -
From: "Abhishek Gupta (LIS)"
To: "Karl Pielorz"
Sent: Wednesday, September 18, 2013 5:50 PM
Subject: RE: Hyper-V 2012 Cluster / Failover - supported? - Any known issues?
> Thanks again Karl! Yes, it should work.
>My understanding is that the failover should be agnostic to the guest OS but
>there could be some integration component
>that we might have missed.
>So it would be good to get to the bottom of this.
>
> Regards,
>
> Abhishek
____
> From: Karl Pielorz
> Sent: Wednesday, September 18, 2013 7:45 AM
> To: Abhishek Gupta (LIS);
> Subject: RE: Hyper-V 2012 Cluster / Failover - supported? - Any known issues?
>
> --On 18 September 2013 14:23 + "Abhishek Gupta (LIS)"
> wrote:
>
>> Hi Karl,
>>
>> Thanks for reporting the issue. Please give us some time to investigate
>> and get back to you on this. In the meantime I wanted to ask if setting
>> up a Hyper-V replica for the FreeBSD VM and then a manual failover
>> reproduces the same symptoms? Please let me know.
>
> Hi,
>
> Manual fail-over appears to work OK - in order, I tested:
>
> - Live migration from one node to the other, and back again (worked)
>
> - Stopping the cluster service on one of the nodes (i.e. from Failover
> Cluster Manager) - this showed the VM moving from the node that was
> stopped, over to the other node (again worked).
>
> - Pulling the power on the active node hosting both VM's (i.e. Windows
> guest, and FreeBSD guest) - this showed the remaining node trying to bring
> up the VM's (of which Windows came up OK, and FreeBSD got corrupted).
>
>
> I've had to stop now as the guy here looking after the Synology kit on the
> test network is applying a firmware update (this is apparently for some
> appletalk issue or something).
>
> I'll re-run the test after this has been done - if it still fails, I'll
> come back with a 'how to reproduce' type report (and I'll obviously let you
> know if we can't reproduce it again!).
>
> At least I know it 'should' work now :)
>
> Thanks,
>
> -Karl
___
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: Hyper-V 2012 Cluster / Failover - supported? - Any known issues?
Great! Thanks for verifying! Abhishek From: Karl Pielorz Sent: Wednesday, September 18, 2013 8:56 AM To: Abhishek Gupta (LIS); freebsd-virtualization@freebsd.org Subject: RE: Hyper-V 2012 Cluster / Failover - supported? - Any known issues? --On 18 September 2013 14:50 + "Abhishek Gupta (LIS)" wrote: > Thanks again Karl! Yes, it should work. My understanding is that the > failover should be agnostic to the guest OS but there could be some > integration component that we might have missed. So it would be good to > get to the bottom of this. Ok, I've repeated the test twice now - and it's succeeded both times, so it looks likely the Synology patch did 'something' that had a knock on effect for this. fwiw/incase anyone else hit this - our test setup comprises of a pair of D412+ NAS's (active/passive) and they're now running DSM v4.3-3776-1 (which was apparently released in the last few days) - so far (fingers crossed) this appears to be working for us now. I'll be re-testing it probably multiple times over the next few days - if I hit any other issues - I'll let you know, and thanks again, Regards, -Karl ___ 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: Hyper-V 2012 Cluster / Failover - supported? - Any known issues?
Thanks again Karl! Yes, it should work. My understanding is that the failover should be agnostic to the guest OS but there could be some integration component that we might have missed. So it would be good to get to the bottom of this. Regards, Abhishek From: Karl Pielorz Sent: Wednesday, September 18, 2013 7:45 AM To: Abhishek Gupta (LIS); freebsd-virtualization@freebsd.org Subject: RE: Hyper-V 2012 Cluster / Failover - supported? - Any known issues? --On 18 September 2013 14:23 + "Abhishek Gupta (LIS)" wrote: > Hi Karl, > > Thanks for reporting the issue. Please give us some time to investigate > and get back to you on this. In the meantime I wanted to ask if setting > up a Hyper-V replica for the FreeBSD VM and then a manual failover > reproduces the same symptoms? Please let me know. Hi, Manual fail-over appears to work OK - in order, I tested: - Live migration from one node to the other, and back again (worked) - Stopping the cluster service on one of the nodes (i.e. from Failover Cluster Manager) - this showed the VM moving from the node that was stopped, over to the other node (again worked). - Pulling the power on the active node hosting both VM's (i.e. Windows guest, and FreeBSD guest) - this showed the remaining node trying to bring up the VM's (of which Windows came up OK, and FreeBSD got corrupted). I've had to stop now as the guy here looking after the Synology kit on the test network is applying a firmware update (this is apparently for some appletalk issue or something). I'll re-run the test after this has been done - if it still fails, I'll come back with a 'how to reproduce' type report (and I'll obviously let you know if we can't reproduce it again!). At least I know it 'should' work now :) Thanks, -Karl ___ 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: Hyper-V 2012 Cluster / Failover - supported? - Any known issues?
Hi Karl,
Thanks for reporting the issue. Please give us some time to investigate and get
back to you on this. In the meantime I wanted to ask if setting up a Hyper-V
replica for the FreeBSD VM and then a manual failover reproduces the same
symptoms? Please let me know.
Thanks,
Abhishek
From: owner-freebsd-virtualizat...@freebsd.org
on behalf of Karl Pielorz
Sent: Wednesday, September 18, 2013 5:42 AM
To: freebsd-virtualization@freebsd.org
Subject: Hyper-V 2012 Cluster / Failover - supported? - Any known issues?
Hi,
As you've probably seen from my previous posts, we're looking at using
Hyper-V with FreeBSD.
We built a test system (2 node cluster) - and had 2 HA hosts running on it
(a Windows 7 install, and a FreeBSD install from base/projects/hyperv
r255634).
Live migration works for both hosts (i.e. to the other cluster node, and
back) - but a failure of the node [power pulled / non-graceful shutdown]
running the VM's - seems to trash the FreeBSD system.
Hyper-V correctly see's the node fail, and restarts both VM's on the
remaining node. Windows 7 boots fine (says it wasn't shut down correctly -
which is correct) - but FreeBSD doesn't survive.
At boot time we get a blank screen with "-" on it (i.e. the first part of
the boot 'spinner') - and nothing else.
Booting to a network copy of FreeBSD and looking at the underlying virtual
disk - it appears to be trashed. You can mount it (but it understandably
warns it's not clean) - however, any access leads to an instant panic ('bad
dir ino 2 at offset 0: mangled entry').
Trying to run fsck against the file system throws up an impressive amounts
of 'bad magic' errors and 'rebuild cylinder group?' prompts.
Should the current FreeBSD Hyper-V drivers support this? (like I said, live
migration worked without an issue - and Windows recovered fine from the
failure).
The Hyper-V is running under WS2012, with a Synology SAN - if you need any
more info, let me know,
Thanks,
-Karl
___
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: Hyper-V driver development status
Hi guys, Thanks for the feedback. I have seen the "caclru: runtime went backwards from xxx usec to yyy usec for pid " off an on but I have not seen any visible system impact because of that. It could be because the clock is virtualized and the system is taking some time to adjust to it. We can file this as a bug in our database and work on resolving it. The "Status: Degraded (Integration services upgrade required)" issue is benign. The "Heartbeat shows as 'OK (No Application Data)" is benign too. Let us know if you guys are seeing some other issues. Thanks, Abhishek From: Karl Pielorz Sent: Wednesday, September 11, 2013 6:15 AM To: Pavel Timofeev; Abhishek Gupta (LIS) Cc: freebsd-virtualization@freebsd.org Subject: Re: Hyper-V driver development status --On 11 September 2013 16:43 +0400 Pavel Timofeev wrote: > I've just checked out and built projects/hyperv and everything looks good. I just did that as well this morning... "FreeBSD 10.0-CURRENT FreeBSD 10.0-CURRENT #6 r255470: Wed Sep 11 10:29:25 UTC 2013 root@:/usr/obj/src/sys/GENERIC amd64" I'm running under Windows Hyper V Server 2012 - the only things I've noticed so far (not been testing long): - I get a myriad of "caclru: runtime went backwards from xxx usec to yyy usec for pid " on the console every now and again. - On the Hyper-V Manager, under Networking it says: "Status: Degraded (Integration services upgrade required)" [I have just the 'Network Adapter' present in the VM - not the Legacy Adapter]. Heartbeat shows as 'OK (No Application Data)' - which I'm guessing is probably cosmetic? -Karl ___ 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: Trying Hyper-V support from the svn project source - panic booting kernel?
Hi Karl, This turned out to be an old issue which is already fixed in the current branch. Please update your code to the current branch and you should not see this issue. Alternatively you can disable witnesses (using set debug.witness.watch=-1) and move past the boot stage. Please let us know if this works for you. Thanks again for taking interest in our drivers. Regards, Abhishek From: Abhishek Gupta (LIS) Sent: Tuesday, September 10, 2013 5:38 PM To: Karl Pielorz; freebsd-virtualization@freebsd.org Subject: RE: Trying Hyper-V support from the svn project source - panic booting kernel? Hi Karl, Sorry, that you are having trouble with the drivers. We have never hit a panic before even when compiling the current branch to test. I will have our team look at the latest code in the current branch today and ensure that any issues are taken care of. One thing I wanted to ask is if you have witness support enabled? Perhaps witness support for testing might get you past the boot stage. Simultaneously we are working on FreeBSD 9.1 ports and as of now that is the only other way to get functional Hyper-V drivers. You have caught us in the middle of the development cycle. If you could just wait for a few more days, you will see detailed instructions from me on the mailing list. Otherwise please wait until tomorrow so I can get this sorted out. Thanks again for your interest in our drivers. Abhishek -Original Message- From: Karl Pielorz [mailto:kpielorz_...@tdx.co.uk] Sent: Tuesday, September 10, 2013 7:18 AM To: Abhishek Gupta (LIS); freebsd-virtualization@freebsd.org Subject: RE: Trying Hyper-V support from the svn project source - panic booting kernel? --On 09 September 2013 14:49 + "Abhishek Gupta (LIS)" wrote: > Hi Kari, > > No this is not known. Does it give a stack trace and point to some > culprit functions? Please let me know. > Do you, or anyone know if there is any code or install I can get from somewhere that will boot at all? (e.g. Snapshot, ISO Image, or 'known good/working' source revision)? Thanks, -Karl ___ 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: Trying Hyper-V support from the svn project source - panic booting kernel?
Hi Karl, Sorry, that you are having trouble with the drivers. We have never hit a panic before even when compiling the current branch to test. I will have our team look at the latest code in the current branch today and ensure that any issues are taken care of. One thing I wanted to ask is if you have witness support enabled? Perhaps witness support for testing might get you past the boot stage. Simultaneously we are working on FreeBSD 9.1 ports and as of now that is the only other way to get functional Hyper-V drivers. You have caught us in the middle of the development cycle. If you could just wait for a few more days, you will see detailed instructions from me on the mailing list. Otherwise please wait until tomorrow so I can get this sorted out. Thanks again for your interest in our drivers. Abhishek -Original Message- From: Karl Pielorz [mailto:kpielorz_...@tdx.co.uk] Sent: Tuesday, September 10, 2013 7:18 AM To: Abhishek Gupta (LIS); freebsd-virtualization@freebsd.org Subject: RE: Trying Hyper-V support from the svn project source - panic booting kernel? --On 09 September 2013 14:49 + "Abhishek Gupta (LIS)" wrote: > Hi Kari, > > No this is not known. Does it give a stack trace and point to some > culprit functions? Please let me know. > Do you, or anyone know if there is any code or install I can get from somewhere that will boot at all? (e.g. Snapshot, ISO Image, or 'known good/working' source revision)? Thanks, -Karl ___ 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: Trying Hyper-V support from the svn project source - panic booting kernel?
Hi Kari, No this is not known. Does it give a stack trace and point to some culprit functions? Please let me know. Thanks, Abhishek From: owner-freebsd-virtualizat...@freebsd.org on behalf of Karl Pielorz Sent: Monday, September 09, 2013 3:28 AM To: freebsd-virtualization@freebsd.org Subject: Trying Hyper-V support from the svn project source - panic booting kernel? Hi, I'm trying to build a Hyper-V aware kernel/system from the SVN source at svn://svn.freebsd.org/base/projects/hyperv (r254955) I got the world compiled, and the new Hyper-V supporting kernel installed, went to boot to single user mode, and get the following panic: " Timecounter "Hyper-V" frequency 1000 Hz quality 1000 panic: acquiring blockable sleep lock with spinlock or critical section held (sleep mutex) 4 Bucket " /usr/src/sys/vm/uma-dbg.c:212 cpuid = 0 KDB: enter: panic [ thread pid 0 tid 10 ] Stopped at kdb_enter+0x3e: movq$0, kdb_why db> " This is under Hyper-V 2012. Any pointers? Is this a known issue? Thanks, -Karl ___ 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: Hyper-V driver development status
Hi Pavel, Yes, FreeBSD 10 is still the target. We are working to make it in to the tree. You should see some traction next week. Thanks, Abhishek From: Pavel Timofeev Sent: Thursday, August 29, 2013 3:31 AM To: Abhishek Gupta (LIS) Cc: Peter Grehan; freebsd-virtualization@freebsd.org Subject: Re: Hyper-V driver development status So, is it going to be included in FreeBSD 10 now? As I can see code freeze for CURRENT is planned on 7 September 2013 (10 days from now). http://www.freebsd.org/releases/10.0R/schedule.html It's not much time. 2013/8/17 Abhishek Gupta (LIS) : > Hi Pavel, > > Thanks for inquiring about the BSD drivers for Hyper-V. We (Microsoft) are > actively working on these drivers and the intent is to get them integrated in > to the kernel within the next month or so. There are some issues we are > trying to address: > > a) Witness panic during boot time due to a specific memory allocation. > b) Bypass usage of disk labels to ensure that devices do not get reordered > under FreeBSD. > c) Locks up on 32 bit builds. > d) Lack of KVP support for BSD drivers > > We are working hard every day to finish these items. > > Even though an official announcement has not gone out, I would highly > encourage you to start testing the drivers. As they are in project branch now > they should be easy to compile. The only requirement is to set up disk labels > before rebooting a kernel that includes the Hyper-V drivers otherwise the > system will not boot up. > > Please let me know if you have more questions or have feedback. > > Thanks again for your interest. > Abhishek > ____ > From: Peter Grehan > Sent: Friday, August 16, 2013 11:30 AM > To: Abhishek Gupta (LIS) > Subject: Fwd: Hyper-V driver development status > > Want to reply to this ? > > > Original Message > Subject: Hyper-V driver development status > Date: Fri, 16 Aug 2013 17:00:57 +0400 > From: Pavel Timofeev > To: freebsd-virtualization@freebsd.org > > Hi all! > I'd like to know what's happening with hyper-v driver development in > FreeBSD. > I know about svn branch but there is no active progress in there. > What's the roadmap? Or we are waiting for something? > > What is the current status of that project? > I could do some tests. Or it's too early? > I'm looking forward to use it =) > ___ > 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: Hyper-V driver development status
Hi Pavel, Thanks for inquiring about the BSD drivers for Hyper-V. We (Microsoft) are actively working on these drivers and the intent is to get them integrated in to the kernel within the next month or so. There are some issues we are trying to address: a) Witness panic during boot time due to a specific memory allocation. b) Bypass usage of disk labels to ensure that devices do not get reordered under FreeBSD. c) Locks up on 32 bit builds. d) Lack of KVP support for BSD drivers We are working hard every day to finish these items. Even though an official announcement has not gone out, I would highly encourage you to start testing the drivers. As they are in project branch now they should be easy to compile. The only requirement is to set up disk labels before rebooting a kernel that includes the Hyper-V drivers otherwise the system will not boot up. Please let me know if you have more questions or have feedback. Thanks again for your interest. Abhishek From: Peter Grehan Sent: Friday, August 16, 2013 11:30 AM To: Abhishek Gupta (LIS) Subject: Fwd: Hyper-V driver development status Want to reply to this ? Original Message Subject: Hyper-V driver development status Date: Fri, 16 Aug 2013 17:00:57 +0400 From: Pavel Timofeev To: freebsd-virtualization@freebsd.org Hi all! I'd like to know what's happening with hyper-v driver development in FreeBSD. I know about svn branch but there is no active progress in there. What's the roadmap? Or we are waiting for something? What is the current status of that project? I could do some tests. Or it's too early? I'm looking forward to use it =) ___ 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"
