Custom Query (16363 matches)
Results (667 - 669 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #20596 | worksforme | unaligned (x86_64 = 2MB) kernel crash the guest in nested mode | ||
| Description |
VirtualBox Version 6.1.26 r145957 (Qt5.6.3) Host : MacOS Guest : Linux ManjaroMacBook 5.10.68-1-MANJARO #1 SMP PREEMPT Wed Sep 22 12:29:47 UTC 2021 x86_64 GNU/Linux If you build a linus kernel < 4.4.124 (IIRC) kernel build script don't align the ELF to 2MB on x86_64 and make the guest crash, may due a triple page fault. This as been addressed in linux kernel tree commit : e3d03598e8ae7d195af5d3d049596dec336f569f testing command inside the guest # qemu-system-x86_64 -kernel linux-4.4 |
|||
| #15733 | duplicate | unable to use an opensuse 13.2 distribution. -> duplicate of #14102 | ||
| Description |
working on it since a few months , I finally made the following conclusion: virtualbox is not able to run a classic opensuse 13.2 distribution and may be more. we manage to run it , but with slow graphic/network performances only with latest 4.x releases, and since 5.x relases that is dramatic ! => bad mouse behaviour (screen flickering) => slow video performance. (unusable for linux developers, you open popup menus, it makes times before displaying ..no accel) => video driver unable to find native resolution. => slow network performances So, for us, it is time to conclude and either have a solution or use a WORKING vm alternative:
we tried it on a dell lattitude e5550 and other systems, these are good perf systems.
who is really using it in a confortable way ???? |
|||
| #1948 | fixed | unable to use VirtualBox on sol10 u4 sparse zone | ||
| Description |
I tried this with a FreeBSD ISO guest image. This error is thrown: VirtualBox kernel driver cannot be opened.
VBox status code: -1911 (VERR_VM_DRIVER_OPEN_ERROR).
Result Code: 0x80004005
Component: Console
Interface: IConsole {d5a1cbda-f5d7-4824-9afe-d640c94c7dcf}
I have already given the raw device access for this zone and (and rebooted), using: add device set match=/dev/vboxdrv end Is it really having problems communicating to that device OR is there a keyboard problem as mentioned below? errno 6 is: #define ENXIO 6 /* No such device or address */ 00:00:03.355 VirtualBox 1.6.4 r33808 solaris.amd64 (Jul 29 2008 20:50:41) release log
00:00:03.355 Log opened 2008-08-12T17:38:10.444932000Z
00:00:03.357 Failed to open "/dev/vboxdrv", errno=6, rc=VERR_VM_DRIVER_OPEN_ERROR
00:00:03.357 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={d5a1cbda-f5d7-4824-9afe-d640c94c7dcf} aComponent={Console} aText={VirtualBox kernel driver cannot be opened.
00:00:03.357 VBox status code: -1911 (VERR_VM_DRIVER_OPEN_ERROR)} aWarning=false, preserve=false
root@rule:/# /opt/VirtualBox/vboxdrv.sh status
Running.
root@rule:/#
|
|||

