It was a quick copy and paste, but more or less its the same, - the dumb sudo...

zapper wrote:

sudo kvm -m (amount of memory for VM, i.e. 2048) -cdrom (name of image, i.e., gnuinos.iso) -boot d name-of.img

To start the image after install do:

sudo kvm -m (amount of memory for VM, i.e. 2048)  name-of.img

Why are you running QEMU with sudo? That's not a good idea — security for virtualised systems isn't the best and elevating the privileges will only make the situation worse.

Whoops, your right, good eye, I forgot myself that isn't a good idea.

sudo kvm -m (amount of memory for VM, i.e. 2048) -cdrom (name of image, i.e., gnuinos.iso) -boot d name-of.img

To start the image after install do:

sudo kvm -m (amount of memory for VM, i.e. 2048)  name-of.img

Why are you running QEMU with sudo? That's not a good idea — security for virtualised systems isn't the best and elevating the privileges will only make the situation worse.

I've had an issue with Aqemu in that I am not doing something correct i.e., thinking I had created an installed 'drive' when it starts in live mode again (image). However I found VirtManager (Virtual Machine Manager to give it it's full title) great at importing my VB .vhd into quemu using the qcow2 converter. It is so much nicer not to have to press the right Ctrl key to free the mouse back to the desktop - the mouse can easily move from a VM to the desktop. (I do have 2 monitors I hasten to add!)

If you want to know how to use qemu to install virtual machines, there is a thread where someone helped me with that...

https://dev1galaxy.org/viewtopic.php?pid=4128#p4128

That is how I do it...

"This is what I do:

qemu-img create -f qcow2 name-of.img 100g

In the directory where you made your image put your iso and:

sudo kvm -m (amount of memory for VM, i.e. 2048) -cdrom (name of image, i.e., gnuinos.iso) -boot d name-of.img

To start the image after install do:

sudo kvm -m (amount of memory for VM, i.e. 2048)  name-of.img

HTH"

i use this

Well done, you have pulled in the libc6 package from sid and prevented it from being subsequently upgraded. Good luck with any future vulnerabilities in that package, your system will be left wide open to them.

@all: don't try this at home.

And just for the record experimental has a pin value of 1 (one) by default so you don't need a preferences entry for that and if you did want to pin a package from ceres (which you don't) then it would only need a pin value of 500 because APT would favour the higher package version automatically.

EDIT: hold on, are you using testing? The above would apply to beowulf users.

If you can use Devuan testing, thankfully virtualbox is in Devuan Ceres. I use this :

/etc/apt/preferences.d/40sid

Package: *
Pin: release a=unstable
Pin-Priority: -1

Package: *
Pin: release a=experimental,n=experimental
Pin-Priority: -1

/etc/apt/preferences.d/90virtualbox-sid

Package: virtualbox*
Pin: release a=unstable
Pin-Priority: 900

Ron wrote:

is Virtualbox not in the repo?

No, it's so shit that the Debian developers removed it from the stable release and won't be backporting it in future.

See https://bugs.debian.org/cgi-bin/bugrepo … bug=794466 for all the gory details.

Ogis1975 wrote:

I prefer qemu-kvm

+1

Seconded...

Qemu-kvm is awesome. 

Virt-maanger, is semi okay...

But, virtualbox has been crap since... well, always really...

Especially when they made it depend on a non-free watcom compiler. 

4.1 was the only version I ever liked even a little bit.

QEMU, FTW!

apt-get install virt-manager

However, I recommend QEMU (+ KVM) with AQEMU GUI:

apt-get install aqemu

QEMU is easy-to-use solution. For example, you can add USB devices into VM out of box without limitations. QEMU also has snapshots support and you don't need to build additional kernel module for virtualization. AQEMU is awesome UI because you can get a command for running configured QEMU without GUI at all ("Show QEMU Arguments" and "Create Shell Script" in right-click menu).

If you need terminal UI you can use this: https://bitbucket.org/PascalRD/nemu/

Ogis1975 wrote:

I prefer qemu-kvm

+1

This is where I've been moving as well. Between it and LXC, virtualbox has pretty much gone by the wayside on *nix stations. Sadly still have to use VB on Windoze stations for work but it beats the licensing cost of VMware!

If you don't like GUI management tools see my fdn guide

It is exelent guide. This instruction helped me a lot!

In Synaptic, kvm is described as "QEMU Full virtualization on x86 hardware." My rig is 64 bit. Can I use kvm on it?

The x86 architecture includes both 32-bit and 64-bit versions. It is possible to run a 64-bit or 32-bit guest in a 64-bit host (but you can't run a 64-bit guest in a 32-bit host).

If you don't like GUI management tools see my fdn guide: http://forums.debian.net/viewtopic.php?f=16&t=144775