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
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
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
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.
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
On Tue, Nov 1, 2016 at 11:24 AM, Randy Terbush <ra...@terbush.org> 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 <freeb
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
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
table, the 512 block image
booted just fine.
Thanks for the help here
--
Randy
On Wed, Oct 26, 2016 at 7:08 AM, Randy Terbush <ra...@terbush.org> 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 b
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
--
Randy
On Tue, Oct 25, 2016 at 9:38 AM, Dave Shariff Yadallee - System
Administrator a.k.a. The Root of the Problem <r...@doctor.nl2k.ab.ca> 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 <doc...
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
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
>
13 matches
Mail list logo