Search results

I believe tsarya is referring to how the sda and sdb set are partitioned into 3, with a bootloader partition, zfs data, and the reserved partition, while the sdc and sdd only have two partitions, missing what looks like the bootloader partition, and why this occurs.

Ok, so I blew away my entire config and reinstalled from scratch (with 5 beta). Installed OVS and the problem seems to be fixed for ipv4 - I must have misconfigured something somewhere on my previous install. However, it looks like link-local ipv6 addresses (fe80::blahblah) are being assigned...

I have two interfaces on my machine, eth0 and eth1. I created two OVS bridges, vmbr0 and vmbr1. vmbr0 has an intport with my local ip for management (10.0.0.21) vmbr1 has no intports, and no ip address configured. Likewise, the physical interfaces have no ip addresses defined. However, vmbr1...

Try disabling "Headless mode" in your bios.

Reinstalled from scratch using a freshly downloaded 4.2 iso. Set up my network bridge, a single vm (freebsd), set up iommu (with unsafe interrupts due to my board), passed my pci devices (lsi sas2008) through and let it run. Workload is extremely light throughout, never exceeding 15%cpu or so...

I'm using a Xeon X5675, ZFS mirror install on the motherboard ICH10 controller. I even changed to new cables to rule that out, but it made no difference.

I'm seeing what I think are these same hangs/crashes every 24 to 48 hours or so too. My machine stays powered on but everything is hung and unresponsive. Neither syslog or the BMC logs show anything interesting. This is running 4.2... I originally thought this was a memory issue, but I swapped...

It seems like passing through my LSI SAS2008 based controllers to an OmniOS guest causes the vm to simply reboot shortly after passing grub (the attached screen is all it shows before it reboots). I know passthrough works because I've tested the controllers on windows, debian, and freebsd...