I typically just login to Windows VM and launch XCP-ng Center and the machine randomly crashes after some time.
Log attached.
Windows 10 build 1909 aborted
-
mikebarkdoll
- Posts: 2
- Joined: 13. Feb 2020, 00:12
Windows 10 build 1909 aborted
- Attachments
-
- Win10-12-16-2019-2020-02-12-16-12-23.zip
- (21.75 KiB) Downloaded 7 times
-
scottgus1
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows, Linux
Re: Windows 10 build 1909 aborted
According to https://github.com/xcp-ng/xcp/wiki, 'XCP-ng' is a XenServer-based hypervisor. Looks like you are trying nested virtualization: XCP-ng inside Virtualbox. There's prerequisites for this in the Virtualbox manual, and the forum gurus only know about Virtualbox-in-Virtualbox. And I don't even know that much, since I haven't tried it yet... 
There doesn't appear to be anything egregious in the log, and that 48-core server sounds sweet!
There doesn't appear to be anything egregious in the log, and that 48-core server sounds sweet!
-
mikebarkdoll
- Posts: 2
- Joined: 13. Feb 2020, 00:12
Re: Windows 10 build 1909 aborted
Just using the XCP-ng client software XCP-ng Center. The XCP-ng server is on a different node. Anyway, after posting this I realized it is Windows 10 1909 which alot of people report being unstable. Think I'll try 1903 instead.scottgus1 wrote:According to https://github.com/xcp-ng/xcp/wiki, 'XCP-ng' is a XenServer-based hypervisor. Looks like you are trying nested virtualization: XCP-ng inside Virtualbox. There's prerequisites for this in the Virtualbox manual, and the forum gurus only know about Virtualbox-in-Virtualbox. And I don't even know that much, since I haven't tried it yet...
There doesn't appear to be anything egregious in the log, and that 48-core server sounds sweet!