![]() Saved State is best used when the host must shut down before the VM can (perhaps from power issues), or when the VM is stored on slow media, like an old hard drive. Also, save-stated VMs have gone bad for unknown reasons and have to discard the saved state to restart. Saved-state is directly tied into the CPU state and memory in the host PC and may have issues restarting on occasion if the host changes sufficiently, perhaps in CPU or memory. "Saved-state" in and of itself is still supported and works, like all computer programs, most of the time. This is consistent, it happens every time, and it's the only way I have found to access my VM once I started experiencing this problem.Īny suggestions on what this might be, and where I would start looking? Any pointers? I access my GNOME desktop and everything is ok). Then I go to Machine -> Reset on the Virtualbox menu, it boots again, I get the login screen. and end up with a blank screen (screen detection problems again?). So I upgraded to Virtualbox 6.1, installed the 6.1 Guest Additions, and problem solved.Įxcept that seems to have introduced a new problem: now every time I start my VM, it boots, I get the login screen, I enter credentials. I regularly run apt update/upgrade on my Ubuntu VM and at a certain point, after one of these upgrades that affected the kernel, the 6.0 Guest Additions seemed to be "insufficient" and I started having trouble with my VM using the full screen size on my laptop (1920x1080 - the option was not even there to set manually). Until not long ago, Virtualbox was 6.0 (possibly 6.0.22? can't recall) and recently I upgraded to 6.1.18 r142142. ![]() I've been running Ubuntu 20.04 LTS for several months now - mostly without problems - as a guest on Virtualbox, with Windows 10 as the host OS. Uname -a: Linux Arturis 3.16.New to the forum, and looking for some guidance here. Laptop Model: Thinkpad X1 Carbon (3rd Generation) Is there something from dmesg that points to a fundamental flaw or something that I am completely overlooking?Īny help would be appreciated as it's prevented me from getting any work done which is extremely frustrating. I have also rebuilt virtualbox several times in case it failed to compile against the current kernel correctly. ![]() I have enabled virtualization from setup so that is not the issue. I have installed virtualbox on many different work laptops (including the same model laptop from a previous generation) and never had any issues. i915 aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd i2c_algo_bit psmouse drm_kms_helper ahci e1000e libahci drm ptp pps_core wmi video Modules linked in: vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) ctr ccm pci_stub uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common videodev arc4 media intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel cdc_mbim cdc_wdm kvm cdc_ncm cdc_acm usbnet mii btusb iwlmvm mac80211 joydev snd_hda_codec_realtek serio_raw snd_hda_codec_hdmi snd_hda_codec_generic iwlwifi lpc_ich snd_hda_intel snd_hda_controller snd_hda_codec rfcomm bnep snd_hwdep cfg80211 snd_seq_midi bluetooth snd_seq_midi_event snd_pcm 6lowpan_iphc mei_me mei shpchp snd_rawmidi snd_seq snd_seq_device snd_timer nvram snd mac_hid soundcore parport_pc ppdev nls_iso8859_1 lp parport uas usb_storage hid_generic usbhid hid dm_crypt crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel vboxdrv: fAsync=0 offMin=0xd8 offMax=0xc60 vboxdrv: fAsync=0 offMin=0xdb offMax=0x2436 vboxdrv: Successfully loaded version 4.3.18_Ubuntu (interface 0x001a0008). vboxdrv: fAsync=0 offMin=0xd8 offMax=0x1d31 vboxpci: IOMMU not found (not registered) vboxdrv: Successfully loaded version 4.3.20 (interface 0x001a0008). vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'. vboxdrv: fAsync=0 offMin=0xcf offMax=0xff9 vboxdrv: module verification failed: signature and/or required key missing - tainting kernel Looking at dmesg is proving very cryptic for me: $ dmesg | grep vbox It basically fails to start the virtual machine when I try boot it and remains stuck on "Starting Virtual Machine" I just got a new work laptop but I am having a lot of difficulty getting VirtualBox to run on it.
0 Comments
Leave a Reply. |