[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-discuss] Starting without '-kernel'; isolating VMs

From: Nikita Karetnikov
Subject: Re: [Qemu-discuss] Starting without '-kernel'; isolating VMs
Date: Sat, 10 Aug 2013 04:16:14 +0400

> Make sure the virtual hard drive image includes a boot loader (such as
> LILO, Grub or extlinux) with appropriate setup, then with options to boot
> from "hda", the virtual machine will start running, then run the boot
> code in sector 0 of hda, and proceed from there just like a real PC.

It seems that “appropriate setup” is a side issue because I get the
following errors instead of GRUB-related ones:

Boot failed: could not read the boot disk

No bootable device.

I’ve also tried a couple of ISO images [1,2] on i686 and mips64el:

$ qemu-img create -f raw livecd.img 7G
$ qemu-system-i386 -cdrom livecd.iso -hda livecd.img -boot d

I’m able to select something like “Install” or “Try without installing.”
Then I see some kernel messages, and after that the whole thing just
hangs.  What am I doing wrong?

> - Set up tap networking as root and grant the specific user for each VM
>  access to that tap device.

Could you suggest a HOWTO?

> - Don't enable features that give the VM access to the guest file
> system.

Are they enabled by default?  How can I check?  Is there a list of such

[1] http://mirror.fsf.org/trisquel-images/trisquel-mini_6.0_i686.iso
[2] http://mirror.fsf.org/trisquel-images/trisquel-netinst_6.0_i686.iso

Attachment: pgp_KRWCrivgw.pgp
Description: PGP signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]