Tag Info

Hot answers tagged

10

qemu-kvm -hdb <device>, where <device> is the USB stick (e.g. /dev/sdb), should do it (tested with Ubuntu 12.04 on an USB stick and it works). You will need write permission to the device (i.e. be root or change its permissions).


8

From qemu's help: Linux/Multiboot boot specific: -kernel bzImage use 'bzImage' as kernel image -append cmdline use 'cmdline' as kernel command line -initrd file use 'file' as initial ram disk -dtb file use 'file' as device tree image A quick test here using Arch's kernel/initrd (qemu -kernel /boot/vmlinuz-linux -initrd /boot/initramfs-linux.img) ...


8

QEMU's -kernel, -boot, and -initrd are BIOS only. They are completely incompatible with EFI (currently). Update: OVMF supports -boot since r13683, and supports -kernel -append -initrd since r13923. Download OVMF-0.1+r14071-1.1.x86_64.rpm or newer version. Extract bios.bin from the rpm: rpm2cpio OVMF-0.1+r14071-1.1.x86_64.rpm | cpio -idmv Specify firmware ...


7

You cannot chroot into different architecture. By chrooting, you are executing the binaries (from the chroot) on your architecture. Executing ARM binaries on x86 (and x86_64 in that matter) would lead to "Exec format error". If you want to run binaries from different architecture you will need an Emulation, Qemu is a good candidate for this, but you will ...


7

It did work out. The kernel booted fine. The error is: Unable to mount root fs on unknown-block(0.0) The kernel is looking for a root filesystem. You need to provide one. You can't interact with a kernel without running processes on it, and the initial process has to be loaded from somewhere: when the kernel starts, it mounts a filesystem (the root ...


6

I don't know why exactly, but Renan's answer didn't quite work for me. KVM said to me it couldn't find a bootable drive (despite the usb partition being marked as such). However I've found another solution. Get the USB device VendorID:ProductID with lsusb. Example: $ lsusb ... Bus 002 Device 007: ID 0781:5406 SanDisk Corp. Cruzer Micro U3 Pass that to ...


6

As it happens, it looks like a bug in debian's package of grub. The -kernel grub.img approach works if I only include the grub modules I need upon grub-mkimage. The -bios grub.bin works with the newer grub package from experimental (2.00-7). However, the grub.bin that comes with it is not very useful. It comes with a memdisk that comes with the grub.cfg. ...


6

KVM is a kernel API for virtualisation. It doesn't deal with serial ports. qemu is a machine (PC and other) emulator which can use kvm for improving virtualisation performance. It can emulate a standard 8250 UART serial port (isa-serial) or paravirtualised serial port (virtio-serial). In qemu, you define your machine with command-line arguments that specify ...


5

Seems my question is answered in the libvirt manual. One needs to specifically ensure that the same IP is handed out via DHCP each time. Here's how this can be specified: <network> … <ip address="192.0.2.1" netmask="255.255.255.0"> <dhcp> <range start="192.0.2.128" end="192.0.2.254"> <host ...


5

Copy kvm virtual machines is not complicated: First, you need to shutdown the virtual machine, then you need to find the disk image where the virtual machine is stored and finally copy it to another place (cp /path/to/disk_image /new_path/). If the virtual machine is stored on its own partition, use dd if=/dev/PARTITION of=/path/to/backup/backup.img bs=1M ...


5

Afaik, libvirt doesn't know what "fully booted" means (neither do I). You could make a service that connect to your host (or another machine) during boot. Or you could try connecting in a loop to your guest, for example with ssh. Another solution would be to rely on an exisiting service that communicate with the host, such as vdagent. You could easily write ...


5

The kernel is telling you, that it doesn't know which device holds the root file system. Your loop mount isn't necessary. (Unmount it before continuing). Try a command like qemu -kernel bzImage -hda disk.img -append root=/dev/sda The -hda disk.img parameter tells qemu to simulate a disk device based on your disk.img. The -append root=/dev/sda switch is ...


5

You can do that in the console with virsh domif-setlink domain interface-device state and check it with virsh domifstat domain interface-device Have a look at the man page for details.


4

Not sure what more you can do; according to http://www.claunia.com/qemu/objectManager.php?sClass=version&iId=305 AIX 6.1 will not install under QEMU.


