Closed evanfietz closed 4 years ago
tstromberg
commented
4 years ago Thank you for your feedback!
Sadly, we've messed up and neither the error message or the logs here are very useful at all for some reason. We'll need to get to the root of tha.t Do you mind sharing the output of:
vboxmanage -versionvboxmanage showvminfo minikubeAlso, see if there are any logs in ~/.VirtualBox/Machines/minikube/Logs
tstromberg
commented
4 years ago Related: #5453
evanfietz
commented
4 years ago vboxmanage -version 6.0.12r133076
vboxmanage showvminfo minikube
Name: minikube
Groups: /
Guest OS: Linux 2.6 / 3.x / 4.x (64-bit)
UUID: 93b5f58b-2322-49e1-8e6c-77845a3a9e99
Config file: /home/fietz/.minikube/machines/minikube/minikube/minikube.vbox
Snapshot folder: /home/fietz/.minikube/machines/minikube/minikube/Snapshots
Log folder: /home/fietz/.minikube/machines/minikube/minikube/Logs
Hardware UUID: 93b5f58b-2322-49e1-8e6c-77845a3a9e99
Memory size 2000MB
Page Fusion: disabled
VRAM size: 8MB
CPU exec cap: 100%
HPET: enabled
CPUProfile: host
Chipset: piix3
Firmware: BIOS
Number of CPUs: 2
PAE: enabled
Long Mode: enabled
Triple Fault Reset: disabled
APIC: enabled
X2APIC: disabled
Nested VT-x/AMD-V: disabled
CPUID Portability Level: 0
CPUID overrides: None
Boot menu mode: disabled
Boot Device 1: DVD
Boot Device 2: DVD
Boot Device 3: HardDisk
Boot Device 4: Not Assigned
ACPI: enabled
IOAPIC: enabled
BIOS APIC mode: APIC
Time offset: 0ms
RTC: UTC
Hardw. virt.ext: enabled
Nested Paging: enabled
Large Pages: enabled
VT-x VPID: enabled
VT-x unr. exec.: enabled
Paravirt. Provider: Default
Effective Paravirt. Prov.: KVM
State: aborted (since 2019-09-25T15:05:23.671000000)
Monitor count: 1
3D Acceleration: disabled
2D Video Acceleration: disabled
Teleporter Enabled: disabled
Teleporter Port: 0
Teleporter Address:
Teleporter Password:
Tracing Enabled: disabled
Allow Tracing to Access VM: disabled
Tracing Configuration:
Autostart Enabled: disabled
Autostart Delay: 0
Default Frontend:
Storage Controller Name (0): SATA
Storage Controller Type (0): IntelAhci
Storage Controller Instance Number (0): 0
Storage Controller Max Port Count (0): 30
Storage Controller Port Count (0): 30
Storage Controller Bootable (0): on
SATA (0, 0): /home/fietz/.minikube/machines/minikube/boot2docker.iso (UUID: a6fa0f27-fa7d-4912-b086-40c208873f59)
SATA (1, 0): /home/fietz/.minikube/machines/minikube/disk.vmdk (UUID: 894016ce-28b4-49f6-92d6-3a15febe1136)
NIC 1: MAC: 080027EC444C, Attachment: NAT, Cable connected: on, Trace: off (file: none), Type: virtio, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: deny, Bandwidth group: none
NIC 1 Settings: MTU: 0, Socket (send: 64, receive: 64), TCP Window (send:64, receive: 64)
NIC 1 Rule(0): name = ssh, protocol = tcp, host ip = 127.0.0.1, host port = 46683, guest ip = , guest port = 22
NIC 2: MAC: 0800278BD590, Attachment: Host-only Interface 'vboxnet0', Cable connected: on, Trace: off (file: none), Type: virtio, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: deny, Bandwidth group: none
NIC 3: disabled
NIC 4: disabled
NIC 5: disabled
NIC 6: disabled
NIC 7: disabled
NIC 8: disabled
Pointing Device: PS/2 Mouse
Keyboard Device: PS/2 Keyboard
UART 1: disabled
UART 2: disabled
UART 3: disabled
UART 4: disabled
LPT 1: disabled
LPT 2: disabled
Audio: enabled (Driver: PulseAudio, Controller: AC97, Codec: STAC9700)
Audio playback: disabled
Audio capture: disabled
Clipboard Mode: disabled
Drag and drop Mode: disabled
VRDE: disabled
OHCI USB: disabled
EHCI USB: disabled
xHCI USB: disabled
USB Device Filters:
medyagh
commented
4 years ago @evanfietz I wonder if you have the same problem in the latest version ?
btw, since you are using ubuntu, I would recommend using kvm driver. which preferred way for linux.
https://minikube.sigs.k8s.io/docs/start/linux/#hypervisor-setup
evanfietz
commented
4 years ago Hello,
I’m not sure as I gave up on Minicube and just built a three node K8 cluster.
Thanks for checking in!
Regards,
Evan
Evan Fietz Solutions Engineer
NetApp 403.862.9461 Mobile Phone fietz@netapp.commailto:name@netapp.com
[signature_56566682]https://www.netapp.com/us/campaigns/gmq-primary-storage-report/index.aspx?ref_source=esignature&cid=33105
From: Medya Ghazizadeh notifications@github.com Reply-To: kubernetes/minikube reply@reply.github.com Date: Wednesday, November 6, 2019 at 12:33 PM To: kubernetes/minikube minikube@noreply.github.com Cc: "Fietz, Evan" Evan.Fietz@netapp.com, Mention mention@noreply.github.com Subject: Re: [kubernetes/minikube] virtualbox: Unable to start VM: Maximum number of retries (5) exceeded (#5449)
NetApp Security WARNING: This is an external email. Do not click links or open attachments unless you recognize the sender and know the content is safe.
@evanfietzhttps://github.com/evanfietz I wonder if you have the same problem in the latest version ?
btw, since you are using ubuntu, I would recommend using kvm driver. which preferred way for linux.
https://minikube.sigs.k8s.io/docs/start/linux/#hypervisor-setup
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/kubernetes/minikube/issues/5449?email_source=notifications&email_token=ANJNRESMRDIYI4ZQV734YQDQSMLYDA5CNFSM4I2DCQL2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDHXCDQ#issuecomment-550465806, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANJNREXCINXAPX6FMB7FFFTQSMLYDANCNFSM4I2DCQLQ.
The exact command to reproduce the issue: fietz@ubuntu:~$ minikube start --logtostderr -v 8
The full output of the command that failed:
The output of the
minikube logscommand:fietz@ubuntu:~$ minikube logs
💣 api load: filestore "minikube": Docker machine "minikube" does not exist. Use "docker-machine ls" to list machines. Use "docker-machine create" to add a new one.
😿 Sorry that minikube crashed. If this was unexpected, we would love to hear from you: 👉 https://github.com/kubernetes/minikube/issues/new/choose fietz@ubuntu:~$
The operating system version: Ubuntu 18.04.3 LTS