Re: Recovering an ZFS vm
At the end of this all, it seemed that some change has taken away my need to be very specific about the grub partitions. By removing the grub_run0 and grub_run1 parameters from the vm-bhyve configs and running simply with the one below, (and showing a bit of patients while it repaired partitions), it booted as expected. I also see that once booted, the / filesystem is an ext4. I really cannot explain and it is entirely possible that this is a memory issue on my part. loader="grub" cpu=2 memory=8G network0_type="virtio-net" network0_switch="public" disk0_type="virtio-blk" disk0_name="disk0" disk0_dev="sparse-zvol" I appreciate all of you taking time out to reply. -- Randy On Tue, Dec 5, 2017 at 4:56 PM, Peter Grehan wrote: > Hi Randy, > > I have a Centos vm that has suddenly stopped booting. At the console, grub >> tells me the following if I attempt to list any of the available >> partitions. >> >> error: not a correct XFS inode. >> error: not a correct XFS inode. >> error: not a correct XFS inode. >> error: not a correct XFS inode. >> error: not a correct XFS inode. >> Filesystem type xfs, UUID 7652ffda-f7c5-408a-b0ce-b554b66fc2e5 - >> Partition >> start at 2048 - Total size 2097152 sectors >> grub> >> >> Is there an easy way to recover this? This has happened more than once. >> Just so happens there is something on this image I would like to have >> access to... >> > > Looks like the grub partition was upgraded to the version of XFS that has > the CRC feature enabled (7.2 ?). Unfortunately this feature is not > understood by grub-bhyve :( > > One way to recover the disk is to create a new VM with the most recent > CentOS, but using UEFI for the bootloader. Then, add this disk to the > guest, and from within the guest I think you can run an XFS utility that > will disable the use of CRCs on that partition. > > The proper fix would be for grub-bhyve to be updated to the latest > version of grub2, though a workaround is to create guests with UEFI and not > use grub-bhyve. > > later, > > Peter. > ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: Recovering an ZFS vm
One of the other VM clones is running. What do I need to do to mount the sparse-zvol dataset that is this disk image that won't boot? I'm still confused as to why one of these VM images would boot and not the other. They are both Centos 7 1708. At any rate, before taking a chance of shutting this image down, I'd appreciate any help to mount this other zvol and make sure the crc feature is disabled. Thanks -- Randy On Tue, Dec 5, 2017 at 4:56 PM, Peter Grehan wrote: > Hi Randy, > > I have a Centos vm that has suddenly stopped booting. At the console, grub >> tells me the following if I attempt to list any of the available >> partitions. >> >> error: not a correct XFS inode. >> error: not a correct XFS inode. >> error: not a correct XFS inode. >> error: not a correct XFS inode. >> error: not a correct XFS inode. >> Filesystem type xfs, UUID 7652ffda-f7c5-408a-b0ce-b554b66fc2e5 - >> Partition >> start at 2048 - Total size 2097152 sectors >> grub> >> >> Is there an easy way to recover this? This has happened more than once. >> Just so happens there is something on this image I would like to have >> access to... >> > > Looks like the grub partition was upgraded to the version of XFS that has > the CRC feature enabled (7.2 ?). Unfortunately this feature is not > understood by grub-bhyve :( > > One way to recover the disk is to create a new VM with the most recent > CentOS, but using UEFI for the bootloader. Then, add this disk to the > guest, and from within the guest I think you can run an XFS utility that > will disable the use of CRCs on that partition. > > The proper fix would be for grub-bhyve to be updated to the latest > version of grub2, though a workaround is to create guests with UEFI and not > use grub-bhyve. > > later, > > Peter. > ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: Recovering an ZFS vm
Allan, Confused by the question. This is a VM that has been running. Loader is 'grub'. Not sure if that implies bhyve given it is running on the bhyve hyperviser. I have another VM that was cloned from this one that is running fine. I did just build from stable yesterday and did a reboot which is when I find that this VM does not run. Not sure if it was corrupted because of a bad shutdown caused by the reboot, or if there is something more explainable as you suggest. I appreciate your help. -- Randy On Tue, Dec 5, 2017 at 3:53 PM, Allan Jude wrote: > On 12/05/2017 16:53, Randy Terbush wrote: > > I have a Centos vm that has suddenly stopped booting. At the console, > grub > > tells me the following if I attempt to list any of the available > partitions. > > > > error: not a correct XFS inode. > > error: not a correct XFS inode. > > error: not a correct XFS inode. > > error: not a correct XFS inode. > > error: not a correct XFS inode. > > Filesystem type xfs, UUID 7652ffda-f7c5-408a-b0ce-b554b66fc2e5 - > Partition > > start at 2048 - Total size 2097152 sectors > > grub> > > > > Is there an easy way to recover this? This has happened more than once. > > Just so happens there is something on this image I would like to have > > access to... > > > > -- > > Randy > > ___ > > freebsd-virtualization@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > > To unsubscribe, send any mail to "freebsd-virtualization- > unsubscr...@freebsd.org" > > > > Is this grub-bhyve? It does not (yet) support the newer version of XFS > with checksums. > > -- > Allan Jude > ___ > freebsd-virtualization@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to "freebsd-virtualization- > unsubscr...@freebsd.org" > ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Recovering an ZFS vm
I have a Centos vm that has suddenly stopped booting. At the console, grub tells me the following if I attempt to list any of the available partitions. error: not a correct XFS inode. error: not a correct XFS inode. error: not a correct XFS inode. error: not a correct XFS inode. error: not a correct XFS inode. Filesystem type xfs, UUID 7652ffda-f7c5-408a-b0ce-b554b66fc2e5 - Partition start at 2048 - Total size 2097152 sectors grub> Is there an easy way to recover this? This has happened more than once. Just so happens there is something on this image I would like to have access to... -- Randy ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Running MacOS on bhyve
Saw a comment in last couple of days regarding running MacOS on bhyve. I too would love to see this and wanted to make sure that the following was on the group's radar as some possible hints toward getting this working. I took a stab awhile back and then ran out of time and patience. https://github.com/kholia/OSX-KVM -- Randy ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: bhyve windows guest unable to ping default gateway or external networks
Peter, I'd recommend giving a try with 118. I had a lot of trouble getting a Win16 image running. Ultimately, it was 118 and a lot of tries with deleting the driver software and reinstalling from the virtio iso to get it to work. I sent a a few emails last month as I was working through the issues. In the end, I think it was mainly dropping back to 118 and many tries to convince new driver to install. -- Randy On Tue, Nov 15, 2016 at 4:30 PM, Matt Thyer wrote: > virtio-win-0.1.102.iso was the last version I've had any success with. > (I haven't tried with bhyve, only VirtualBox Windows VMs). > > On 16 November 2016 at 08:43, Peter Grehan wrote: > > > Hi Jonathan, > > > > In particular, I used virtio-win-0.1.126.iso with driver net-kvm/windows > >> 2k16/amd64 for my attempt with Server 2016 and the 2k12r2/amd64 driver > >> for Server 2012 R2. > >> > > > > I've not had any success with 0.1.126 - it installs, but doesn't appear > > to pass packets. I'd recommend going with 0.1.96 > > > > later, > > > > Peter. > > > > > > ___ > > freebsd-virtualization@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > > To unsubscribe, send any mail to "freebsd-virtualization-unsubs > > cr...@freebsd.org" > > > ___ > freebsd-virtualization@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to "freebsd-virtualization- > unsubscr...@freebsd.org" > ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: Windows 2016
On Tue, Nov 1, 2016 at 11:24 AM, Randy Terbush wrote: > On Tue, Nov 1, 2016 at 9:21 AM, Matt Churchyard < > matt.churchy...@userve.net> wrote: > >> On Tue, Nov 1, 2016 at 8:58 AM, Matt Churchyard via >> freebsd-virtualization wrote: >> >> On Tue, Nov 01, 2016 at 03:16:12PM +0100, Daniel Tihanyi wrote: >> > On Tue, 2016-11-01 at 08:02 -0600, The Doctor wrote: >> > > On Tue, Nov 01, 2016 at 09:02:57AM +, Matt Churchyard wrote: >> > > > >> > > > > >> > > > > I was able to install the Windows 2016 using the GUI method. >> > > > > >> > > > > One problem. >> > > > > >> > > > > It is assigned an IP but >> > > > > >> > > > > the netmask and the default route is not showing up. >> > > > > >> > > > > Also??The virtual Windows 2016 box does not see a network >> > > > > interface. >> > > > This makes very little sense. You usually specify the netmask and >> > > > default route when you assign Windows an IP address. >> > > > And how have you assigned the guest an IP address if it has no >> > > > network interface? >> > > > >> > > The taps are allocated an IP address. >> > > >> > > I fully concur. >> > > >> > > In the install at one point, I declare that the IP address, netmask >> > > and gateway are 'declared' at the 'MB ' BIOS interface. >> > > >> > > >> > > > >> > > > > >> > > > > What must I do to convince this box that is it on a switch >> > > > On the bhyve host it should be configured just like any other >> > > > bhyve virtual machine. The guest should have a virtio-net device, >> > > > which is linked to a tap interface on the host. That tap interface >> > > > should be bridged with whichever physical network adapter you want >> > > > the guest connected to. >> > > > >> > > > However, I think I mentioned in a previous message that Windows >> > > > does not have the virtio-net drivers by default. You need to boot >> > > > the guest with the virtio-net driver ISO attached and install the >> > > > driver. You should see the interface in Device Manager flagged as >> > > > not installed/working. >> > > > >> > > >> > > That is correct . >> > > >> > > I do have an iso of the MB drivers, >> > > >> > > namely a Supermicro??X10DRW-i MB? >> > > >> > > and? >> > > >> > > from Intel I did obtain the .exe file for the i350GbE drivers. >> > > I script a 2 phase installation as follows: >> > > >> > > 1) >> > > >> > > >> > > /usr/sbin/bhyve -c 2 -m 4G -w -H -s 3,ahci-cd,./.iso/14393.0.160715- >> > > 1616.RS1_RELEASE_SERVER_EVAL_X64FRE_EN-US.ISO -s 4,ahci- >> > > hd,windows2016.img -s 5,virtio-net,tap15 -s >> > > 29,fbuf,tcp=0.0.0.0:5900,w=800,h=600,wait -s 30,xhci,tablet -s >> > > 31,lpc -l com1,stdio -l >> > > bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd >> > > windows2016guest >> > > >> > > 2) >> > > >> > > >> > > /usr/sbin/bhyve -c 2 -m 4G -w -H -s >> > > 3,ahci-cd,./.iso/null-install.iso -s 4,ahci-hd,windows2016.img -s >> > > 5,virtio-net,tap15 -s 29,fbuf,tcp=0.0.0.0:5900,w=1024,h=768,wait -s >> > > 30,xhci,tablet -s 31,lpc -l com1,/dev/nmdm15A -l >> > > bootrom,/usr/local/share/uefi- firmware/BHYVE_UEFI.fd >> > > windows2016guest & >> > > >> > > As I said, I have picked up an ISO from the MB manufacturer >> > > >> > > let's call it manufacturer.iso . >> > > >> > > Where do I place said iso in the 'phase' of things? >> > >> > You use virtio network adapters, you have to install the virtio >> > drivers and NOT the drivers for the physical interface. Then configure >> > the IP Address, gateway, etc. in Windows. >> >> >All right, let me repeat what I am up aginst. >> >> >I do set the IP configuration in the virtual BIOS. >> >> >However when the Win2016 VM boots it sees >> >> >1) the localhost >> >> >2) its assigned IP address >> >> >3) A ye
Re: Windows 2016
On Tue, Nov 1, 2016 at 9:21 AM, Matt Churchyard wrote: > On Tue, Nov 1, 2016 at 8:58 AM, Matt Churchyard via freebsd-virtualization > wrote: > > On Tue, Nov 01, 2016 at 03:16:12PM +0100, Daniel Tihanyi wrote: > > On Tue, 2016-11-01 at 08:02 -0600, The Doctor wrote: > > > On Tue, Nov 01, 2016 at 09:02:57AM +, Matt Churchyard wrote: > > > > > > > > > > > > > > I was able to install the Windows 2016 using the GUI method. > > > > > > > > > > One problem. > > > > > > > > > > It is assigned an IP but > > > > > > > > > > the netmask and the default route is not showing up. > > > > > > > > > > Also??The virtual Windows 2016 box does not see a network > > > > > interface. > > > > This makes very little sense. You usually specify the netmask and > > > > default route when you assign Windows an IP address. > > > > And how have you assigned the guest an IP address if it has no > > > > network interface? > > > > > > > The taps are allocated an IP address. > > > > > > I fully concur. > > > > > > In the install at one point, I declare that the IP address, netmask > > > and gateway are 'declared' at the 'MB ' BIOS interface. > > > > > > > > > > > > > > > > > > > > What must I do to convince this box that is it on a switch > > > > On the bhyve host it should be configured just like any other > > > > bhyve virtual machine. The guest should have a virtio-net device, > > > > which is linked to a tap interface on the host. That tap interface > > > > should be bridged with whichever physical network adapter you want > > > > the guest connected to. > > > > > > > > However, I think I mentioned in a previous message that Windows > > > > does not have the virtio-net drivers by default. You need to boot > > > > the guest with the virtio-net driver ISO attached and install the > > > > driver. You should see the interface in Device Manager flagged as > > > > not installed/working. > > > > > > > > > > That is correct . > > > > > > I do have an iso of the MB drivers, > > > > > > namely a Supermicro??X10DRW-i MB? > > > > > > and? > > > > > > from Intel I did obtain the .exe file for the i350GbE drivers. > > > I script a 2 phase installation as follows: > > > > > > 1) > > > > > > > > > /usr/sbin/bhyve -c 2 -m 4G -w -H -s 3,ahci-cd,./.iso/14393.0.160715- > > > 1616.RS1_RELEASE_SERVER_EVAL_X64FRE_EN-US.ISO -s 4,ahci- > > > hd,windows2016.img -s 5,virtio-net,tap15 -s > > > 29,fbuf,tcp=0.0.0.0:5900,w=800,h=600,wait -s 30,xhci,tablet -s > > > 31,lpc -l com1,stdio -l > > > bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd > > > windows2016guest > > > > > > 2) > > > > > > > > > /usr/sbin/bhyve -c 2 -m 4G -w -H -s > > > 3,ahci-cd,./.iso/null-install.iso -s 4,ahci-hd,windows2016.img -s > > > 5,virtio-net,tap15 -s 29,fbuf,tcp=0.0.0.0:5900,w=1024,h=768,wait -s > > > 30,xhci,tablet -s 31,lpc -l com1,/dev/nmdm15A -l > > > bootrom,/usr/local/share/uefi- firmware/BHYVE_UEFI.fd > > > windows2016guest & > > > > > > As I said, I have picked up an ISO from the MB manufacturer > > > > > > let's call it manufacturer.iso . > > > > > > Where do I place said iso in the 'phase' of things? > > > > You use virtio network adapters, you have to install the virtio > > drivers and NOT the drivers for the physical interface. Then configure > > the IP Address, gateway, etc. in Windows. > > >All right, let me repeat what I am up aginst. > > >I do set the IP configuration in the virtual BIOS. > > >However when the Win2016 VM boots it sees > > >1) the localhost > > >2) its assigned IP address > > >3) A yellow triangle where the ethernet adaptor is. > > I'm not sure what people find so difficult about this - Just treat it like > it was a real Windows machine > > 1) Do not assign the guest's IP address on the host > 2) Do not set the IP in the guest BIOS (I'm not even sure what you mean by > this) > > As you have found, the virtio-net network adapter has a yellow triangle in > Windows, because it is not installed. You need to run bhyve but replace the > Windows ISO with the virtio-net driver ISO, which you can download off the > Internet; Then install the network driver through VNC. The guest has a > "virtio-net" interface which is created by bhyve - This has nothing to do > with your motherboard and you do not need to install any of the motherboard > or physical interface drivers in the guest. > > Once you have the virtio driver installed, you will have a "Redhat VirtIO" > network adapter in Windows, and you can assign an IP/Netmask/Gateway to > this just as you normally would in Windows. > > Forget about the Linux machines. They have the virtio-net driver built in, > so you can just configure eth0 out-of-the-box like normal. If you've > configured their IP addresses on the bhyve host then that's not really the > correct way to configure things, even if it doesn't actually break > anything; The IP address should be configured inside the guest OS. > > Matt > > > > > > >Can you guys confirm that you actually have a Windows 2016 vm running? > > > > >As I have said, I
Re: Windows 2016
On Tue, Nov 1, 2016 at 8:58 AM, Matt Churchyard via freebsd-virtualization < freebsd-virtualization@freebsd.org> wrote: > On Tue, Nov 01, 2016 at 03:16:12PM +0100, Daniel Tihanyi wrote: > > On Tue, 2016-11-01 at 08:02 -0600, The Doctor wrote: > > > On Tue, Nov 01, 2016 at 09:02:57AM +, Matt Churchyard wrote: > > > > > > > > > > > > > > I was able to install the Windows 2016 using the GUI method. > > > > > > > > > > One problem. > > > > > > > > > > It is assigned an IP but > > > > > > > > > > the netmask and the default route is not showing up. > > > > > > > > > > Also??The virtual Windows 2016 box does not see a network > > > > > interface. > > > > This makes very little sense. You usually specify the netmask and > > > > default route when you assign Windows an IP address. > > > > And how have you assigned the guest an IP address if it has no > > > > network interface? > > > > > > > The taps are allocated an IP address. > > > > > > I fully concur. > > > > > > In the install at one point, I declare that the IP address, netmask > > > and gateway are 'declared' at the 'MB ' BIOS interface. > > > > > > > > > > > > > > > > > > > > What must I do to convince this box that is it on a switch > > > > On the bhyve host it should be configured just like any other > > > > bhyve virtual machine. The guest should have a virtio-net device, > > > > which is linked to a tap interface on the host. That tap interface > > > > should be bridged with whichever physical network adapter you want > > > > the guest connected to. > > > > > > > > However, I think I mentioned in a previous message that Windows > > > > does not have the virtio-net drivers by default. You need to boot > > > > the guest with the virtio-net driver ISO attached and install the > > > > driver. You should see the interface in Device Manager flagged as > > > > not installed/working. > > > > > > > > > > That is correct . > > > > > > I do have an iso of the MB drivers, > > > > > > namely a Supermicro??X10DRW-i MB? > > > > > > and? > > > > > > from Intel I did obtain the .exe file for the i350GbE drivers. > > > I script a 2 phase installation as follows: > > > > > > 1) > > > > > > > > > /usr/sbin/bhyve -c 2 -m 4G -w -H -s 3,ahci-cd,./.iso/14393.0.160715- > > > 1616.RS1_RELEASE_SERVER_EVAL_X64FRE_EN-US.ISO -s 4,ahci- > > > hd,windows2016.img -s 5,virtio-net,tap15 -s > > > 29,fbuf,tcp=0.0.0.0:5900,w=800,h=600,wait -s 30,xhci,tablet -s > > > 31,lpc -l com1,stdio -l > > > bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd > > > windows2016guest > > > > > > 2) > > > > > > > > > /usr/sbin/bhyve -c 2 -m 4G -w -H -s > > > 3,ahci-cd,./.iso/null-install.iso -s 4,ahci-hd,windows2016.img -s > > > 5,virtio-net,tap15 -s 29,fbuf,tcp=0.0.0.0:5900,w=1024,h=768,wait -s > > > 30,xhci,tablet -s 31,lpc -l com1,/dev/nmdm15A -l > > > bootrom,/usr/local/share/uefi- firmware/BHYVE_UEFI.fd > > > windows2016guest & > > > > > > As I said, I have picked up an ISO from the MB manufacturer > > > > > > let's call it manufacturer.iso . > > > > > > Where do I place said iso in the 'phase' of things? > > > > You use virtio network adapters, you have to install the virtio > > drivers and NOT the drivers for the physical interface. Then configure > > the IP Address, gateway, etc. in Windows. > > >All right, let me repeat what I am up aginst. > > >I do set the IP configuration in the virtual BIOS. > > >However when the Win2016 VM boots it sees > > >1) the localhost > > >2) its assigned IP address > > >3) A yellow triangle where the ethernet adaptor is. > > I'm not sure what people find so difficult about this - Just treat it like > it was a real Windows machine > > 1) Do not assign the guest's IP address on the host > 2) Do not set the IP in the guest BIOS (I'm not even sure what you mean by > this) > > As you have found, the virtio-net network adapter has a yellow triangle in > Windows, because it is not installed. You need to run bhyve but replace the > Windows ISO with the virtio-net driver ISO, which you can download off the > Internet; Then install the network driver through VNC. The guest has a > "virtio-net" interface which is created by bhyve - This has nothing to do > with your motherboard and you do not need to install any of the motherboard > or physical interface drivers in the guest. > > Once you have the virtio driver installed, you will have a "Redhat VirtIO" > network adapter in Windows, and you can assign an IP/Netmask/Gateway to > this just as you normally would in Windows. > > Forget about the Linux machines. They have the virtio-net driver built in, > so you can just configure eth0 out-of-the-box like normal. If you've > configured their IP addresses on the bhyve host then that's not really the > correct way to configure things, even if it doesn't actually break > anything; The IP address should be configured inside the guest OS. > > Matt > > Can you guys confirm that you actually have a Windows 2016 vm running? As I have said, I have installed nearly every version of Wi
Re: Windows 2016
On Tue, Nov 1, 2016 at 3:21 AM, Matt Churchyard via freebsd-virtualization < freebsd-virtualization@freebsd.org> wrote: > >I was able to install the Windows 2016 using the GUI method. > > >One proble. > > >It is assigned an IP but > > >the netmask and the default route is not showing up. > > >Also The virtual Windows 2016 box does not see a network interface. > > This makes very little sense. You usually specify the netmask and default > route when you assign Windows an IP address. > And how have you assigned the guest an IP address if it has no network > interface? > > >What must I do to convince this box that is it on a switch > > On the bhyve host it should be configured just like any other bhyve > virtual machine. The guest should have a virtio-net device, which is linked > to a tap interface on the host. That tap interface should be bridged with > whichever physical network adapter you want the guest connected to. > > However, I think I mentioned in a previous message that Windows does not > have the virtio-net drivers by default. You need to boot the guest with the > virtio-net driver ISO attached and install the driver. You should see the > interface in Device Manager flagged as not installed/working. > > > Just one other thing to add to this. I'm not sure if this is the case > here, but it's something I've seen a few times now. > When configuring IP addresses, etc for a guest, this should be done > -inside- the guest. > Do not assign a guest's IP address to the host, or to the tap interface. > Bhyve works just like any other hypervisor. IP settings are done in the > guest as if it was a real machine, the host just acts like a switch. > > > > This issue may be unique to Windows 2016. I've had success installing most Windows releases with exception of Windows 2016. Windows 10 Enterprise and others ultimately work after attaching the virtio ISO and installing the drivers by hand, however, note of caution that the 126 release of virtio drivers did not work for me. Version 102 does. This is still work in progress from my perspective. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: Installing SQL Server on Windows 2012 bhyve guests
I can confirm that the following template file and vm-bhyve allows me to do an unattended install of win2012r2 that will also allow a successful install of SQL Server 2014. guest="windows" uefi="yes" cpu=2 memory=4G network0_type="virtio-net" network0_switch="public" disk0_type="ahci-hd" disk0_name="disk0.img" disk0_opts="sectorsize=512" I'll see about trying with 4k blocks but for some reason, was having trouble booting new VMs yesterday which led me to try 512 which also failed, but after a fresh buildworld on 11-stable, the 512 block image booted just fine. Thanks for the help here -- Randy On Wed, Oct 26, 2016 at 7:08 AM, Randy Terbush wrote: > Thanks guys, I'll report back once I nail this down. > > I've tried both 4096 and 512 and cannot seem to get an image to boot past > the failed EFI message. Not sure if something has changed lately in stable > to create that result, but will investigate and report back. > > Thanks again for the guidance here. > > -- > Randy > > On Wed, Oct 26, 2016 at 3:30 AM, Matt Churchyard < > matt.churchy...@userve.net> wrote: > >> -Original Message- >> From: owner-freebsd-virtualizat...@freebsd.org [mailto: >> owner-freebsd-virtualizat...@freebsd.org] On Behalf Of Peter Grehan >> Sent: 25 October 2016 19:19 >> To: Randy Terbush >> Cc: freebsd-virtualization@freebsd.org >> Subject: Re: Installing SQL Server on Windows 2012 bhyve guests >> >> >Hi Randy, >> >> > I've followed the info provided here >> > https://wiki.freebsd.org/bhyve/Windows >> > to create a Windows Server 2012 image that I successfully installed on >> > the bhyve hypervisor. After getting a working Win2012 image running, >> > applying updates, etc. I attempted to install SQL Server 2014. In the >> > late stages of that install, the process attempts to start the SQL >> server engine and fails. >> >> > There have been some reports of this previously. What might be >> happening is that SQL Server has stricter requirements on the underlying >> block >size than NTFS itself has. >> >> > Since you are using a file-backed image, the reported block size from >> the emulated storage controller may be 8KB or even higher, depending on >> >the underlying filesystem type. >> >> > A suggestion is to force the block size to 4KB (has to be done during >> install as well), and if the problem persists, try 512 bytes. This is done >> by using >the 'sectorsize=' parameter to the disk configuration e.g. >> >> > -s 4,ahci-hd,/path/to/disk.img,sectorsize=4096 >> >> Just to add, if you're using vm-bhyve you should be able to add this with >> the diskX_opts template/config option >> >> disk0_opts="sectorsize=4096" >> >> I may adjust the sample templates to include a sectorsize option for >> Windows guests, although I'm not 100% clear on what exact OS versions or >> applications require specific settings. I do know that SQL Server has been >> reported to suddenly fall over unless a valid block size is used (although >> I believe it did install and run), but again I'm not sure exactly what the >> "correct" settings are. >> >> Also note that you shouldn't need any grub_* template options if you're >> using UEFI. Those options only apply to grub-bhyve. >> >> Matt >> >> >later, >> >> >Peter. >> >> > ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: Installing SQL Server on Windows 2012 bhyve guests
Thanks guys, I'll report back once I nail this down. I've tried both 4096 and 512 and cannot seem to get an image to boot past the failed EFI message. Not sure if something has changed lately in stable to create that result, but will investigate and report back. Thanks again for the guidance here. -- Randy On Wed, Oct 26, 2016 at 3:30 AM, Matt Churchyard wrote: > -Original Message- > From: owner-freebsd-virtualizat...@freebsd.org [mailto:owner-freebsd- > virtualizat...@freebsd.org] On Behalf Of Peter Grehan > Sent: 25 October 2016 19:19 > To: Randy Terbush > Cc: freebsd-virtualization@freebsd.org > Subject: Re: Installing SQL Server on Windows 2012 bhyve guests > > >Hi Randy, > > > I've followed the info provided here > > https://wiki.freebsd.org/bhyve/Windows > > to create a Windows Server 2012 image that I successfully installed on > > the bhyve hypervisor. After getting a working Win2012 image running, > > applying updates, etc. I attempted to install SQL Server 2014. In the > > late stages of that install, the process attempts to start the SQL > server engine and fails. > > > There have been some reports of this previously. What might be > happening is that SQL Server has stricter requirements on the underlying > block >size than NTFS itself has. > > > Since you are using a file-backed image, the reported block size from > the emulated storage controller may be 8KB or even higher, depending on > >the underlying filesystem type. > > > A suggestion is to force the block size to 4KB (has to be done during > install as well), and if the problem persists, try 512 bytes. This is done > by using >the 'sectorsize=' parameter to the disk configuration e.g. > > > -s 4,ahci-hd,/path/to/disk.img,sectorsize=4096 > > Just to add, if you're using vm-bhyve you should be able to add this with > the diskX_opts template/config option > > disk0_opts="sectorsize=4096" > > I may adjust the sample templates to include a sectorsize option for > Windows guests, although I'm not 100% clear on what exact OS versions or > applications require specific settings. I do know that SQL Server has been > reported to suddenly fall over unless a valid block size is used (although > I believe it did install and run), but again I'm not sure exactly what the > "correct" settings are. > > Also note that you shouldn't need any grub_* template options if you're > using UEFI. Those options only apply to grub-bhyve. > > Matt > > >later, > > >Peter. > > ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: Windows 2016 Server
-- Randy On Tue, Oct 25, 2016 at 9:38 AM, Dave Shariff Yadallee - System Administrator a.k.a. The Root of the Problem wrote: > On Tue, Oct 25, 2016 at 08:33:47AM -0600, Randy Terbush wrote: > > On Tue, Oct 25, 2016 at 7:58 AM, The Doctor > > wrote: > > > > > On Tue, Oct 25, 2016 at 09:20:28AM +, Matt Churchyard wrote: > > > > > > > One other issue is that Windows doesn't support the virtio-net > network > > > device by default. The easiest way to get this working is to boot the > > > guest with the virtio driver ISO attached instead of the Windows > install > > > disk (once Windows is installed and working). You can then install the > > > driver for the network interface from the CD using the VNC console. > > > > > > > > Depending on what you are doing you may find it easier to use > something > > > like iohyve/chyves/vm-bhyve/vmrc that handles all the raw bhyve > commands > > > for you. > > > > > > > > Matt > > > > > > I will look into the iohyve , saw that last night. > > > > > > Does this also apply to UEFU BSDs / Linuxes ? > > > > > > > ???Just to chime in quickly on this thread... I am a big fan of > vm-bhyve. It > > has made it much easier to sort bhyve out in general and get through some > > of these new options for supported guests. > > > > Regarding Linux and UEFI, much of this also applies there. I've > > successfully installed a LinuxMint guest. I will offer that after the > > install, the boot process hung at the EFI. After exiting from the Shell> > > prompt that eventually appears, it is possible to navigate the UEFI bios > > settings to pick a bootable device. Only after rerunning 'grub2-install' > > was I able to have a Linux guest that would boot without fiddling. > > ??? > Let me give you my setup. > > No Zpool here. > > I am running FreeBSD 11 UEFI on x86_64. > > I have set up some non-UEFI guest successfull , > > Fedora, Centos and Ubuntu. > > If it the UEFI part using a non-zpool environment > > that I am trying to wrap my head around. > > Smilir to Windows, I did install Fedora using > UEFI but then > could not go to the > second stage, i.e. booting into the VM. > > Hence I do need to understand how to this with my environment using > purely bhyve. As mentioned, I'm using vm-bhyve to insulating me from the learning curve of "pure bhyve". https://github.com/churchers/vm-bhyve A few more details about my setup. FreeBSD 11-stable (reguired for vnc graphics to work with UEFI guests) Relevant installed packages: vm-bhyve bhyve-firmware grub2-bhyve uefi-edk2-bhyve uefi-edk2-bhyve-csm While vm-bhyve is running in a zpool, the guests are using disk image files. The following template allowed me to install LinuxMint through graphic VNC interface. guest="linux" uefi="yes" cpu=1 memory=2G graphics="yes" graphics_res="1600x1200" graphics_wait="yes" xhci_mouse="yes" network0_type="virtio-net" network0_switch="public" disk0_type="virtio-blk" disk0_name="disk0.img" grub_run_partition="1" vm create -t mint -s 30G mint vm install mint linuxmint-18-cinnamon-64bit.iso (32bit would not install as a UEFI guest) vm list (shows running bhyve guests and indicates the IP and port that VNC is running on for this guest) vncviewer 127.0.0.1:5900 Top-level listing of the vm zpool shows the layout which includes a .template and .iso directory to collect your configs and install isos. Nice clean setup. [root: /vm]# ls -l total 171 drwxr-xr-x 2 root wheel 5 Jul 20 10:01 .config drwxr-xr-x 2 root wheel 10 Oct 24 12:10 .iso drwxr-xr-x 2 root wheel 17 Oct 24 11:56 .templates drwxr-xr-x 2 root wheel 8 Oct 3 21:41 kali drwxr-xr-x 2 root wheel 6 Oct 2 18:13 macos drwxr-xr-x 2 root wheel 8 Oct 25 05:37 mint drwxr-xr-x 2 root wheel 7 Oct 22 15:31 win2012 drwxr-xr-x 2 root wheel 5 Oct 10 16:58 winapp (NOTE: still trying to get a working MacOS guest running...) ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Installing SQL Server on Windows 2012 bhyve guests
This may be a stretch to report here, but read it as a plea for help as to how to debug this issue further. I've followed the info provided here https://wiki.freebsd.org/bhyve/Windows to create a Windows Server 2012 image that I successfully installed on the bhyve hypervisor. After getting a working Win2012 image running, applying updates, etc. I attempted to install SQL Server 2014. In the late stages of that install, the process attempts to start the SQL server engine and fails. Here is where the fun begins: The first installation of WinServer 2012 was run as an unattended install. I've since tried reinstalling it many times changing to an interactive install, Windows 2016 install etc. and I find that the installation of SQL Server 2014 fails every time in the same way. I've attempted to follow some similar reports on the web for other people installing on dedicated servers by removing all authorization restrictions, etc. yet the server still fails to run. Log files generated by SQL Server leave very little to go on and everything logged seems to point back to the more common solutions regarding permissions and filesystem access. I am at a place where I am starting to believe that this is somehow related to the hypervisor, yet I don't have a lot of evidence to base that on. I'm hoping that someone here might have some ideas of how to further debug this. I've read that SQL server has some problem running on some filesystem types, so not sure if there could be some lower level virtio missing piece that could be causing the failure. One other bit of data that I have that may or may not be interesting is the following output from the file cmd on the disk0.img: disk0.img: DOS/MBR boot sector MS-MBR Windows 7 english at offset 0x163 "Invalid partition table" at offset 0x17b "Error loading operating system" at offset 0x19a "Missing operating system"; partition 1 : ID=0xee, start-CHS (0x0,0,2), end-CHS (0x3ff,255,63), startsector 1, 4294967295 sectors This output has been the same for every Windows guest I have created, regardless of version. Any help would be greatly appreciated. -- Randy ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: Windows 2016 Server
On Tue, Oct 25, 2016 at 7:58 AM, The Doctor wrote: > On Tue, Oct 25, 2016 at 09:20:28AM +, Matt Churchyard wrote: > > > One other issue is that Windows doesn't support the virtio-net network > device by default. The easiest way to get this working is to boot the > guest with the virtio driver ISO attached instead of the Windows install > disk (once Windows is installed and working). You can then install the > driver for the network interface from the CD using the VNC console. > > > > Depending on what you are doing you may find it easier to use something > like iohyve/chyves/vm-bhyve/vmrc that handles all the raw bhyve commands > for you. > > > > Matt > > I will look into the iohyve , saw that last night. > > Does this also apply to UEFU BSDs / Linuxes ? > Just to chime in quickly on this thread... I am a big fan of vm-bhyve. It has made it much easier to sort bhyve out in general and get through some of these new options for supported guests. Regarding Linux and UEFI, much of this also applies there. I've successfully installed a LinuxMint guest. I will offer that after the install, the boot process hung at the EFI. After exiting from the Shell> prompt that eventually appears, it is possible to navigate the UEFI bios settings to pick a bootable device. Only after rerunning 'grub2-install' was I able to have a Linux guest that would boot without fiddling. ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