3

QEMU comes with the qemu-img program to convert between image formats. qemu-img convert -f qcow2 -O raw my-qcow2.img /dev/sdb


3

There's no need to background the application with the ampersand when it has a built-in option for doing so. Such is the case with qemu (unless you've removed it): % qemu-kvm --help | grep daemon -daemonize daemonize QEMU after initializing


3

virt-install ... --disk [path to your existing image] --import ... --import Skip the OS installation process, and build a guest around an existing disk image. The device used for booting is the first device specified via "--disk" or "--file". --disk [path] path - A path to some storage media to use, existing or not. Existing media can be a file or block ...


3

That usually indicates that you don't have a bootable hard disk or CD/DVD image attached. Check your virtual machine's configuration and make sure you have a bootable ISO for a LiveCD or installer mounted. That message could also indicate that you're attempting to boot a 64-bit operating system in a 32-bit virtualized environment. Make sure your VM is ...


3

I think the problem is that you should not copy qemu-arm but qemu-arm-static. This is a static compiled executable able to run from inside the chroot without any libraries. You can also look in /proc/sys/fs/binfmt_misc if there exists a file qemu-arm. If not restart the service binfmt_support.


3

I don't think you would have to start debugging the kernel right away. This error message means that the kernel is unable to mount the partition you requested to be /. This would happen for example if you gave it an empty disk image (my hunch is this is your case) - the kernel in the VM sees an unpartitioned drive, there is no /dev/sda1 just /dev/sda. To ...


3

Qemu runs on top of a host operating system. A bootloader such as Grub doesn't provide enough services for Qemu. Qemu runs as an ordinary process inside the host, it needs the host kernel to perform memory management, to access filesystems, etc. If you meant to run an OS compiled for a different processor architecture, that won't work. The virtual machine ...


3

From QEMU wiki, QEMU doesn't support ICMP on the SLIRP backend. User Networking (SLIRP) This is the default networking backend and generally is the easiest to use. It does not require root / Administrator privileges. It has the following limitations: there is a lot of overhead so the performance is poor ICMP traffic does not work (so you ...


3

Keyboard method You can release focus using the Left Ctrl+ Left Alt. Notice you have to use the left keys! Focus free method See my question I posted on this exact thing on ServerFault. The Q&A is titled: Any way to release focus on a KVM guest in virt-manager without having to click Ctrl_L + Alt_L?. This will allow you to no longer have to use the ...


3

I think that the error does not come from the -net statement, but from: -chardev socket,host=localhost,port=7777,server,nowait,id=port1-char The statement uses already the port 7777. For the port forwarding, with -net user,hostfwd=tcp::7777-:8001 it works fine when not setting up the virtio serial channel. If I understand right, you want to set up a ...


3

Instead of using an image file (or in addition to an image file) you can use a block device (LVM or loop device) and pass this to the VM (which sees it as disk drive). You can mount it from the guest and from the host. But you should make sure this is not done simultaneously. The obvious disadvantage: This volume does not grow with the need. But you can ...


3

The direct answer to your question is grep -f /path/to/runlist /path/to/file.xml But I think this is an XY question: without thinking about how to solve the question, what are you trying to do? Given that runlist is a file containing xml filenames, I'd use an xml processing tool (like xmlstarlet) to extract the vcpu: $ cat runlist sample1.xml ...


2

I found the answer here: http://www.pantz.org/software/ssh/badwindowerrorwithqemu.html. Use the -Y option with ssh instead of -X, to enable trusted X11 forwarding.


2

Qemu is not the right tool for the job. Qemu emulates a whole computer, including the CPU. This is useful to run a virtual machine on where the virtual hardware is different from the host hardware, but this is not required here. Furthermore, emulating an amd64 CPU is likely to be slower than emulating an i386 CPU. This alone might explain the difference ...


2

Painfully slow might be in relation to your I/O. I came to find out the hard way that this might be remedied by telling libvirt to use the virtio. To verify mine: # virsh list Id Name State ---------------------------------- 11 ca running 13 new_box running ..... # virsh dumpxml ca|awk ...



Only top voted, non community-wiki answers of a minimum length are eligible