Ubuntu :: Does Qemu-KVM Not Support Qcow2 Encryption?
Feb 28, 2010
I just tried to create a qemu qcow2 image with encryption:
Code:
qemu-img create -e -f qcow2 foo.qcow2 100G
Formatting 'foo.qcow2', fmt=qcow2 size=107374182400 encryption=on cluster_size=0
It's some time ago I played with qemu, but I think it's supposed to ask for a password.
If I start the image with
Code:
qemu foo.qcow2
it just says 'QEMU [Stopped]' in the popup terminal window. It starts normally without the encryption option on qemu-img.
Is encryption known to be broken? Is this perhaps specific to qemu with KVM patch or to the 64-bit version?
Ubuntu 9.10
qemu-kvm 0.11.0-0ubuntu6.3
Linux wallace 2.6.31-19-generic #56-Ubuntu SMP Thu Jan 28 02:39:34 UTC 2010 x86_64 GNU/Linux
Does anyone know any software for whole system drive encryption for Linux, I used to use truecrypt for windows, but truecrypt doesnt support system/OS partition/drive encryption....
When I try this yum install kvm qemu libvirt python-virtinst qemu-kvm I become this error
Transaction Check Error: file /usr/share/man/man1/qemu-img.1.gz from install of qemu-img-0.10.5-1.el5.2.x86_64 conflicts with file from package kvm-qemu-img-83-164.el5_5.25.x86_64
When I run the following GET commad: ./snmpget -m ALL -M /data/net/naamab/snmp/snmp_mib/ -v 3 -a MD5 -l authPriv -u test1 -A welcome1 -x DES -X privpass 127.0.0.1 NOVELSAT-MODULATOR-MIB::nsModLineCMMode.0 -d
I get the error: Encryption support not enabled. snmpget: USM encryption error
I have defined a user (and user, view and access) that should work with encryption: snmpd.conf: createUser test1 MD5 welcome1 DES privpass group debugGroup usm test1 view debugView included .1 access debugGroup "" usm priv exact debugView debugView none
General details: I am using net-snmp on linux embedded version 5.5 Configuration (part of it): ./configure --target=mips64-octeon-linux-gnu --build=mips64-octeon-linux-gnu --host=i686-pc-linux-gnu
I would love to be able to use TrueCrypt consistently across all my machines, be they Windows or Linux. As it stands, I can do full-disk encryption with pre-boot authentication only on Windows.
I don't really understand why this is. Are there technical challenges specific to Linux/Mac that make full disk encryption harder? Does anyone know whether TrueCrypt will support this in the near future.
PS. yes, I'm aware that there are other options. My goal is to simplify my life here and use the one tool across all machines.
Has anyone actually gotten this to work on Fedora 12? I ran the convert and have tried every single option imaginable to qemu-kvm to get it to boot the image but no luck. I get the "A disk read error occurred" message every time it goes to boot. Also tried booting the vmdk directly (same error), running windows recovery and running fixboot and fixmbr (same error), etc.I've spent most of the day on this off and on and feel like I'm running out of options. Are there some debugging tools I can use to give me some more direction?
I have a large qcow2 formatted disk image, which I use as storage. Often I need to move data to and from this disk image. I mount the disk using the qemu-nbd tool as follows:
modprobe nbd max_part=63 qemu-nbd -c /dev/nbd0 /host/disk100G.img mount /dev/nbd0p1 /home/rup/disk
But disk access fails every now and then in the midst of some I/O operation with an "Input/output error". At that point I have to manually unmount the disk and re-mount it so that I can run the program again:qemu-nbd -d /dev/nbd0umount joborkhaki/What could be the reason for this? Is there a better tool that I can use to maintain a qcow2 disk image?
I am running Red Hat Enterprise Server 6.0 I am having issues getting kerberos configured as a client to join a domain. Im getting below error message. "Failed to join domain: failed to connect to AD: KDC has no support for encryption type"
I'm trying to set up a virtual machine environment in Centos5.5. My hardware fully supports virtualization, and I'm running qemu as the hypervisor with Virtual Machine Manager as the GUI to manage and create VMs. Host hardware is a Dell PowerEdge T710, with a quad core Xenon processor and four 1TB disks in a raid 6 array.
Within the Virtual Machine Manager when trying to create a new VM, there is the option to not "allocate entire virtual disk now". What format is created when you "allocate entire virtual disk now" and when you don't?
I want to create a qcow2 image format, but it doesn't look like it is supported. Does anybody know how to create a VM with a qcow2 image format?
When you create a blank disk with "qemu-img create -f qcow2 disk.qcow2 3700G", it indeed does create a qcow2 image. However, Virtual Machine Manager is unable to read these images, claiming that it is 15 megs or so in size (which is what it actually occupies in host disk space until you try and put a VM into it).
when i apply this command $ make install --> that for build qemu for symbian in ubuntu i face this error -->mkdir -p "/amn/symbian/gcc/sf/adapt/oss+FCL+adapt+qemu.hg/symbian-qemu-0.9.1-12/bin" mkdir: cannot create directory `/amn': Permission denied
is there a way to write/unpack .qcow2 hard disk image directly to real hard drive in Linux?(I know it's possible to unpack .qcow2 to .raw and then dd to drive, but I'd like to skip .raw since its large)
I am building an active directory and using BIND9 as my DNS. To allow for secure dynamic updates from the domain, I am enabling GSS-TSIG as detailed here and here. Unfortunately, some of the commands and configurations used here seem to be depreciated, at least in the newer versions that I'm using. My issue is one of keytab encryption. I generated a keytab using ktpass.exe on the Windows Server 2008 domain controller. I have tried DES/MD5, AES128/SHA1 and AES256/SHA1, each have been turned down by ktutil on the kerberos server (FreeBSD). Each time, it outputs the following error: ktutil: AES256/SHA1*: encryption type AES256/SHA1* not supported *Respective to encryption used.
I cannot find a list of suitable encryption schemes that ktutil will accept. The FreeBSD handbook details a means of producing a keytab file, but I'm not sure how to configure the Domain Controller to use the keytab.
The Karmic installers for ARM CPUs are .img files that are meant to be written directly to Flash media, rather than .iso files that are meant to be burned to CD.
I'd like to run the ARM port of Karmic under the QEMU hardware emulator. This should be possible, because the .img files are sector-for-sector images of a hard disk drive. But when I try, I get a panic because the kernel can't mount the root filesystem.
I think the problem is that hard drives are provided by QEMU by emulating an IDE controller, whereas the ARM .image files are meant to be run from a USB stick. Those are accessed via SCSI rather than IDE.
Perhaps my problem is that the kernel I'm using with QEMU doesn't contain an IDE controller. It appears that QEMU doesn't provide a SCSI emulation, just IDE. An alternative would be to convert the .img installer file to a bootable CD-ROM image. Is there a way I can do that? Here is my command line:
Code: $ qemu-system-arm -M versatilepb -kernel ~/Documents/Kernels/ARM/vmlinuz-2.6.28-versatile -hda ubuntu-9.10-desktop-armel+dove.img -m 256M -append "root=/dev/sda1 rw" It doesn't work to say "root=/dev/hda1 rw" - it still can't find the root filesystem.
After patiently waiting for 30+ hours during install attempts with the "Virtual Machine Manager", I realized that it wasn't going to happen. So then I read about a possibly working version, qemu-kvm How to use this to get a VM install up and going ? For instance, this command appears to begin an install, but where does it actually create a vm image from that?
I am using DSL thru QEMU. I was able to install it to a hard drive image.I started the SSH Service but I'm not able to connect to it from my Win 7 box via putty. I've edited the hosts.allow file to ALLOW external usersI've turned on the 22 port on my win 7 box firewall.
ive been struggling with this for the past 4-5 days, and finally give up trying to solve it by myself. ive been following the guide here: [URL].. everything works up until i get to the iptables command, when i put it in, i get the following message:
Code: iptables v1.4.10: can't initialize iptables table `nat': Table does not exist (do you need to insmod?) Perhaps iptables or your kernel needs to be upgraded. this led me to believe that i did not configure my kernel correctly, so i rebuilt my kernel, building in all the modules that were listed. unfortunately, the only ones that were actually present in the make xconfig were
I installed Windows XP on my system using QEMU as a 2GB virtual drive in my home directory. I don't want to have it anymore, however I can't get rid of this 2GB used space with windows XP. I can't even delete QEMU, because the command sudo apt-get remove qemu tells me that package qemu is not installed. (however it is there, works, and is able to start Windows XP as usual).
How can I get rid of this qemu/Win XP and have 2GB of my home folder available again?
how to connect OS "ubuntu 9:10" as the host, with Qemu as a guest.?I can not connect from the host to geust, how to connect??I use Samba to connect the host to the guest.I was able to ping from guest to host, but from host to guest can not ping .. why?
I have a HP laptop which can support 1600x900. But after I install ubuntu 9.10 on it, it can only support up to 1280x700. My laptop has a Nvidia graphics card. And i am using GNOME as my desktop environment.
I am trying to convert my VirtualBox hard drives (.vdi) to VMware Workstation format (.vmdk). I found this link [URL] but cannot find the path for qemu-img. I downloaded Qemu Manager v7.0 from [URL]. Please disregard. I found it. C:Program Files (x86)QemuManagerqemuqemu-img
Qemu works normally for me, but the available resolutions do not include a widescreen option. Is there a work around or a command line parameter I can add to enable widescreen resolutions?
today I setup a USB drive to use Qemu to boot Backtrack. It was so easy my grandma could do this! My thanks goes out to anyone who worked on the Qemu project!Now, I am wondering, how hard it is to get a distro to run persistently, using Qemu. I would like to have my .bashrc, apps I install, small scripts I write, etc. saved instead of the default bootup each time.
It doesn't matter which distro it is as long as it is Debian based. I did find this thread which I will try later but it sounds almost like I need to boot from USB first... not quite sure. I was hoping I could get further insight from someone before I waist too much time working toward something that will not happen.
After I boot from a CD rom in QEMU, trying to reboot within the virtual machine (e.g. doing the "reboot" command at the root shell on Linux running inside), fails. The OS goes through the motions and the virtual machine starts to reboot. But then it cannot get to the CD the 2nd time around. The message I see in QEMU is:
Code:
Starting SeaBIOS (version pre-0.6.1-20100902_143500-palmer) Booting from CD-Rom... Boot failed: Could not read from CDROM (code 0003) No bootable device.
The qemu command I'm running is:
Code:
qemu-system-x86_64 -alt-grab -hda hda.img -cdrom cda.iso -m 1024 -boot d -net nic -net user -redir tcp:19043::22 -monitor stdio
SOLVED: not a QEMU problem at all..installers eject CD media when done and QEMU emulates this action correctly.
For some reason my QEMU guest no longer can connect to the internet. I have no idea what changed but it was working just a few days ago. I have an Ubuntu host and a debian guest. what I might be missing ?
Google says this has something to do with Intel hardware and the way it handles real mode. run it with -no-kvm, but that's not much of a fix really.. so in the mean time I reverted to using qemu-kvm-devel-88 which works well, but is pretty old.
