1)o /etc/group está assim (parte final): plugdev:x:83:cezar power:x:84:cezar netdev:x:86:cezar pop:x:90:pop scanner:x:93:cezar
2)e eu habilitei no bios o secure virtual machine mode (SVM), existe essa opção 3) por esse comando acho tem o retorno svm, ou estou vendo errado? bash-4.3# egrep '(vmx|svm)' /proc/cpuinfo flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 popcnt aes xsave avx f16c lahf_lm cmp_legacy *svm* extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb arat cpb hw_pstate npt lbrv *svm*_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold bmi1 flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 popcnt aes xsave avx f16c lahf_lm cmp_legacy *svm* extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb arat cpb hw_pstate npt lbrv *svm*_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold bmi1 flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 popcnt aes xsave avx f16c lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb arat cpb hw_pstate npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold bmi1 flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 popcnt aes xsave avx f16c lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb arat cpb hw_pstate npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold bmi1 flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 popcnt aes xsave avx f16c lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb arat cpb hw_pstate npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold bmi1 flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 popcnt aes xsave avx f16c lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb arat cpb hw_pstate npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold bmi1 bash-4.3# 4) o único erro que persiste é esse, mas acho está chegando lá bash-4.3# /etc/init.d/vbvoxdv setup bash: /etc/init.d/vbvoxdv: No such file or directory bash-4.3# Em 5 de setembro de 2014 13:39, Max Miorim <[email protected]> escreveu: > Só me corrigindo, a flag nos processadores da AMD é svm e não smx. > > E tem mais isso: > > Any user accounts that plan to use virtualbox will need to be members > of the "vboxusers" group. > > In order to use USB devices in VirtualBox Guests you may have to restart > your host system after installing the virtualbox package. > > > http://slackbuilds.org/slackbuilds/14.1/system/virtualbox/README.SLACKWARE > > On Fri, Sep 5, 2014 at 12:26 PM, Max Miorim <[email protected]> wrote: > > Eu acho que tu tem que colocar o teu usuário no grupo do virtualbox. > > > > O readme do slackbuild deve falar algo sobre isso. > > > > Já sobre o processador, tu não tem as extensões de virtualização > > habilitadas. Eu não sei se é porque não são suportadas pelo processador, > > placa mãe ou se o fabricante decidiu te sacanear e tirou (ou nunca > permitiu > > acesso à) isso da BIOS. > > > > Em 05/09/2014 10:28, "Cezar Rangel" <[email protected]> escreveu: > > > >> 1)habilitei no bios, porei não encontro a flag smx ou vmx. o cpuinfo > está > >> como abaixo e está sendo informado: > >> > >> The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or > there > >> is a permission problem with /dev/vboxdrv. Please reinstall the kernel > >> module by executing > >> > >> '/etc/init.d/vboxdrv setup' > >> > >> as root. If it is available in your distribution, you should install the > >> DKMS package first. This package keeps track of Linux kernel changes and > >> recompiles the vboxdrv kernel module if necessary. > >> > >> 2)sobre o dkms já instalei e ainda aparece esse aviso. sobre o > >> /etc/init;d/vbvoxdv setup retorna :bash-4.3# /etc/init;d/vbvoxdv setup > >> bash: /etc/init: No such file or directory > >> bash: d/vbvoxdv: No such file or directory > >> bash-4.3# > >> > >> 3)#modprobe vboxdrv > >> bash-4.3# > >> > >> não retorna erro > >> > >> 4)abaixo como está o cpuinfo: não vi as flas vmx ou smx . vi vme. mas > com > >> certeza habilitei no biox virtual machine secure na parte CPU > >> > >> processor : 0 > >> vendor_id : AuthenticAMD > >> cpu family : 21 > >> model : 2 > >> model name : AMD FX(tm)-6300 Six-Core Processor > >> stepping : 0 > >> microcode : 0x6000822 > >> cpu MHz : 3500.000 > >> cache size : 2048 KB > >> physical id : 0 > >> siblings : 6 > >> core id : 0 > >> cpu cores : 3 > >> apicid : 16 > >> initial apicid : 0 > >> fpu : yes > >> fpu_exception : yes > >> cpuid level : 13 > >> wp : yes > >> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge > mca > >> cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt > >> pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc ext$ > >> bogomips : 7031.23 > >> TLB size : 1536 4K pages > >> clflush size : 64 > >> cache_alignment : 64 > >> address sizes : 48 bits physical, 48 bits virtual > >> power management: ts ttp tm 100mhzsteps hwpstate cpb eff_freq_ro > >> > >> processor : 1 > >> vendor_id : AuthenticAMD > >> cpu family : 21 > >> model : 2 > >> model name : AMD FX(tm)-6300 Six-Core Processor > >> stepping : 0 > >> microcode : 0x6000822 > >> cpu MHz : 3500.000 > >> cache size : 2048 KB > >> physical id : 0 > >> siblings : 6 > >> core id : 1 > >> cpu cores : 3 > >> apicid : 17 > >> initial apicid : 1 > >> fpu : yes > >> fpu_exception : yes > >> cpuid level : 13 > >> wp : yes > >> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge > mca > >> cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt > >> pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc ext$ > >> bogomips : 7031.23 > >> TLB size : 1536 4K pages > >> clflush size : 64 > >> cache_alignment : 64 > >> address sizes : 48 bits physical, 48 bits virtual > >> power management: ts ttp tm 100mhzsteps hwpstate cpb eff_freq_ro > >> > >> processor : 2 > >> vendor_id : AuthenticAMD > >> cpu family : 21 > >> model : 2 > >> model name : AMD FX(tm)-6300 Six-Core Processor > >> stepping : 0 > >> microcode : 0x6000822 > >> cpu MHz : 3500.000 > >> cache size : 2048 KB > >> physical id : 0 > >> siblings : 6 > >> core id : 2 > >> cpu cores : 3 > >> apicid : 18 > >> initial apicid : 2 > >> Kernel driver not installed (rc=-1908) > >> > >> The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or > there > >> is a permission problem with /dev/vboxdrv. Please reinstall the kernel > >> module by executing > >> > >> '/etc/init.d/vboxdrv setup' > >> > >> as root. If it is available in your distribution, you should install the > >> DKMS package first. This package keeps track of Linux kernel changes and > >> recompiles the vboxdrv kernel module if necessary. > >> fpu $ > >> fpu_exception : yes > >> cpuid level : 13 > >> wp : yes > >> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge > mca > >> cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt > >> pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc ext$ > >> bogomips : 7031.23 > >> TLB size : 1536 4K pages > >> clflush size : 64 > >> cache_alignment : 64 > >> address sizes : 48 bits physical, 48 bits virtual > >> power management: ts ttp tm 100mhzsteps hwpstate cpb eff_freq_ro > >> > >> processor : 3 > >> vendor_id : AuthenticAMD > >> cpu family : 21 > >> model : 2 > >> model name : AMD FX(tm)-6300 Six-Core Processor > >> stepping : 0 > >> microcode : 0x6000822 > >> cpu MHz : 3500.000 > >> cache size : 2048 KB > >> physical id : 0 > >> siblings : 6 > >> core id : 3 > >> cpu cores : 3 > >> apicid : 19 > >> initial apicid : 3 > >> fpu : yes > >> fpu_exception : yes > >> cpuid level : 13 > >> wp : yes > >> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge > mca > >> cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt > >> pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc ext$ > >> bogomips : 7031.23 > >> TLB size : 1536 4K pages > >> clflush size : 64 > >> cache_alignment : 64 > >> address sizes : 48 bits physical, 48 bits virtual > >> power management: ts ttp tm 100mhzsteps hwpstate cpb eff_freq_ro > >> > >> processor : 4 > >> vendor_id : AuthenticAMD > >> cpu family : 21 > >> model : 2 > >> model name : AMD FX(tm)-6300 Six-Core Processor > >> stepping : 0 > >> microcode : 0x6000822 > >> cpu MHz : 3500.000 > >> cache size : 2048 KB > >> physical id : 0 > >> siblings : 6 > >> core id : 4 > >> cpu cores : 3 > >> apicid : 20 > >> initial apicid : 4 > >> fpu : yes > >> fpu_exception : yes > >> cpuid level : 13 > >> wp : yes > >> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge > mca > >> cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt > >> pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc ext$ > >> bogomips : 7031.23 > >> TLB size : 1536 4K pages > >> clflush size : 64 > >> cache_alignment : 64 > >> address sizes : 48 bits physical, 48 bits virtual > >> power management: ts ttp tm 100mhzsteps hwpstate cpb eff_freq_ro > >> > >> processor : 5 > >> vendor_id : AuthenticAMD > >> cpu family : 21 > >> model : 2 > >> model name : AMD FX(tm)-6300 Six-Core Processor > >> stepping : 0 > >> microcode : 0x6000822 > >> cpu MHz : 3500.000 > >> cache size : 2048 KB > >> physical id : 0 > >> siblings : 6 > >> core id : 5 > >> cpu cores : 3 > >> apicid : 21 > >> initial apicid : 5 > >> fpu : yes > >> fpu_exception : yes > >> cpuid level : 13 > >> wp : yes > >> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge > mca > >> cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt > >> pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc ext$ > >> bogomips : 7031.23 > >> TLB size : 1536 4K pages > >> clflush size : 64 > >> cache_alignment : 64 > >> address sizes : 48 bits physical, 48 bits virtual > >> power management: ts ttp tm 100mhzsteps hwpstate cpb eff_freq_ro > >> processor : 5 > >> vendor_id : AuthenticAMD > >> cpu family : 21 > >> model : 2 > >> model name : AMD FX(tm)-6300 Six-Core Processor > >> stepping : 0 > >> microcode : 0x6000822 > >> cpu MHz : 3500.000 > >> cache size : 2048 KB > >> physical id : 0 > >> siblings : 6 > >> core id : 5 > >> cpu cores : 3 > >> apicid : 21 > >> initial apicid : 5 > >> fpu : yes > >> fpu_exception : yes > >> cpuid level : 13 > >> wp : yes > >> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge > mca > >> cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt > >> pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc ext$ > >> bogomips : 7031.23 > >> TLB size : 1536 4K pages > >> clflush size : 64 > >> cache_alignment : 64 > >> address sizes : 48 bits physical, 48 bits virtual > >> power management: ts ttp tm 100mhzsteps hwpstate cpb eff_freq_ro > >> > >> > >> > >> > >> > >> > >> Em 5 de setembro de 2014 00:50, Max Miorim <[email protected]> > escreveu: > >>> > >>> Olha no /proc/cpuinfo se o teu processador tem as flags vmx ou smx. Se > >>> não tiver, tu tem que habilitar na BIOS, carregar o modulo apropriado > (tem > >>> um comentário no rc.modules sobre isso) ou desabilitar a virtualização > por > >>> hardware na máquina virtual (fica mais lento). > >>> > >>> Em 05/09/2014 00:35, "Cezar Rangel" <[email protected]> escreveu: > >>>> > >>>> olá a todos, depois da instalação com sucesso da virtual box, quando > >>>> tento iniciar dá o erro abaixo: > >>>> > >>>> "Falha ao abrir uma sessão para a máquina virtual chackra. > >>>> > >>>> AMD-V is disabled in the BIOS (or by the host OS). > (VERR_SVM_DISABLED)" > >>>> > >>>> já fui lá no bios e não vi nada o que habilitar nesse sentido. > >>>> > >>>> antes, sempre tenho que executar #modprobe vboxdrv. mas sempre isso > >>>> toda vez que inicio. aí segue, mas esbarra no erro acimo da tal > habilitação > >>>> falltando. > >>>> > >>>> > >>>> > >>>> > >>>> -- > >>>> GUS-BR - Grupo de Usuários de Slackware Brasil > >>>> http://www.slackwarebrasil.org/ > >>>> http://groups.google.com/group/slack-users-br > >>>> > >>>> Antes de perguntar: > >>>> > >>>> > http://www.vivaolinux.com.br/artigo/Como-elaborar-perguntas-para-listas-de-discussao > >>>> > >>>> Para sair da lista envie um e-mail para: > >>>> [email protected] > >>>> --- > >>>> Você recebeu essa mensagem porque está inscrito no grupo > quot;Slackware > >>>> Users Group - Brazil" dos Grupos do Google. > >>>> Para cancelar inscrição nesse grupo e parar de receber e-mails dele, > >>>> envie um e-mail para [email protected]. > >>>> Para mais opções, acesse https://groups.google.com/d/optout. > >>> > >>> -- > >>> GUS-BR - Grupo de Usuários de Slackware Brasil > >>> http://www.slackwarebrasil.org/ > >>> http://groups.google.com/group/slack-users-br > >>> > >>> Antes de perguntar: > >>> > >>> > http://www.vivaolinux.com.br/artigo/Como-elaborar-perguntas-para-listas-de-discussao > >>> > >>> Para sair da lista envie um e-mail para: > >>> [email protected] > >>> --- > >>> Você recebeu essa mensagem porque está inscrito no grupo quot;Slackware > >>> Users Group - Brazil" dos Grupos do Google. > >>> Para cancelar inscrição nesse grupo e parar de receber e-mails dele, > >>> envie um e-mail para [email protected]. > >>> Para mais opções, acesse https://groups.google.com/d/optout. > >> > >> > >> > >> > >> -- > >> Cezar Rangel > >> [email protected] > >> > >> -- > >> GUS-BR - Grupo de Usuários de Slackware Brasil > >> http://www.slackwarebrasil.org/ > >> http://groups.google.com/group/slack-users-br > >> > >> Antes de perguntar: > >> > >> > http://www.vivaolinux.com.br/artigo/Como-elaborar-perguntas-para-listas-de-discussao > >> > >> Para sair da lista envie um e-mail para: > >> [email protected] > >> --- > >> Você recebeu essa mensagem porque está inscrito no grupo quot;Slackware > >> Users Group - Brazil" dos Grupos do Google. > >> Para cancelar inscrição nesse grupo e parar de receber e-mails dele, > envie > >> um e-mail para [email protected]. > >> Para mais opções, acesse https://groups.google.com/d/optout. > > -- > GUS-BR - Grupo de Usuários de Slackware Brasil > http://www.slackwarebrasil.org/ > http://groups.google.com/group/slack-users-br > > Antes de perguntar: > > http://www.vivaolinux.com.br/artigo/Como-elaborar-perguntas-para-listas-de-discussao > > Para sair da lista envie um e-mail para: > [email protected] > --- > Você está recebendo esta mensagem porque se inscreveu no grupo "Slackware > Users Group - Brazil" dos Grupos do Google. > Para cancelar inscrição nesse grupo e parar de receber e-mails dele, envie > um e-mail para [email protected]. > Para obter mais opções, acesse https://groups.google.com/d/optout. > -- * Cezar Rangel* *[email protected] <[email protected]>* -- GUS-BR - Grupo de Usuários de Slackware Brasil http://www.slackwarebrasil.org/ http://groups.google.com/group/slack-users-br Antes de perguntar: http://www.vivaolinux.com.br/artigo/Como-elaborar-perguntas-para-listas-de-discussao Para sair da lista envie um e-mail para: [email protected] --- Você está recebendo esta mensagem porque se inscreveu no grupo "Slackware Users Group - Brazil" dos Grupos do Google. Para cancelar inscrição nesse grupo e parar de receber e-mails dele, envie um e-mail para [email protected]. Para obter mais opções, acesse https://groups.google.com/d/optout.
