Author

Topic: anyone running BitCoinCore on Ubuntu in a VM? (Read 234 times)

newbie
Activity: 12
Merit: 0
August 29, 2018, 06:38:20 PM
#10
I always have issues with running Core on VM. Have you tried VirtualBox? I know VM is better but sometimes I've had better luck with VB.
legendary
Activity: 3346
Merit: 3130
setting up a fresh VM (VMWare ESXi 6.5) of Ubuntu 16.04.5 (fresh install), and when i launch bitcoin core (to allow it to sync up to the chain) the whole VM freezes up. got plenty of ram, cores and drive space setup for the VM. the 10 other VMs on my server box are running fine.

First take a look to the minimum requirements:

Minimum Requirements

Bitcoin Core full nodes have certain requirements. If you try running a node on weak hardware, it may work—but you’ll likely spend more time dealing with issues. If you can meet the following requirements, you’ll have an easy-to-use node.

    Desktop or laptop hardware running recent versions of Windows, Mac OS X, or Linux.

    145 gigabytes of free disk space, accessable at a minimum read/write speed of 100 MB/s.

    2 gigabytes of memory (RAM)

    A broadband Internet connection with upload speeds of at least 400 kilobits (50 kilobytes) per second

    An unmetered connection, a connection with high upload limits, or a connection you regularly monitor to ensure it doesn’t exceed its upload limits. It’s common for full nodes on high-speed connections to use 200 gigabytes upload or more a month. Download usage is around 20 gigabytes a month, plus around an additional 140 gigabytes the first time you start your node.

    6 hours a day that your full node can be left running. (You can do other things with your computer while running a full node.) More hours would be better, and best of all would be if you can run your node continuously.

    Note: many operating systems today (Windows, Mac, and Linux) enter a low-power mode after the screensaver activates, slowing or halting network traffic. This is often the default setting on laptops and on all Mac OS X laptops and desktops. Check your screensaver settings and disable automatic “sleep” or “suspend” options to ensure you support the network whenever your computer is running.

If you have that hardware in your virtual machine and it still freezing, then you should try with other operative system like centos.
newbie
Activity: 5
Merit: 0
Im running it fine.

Msg me with any questions
HCP
legendary
Activity: 2086
Merit: 4361
anyways, i checked the logs, all empty. it seems to freeze up immediately, never writes any data to disk.
If it isn't writing anything to disk, then it sounds more like a permissions issue or something... I'd expect it to at least output something??!? Or perhaps it is a corrupted download/install? Huh

- Have you checked the checksums for the downloaded file?
- What is the commandline that you're using when you attempt to start up Bitcoin Core?

copper member
Activity: 2856
Merit: 3071
https://bit.ly/387FXHi lightning theory
technically ESXi is the host OS, and its running a VM of Ubuntu (full OS) and thats where the BCCore is installed.

backstory:

virtual machine or VM = a full OS version of whatever OS i wanna run, on a host system. the host system can just be your desktop with VirutalBox installed. however i have a server box with a hypervisor. a HV is a host system designed to boot to it's own OS and runs many, many VMs. such as hyperV, ESXi, proxmox, etc. this is how modern data centers work, a single server running VMs of many, many, OSes.


anyways, i checked the logs, all empty. it seems to freeze up immediately, never writes any data to disk.

Not to dive to much into that but your one server isn't exactly a data center and the exact problem of using VMs on a server is that they freeze and you can't get remote access to the server once you have filled up the memory then you can't remote into it as easily as you can with a regular OS running.

Do you definitely have all of the dependencies installed and up to date?
You can find them on the github or from the repository that you cloned (I can't find the page atm and am a bit distracted)...
newbie
Activity: 3
Merit: 1
technically ESXi is the host OS, and its running a VM of Ubuntu (full OS) and thats where the BCCore is installed.

backstory:

virtual machine or VM = a full OS version of whatever OS i wanna run, on a host system. the host system can just be your desktop with VirutalBox installed. however i have a server box with a hypervisor. a HV is a host system designed to boot to it's own OS and runs many, many VMs. such as hyperV, ESXi, proxmox, etc. this is how modern data centers work, a single server running VMs of many, many, OSes.


anyways, i checked the logs, all empty. it seems to freeze up immediately, never writes any data to disk.


copper member
Activity: 2856
Merit: 3071
https://bit.ly/387FXHi lightning theory
i am running full Ubuntu as an OS, but in a VM in ESXi. ESXi is like HyperV, only linux based. (not everybody uses, or even ever _wants_ to use, windows)


Why not just put it on the main Ubuntu OS though?
And I didn't realise there was a linux version of hyperv.

Onto the freezing it does sound like a ram/memory issue although you say you have a lot of it available. Do you have the debug.log in the ~/.Bitcoin folder (if you haven't changed the datadir).
newbie
Activity: 3
Merit: 1
i am running full Ubuntu as an OS, but in a VM in ESXi. ESXi is like HyperV, only linux based. (not everybody uses, or even ever _wants_ to use, windows)
copper member
Activity: 2856
Merit: 3071
https://bit.ly/387FXHi lightning theory
Why are you trying to run it on a VM and not the server itself on an OS?

As far as I can remember, hyperV is free and allows you to run multiple operating systems at the same time (but I haven't used it in a while)...
newbie
Activity: 3
Merit: 1
setting up a fresh VM (VMWare ESXi 6.5) of Ubuntu 16.04.5 (fresh install), and when i launch bitcoin core (to allow it to sync up to the chain) the whole VM freezes up. got plenty of ram, cores and drive space setup for the VM. the 10 other VMs on my server box are running fine.
Jump to: