Custom Query (16363 matches)
Results (1795 - 1797 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #3240 | duplicate | grsecurity host hangs after trying to run guest | ||
| Description |
When host uses hardened kernel 2.6.24 or higher with pax patch, then host hangs after trying to run guest. steps to reproduce:
result: host will hang after opening guest window and before guest begins to boot without any log. I tried to create a core dump after opening guest window, but before host hangs. Dump is in attachment. I reported this to pax paxteam too. Here are our current mails:
I'm not be able to create patch into kernel or modules, but when you will write patches then I can test them and send result back to you. I tested older versions of grsecurity. In current stable grsecurity-2.1.11-2.6.24.5-200804211829 vmware still reboots, but vbox didn't crash and write this message: vboxdrv: Trying to deactivate the NMI watchdog permanently... vboxdrv: Successfully done. vboxdrv: Found 2 processor cores. vboxdrv: fAsync=1 offMin=0x535c2 offMax=0x535c2 vboxdrv: TSC mode is 'asynchronous', kernel timer mode is 'normal'. vboxdrv: Successfully loaded version 2.0.4 (interface 0x00090000). PAX: VirtualBox:12283, uid/euid: 1000/1000, invalid execution attempt at ffffc20004969000 RIP:
PGD 8000000000530063 PUD 9f015067 PMD 9e384063 PTE 80c8e003 Oops: 0011 [1] PREEMPT SMP CPU 0 Modules linked in: vboxdrv snd_pcm_oss snd_mixer_oss snd_seq_oss snd_seq_midi_event snd_seq snd_seq_devic e bridge llc fuse ide_cd pcmcia cdrom ata_piix snd_hda_intel yenta_socket ohci1394 snd_pcm rsrc_nonstatic
dev pcspkr snd_hwdep video cfg80211 snd output button Pid: 12283, comm: VirtualBox Not tainted 2.6.24.5-grsec #2 RIP: 0010:[<ffffc20004969000>] [<ffffc20004969000>] RSP: 0018:ffff810094bc7d70 EFLAGS: 00010046 RAX: 000000000000000f RBX: 0000000000000246 RCX: ffff81008b5b0810 RDX: 0000000000000000 RSI: 000000000000000f RDI: ffffc200050a7000 RBP: ffff810094bc7d98 R08: ffff81008b5b0810 R09: 0000000000000000 R10: 0000000000000000 R11: ffffffff803463fa R12: ffffc200050a7000 R13: 00000000ffffffdb R14: ffff81008b5b0810 R15: 0000000040234e50 FS: 0000000040235950(0063) GS:ffffffff8066e000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b CR2: ffffc20004969000 CR3: 000000008b5a6000 CR4: 00000000000006e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Process VirtualBox (pid: 12283, threadinfo ffff810094bc6000, task ffff81008b47cf60) Stack: ffffffff8820f734 0000000000000000 ffff81008b596240 ffff8100949bff10
Call Trace:
Code: 49 89 f9 49 8d 91 20 03 00 00 8c c8 50 e8 0e 00 00 00 c3 cc RIP [<ffffc20004969000>]
CR2: ffffc20004969000 ---[ end trace e68c0759744cb53c ]--- I didn't find older version of grsecurity or pax patches, but I tried gentoo hardened-sources-2.6.23-r13, on this version everything works fine. I hope that it's helpful. Martin |
|||
| #1193 | worksforme | group ownership problem | ||
| Description |
Starting VirtualBox ( Version 1.5.4 on Debian Lenny, Kernel 2.6.22-3-686 ) issues a warning message: volker@eos ~ > VirtualBox
WARNING: You are not a member of the "vboxusers" group. Please add yourself
to this group before starting VirtualBox.
You will not be able to start VMs until this problem is fixed.
volker is member of vboxusers volker@eos ~ > id volker uid=xxx(volker) ...,1001(vboxusers),... /dev/vboxdrv exists and is group writeable volker@eos ~ > ls -l /dev/vboxdrv crw-rw---- 1 root vboxusers 10, 62 2008-02-13 21:31 /dev/vboxdrv As a consequence starting a virtual machine in VirtualBox will throw an error. It is not possible to start a virtual machine. N.B. this system is integrated into NIS/automounter environment. Workaround: change ownership of /dev/vboxdrv to volker. |
|||
| #11378 | obsolete | group functionality broke snapshot path. | ||
| Description |
When I use the new group functionality to group vms and then restore some snapshot it broke the snapshots paths. I must edit the .vbox file to fix it. Some times it deletes the last snapshot used. The paths became something like Snapshot/UUID/Shapshot/UUID/Snapshot/REAL_UUID. |
|||

