It's definitly less den 8 days. Because I use the host minimum once a week
(same day in the week).
Best regards,
2017-11-23 16:56 GMT+01:00 Julian Elischer :
> On 22/11/17 10:35 pm, Martin Schweizer wrote:
>
>> Hello
>>
>> All is running fine. No problems. After about one week FreeBSD hangs,
>>
I have same problem on KVM virtualization.
ср, 22 нояб. 2017 г. в 17:36, Martin Schweizer :
> Hello
>
> All is running fine. No problems. After about one week FreeBSD hangs, means
> does no more respond (also no ssh connection). At the console you can type
> in the user name and then no reaction.
On 22/11/17 10:35 pm, Martin Schweizer wrote:
Hello
All is running fine. No problems. After about one week FreeBSD hangs, means
does no more respond (also no ssh connection). At the console you can type
in the user name and then no reaction. No error message on the screen on
/var/log/messages. S
Hello
All is running fine. No problems. After about one week FreeBSD hangs, means
does no more respond (also no ssh connection). At the console you can type
in the user name and then no reaction. No error message on the screen on
/var/log/messages. Shutdown the sysmtem resolve the problem for the
On Wed, Nov 02, 2016 at 09:28:59PM -0600, The Doctor wrote:
> On Wed, Nov 02, 2016 at 07:00:08PM -0700, Peter Grehan wrote:
> > Hi,
> >
> > > So the question is how do I pass to Windows 2016 that the CPU it is using
> > > is a CPU capable of Hyper-V ?
> >
On Wed, Nov 02, 2016 at 07:00:08PM -0700, Peter Grehan wrote:
> Hi,
>
> > So the question is how do I pass to Windows 2016 that the CPU it is using
> > is a CPU capable of Hyper-V ?
>
> That requires nested hypervisor support, which isn't yet in bhyve.
>
So
Hi,
So the question is how do I pass to Windows 2016 that the CPU it is using
is a CPU capable of Hyper-V ?
That requires nested hypervisor support, which isn't yet in bhyve.
later,
Peter.
___
freebsd-virtualization@freebsd.org mailing
Yes you can get Windows 2016 to work on a FreeBSD VM
Summary below with edits.
On Tue, Nov 01, 2016 at 03:04:19PM -0600, The Doctor wrote:
> On Tue, Nov 01, 2016 at 12:34:20PM -0600, The Doctor wrote:
> > On Tue, Nov 01, 2016 at 03:21:45PM +, Matt Churchyard wrote:
> > > O
; > 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:
> > > > >
> > > > > >
> > > > &
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.
> > > > >
> > >
gt;
> > > > On Tue, Nov 01, 2016 at 09:02:57AM +, Matt Churchyard wrote:
> > > > >
> > > > >
> > > > > >
> > > > > >
> > > > > > I was able to install the Windows 2016 using the GUI method.
>
016 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 t
gt; 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.
> > > &g
7AM +, Matt Churchyard wrote:
> > >
> > > >
> > > > I was able to install the Windows 2016 using the GUI method.
> > > >
> > > > One problem.
> > > >
> > > > It is assigned an IP but
> > > >
> > &g
t 09:02:57AM +, Matt Churchyard wrote:
> > > >
> > > > >
> > > > > I was able to install the Windows 2016 using the GUI method.
> > > > >
> > > > > One problem.
> > > > >
> > > > > It is ass
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
57AM +, Matt Churchyard wrote:
> > > >
> > > >
> > > > >
> > > > >
> > > > > I was able to install the Windows 2016 using the GUI method.
> > > > >
> > > > > One problem.
> > > > >
> > > > > It is a
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
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.
> > >
> >
On Tue, Nov 01, 2016 at 08:08:35AM -0600, Randy Terbush wrote:
> 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.
> >
&
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
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 T
; What do you use for DHCP Server? Is it configured properly?
> Thank you very much!
>
It is bhyve and I do not use DHCP.
Please NEVER top post!
> --
> Daniel Tihanyi
>
> On Tue, Nov 1, 2016, at 04:45, The Doctor wrote:
> > I was able to install the Windows 2016 using the GU
>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
>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
On Tue, Nov 1, 2016, at 04:45, The Doctor 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
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.
What must I do to convince this box that is it on a switch
192.168.0.60
--
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 +
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
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
On Tue, Oct 25, 2016 at 09:20:28AM +, Matt Churchyard wrote:
> >On Mon, Oct 24, 2016 at 08:07:13AM +, Matt Churchyard wrote:
> > On Fri, Oct 21, 2016 at 03:21:10PM -0700, Peter Grehan wrote:
> > > >> [Windows could not parse or process unattend answer file
> > > >> [D:\autounattend.xml] fo
>On Mon, Oct 24, 2016 at 08:07:13AM +, Matt Churchyard wrote:
> On Fri, Oct 21, 2016 at 03:21:10PM -0700, Peter Grehan wrote:
> > >> [Windows could not parse or process unattend answer file
> > >> [D:\autounattend.xml] for pass [windowsPE]. The answer file is
> > >> invalid.]
> > >
> > > Some
On Mon, Oct 24, 2016 at 08:07:13AM +, Matt Churchyard wrote:
> On Fri, Oct 21, 2016 at 03:21:10PM -0700, Peter Grehan wrote:
> > >> [Windows could not parse or process unattend answer file
> > >> [D:\autounattend.xml] for pass [windowsPE]. The answer file is
> > >> invalid.]
> > >
> > > Somet
On Fri, Oct 21, 2016 at 03:21:10PM -0700, Peter Grehan wrote:
> >> [Windows could not parse or process unattend answer file
> >> [D:\autounattend.xml] for pass [windowsPE]. The answer file is
> >> invalid.]
> >
> > Something is wrong with your autounattend.xml file.
>
> Still working on the 2k
On Fri, Oct 21, 2016 at 03:21:10PM -0700, Peter Grehan wrote:
> >> [Windows could not parse or process unattend answer file
> >> [D:\autounattend.xml] for pass [windowsPE]. The answer file is
> >> invalid.]
> >
> > Something is wrong with your autounattend.xml file.
>
> Still working on the 2k16
[Windows could not parse or process unattend answer file
[D:\autounattend.xml] for pass [windowsPE]. The answer file is
invalid.]
Something is wrong with your autounattend.xml file.
Still working on the 2k16 unattend file. Unfortunately things have
changed from TP5 in a non-obvious way :(
On Fri, 21 Oct 2016, The Doctor wrote:
> What went wrong?
Windows:
> [Windows could not parse or process unattend answer file
> [D:\autounattend.xml] for pass [windowsPE]. The answer file is invalid.]
Something is wrong with your autounattend.xml file.
Marcin
On Fri, Oct 21, 2016 at 12:31:20PM -0600, The Doctor wrote:
> Does anyone have Windows 2016 Server Release 1 working on thier sysem.
>
> After following https://wiki.freebsd.org/bhyve/Windows
>
> I run
>
> /usr/sbin/bhyve -c 2 -s 0,hostbridge -s 3,ahci-hd,./windows201
Does anyone have Windows 2016 Server Release 1 working on thier sysem.
After following https://wiki.freebsd.org/bhyve/Windows
I run
/usr/sbin/bhyve -c 2 -s 0,hostbridge -s 3,ahci-hd,./windows2016.img -s
4,ahci-cd,./.iso/win2k16install.iso -s 10,virtio-net,tap15 -s 31,lpc -l
com1,/dev/nmdm15A
39 matches
Mail list logo
