* [gentoo-user] Is my machine too old for virtualbox?
@ 2009-09-27 13:28 Walter Dnes
2009-09-27 15:15 ` [gentoo-user] " walt
` (2 more replies)
0 siblings, 3 replies; 12+ messages in thread
From: Walter Dnes @ 2009-09-27 13:28 UTC (permalink / raw
To: Gentoo Users List
I installed Sun's virtualbox manually, because portage couldn't build
it. DMESG says...
kvm: no hardware support
...and during bootup, I get...
* Starting VirtualBox kernel module ...
* modprobe vboxdrv failed. Please use 'dmesg' to find out why
My machine is a 2-year-old Dell D530 with a dual core. Here is the
first one, according to /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Genuine Intel(R) CPU 2140 @ 1.60GHz
stepping : 2
cpu MHz : 1600.000
cache size : 1024 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 2
apicid : 0
initial apicid : 0
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmon pebs bts pni dtes64 monitor ds_cpl est tm2 ssse3 cx16 xtpr pdcm lahf_lm
bogomips : 3192.17
clflush size : 64
power management:
--
Walter Dnes <waltdnes@waltdnes.org>
^ permalink raw reply [flat|nested] 12+ messages in thread
* [gentoo-user] Re: Is my machine too old for virtualbox?
2009-09-27 13:28 [gentoo-user] Is my machine too old for virtualbox? Walter Dnes
@ 2009-09-27 15:15 ` walt
2009-09-27 18:01 ` Walter Dnes
2009-09-27 18:51 ` [gentoo-user] " Walter Dnes
2009-09-29 23:40 ` Walter Dnes
2 siblings, 1 reply; 12+ messages in thread
From: walt @ 2009-09-27 15:15 UTC (permalink / raw
To: gentoo-user
On 09/27/2009 06:28 AM, Walter Dnes wrote:
> I installed Sun's virtualbox manually, because portage couldn't build
> it. DMESG says...
>
> kvm: no hardware support
>
> ...and during bootup, I get...
>
> * Starting VirtualBox kernel module ...
> * modprobe vboxdrv failed. Please use 'dmesg' to find out why
Well, that's all a bit strange. 'kvm' is one of the two kernel modules
used by kvm (naturally) which is a completely different product from
vbox. kvm is great for machines with hardware virtualization support,
but doesn't work at all without it.
VirtualBox OTOH does not need hardware support at all and uses its own
kernel module name vboxdrv (has nothing to do with kvm). I'm thinking
you looked at the wrong part of dmesg -- but why there is an error
message there from kvm I can't guess.
I'm using the vbox svn repository from Sun, so I haven't tried building
the portage version. What problem do you see?
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [gentoo-user] Re: Is my machine too old for virtualbox?
2009-09-27 15:15 ` [gentoo-user] " walt
@ 2009-09-27 18:01 ` Walter Dnes
2009-09-27 18:06 ` Volker Armin Hemmann
` (2 more replies)
0 siblings, 3 replies; 12+ messages in thread
From: Walter Dnes @ 2009-09-27 18:01 UTC (permalink / raw
To: gentoo-user
[-- Attachment #1: Type: text/plain, Size: 499 bytes --]
On Sun, Sep 27, 2009 at 08:15:46AM -0700, walt wrote
> I'm using the vbox svn repository from Sun, so I haven't tried building
> the portage version.
As I mentioned, I'm using Sun's install because the portage install
dies.
> What problem do you see?
At bootup I get...
* Starting VirtualBox kernel module ...
* modprobe vboxdrv failed. Please use 'dmesg' to find out why
I'm attaching dmesg output in the hope that someone can figure this
out.
--
Walter Dnes <waltdnes@waltdnes.org>
[-- Attachment #2: dmesg.txt --]
[-- Type: text/plain, Size: 28411 bytes --]
Linux version 2.6.29-gentoo-r5 (root@d530) (gcc version 4.3.2 (Gentoo 4.3.2-r3 p1.6, pie-10.1.5) ) #1 SMP Fri Jul 10 23:46:49 EDT 2009
KERNEL supported cpus:
Intel GenuineIntel
AMD AuthenticAMD
NSC Geode by NSC
Cyrix CyrixInstead
Centaur CentaurHauls
Transmeta GenuineTMx86
Transmeta TransmetaCPU
UMC UMC UMC UMC
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 0000000000099c00 (usable)
BIOS-e820: 0000000000099c00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000007f590000 (usable)
BIOS-e820: 000000007f590000 - 000000007f5e3000 (ACPI NVS)
BIOS-e820: 000000007f5e3000 - 000000007f5f0000 (ACPI data)
BIOS-e820: 000000007f5f0000 - 000000007f600000 (reserved)
BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
DMI 2.5 present.
last_pfn = 0x7f590 max_arch_pfn = 0x100000
kernel direct mapping tables up to 377fe000 @ 7000-c000
ACPI: RSDP 000F96C0, 0024 (r2 DELL )
ACPI: XSDT 7F5E3080, 005C (r1 DELL FX09 42302E31 AWRD 0)
ACPI: FACP 7F5E7200, 00F4 (r3 DELL FX09 42302E31 AWRD 0)
ACPI Warning (tbfadt-0568): 32/64X length mismatch in Pm1aEventBlock: 32/8 [20081204]
ACPI Warning (tbfadt-0568): 32/64X length mismatch in Pm1aControlBlock: 16/8 [20081204]
ACPI Warning (tbfadt-0568): 32/64X length mismatch in PmTimerBlock: 32/8 [20081204]
ACPI Warning (tbfadt-0568): 32/64X length mismatch in Gpe0Block: 128/8 [20081204]
ACPI Warning (tbfadt-0412): Invalid length for Pm1aEventBlock: 8, using default 32 [20081204]
ACPI Warning (tbfadt-0412): Invalid length for Pm1aControlBlock: 8, using default 16 [20081204]
ACPI Warning (tbfadt-0412): Invalid length for PmTimerBlock: 8, using default 32 [20081204]
FADT: X_PM1a_EVT_BLK.bit_width (16) does not match PM1_EVT_LEN (4)
ACPI: DSDT 7F5E3200, 3FFC (r1 DELL AWRDACPI 1000 MSFT 3000000)
ACPI: FACS 7F590000, 0040
ACPI: HPET 7F5E73C0, 0038 (r1 DELL FX09 42302E31 AWRD 98)
ACPI: MCFG 7F5E7400, 003C (r1 DELL FX09 42302E31 AWRD 0)
ACPI: SLIC 7F5E7440, 0176 (r1 DELL FX09 42302E31 AWRD 0)
ACPI: DMY2 7F5E75C0, 0080 (r1 DELL FX09 42302E31 AWRD 0)
ACPI: APIC 7F5E7300, 0084 (r1 DELL FX09 42302E31 AWRD 0)
ACPI: SSDT 7F5E7CA0, 0380 (r1 PmRef CpuPm 3000 INTL 20041203)
ACPI: Local APIC address 0xfee00000
1149MB HIGHMEM available.
887MB LOWMEM available.
mapped low ram: 0 - 377fe000
low ram: 00000000 - 377fe000
bootmap 00008000 - 0000ef00
(8 early reservations) ==> bootmem [0000000000 - 00377fe000]
#0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000]
#1 [0000001000 - 0000002000] EX TRAMPOLINE ==> [0000001000 - 0000002000]
#2 [0000006000 - 0000007000] TRAMPOLINE ==> [0000006000 - 0000007000]
#3 [0000100000 - 0000705d54] TEXT DATA BSS ==> [0000100000 - 0000705d54]
#4 [0000706000 - 0000709000] INIT_PG_TABLE ==> [0000706000 - 0000709000]
#5 [0000099c00 - 0000100000] BIOS reserved ==> [0000099c00 - 0000100000]
#6 [0000007000 - 0000008000] PGTABLE ==> [0000007000 - 0000008000]
#7 [0000008000 - 000000f000] BOOTMAP ==> [0000008000 - 000000f000]
found SMP MP-table at [c00f3e30] 000f3e30
Zone PFN ranges:
DMA 0x00000000 -> 0x00001000
Normal 0x00001000 -> 0x000377fe
HighMem 0x000377fe -> 0x0007f590
Movable zone start PFN for each node
early_node_map[2] active PFN ranges
0: 0x00000000 -> 0x00000099
0: 0x00000100 -> 0x0007f590
On node 0 totalpages: 521513
free_area_init_node: node 0, pgdat c06264c0, node_mem_map c1000000
DMA zone: 32 pages used for memmap
DMA zone: 0 pages reserved
DMA zone: 3961 pages, LIFO batch:0
Normal zone: 1744 pages used for memmap
Normal zone: 221486 pages, LIFO batch:31
HighMem zone: 2300 pages used for memmap
HighMem zone: 291990 pages, LIFO batch:31
ACPI: PM-Timer IO Port: 0x408
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] disabled)
ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] disabled)
ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
ACPI: IOAPIC (id[0x04] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 4, version 32, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Enabling APIC mode: Flat. Using 1 I/O APICs
Using ACPI (MADT) for SMP configuration information
ACPI: HPET id: 0x8086a201 base: 0xfed00000
4 Processors exceeds NR_CPUS limit of 2
SMP: Allowing 2 CPUs, 0 hotplug CPUs
nr_irqs_gsi: 24
PM: Registered nosave memory: 0000000000099000 - 000000000009a000
PM: Registered nosave memory: 000000000009a000 - 00000000000a0000
PM: Registered nosave memory: 00000000000a0000 - 00000000000f0000
PM: Registered nosave memory: 00000000000f0000 - 0000000000100000
Allocating PCI resources starting at 80000000 (gap: 7f600000:60a00000)
NR_CPUS:2 nr_cpumask_bits:2 nr_cpu_ids:2 nr_node_ids:1
PERCPU: Allocating 32768 bytes of per cpu data
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 517437
Kernel command line: BOOT_IMAGE=Production ro root=805 nofirewire noexec=on noexec32=on
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 16384 bytes)
Fast TSC calibration using PIT
Detected 1596.088 MHz processor.
Console: colour VGA+ 80x60
console [tty0] enabled
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 2061788k/2086464k available (3918k kernel code, 23432k reserved, 1452k data, 320k init, 1177160k highmem)
virtual kernel memory layout:
fixmap : 0xfff9f000 - 0xfffff000 ( 384 kB)
pkmap : 0xff800000 - 0xffc00000 (4096 kB)
vmalloc : 0xf7ffe000 - 0xff7fe000 ( 120 MB)
lowmem : 0xc0000000 - 0xf77fe000 ( 887 MB)
.init : 0xc0646000 - 0xc0696000 ( 320 kB)
.data : 0xc04d389b - 0xc063ec08 (1452 kB)
.text : 0xc0100000 - 0xc04d389b (3918 kB)
Checking if this processor honours the WP bit even in supervisor mode...Ok.
hpet clockevent registered
HPET: 4 timers in total, 0 timers will be used for per-cpu timer
Calibrating delay loop (skipped), value calculated using timer frequency.. 3192.17 BogoMIPS (lpj=6384352)
Mount-cache hash table entries: 512
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 1024K
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
using mwait in idle threads.
Checking 'hlt' instruction... OK.
ACPI: Core revision 20081204
..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
CPU0: Genuine Intel(R) CPU 2140 @ 1.60GHz stepping 02
Booting processor 1 APIC 0x1 ip 0x6000
Initializing CPU#1
Calibrating delay using timer specific routine.. 3192.00 BogoMIPS (lpj=6384018)
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 1024K
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 1
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#1.
CPU1: Genuine Intel(R) CPU 2140 @ 1.60GHz stepping 02
checking TSC synchronization [CPU#0 -> CPU#1]: passed.
Brought up 2 CPUs
Total of 2 processors activated (6384.18 BogoMIPS).
net_namespace: 504 bytes
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 255
PCI: MCFG area at e0000000 reserved in E820
PCI: Using MMCONFIG for extended config space
PCI: Using configuration type 1 for base access
mtrr: your CPUs had inconsistent fixed MTRR settings
mtrr: probably your BIOS does not setup all CPUs.
mtrr: corrected configuration.
bio: create slab <bio-0> at 0
ACPI: EC: Look up EC in DSDT
ACPI: Interpreter enabled
ACPI: (supports S0 S4 S5)
ACPI: Using IOAPIC for interrupt routing
ACPI: No dock devices found.
ACPI: PCI Root Bridge [PCI0] (0000:00)
pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
pci 0000:00:01.0: PME# disabled
pci 0000:00:02.0: reg 10 32bit mmio: [0xfdf00000-0xfdf7ffff]
pci 0000:00:02.0: reg 14 io port: [0xff00-0xff07]
pci 0000:00:02.0: reg 18 32bit mmio: [0xc0000000-0xcfffffff]
pci 0000:00:02.0: reg 1c 32bit mmio: [0xfdd00000-0xfddfffff]
pci 0000:00:19.0: reg 10 32bit mmio: [0xfdfc0000-0xfdfdffff]
pci 0000:00:19.0: reg 14 32bit mmio: [0xfdfff000-0xfdffffff]
pci 0000:00:19.0: reg 18 io port: [0xfe00-0xfe1f]
pci 0000:00:19.0: PME# supported from D0 D3hot D3cold
pci 0000:00:19.0: PME# disabled
pci 0000:00:1a.0: reg 20 io port: [0xfd00-0xfd1f]
pci 0000:00:1a.1: reg 20 io port: [0xfc00-0xfc1f]
pci 0000:00:1a.2: reg 20 io port: [0xfb00-0xfb1f]
pci 0000:00:1a.7: reg 10 32bit mmio: [0xfdffe000-0xfdffe3ff]
pci 0000:00:1a.7: PME# supported from D0 D3hot D3cold
pci 0000:00:1a.7: PME# disabled
pci 0000:00:1b.0: reg 10 64bit mmio: [0xfdff4000-0xfdff7fff]
pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
pci 0000:00:1b.0: PME# disabled
pci 0000:00:1d.0: reg 20 io port: [0xfa00-0xfa1f]
pci 0000:00:1d.1: reg 20 io port: [0xf900-0xf91f]
pci 0000:00:1d.2: reg 20 io port: [0xf800-0xf81f]
pci 0000:00:1d.7: reg 10 32bit mmio: [0xfdffd000-0xfdffd3ff]
pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
pci 0000:00:1d.7: PME# disabled
pci 0000:00:1f.0: quirk: region 0400-047f claimed by ICH6 ACPI/GPIO/TCO
pci 0000:00:1f.0: quirk: region 0480-04bf claimed by ICH6 GPIO
pci 0000:00:1f.0: ICH7 LPC Generic IO decode 1 PIO at 0800 (mask 003f)
pci 0000:00:1f.0: ICH7 LPC Generic IO decode 2 PIO at 0290 (mask 003f)
pci 0000:00:1f.2: reg 10 io port: [0xf700-0xf707]
pci 0000:00:1f.2: reg 14 io port: [0xf600-0xf603]
pci 0000:00:1f.2: reg 18 io port: [0xf500-0xf507]
pci 0000:00:1f.2: reg 1c io port: [0xf400-0xf403]
pci 0000:00:1f.2: reg 20 io port: [0xf300-0xf31f]
pci 0000:00:1f.2: reg 24 32bit mmio: [0xfdffc000-0xfdffc7ff]
pci 0000:00:1f.2: PME# supported from D3hot
pci 0000:00:1f.2: PME# disabled
pci 0000:00:1f.3: reg 10 64bit mmio: [0xfdffb000-0xfdffb0ff]
pci 0000:00:1f.3: reg 20 io port: [0x500-0x51f]
pci 0000:00:01.0: bridge io port: [0xd000-0xdfff]
pci 0000:00:01.0: bridge 32bit mmio: [0xfdb00000-0xfdbfffff]
pci 0000:00:01.0: bridge 64bit mmio pref: [0xfdc00000-0xfdcfffff]
pci 0000:02:00.0: reg 10 32bit mmio: [0xd0000000-0xdfffffff]
pci 0000:02:00.0: reg 14 io port: [0xcc00-0xccff]
pci 0000:02:00.0: reg 18 32bit mmio: [0xfdef0000-0xfdefffff]
pci 0000:02:00.0: reg 30 32bit mmio: [0x000000-0x01ffff]
pci 0000:02:00.0: supports D1 D2
pci 0000:02:01.0: reg 10 io port: [0xcf00-0xcf07]
pci 0000:02:01.0: supports D2
pci 0000:02:01.0: PME# supported from D0 D2 D3hot D3cold
pci 0000:02:01.0: PME# disabled
pci 0000:00:1e.0: transparent bridge
pci 0000:00:1e.0: bridge io port: [0xc000-0xcfff]
pci 0000:00:1e.0: bridge 32bit mmio: [0xfde00000-0xfdefffff]
pci 0000:00:1e.0: bridge 64bit mmio pref: [0xd0000000-0xdfffffff]
pci_bus 0000:00: on NUMA node 0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.HUB0._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs *3 4 5 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 7 9 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 7 9 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 7 9 *10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 *5 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNK0] (IRQs 3 *4 5 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 5 7 *9 10 11 12 14 15)
SCSI subsystem initialized
libata version 3.00 loaded.
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
PCI: Using ACPI for IRQ routing
hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0
hpet0: 4 comparators, 64-bit 14.318180 MHz counter
pnp: PnP ACPI init
ACPI: bus type pnp registered
pnp: PnP ACPI: found 12 devices
ACPI: ACPI bus type pnp unregistered
system 00:01: ioport range 0x4d0-0x4d1 has been reserved
system 00:01: ioport range 0x800-0x87f has been reserved
system 00:01: ioport range 0x290-0x297 has been reserved
system 00:01: ioport range 0x880-0x88f has been reserved
system 00:08: ioport range 0x400-0x4bf could not be reserved
system 00:0a: iomem range 0xe0000000-0xefffffff has been reserved
system 00:0b: iomem range 0xf0000-0xfffff could not be reserved
system 00:0b: iomem range 0x7f600000-0x7f6fffff has been reserved
system 00:0b: iomem range 0xfed00000-0xfed000ff has been reserved
system 00:0b: iomem range 0x7f590000-0x7f5fffff could not be reserved
system 00:0b: iomem range 0x0-0x9ffff could not be reserved
system 00:0b: iomem range 0x100000-0x7f58ffff could not be reserved
system 00:0b: iomem range 0xfec00000-0xfec00fff has been reserved
system 00:0b: iomem range 0xfed14000-0xfed1dfff has been reserved
system 00:0b: iomem range 0xfed20000-0xfed9ffff has been reserved
system 00:0b: iomem range 0xfee00000-0xfee00fff has been reserved
system 00:0b: iomem range 0xffb00000-0xffb7ffff has been reserved
system 00:0b: iomem range 0xfff00000-0xffffffff has been reserved
system 00:0b: iomem range 0xe0000-0xeffff has been reserved
pci 0000:00:01.0: PCI bridge, secondary bus 0000:01
pci 0000:00:01.0: IO window: 0xd000-0xdfff
pci 0000:00:01.0: MEM window: 0xfdb00000-0xfdbfffff
pci 0000:00:01.0: PREFETCH window: 0x000000fdc00000-0x000000fdcfffff
pci 0000:00:1e.0: PCI bridge, secondary bus 0000:02
pci 0000:00:1e.0: IO window: 0xc000-0xcfff
pci 0000:00:1e.0: MEM window: 0xfde00000-0xfdefffff
pci 0000:00:1e.0: PREFETCH window: 0x000000d0000000-0x000000dfffffff
pci 0000:00:01.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
pci 0000:00:01.0: setting latency timer to 64
pci 0000:00:1e.0: setting latency timer to 64
pci_bus 0000:00: resource 0 io: [0x00-0xffff]
pci_bus 0000:00: resource 1 mem: [0x000000-0xffffffff]
pci_bus 0000:01: resource 0 io: [0xd000-0xdfff]
pci_bus 0000:01: resource 1 mem: [0xfdb00000-0xfdbfffff]
pci_bus 0000:01: resource 2 mem: [0xfdc00000-0xfdcfffff]
pci_bus 0000:01: resource 3 mem: [0x0-0x0]
pci_bus 0000:02: resource 0 io: [0xc000-0xcfff]
pci_bus 0000:02: resource 1 mem: [0xfde00000-0xfdefffff]
pci_bus 0000:02: resource 2 mem: [0xd0000000-0xdfffffff]
pci_bus 0000:02: resource 3 io: [0x00-0xffff]
pci_bus 0000:02: resource 4 mem: [0x000000-0xffffffff]
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
NET: Registered protocol family 1
kvm: no hardware support
Machine check exception polling timer started.
microcode: no support for this CPU vendor
highmem bounce pool size: 64 pages
NTFS driver 2.1.29 [Flags: R/W].
msgmni has been set to 1729
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
pci 0000:02:00.0: Boot video device
Real Time Clock Driver v1.12b
Linux agpgart interface v0.103
Hangcheck: starting hangcheck timer 0.9.0 (tick is 180 seconds, margin is 60 seconds).
Hangcheck: Using get_cycles().
input: Power Button (FF) as /class/input/input0
ACPI: Power Button (FF) [PWRF]
input: Power Button (CM) as /class/input/input1
ACPI: Power Button (CM) [PWRB]
ACPI: SSDT 7F5E7680, 022A (r1 PmRef Cpu0Ist 3000 INTL 20041203)
processor ACPI_CPU:00: registered as cooling_device0
ACPI: SSDT 7F5E7B40, 0152 (r1 PmRef Cpu1Ist 3000 INTL 20041203)
processor ACPI_CPU:01: registered as cooling_device1
thermal LNXTHERM:01: registered as thermal_zone0
ACPI: Thermal Zone [THRM] (40 C)
[drm] Initialized drm 1.1.0 20060810
Serial: 8250/16550 driver, 5 ports, IRQ sharing disabled
serial 0000:02:01.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
0000:02:01.0: ttyS4 at I/O 0xcf00 (irq = 16) is a 16550A
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
brd: module loaded
loop: module loaded
e1000e: Intel(R) PRO/1000 Network Driver - 0.3.3.3-k6
e1000e: Copyright (c) 1999-2008 Intel Corporation.
e1000e 0000:00:19.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
e1000e 0000:00:19.0: setting latency timer to 64
e1000e 0000:00:19.0: irq 24 for MSI/MSI-X
Switched to high resolution mode on CPU 1
Switched to high resolution mode on CPU 0
0000:00:19.0: eth0: (PCI Express:2.5GB/s:Width x1) 00:1a:a0:8c:0d:b2
0000:00:19.0: eth0: Intel(R) PRO/10/100 Network Connection
0000:00:19.0: eth0: MAC: 6, PHY: 7, PBA No: ffffff-0ff
PPP generic driver version 2.4.2
PPP Deflate Compression module registered
PPP BSD Compression module registered
console [netcon0] enabled
netconsole: network logging started
Linux video capture interface: v2.00
3ware Storage Controller device driver for Linux v1.26.02.002.
Driver 'sd' needs updating - please use bus_type methods
Driver 'sr' needs updating - please use bus_type methods
ahci 0000:00:1f.2: version 3.0
ahci 0000:00:1f.2: PCI INT A -> GSI 19 (level, low) -> IRQ 19
ahci 0000:00:1f.2: irq 25 for MSI/MSI-X
ahci 0000:00:1f.2: AHCI 0001.0200 32 slots 6 ports 3 Gbps 0x3f impl RAID mode
ahci 0000:00:1f.2: flags: 64bit ncq sntf led clo pmp pio slum part ems
ahci 0000:00:1f.2: setting latency timer to 64
scsi0 : ahci
scsi1 : ahci
scsi2 : ahci
scsi3 : ahci
scsi4 : ahci
scsi5 : ahci
ata1: SATA max UDMA/133 abar m2048@0xfdffc000 port 0xfdffc100 irq 25
ata2: SATA max UDMA/133 abar m2048@0xfdffc000 port 0xfdffc180 irq 25
ata3: SATA max UDMA/133 abar m2048@0xfdffc000 port 0xfdffc200 irq 25
ata4: SATA max UDMA/133 abar m2048@0xfdffc000 port 0xfdffc280 irq 25
ata5: SATA max UDMA/133 abar m2048@0xfdffc000 port 0xfdffc300 irq 25
ata6: SATA max UDMA/133 abar m2048@0xfdffc000 port 0xfdffc380 irq 25
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata1.00: ATA-8: SAMSUNG HD501LJ, CR100-11, max UDMA7
ata1.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata1.00: configured for UDMA/133
scsi 0:0:0:0: Direct-Access ATA SAMSUNG HD501LJ CR10 PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 976773168 512-byte hardware sectors: (500 GB/465 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 0:0:0:0: [sda] 976773168 512-byte hardware sectors: (500 GB/465 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sda: sda1 < sda5 sda6 sda7 >
sd 0:0:0:0: [sda] Attached SCSI disk
sd 0:0:0:0: Attached scsi generic sg0 type 0
ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata2.00: ATAPI: HL-DT-ST CD-RW/DVD-ROM GCC-H10N, C103, max UDMA/100
ata2.00: configured for UDMA/100
scsi 1:0:0:0: CD-ROM HL-DT-ST CDRW/DVD GCCH10N C103 PQ: 0 ANSI: 5
sr0: scsi3-mmc drive: 48x/48x writer cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
sr 1:0:0:0: Attached scsi CD-ROM sr0
sr 1:0:0:0: Attached scsi generic sg1 type 5
ata3: SATA link down (SStatus 0 SControl 300)
ata4: SATA link down (SStatus 0 SControl 300)
ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata5.00: ATAPI: HL-DT-STDVD+-RW GSA-H31N, B109, max UDMA/100
ata5.00: configured for UDMA/100
scsi 4:0:0:0: CD-ROM HL-DT-ST DVD+-RW GSA-H31N B109 PQ: 0 ANSI: 5
sr1: scsi3-mmc drive: 48x/48x writer cd/rw xa/form2 cdda tray
sr 4:0:0:0: Attached scsi CD-ROM sr1
sr 4:0:0:0: Attached scsi generic sg2 type 5
ata6: SATA link down (SStatus 0 SControl 300)
Fusion MPT base driver 3.04.07
Copyright (c) 1999-2008 LSI Corporation
Fusion MPT SPI Host driver 3.04.07
ieee1394: raw1394: /dev/raw1394 device initialized
usbmon: debugfs is not available
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci_hcd 0000:00:1a.7: PCI INT C -> GSI 18 (level, low) -> IRQ 18
ehci_hcd 0000:00:1a.7: setting latency timer to 64
ehci_hcd 0000:00:1a.7: EHCI Host Controller
ehci_hcd 0000:00:1a.7: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:1a.7: debug port 1
ehci_hcd 0000:00:1a.7: cache line size of 32 is not supported
ehci_hcd 0000:00:1a.7: irq 18, io mem 0xfdffe000
ehci_hcd 0000:00:1a.7: USB 2.0 started, EHCI 1.00
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 6 ports detected
ehci_hcd 0000:00:1d.7: PCI INT A -> GSI 23 (level, low) -> IRQ 23
ehci_hcd 0000:00:1d.7: setting latency timer to 64
ehci_hcd 0000:00:1d.7: EHCI Host Controller
ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 2
ehci_hcd 0000:00:1d.7: debug port 1
ehci_hcd 0000:00:1d.7: cache line size of 32 is not supported
ehci_hcd 0000:00:1d.7: irq 23, io mem 0xfdffd000
ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 6 ports detected
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
uhci_hcd: USB Universal Host Controller Interface driver
uhci_hcd 0000:00:1a.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
uhci_hcd 0000:00:1a.0: setting latency timer to 64
uhci_hcd 0000:00:1a.0: UHCI Host Controller
uhci_hcd 0000:00:1a.0: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:1a.0: irq 16, io base 0x0000fd00
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
uhci_hcd 0000:00:1a.1: PCI INT B -> GSI 21 (level, low) -> IRQ 21
uhci_hcd 0000:00:1a.1: setting latency timer to 64
uhci_hcd 0000:00:1a.1: UHCI Host Controller
uhci_hcd 0000:00:1a.1: new USB bus registered, assigned bus number 4
uhci_hcd 0000:00:1a.1: irq 21, io base 0x0000fc00
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
uhci_hcd 0000:00:1a.2: PCI INT D -> GSI 19 (level, low) -> IRQ 19
uhci_hcd 0000:00:1a.2: setting latency timer to 64
uhci_hcd 0000:00:1a.2: UHCI Host Controller
uhci_hcd 0000:00:1a.2: new USB bus registered, assigned bus number 5
uhci_hcd 0000:00:1a.2: irq 19, io base 0x0000fb00
usb usb5: configuration #1 chosen from 1 choice
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 2 ports detected
uhci_hcd 0000:00:1d.0: PCI INT A -> GSI 23 (level, low) -> IRQ 23
uhci_hcd 0000:00:1d.0: setting latency timer to 64
uhci_hcd 0000:00:1d.0: UHCI Host Controller
uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 6
uhci_hcd 0000:00:1d.0: irq 23, io base 0x0000fa00
usb usb6: configuration #1 chosen from 1 choice
hub 6-0:1.0: USB hub found
hub 6-0:1.0: 2 ports detected
uhci_hcd 0000:00:1d.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19
uhci_hcd 0000:00:1d.1: setting latency timer to 64
uhci_hcd 0000:00:1d.1: UHCI Host Controller
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 7
uhci_hcd 0000:00:1d.1: irq 19, io base 0x0000f900
usb usb7: configuration #1 chosen from 1 choice
hub 7-0:1.0: USB hub found
hub 7-0:1.0: 2 ports detected
uhci_hcd 0000:00:1d.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
uhci_hcd 0000:00:1d.2: setting latency timer to 64
uhci_hcd 0000:00:1d.2: UHCI Host Controller
uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 8
uhci_hcd 0000:00:1d.2: irq 18, io base 0x0000f800
usb usb8: configuration #1 chosen from 1 choice
hub 8-0:1.0: USB hub found
hub 8-0:1.0: 2 ports detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
PNP: No PS/2 controller found. Probing ports directly.
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
mice: PS/2 mouse device common for all mice
cpuidle: using governor ladder
cpuidle: using governor menu
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
Advanced Linux Sound Architecture Driver Version 1.0.18a.
HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
HDA Intel 0000:00:1b.0: setting latency timer to 64
ALSA device list:
#0: HDA Intel at 0xfdff4000 irq 22
Netfilter messages via NETLINK v0.30.
nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
ip_tables: (C) 2000-2006 Netfilter Core Team
TCP cubic registered
NET: Registered protocol family 17
Using IPI No-Shortcut mode
VFS: Mounted root (ext2 filesystem) readonly on device 8:5.
Freeing unused kernel memory: 320k freed
usb 2-3: new high speed USB device using ehci_hcd and address 2
usb 2-3: configuration #1 chosen from 1 choice
scsi6 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 2
usb-storage: waiting for device to settle before scanning
usb 4-2: new low speed USB device using uhci_hcd and address 2
udev: starting version 141
udev: deprecated sysfs layout; update the kernel or disable CONFIG_SYSFS_DEPRECATED; some udev features will not work correctly
usb 4-2: configuration #1 chosen from 1 choice
input: Dell Dell USB Keyboard as /class/input/input2
generic-usb 0003:413C:2003.0001: input: USB HID v1.10 Keyboard [Dell Dell USB Keyboard] on usb-0000:00:1a.1-2/input0
usb 5-1: new low speed USB device using uhci_hcd and address 2
usb 5-1: configuration #1 chosen from 1 choice
input: Logitech USB-PS/2 Trackball as /class/input/input3
generic-usb 0003:046D:C401.0002: input: USB HID v1.00 Mouse [Logitech USB-PS/2 Trackball] on usb-0000:00:1a.2-1/input0
agpgart-intel 0000:00:00.0: Intel G33 Chipset
agpgart-intel 0000:00:00.0: detected 7164K stolen memory
agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xc0000000
pci 0000:02:00.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
pci 0000:02:00.0: setting latency timer to 64
[drm] Initialized radeon 1.29.0 20080528 on minor 0
scsi 6:0:0:0: Direct-Access Generic USB SD Reader 1.00 PQ: 0 ANSI: 0
sd 6:0:0:0: [sdb] Attached SCSI removable disk
sd 6:0:0:0: Attached scsi generic sg3 type 0
scsi 6:0:0:1: Direct-Access Generic USB CF Reader 1.01 PQ: 0 ANSI: 0
sd 6:0:0:1: [sdc] Attached SCSI removable disk
sd 6:0:0:1: Attached scsi generic sg4 type 0
scsi 6:0:0:2: Direct-Access Generic USB SM Reader 1.02 PQ: 0 ANSI: 0
sd 6:0:0:2: [sdd] Attached SCSI removable disk
sd 6:0:0:2: Attached scsi generic sg5 type 0
scsi 6:0:0:3: Direct-Access Generic USB MS Reader 1.03 PQ: 0 ANSI: 0
sd 6:0:0:3: [sde] Attached SCSI removable disk
sd 6:0:0:3: Attached scsi generic sg6 type 0
usb-storage: device scan complete
ReiserFS: sda7: found reiserfs format "3.6" with standard journal
ReiserFS: sda7: using ordered data mode
ReiserFS: sda7: journal params: device sda7, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: sda7: checking transaction log (sda7)
ReiserFS: sda7: Using r5 hash to sort names
Adding 3911788k swap on /dev/sda6. Priority:-1 extents:1 across:3911788k
e1000e 0000:00:19.0: irq 24 for MSI/MSI-X
e1000e 0000:00:19.0: irq 24 for MSI/MSI-X
e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: None
0000:00:19.0: eth0: 10/100 speed: disabling TSO
0000:00:19.0: eth0: changing MTU from 1500 to 1454
e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: None
0000:00:19.0: eth0: 10/100 speed: disabling TSO
[drm] Setting GART location based on new memory map
[drm] Loading R200 Microcode
[drm] writeback test succeeded in 2 usecs
IN= OUT=lo SRC=127.0.0.2 DST=127.0.0.2 LEN=40 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=TCP SPT=80 DPT=36255 WINDOW=0 RES=0x00 ACK RST URGP=0
IN= OUT=lo SRC=127.0.0.2 DST=127.0.0.2 LEN=40 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=TCP SPT=80 DPT=36255 WINDOW=0 RES=0x00 ACK RST URGP=0
IN= OUT=lo SRC=127.0.0.2 DST=127.0.0.2 LEN=40 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=TCP SPT=80 DPT=36255 WINDOW=0 RES=0x00 ACK RST URGP=0
IN= OUT=lo SRC=127.0.0.2 DST=127.0.0.2 LEN=40 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=TCP SPT=80 DPT=36255 WINDOW=0 RES=0x00 ACK RST URGP=0
IN= OUT=lo SRC=127.0.0.2 DST=127.0.0.2 LEN=40 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=TCP SPT=80 DPT=36255 WINDOW=0 RES=0x00 ACK RST URGP=0
[drm] Loading R200 Microcode
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [gentoo-user] Re: Is my machine too old for virtualbox?
2009-09-27 18:01 ` Walter Dnes
@ 2009-09-27 18:06 ` Volker Armin Hemmann
2009-09-27 18:09 ` Jesús Guerrero
2009-09-27 18:10 ` David Relson
2 siblings, 0 replies; 12+ messages in thread
From: Volker Armin Hemmann @ 2009-09-27 18:06 UTC (permalink / raw
To: gentoo-user
On Sonntag 27 September 2009, Walter Dnes wrote:
> On Sun, Sep 27, 2009 at 08:15:46AM -0700, walt wrote
>
> > I'm using the vbox svn repository from Sun, so I haven't tried building
> > the portage version.
>
> As I mentioned, I'm using Sun's install because the portage install
> dies.
>
> > What problem do you see?
>
> At bootup I get...
> * Starting VirtualBox kernel module ...
> * modprobe vboxdrv failed. Please use 'dmesg' to find out why
>
> I'm attaching dmesg output in the hope that someone can figure this
> out.
>
how about dmesg after you tried to load vboxdrv?
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [gentoo-user] Re: Is my machine too old for virtualbox?
2009-09-27 18:01 ` Walter Dnes
2009-09-27 18:06 ` Volker Armin Hemmann
@ 2009-09-27 18:09 ` Jesús Guerrero
2009-09-27 18:10 ` David Relson
2 siblings, 0 replies; 12+ messages in thread
From: Jesús Guerrero @ 2009-09-27 18:09 UTC (permalink / raw
To: gentoo-user
On Sun, 27 Sep 2009 14:01:02 -0400, "Walter Dnes" <waltdnes@waltdnes.org>
wrote:
> On Sun, Sep 27, 2009 at 08:15:46AM -0700, walt wrote
>
>> I'm using the vbox svn repository from Sun, so I haven't tried building
>> the portage version.
>
> As I mentioned, I'm using Sun's install because the portage install
> dies.
>
>> What problem do you see?
>
> At bootup I get...
> * Starting VirtualBox kernel module ...
> * modprobe vboxdrv failed. Please use 'dmesg' to find out why
>
> I'm attaching dmesg output in the hope that someone can figure this
> out.
The attached output doesn't seem to have anything related to vboxdrv at
all.
In any case, did you check that you are compiling the driver against the
right kernel? Look at the output of uname -r, and make sure that the
symlink /usr/src/linux points to the current kernel version, then recompile
the drivers package.
--
Jesús Guerrero
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [gentoo-user] Re: Is my machine too old for virtualbox?
2009-09-27 18:01 ` Walter Dnes
2009-09-27 18:06 ` Volker Armin Hemmann
2009-09-27 18:09 ` Jesús Guerrero
@ 2009-09-27 18:10 ` David Relson
2009-09-27 18:16 ` Volker Armin Hemmann
2 siblings, 1 reply; 12+ messages in thread
From: David Relson @ 2009-09-27 18:10 UTC (permalink / raw
To: gentoo-user; +Cc: waltdnes
On Sun, 27 Sep 2009 14:01:02 -0400
Walter Dnes wrote:
> On Sun, Sep 27, 2009 at 08:15:46AM -0700, walt wrote
>
> > I'm using the vbox svn repository from Sun, so I haven't tried
> > building the portage version.
>
> As I mentioned, I'm using Sun's install because the portage install
> dies.
>
> > What problem do you see?
>
> At bootup I get...
> * Starting VirtualBox kernel module ...
> * modprobe vboxdrv failed. Please use 'dmesg' to find out why
>
> I'm attaching dmesg output in the hope that someone can figure this
> out.
>
> --
> Walter Dnes <waltdnes@waltdnes.org>
Do you have vboxdrv in your kernel? My kernel has the module build,
as evidenced by command 'locate vboxdrv' displaying:
/lib64/modules/2.6.28-gentoo-r5-xfs/misc/vboxdrv.ko
I'm don't know which kernel option creates vboxdrv, but google surely
knows :->
HTH,
David
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [gentoo-user] Re: Is my machine too old for virtualbox?
2009-09-27 18:10 ` David Relson
@ 2009-09-27 18:16 ` Volker Armin Hemmann
0 siblings, 0 replies; 12+ messages in thread
From: Volker Armin Hemmann @ 2009-09-27 18:16 UTC (permalink / raw
To: gentoo-user
On Sonntag 27 September 2009, David Relson wrote:
> On Sun, 27 Sep 2009 14:01:02 -0400
>
> Walter Dnes wrote:
> > On Sun, Sep 27, 2009 at 08:15:46AM -0700, walt wrote
> >
> > > I'm using the vbox svn repository from Sun, so I haven't tried
> > > building the portage version.
> >
> > As I mentioned, I'm using Sun's install because the portage install
> > dies.
> >
> > > What problem do you see?
> >
> > At bootup I get...
> > * Starting VirtualBox kernel module ...
> > * modprobe vboxdrv failed. Please use 'dmesg' to find out why
> >
> > I'm attaching dmesg output in the hope that someone can figure this
> > out.
>
> Do you have vboxdrv in your kernel? My kernel has the module build,
> as evidenced by command 'locate vboxdrv' displaying:
>
> /lib64/modules/2.6.28-gentoo-r5-xfs/misc/vboxdrv.ko
>
> I'm don't know which kernel option creates vboxdrv, but google surely
> knows :->
>
> HTH,
>
> David
>
none does. You have to emerge the vbox driver.
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [gentoo-user] Is my machine too old for virtualbox?
2009-09-27 13:28 [gentoo-user] Is my machine too old for virtualbox? Walter Dnes
2009-09-27 15:15 ` [gentoo-user] " walt
@ 2009-09-27 18:51 ` Walter Dnes
2009-09-27 18:59 ` Volker Armin Hemmann
2009-09-27 19:02 ` Jesús Guerrero
2009-09-29 23:40 ` Walter Dnes
2 siblings, 2 replies; 12+ messages in thread
From: Walter Dnes @ 2009-09-27 18:51 UTC (permalink / raw
To: Gentoo Users List
On Sun, Sep 27, 2009 at 09:28:03AM -0400, Walter Dnes wrote
I apologize for wasting everybody's time. I didn't RTFM thoroughly
enough. Apparently, with the Sun install, and any time you build a new
kernel, you have to "/etc/init.d/vboxdrv setup". The result is...
[d530][root][~] /etc/init.d/vboxdrv setup
* Stopping VirtualBox kernel module ...
* [ ok ] * Recompiling VirtualBox kernel module ...
* [ ok ] * Starting VirtualBox kernel module ...
[d530][root][~]
...and on rebooting, I get...
* Starting VirtualBox kernel module ... * [ ok ]
While I'm at it, here's what I have in my .config regarding KVM. Since
I don't use KVM, can I turn off all the options here without affecting
virtualbox?
# CONFIG_CRYPTO_HW is not set
CONFIG_HAVE_KVM=y
CONFIG_HAVE_KVM_IRQCHIP=y
CONFIG_VIRTUALIZATION=y
CONFIG_KVM=y
CONFIG_KVM_INTEL=y
# CONFIG_KVM_AMD is not set
# CONFIG_KVM_TRACE is not set
# CONFIG_LGUEST is not set
# CONFIG_VIRTIO_PCI is not set
# CONFIG_VIRTIO_BALLOON is not set
# CONFIG_BINARY_PRINTF is not set
--
Walter Dnes <waltdnes@waltdnes.org>
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [gentoo-user] Is my machine too old for virtualbox?
2009-09-27 18:51 ` [gentoo-user] " Walter Dnes
@ 2009-09-27 18:59 ` Volker Armin Hemmann
2009-09-27 19:02 ` Jesús Guerrero
1 sibling, 0 replies; 12+ messages in thread
From: Volker Armin Hemmann @ 2009-09-27 18:59 UTC (permalink / raw
To: gentoo-user
On Sonntag 27 September 2009, Walter Dnes wrote:
> On Sun, Sep 27, 2009 at 09:28:03AM -0400, Walter Dnes wrote
>
> I apologize for wasting everybody's time. I didn't RTFM thoroughly
> enough. Apparently, with the Sun install, and any time you build a new
> kernel, you have to "/etc/init.d/vboxdrv setup". The result is...
>
> [d530][root][~] /etc/init.d/vboxdrv setup
> * Stopping VirtualBox kernel module ...
> * [ ok ] * Recompiling VirtualBox kernel module ...
> * [ ok ] * Starting VirtualBox kernel module ...
>
> [d530][root][~]
>
> ...and on rebooting, I get...
>
> * Starting VirtualBox kernel module ... * [ ok ]
>
> While I'm at it, here's what I have in my .config regarding KVM. Since
> I don't use KVM, can I turn off all the options here without affecting
> virtualbox?
yes
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [gentoo-user] Is my machine too old for virtualbox?
2009-09-27 18:51 ` [gentoo-user] " Walter Dnes
2009-09-27 18:59 ` Volker Armin Hemmann
@ 2009-09-27 19:02 ` Jesús Guerrero
1 sibling, 0 replies; 12+ messages in thread
From: Jesús Guerrero @ 2009-09-27 19:02 UTC (permalink / raw
To: gentoo-user
On Sun, 27 Sep 2009 14:51:45 -0400, "Walter Dnes" <waltdnes@waltdnes.org>
wrote:
> On Sun, Sep 27, 2009 at 09:28:03AM -0400, Walter Dnes wrote
>
> I apologize for wasting everybody's time. I didn't RTFM thoroughly
> enough. Apparently, with the Sun install, and any time you build a new
> kernel, you have to "/etc/init.d/vboxdrv setup". The result is...
>
> [d530][root][~] /etc/init.d/vboxdrv setup
> * Stopping VirtualBox kernel module ...
> * [ ok ] * Recompiling VirtualBox kernel module ...
> * [ ok ] * Starting VirtualBox kernel module ...
>
> [d530][root][~]
>
> ...and on rebooting, I get...
>
> * Starting VirtualBox kernel module ... * [ ok ]
>
> While I'm at it, here's what I have in my .config regarding KVM.
Since
> I don't use KVM, can I turn off all the options here without affecting
> virtualbox?
>
> # CONFIG_CRYPTO_HW is not set
> CONFIG_HAVE_KVM=y
> CONFIG_HAVE_KVM_IRQCHIP=y
> CONFIG_VIRTUALIZATION=y
> CONFIG_KVM=y
> CONFIG_KVM_INTEL=y
> # CONFIG_KVM_AMD is not set
> # CONFIG_KVM_TRACE is not set
> # CONFIG_LGUEST is not set
> # CONFIG_VIRTIO_PCI is not set
> # CONFIG_VIRTIO_BALLOON is not set
> # CONFIG_BINARY_PRINTF is not set
kvm and virtualbox are not related, you can turn those on if you don't
need kvm. Virtualbox will continue working.
--
Jesús Guerrero
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [gentoo-user] Is my machine too old for virtualbox?
2009-09-27 13:28 [gentoo-user] Is my machine too old for virtualbox? Walter Dnes
2009-09-27 15:15 ` [gentoo-user] " walt
2009-09-27 18:51 ` [gentoo-user] " Walter Dnes
@ 2009-09-29 23:40 ` Walter Dnes
2009-09-30 15:03 ` Paul Hartman
2 siblings, 1 reply; 12+ messages in thread
From: Walter Dnes @ 2009-09-29 23:40 UTC (permalink / raw
To: Gentoo Users List
OK, I got the VirtualBox software going, but I really wanted to get
OS/2 going. When I launched the VM, I got the warning...
> VT-x/AMD-V hardware acceleration has been enabled, but is not
> operational. Certain guests (e.g. OS/2 and QNX) require this feature.
> Please ensure that you have enabled VT-x/AMD-V properly in the BIOS
> of your host computer.
I ignored it and went into the OS/2 install. You will be glad to know
that Reiserfs managed to recover nicely, without any data loss, after I
totally locked up my machine <G>. When I say totally locked up, not
even the Magic SysReq Key got any response.
There doesn't seem to be anything in my Dell's BIOS setup about VT-x.
Is there any software that can probe the BIOS and enable VT-x, assuming
it exists? If not, I'm out of luck for OS/2 on this machine.
--
Walter Dnes <waltdnes@waltdnes.org>
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [gentoo-user] Is my machine too old for virtualbox?
2009-09-29 23:40 ` Walter Dnes
@ 2009-09-30 15:03 ` Paul Hartman
0 siblings, 0 replies; 12+ messages in thread
From: Paul Hartman @ 2009-09-30 15:03 UTC (permalink / raw
To: gentoo-user
[-- Attachment #1: Type: text/plain, Size: 1150 bytes --]
On Tue, Sep 29, 2009 at 6:40 PM, Walter Dnes <waltdnes@waltdnes.org> wrote:
> OK, I got the VirtualBox software going, but I really wanted to get
> OS/2 going. When I launched the VM, I got the warning...
>
> > VT-x/AMD-V hardware acceleration has been enabled, but is not
> > operational. Certain guests (e.g. OS/2 and QNX) require this feature.
> > Please ensure that you have enabled VT-x/AMD-V properly in the BIOS
> > of your host computer.
>
> I ignored it and went into the OS/2 install. You will be glad to know
> that Reiserfs managed to recover nicely, without any data loss, after I
> totally locked up my machine <G>. When I say totally locked up, not
> even the Magic SysReq Key got any response.
>
> There doesn't seem to be anything in my Dell's BIOS setup about VT-x.
> Is there any software that can probe the BIOS and enable VT-x, assuming
> it exists? If not, I'm out of luck for OS/2 on this machine.
>
Maybe check Dell's site to see if there are any BIOS updates for your model.
On my Dell Optiplex 745, there was no virtualization option in BIOS until I
upgraded to a newer revision (and it was disabled by default!).
[-- Attachment #2: Type: text/html, Size: 1494 bytes --]
^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2009-09-30 15:03 UTC | newest]
Thread overview: 12+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-09-27 13:28 [gentoo-user] Is my machine too old for virtualbox? Walter Dnes
2009-09-27 15:15 ` [gentoo-user] " walt
2009-09-27 18:01 ` Walter Dnes
2009-09-27 18:06 ` Volker Armin Hemmann
2009-09-27 18:09 ` Jesús Guerrero
2009-09-27 18:10 ` David Relson
2009-09-27 18:16 ` Volker Armin Hemmann
2009-09-27 18:51 ` [gentoo-user] " Walter Dnes
2009-09-27 18:59 ` Volker Armin Hemmann
2009-09-27 19:02 ` Jesús Guerrero
2009-09-29 23:40 ` Walter Dnes
2009-09-30 15:03 ` Paul Hartman
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox