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

Re: Recovering an ZFS vm

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.

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

Re: Recovering an ZFS vm

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

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

[Bug 215972] Bhyve crash more then 1 cpu AMD

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215972 domhau...@gmail.com changed: What|Removed |Added CC||domhau...@gmail.com ---

[Bug 213333] FreeBSD 11-RELEASE fails to boot under KVM/Qemu

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=21 --- Comment #17 from Cameron --- I've managed to work around this. There's 2 issues here: 1. Rather than using an Opteron_* model in kvm for the CPU, etc. Use kvm64. Others may work as well. I believe this alone will

Re: Bhyve. Unable install Windows 7/Server 2008R2

Bezüglich Lars Engels's Nachricht vom 05.12.2017 17:57 (localtime): > On Tue, Dec 05, 2017 at 04:49:45AM -0800, Rodney W. Grimes wrote: >>> Hi, >>> bhyve -c 2 -s 0,hostbridge -s 3,ahci-hd,/dev/zvol/my_zroot/VM/img/win7/disk0 >>> For win7/2k8*, the sector size presented to the guest

Re: Bhyve. Unable install Windows 7/Server 2008R2

On Tue, Dec 05, 2017 at 04:49:45AM -0800, Rodney W. Grimes wrote: > > Hi, > > > > > bhyve -c 2 -s 0,hostbridge -s > > > 3,ahci-hd,/dev/zvol/my_zroot/VM/img/win7/disk0 > > > > For win7/2k8*, the sector size presented to the guest has to be forced > > to 512 bytes i.e. for the ahci-cd slot,

Re: Storage overhead on zvols

> On Dec 5, 2017, at 10:41 AM, Rodney W. Grimes > wrote: > >> >> >> Dustin Wenz wrote: >>> I'm not using ZFS in my VMs for data integrity (the host already >>> provides that); it's mainly for the easy creation and management of >>> filesystems, and the

Re: Storage overhead on zvols

> > > Dustin Wenz wrote: > > I'm not using ZFS in my VMs for data integrity (the host already > > provides that); it's mainly for the easy creation and management of > > filesystems, and the ability to do snapshots for rollback and > > replication. > > snapshot and replication works fine on the

Re: Storage overhead on zvols

Hi all, > Am 05.12.2017 um 16:41 schrieb Paul Vixie : > in some bsd related meeting this year i asked allan jude for a bhyve level > null mount, > so that we could access at / inside the guest some subtree of the host, and > avoid block > devices and file systems altogether.

Re: Storage overhead on zvols

Dustin Wenz wrote: I'm not using ZFS in my VMs for data integrity (the host already provides that); it's mainly for the easy creation and management of filesystems, and the ability to do snapshots for rollback and replication. snapshot and replication works fine on the host, acting on the

Re: Storage overhead on zvols

> I'm not using ZFS in my VMs for data integrity (the host already provides > that); it's mainly for the easy creation and management of filesystems, and > the ability to do snapshots for rollback and replication. Some of my > deployments have hundreds of filesystems in an organized hierarchy,

Re: Storage overhead on zvols

the surprising fact that came up in recent threads is that some of you run zfs in your guests. that's quite a bit of unnec'y redundancy and other overheads. i am using UFS in my guests. ___ freebsd-virtualization@freebsd.org mailing list

Re: Storage overhead on zvols

Thanks for linking that resource. The purpose of my posting was to increase the body of knowledge available to people who are running bhyve on zfs. It's a versatile way to deploy guests, but I haven't seen much practical advise about doing it efficiently. Allan's explanation yesterday of how

[Bug 213333] FreeBSD 11-RELEASE fails to boot under KVM/Qemu

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=21 mainl...@apeiron.net changed: What|Removed |Added CC||mainl...@apeiron.net ---

Re: Bhyve. Unable install Windows 7/Server 2008R2

> Hi, > > > bhyve -c 2 -s 0,hostbridge -s > > 3,ahci-hd,/dev/zvol/my_zroot/VM/img/win7/disk0 > > For win7/2k8*, the sector size presented to the guest has to be forced > to 512 bytes i.e. for the ahci-cd slot, the config would look like: > > -s