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),
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
boot 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
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 corre
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://gith
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 issue
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, 2
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
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 Ch
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
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
> t
e 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: Ra
--
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 T
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 worki
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 drive
15 matches
Mail list logo
