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: 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: Hyper-V driver development status
fs: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/label/rootfs: clean, 8460523 free (4739 frags, 1056973 blocks, 0.0% fragmentation) Mounting local file systems:. Writing entropy file:. Setting hostname: bsdtest. Waiting on "rndis sema" with the following non-sleepable locks held: exclusive sleep mutex NetVSCLock (network driver) r = 0 (0xf80002830030) locked @ /usr/src/sys/dev/hyperv/netvsc/hv_netvsc_drv_freebsd.c:904 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe003d395550 kdb_backtrace() at kdb_backtrace+0x39/frame 0xfe003d395600 witness_warn() at witness_warn+0x4a8/frame 0xfe003d3956c0 _cv_timedwait_sbt() at _cv_timedwait_sbt+0x96/frame 0xfe003d395740 _sema_timedwait() at _sema_timedwait+0x74/frame 0xfe003d395780 hv_rf_set_packet_filter() at hv_rf_set_packet_filter+0x184/frame 0xfe003d3957c0 hv_rf_on_open() at hv_rf_on_open+0x46/frame 0xfe003d3957e0 hn_ifinit() at hn_ifinit+0xbe/frame 0xfe003d395820 ether_ioctl() at ether_ioctl+0x8a/frame 0xfe003d395850 hn_ioctl() at hn_ioctl+0x28a/frame 0xfe003d3958b0 in_control() at in_control+0xbe5/frame 0xfe003d395960 ifioctl() at ifioctl+0xf52/frame 0xfe003d395a20 kern_ioctl() at kern_ioctl+0x2ca/frame 0xfe003d395a90 sys_ioctl() at sys_ioctl+0x11f/frame 0xfe003d395ae0 amd64_syscall() at amd64_syscall+0x265/frame 0xfe003d395bf0 Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfe003d395bf0 --- syscall (54, FreeBSD ELF64, sys_ioctl), rip = 0x80119c1fa, rsp = 0x7fffd488, rbp = 0x7fffd4d0 --- Starting Network: lo0 de0 hn0. lo0: flags=8049 metric 0 mtu 16384 options=63 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 inet 127.0.0.1 netmask 0xff00 nd6 options=21 de0: flags=8802 metric 0 mtu 1500 ether 00:15:5d:02:9a:6f nd6 options=29 media: Ethernet autoselect hn0: flags=8843 metric 0 mtu 1500 options=18 ether 00:15:5d:02:9a:6e inet 192.168.25.5 netmask 0xffc0 broadcast 192.168.25.63 inet6 fe80::215:5dff:fe02:9a6e%hn0 prefixlen 64 scopeid 0x3 nd6 options=29 Starting devd. Starting Network: de0. de0: flags=8802 metric 0 mtu 1500 ether 00:15:5d:02:9a:6f nd6 options=29 media: Ethernet autoselect add net default: gateway 192.168.25.1 add net fe80::: gateway ::1 add net ff02::: gateway ::1 add net :::0.0.0.0: gateway ::1 add net ::0.0.0.0: gateway ::1 Creating and/or trimming log files. Starting syslogd. No core dumps found. ELF ldconfig path: /lib /usr/lib /usr/lib/compat 32-bit compatibility ldconfig path: /usr/lib32 Clearing /tmp (X related). Updating motd:. Mounting late file systems:. Configuring syscons: blanktime. Performing sanity check on sshd configuration. Starting sshd. Starting cron. Starting background file system checks in 60 seconds. Wed Sep 11 16:28:18 MSK 2013 lock order reversal: 1st 0xfe003d50e970 bufwait (bufwait) @ /usr/src/sys/kern/vfs_bio.c:3059 2nd 0xf80002e14a00 dirhash (dirhash) @ /usr/src/sys/ufs/ufs/ufs_dirhash.c:284 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe003d3db660 kdb_backtrace() at kdb_backtrace+0x39/frame 0xfe003d3db710 witness_checkorder() at witness_checkorder+0xd23/frame 0xfe003d3db7a0 _sx_xlock() at _sx_xlock+0x75/frame 0xfe003d3db7e0 ufsdirhash_remove() at ufsdirhash_remove+0x37/frame 0xfe003d3db810 ufs_dirremove() at ufs_dirremove+0x11b/frame 0xfe003d3db860 ufs_remove() at ufs_remove+0x75/frame 0xfe003d3db8c0 VOP_REMOVE_APV() at VOP_REMOVE_APV+0xf0/frame 0xfe003d3db8f0 kern_unlinkat() at kern_unlinkat+0x20c/frame 0xfe003d3dbae0 amd64_syscall() at amd64_syscall+0x265/frame 0xfe003d3dbbf0 Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfe003d3dbbf0 --- syscall (10, FreeBSD ELF64, sys_unlink), rip = 0x80093958a, rsp = 0x7fffda18, rbp = 0x7fffdae0 --- 2013/8/29 Abhishek Gupta (LIS) : > 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
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
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
Thanks a lot, Abhishek! 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"
Hyper-V driver development status
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"
