Oct 29 11:30:07 * Ohmu (n=spud@59.161.149.142) has joined #vbox
Oct 29 11:30:26 * __coredump__ has quit (Remote closed the connection)
Oct 29 11:30:26 <Lamaro> oh :)
Oct 29 11:30:28 <Ohmu> Hi all, I've just installed VirtualBox and downloaded the iso for XP. Can anyone help me thru getting a virtual XP running on my Ubuntu desktop? I'm a little stupid, but keen to learn.
Oct 29 11:31:40 <JshWright> Ohmu: just checking... I assume you have an MSDN account or something to download an XP iso?
Oct 29 11:32:33 <Teknomancer> JshWright: I think he's downloade the ISO already
Oct 29 11:32:50 <Ohmu> JshWright, I torrented it. I have the serial from my XP CD but the CD is b0rked.
Oct 29 11:33:20 <Lamaro> these days you have so many "cool" apps (once executed, the mess up os) I trust the host but if vbox has access to host (through flaws like blaster worm type) it can be little complicated for users... michael
Oct 29 11:35:04 <Ohmu> Do I need to create a partition with the ISO in it, or just a folder? And where will it put the virtual XP? Do I have to specify a partition for that? Or a folder?
Oct 29 11:35:50 <JshWright> Ohmu: create a new VM (just follow the wizard), then in the setting for that VM you can attach the iso as the VM's cd drive
Oct 29 11:36:11 <JshWright> start the VM and go through the install as normal
Oct 29 11:36:16 <Teknomancer> Ohmu: there's a user manual as well which explains these quite a bit.
Oct 29 11:36:41 <Teknomancer> Ohmu: should be installed already with VBox, if not u can download it from virtualbox.org download section
Oct 29 11:37:21 <erstazi> Ohmu: yes the user manual is a very good start... very good and loads of valuable information
Oct 29 12:00:18 <Ohmu> guys, I've followed the wizard, and when it finished, I set up all the other things like 'shared folder' in the options. But now it says my VirtualXP is 'Powered Off' and right-click-restart is greyed out. and on the right panel, 'cd/dvd rom' is 'not mounted' even tho I specifically set it to the xp.iso.... whats going on?
Oct 29 12:03:24 <JshWright> Ohmu: have you started the VM?
Oct 29 12:04:06 <Ohmu> JshWright, I don't seem able to. its greyed out.
Oct 29 12:05:06 <JshWright> try double clicking on the vm
Oct 29 12:05:37 <Ohmu> no luck. and everything but 'show log' is greyed. and the logfile doesnt exist.
Oct 29 12:07:11 <Ohmu> oh. just had to restart it.
Oct 29 12:13:42 <Ohmu> I'm getting this error: VirtualBox kernel driver not installed. The vboxdrv kernel module was either not loaded or /dev/vboxdrv was not created for some reason. Please install the virtualbox-ose-modules package for your kernel, e.g. virtualbox-ose-modules-generic.. I'm not sure to install modules-generic or modules-386 or something else ... ?
Oct 29 12:13:50 <JshWright> https://help.ubuntu.com/community/VirtualBox#USB
Oct 29 12:15:39 <fmehnert> Ohmu: You run Ubuntu? Please install the dkms package. After that, please do '/etc/init.d/vboxdrv setup' as root.
Oct 29 12:19:39 <Ohmu> fmehnert, cool. what on earth does that do? it is made by dell???
Oct 29 12:19:42 <JshWright> it'll still throw a warning when you start VBox
Oct 29 12:20:19 <fmehnert> Ohmu: The DKMS package is indeed something what Dell proposed. This package keeps track of kernel changes and will recompile kernel modules on demand.
Oct 29 12:21:40 <Ohmu> fmehnert, did you mean /etc/init.d/vboxdrv start ?
Oct 29 12:22:09 <fmehnert> I meant the dkms package. /etc/init.d/vboxdrv is part of the VirtualBox package.
Oct 29 12:22:11 <Ohmu> fmehnert, so when a new ver of the linux kernel comes out, it auto-grabs it and recompiles my kernel?
Oct 29 12:22:49 <fmehnert> Ohmu: No. If a new kernel is installed on your system, the vboxdrv module will be adapted to that new kernel.
Oct 29 12:24:57 <Ohmu> fmehnert, oh. so DKMS makes sure bvoxdrv gets recompiled whenever the kernels updated, and vboxdrv is the 'engine' that makes the linuxkernel act as the VM ...?
Oct 29 12:25:43 <fmehnert> Yes, except that vboxdrv is not the engine but only a small part of the VMM which is necessary to access some functions of the kernel to make the VMM work.
Oct 29 12:26:37 <Ohmu> so its the interface between the VMM and the kernel?
Oct 29 12:27:16 <Ohmu> (if you don't mind me 'parity checking' to make sure I understand...)
Oct 29 12:27:40 <JshWright> Ohmu: that's correct
Oct 29 12:28:40 <Ohmu> great! and it looks like /etc/init.d/vboxdrv is a daemon (everything is a daeomn in init.d??) ... so I need to start it every time I load VirtualBox?
Oct 29 12:29:08 <Ohmu> and it'll sit in the background waiting for kernel-updates.
Oct 29 12:29:12 <JshWright> it start start when you boot
Oct 29 12:29:24 <Ohmu> why doesn't VirtualBox simply check for kernel updates every time it's executed?
Oct 29 12:29:32 <Ohmu> why is a daemon needed?
Oct 29 12:29:37 <JshWright> with dkms, it does
Oct 29 12:30:04 <JshWright> it's not a "daemon", /etc/init.d/vboxdrv ensures the kernel module is loaded
Oct 29 12:30:35 <JshWright> "(12:28:49 PM) JshWright: it start start when you boot" <-- "start start"? wtf?
Oct 29 12:31:35 <fmehnert> Actually dkms is the proper abstraction to keep track of kernel upgrades on different Linux distributions.
Oct 29 12:32:41 <Ohmu> why is vboxdrv loading on boot, and not when I start VirtualBox? Isn't this inefficient?
Oct 29 12:33:11 <ggeller> Ohmu: Keep a Linux Journal handy to read while your machine boots.
Oct 29 12:33:30 <Ohmu> ggeller, :)
Oct 29 12:33:36 <Ohmu> ggeller, I have a guitar
Oct 29 12:33:53 <fmehnert> Ohmu: That's a permission problem.
Oct 29 12:34:26 <Ohmu> fmehnert, OH! only root can load kernel modules!
Oct 29 12:35:52 <Ohmu> spud@spud-laptop:/dev$ sudo /etc/init.d/vboxdrv start
Oct 29 12:35:53 <Ohmu> * Starting VirtualBox kernel module vboxdrv
Oct 29 12:35:53 <Ohmu> * No suitable module for running kernel found.
Oct 29 12:36:08 <Ohmu> (hope 3 lines is ok..)
Oct 29 12:36:20 <fmehnert> Ohmu: Please do 'setup', not 'start'
Oct 29 12:36:46 <fmehnert> (You have to do this once, dkms will do something like this on a kernel update)
Oct 29 12:36:51 <Ohmu> spud@spud-laptop:/dev$ sudo /etc/init.d/vboxdrv setup
Oct 29 12:36:52 <Ohmu> * Usage: /etc/init.d/vboxdrv {start|stop|restart|status}
Oct 29 12:36:59 <Ohmu> I got that, so I tried start instead
Oct 29 12:37:16 <fmehnert> Ohmu: Oh, in that case you have the OSE version. So you have to install the proper ose-modules.
Oct 29 12:37:39 <Ohmu> ? OSE version ?
Oct 29 12:37:44 * Ohmu heads off to package-manager
Oct 29 12:37:54 <fmehnert> Which distro is that?
Oct 29 12:38:07 <Ohmu> fmehnert, Ubuntu
Oct 29 12:38:22 <fmehnert> And what does 'dpkg -s virtualbox' say?
Oct 29 12:38:55 <Ohmu> spud@spud-laptop:/dev$ dpkg -s virtualbox
Oct 29 12:38:56 <Ohmu> Package `virtualbox' is not installed and no info is available.
Oct 29 12:39:11 <fmehnert> virtualbox-ose?
Oct 29 12:39:17 <fmehnert> And what does 'dpkg -s virtualbox-ose' say?
Oct 29 12:39:33 <Ohmu> same
Oct 29 12:39:59 <Ohmu> huh? I just *ran* virtualbox???
Oct 29 12:40:20 <fmehnert> If you run it, what does the about dialog say about the version?
Oct 29 12:40:53 <Ohmu> says its 1.56 OSE
Oct 29 12:41:18 <Ohmu> OSE == open source edition I guess
Oct 29 12:41:31 <fmehnert> Good. There you are: You have to install the proper ose modules according to your kernel.
Oct 29 12:44:39 <Ohmu> do I do i386 or generic?
Oct 29 12:45:19 <Ohmu> I get the modules *and* the guest modules?
Oct 29 12:45:31 <JshWright> no, the guest modules are for VBox guests
Oct 29 12:45:54 <Ohmu> Is my virtualXP a Vbox guest?
Oct 29 12:46:05 <JshWright> yes
Oct 29 12:46:09 <Ohmu> k
Oct 29 12:46:19 <JshWright> you need to install the virtualbox guest additions in the guest
Oct 29 12:47:34 <Ohmu> so that'll be a windows binary...
Oct 29 12:47:46 <JshWright> yes
Oct 29 12:48:44 <Ohmu> ok for mykernel ver, I've got 386,generic,openvz,rt,server,virtual. Do I need all these packages?
Oct 29 12:48:59 <JshWright> no, what's your uname -r
Oct 29 12:50:02 <Ohmu> 2.6.24-21-generic
Oct 29 12:50:07 <Ohmu> I did that already
Oct 29 12:50:12 <JshWright> then you'll need the generic ose module
Oct 29 12:50:34 <Ohmu> why not i386?
Oct 29 12:50:48 <JshWright> because you're using the generic kernel
Oct 29 12:51:02 <JshWright> the module obviously needs to match the kernel
Oct 29 12:51:06 * Ohmu slaps self with a fish
Oct 29 12:51:13 <Ohmu> ok
Oct 29 12:57:10 <Ohmu> ok got a new error...: The VirtualBox kernel driver is not accessible to the current user. Make sure that the user has write permissions for /dev/vboxdrv by adding them to the vboxusers groups. You will need to logout for the change to take effect..
Oct 29 12:57:40 <Ohmu> where's the vboxusers groups thing?
Oct 29 12:57:44 <JshWright> sudo usermod -G vboxusers -a `whoami`
Oct 29 12:57:55 <JshWright> copy and paste that command to add yourself to the vboxusers group
Oct 29 12:58:07 <JshWright> you'll need to log out and log back in for it to take effect
Oct 29 12:58:39 * lelikvb has quit (Read error: 113 (No route to host))
Oct 29 12:59:22 <Ohmu> ok. is this like .... theres different groups on my linux - and vbox has created another? I'm not aware of groups
Oct 29 12:59:39 <JshWright> currect
Oct 29 12:59:44 <JshWright> s/u/o/
Oct 29 13:00:06 * qbmaniac (n=miffe@207.248.42.1) has joined #vbox
Oct 29 13:00:49 <Ohmu> s/u/o/? superuser / user / other?
Oct 29 13:01:15 <Ohmu> how do I see all the groups?
Oct 29 13:01:41 <JshWright> heh, no... "substitute 'o' for 'u' in my last message"
Oct 29 13:01:49 <JshWright> cat /etc/group
Oct 29 13:01:54 <Ohmu> 'gropus' doesn't contain
Oct 29 13:01:57 <Ohmu> ok hehe
Oct 29 13:01:57 <Ohmu> thx
Oct 29 13:03:52 * sidmori_ (n=sidmori@75.149.75.137) has joined #vbox
Oct 29 13:04:17 * michael-vb (n=michael@nat/sun/x-721e51cd5fc2bc99) has joined #vbox
Oct 29 13:04:17 * ChanServ gives channel operator status to michael-vb
Oct 29 13:04:55 * Vsugi has quit (Read error: 104 (Connection reset by peer))
Oct 29 13:07:15 * balboah has quit ()
Oct 29 13:07:17 * Ohmu logs out
Oct 29 13:07:27 * hwilde (n=hwilde@64.58.242.11) has joined #vbox
Oct 29 13:07:30 * poetzsch_ has quit ("Leaving")
Oct 29 13:08:13 * ringo999 has quit ("leaving")
Oct 29 13:08:56 <hwilde> hello vbox
Oct 29 13:09:27 <hwilde> I have a computer with two harddrives. on hd1 there is windows vista 64bit. on hd2 there is ubuntu 8.04 64bit
Oct 29 13:09:29 * Ohmu_ (n=spud@59.161.152.133) has joined #vbox
Oct 29 13:09:40 <hwilde> what is the best/easiest/fastest way to vbox these so I can go into Ubuntu, and then virtualize Vista
Oct 29 13:10:54 * codehai (n=codehai@cable-81-173-134-244.netcologne.de) has joined #vbox
Oct 29 13:11:05 * lelikvb (n=Lelik@nat/sun/x-c7d51a05d96c8a8c) has joined #vbox
Oct 29 13:11:05 * ChanServ gives channel operator status to lelikvb
Oct 29 13:11:44 <hwilde> anybody out there ?
Oct 29 13:12:02 <Ohmu_> OMG it's working!
Oct 29 13:14:06 <Ohmu_> thankyou ppl so much for the patient guidance!
Oct 29 13:15:31 <Ohmu_> this software is mindblowing
Oct 29 13:16:02 <Ohmu_> have to go to bed now. dang. tomorrow XP!
Oct 29 13:16:05 <Ohmu_> again thanks
Oct 29 13:16:07 <Ohmu_> nn
Oct 29 13:16:19 * Ohmu_ has quit ("There is no technical problem that cannot be resolved with a sufficiently large hammer")
Oct 29 13:17:12 * michael-vb|away has quit (Read error: 110 (Connection timed out))
Oct 29 13:19:58 * ringo999 (n=ringo999@c-ce1670d5.018-2-6d6c6d10.cust.bredbandsbolaget.se) has joined #vbox
Oct 29 13:20:24 * michael-vb is now known as michael-vb|away
Oct 29 13:21:19 <ringo999> hi, using macosx host, debian guest: does seamless mode work ? X -version gives me 7.1.1, yet seamless mode is not available...Any idea?
Oct 29 13:22:40 * ron1n has quit (Read error: 104 (Connection reset by peer))
Oct 29 13:23:18 * ron1n (n=ron1n@208.253.111.18) has joined #vbox
Oct 29 13:27:11 <klaus-vb> ringo: which debian version is this? looks really old, because this is a pre-xorg version number.
Oct 29 13:27:19 <klaus-vb> +999 ;)
Oct 29 13:27:24 <ringo999> ;-)
Oct 29 13:27:27 <ringo999> debian etch 4.0
Oct 29 13:28:08 * Ohmu has quit (Read error: 110 (Connection timed out))