similar to: qemu-kvm

Hi there, I have used qemu to install FreeBSD 9.2 release, and i can boot it fine with: $ qemu-system-x86_64 -hda images/FreeBSD-9.2-RELEASE-amd64.img I then made virsh aware of my brand new VM (see attached XML), but when i run it via virsh, It hangs after the bootloader whith this message: Booting... CPU doesn't support long mode From the log, here is the generated qemu command:

On Thu, Nov 14, 2013 at 12:48:51PM +1300, Christian Gagneraud wrote: > On 14/11/13 10:53, Christian Gagneraud wrote: > >Hi there, > > > >I have used qemu to install FreeBSD 9.2 release, and i can boot it fine > >with: > >$ qemu-system-x86_64 -hda images/FreeBSD-9.2-RELEASE-amd64.img > > > >I then made virsh aware of my brand new VM (see attached XML),

Dear list, I have moved my HVMs from xen to kvm and it worked well except some problems using virsh. First, one OpenSolaris HVM does boot with warnings: WARNING: /pci at 0,0/pci1af4,1100 at 1,2 (uhci1): No SOF interrupts have been received, this USB UHCI host controller is unusable* *The corresponding process: /usr/bin/qemu-system-x86_64 -S -M pc-0.12 -enable-kvm -m 1024 -smp

On Tue, Feb 18, 2014 at 09:10:58AM +0100, Martin Kletzander wrote: > On Mon, Feb 17, 2014 at 05:01:05PM +0100, Niccolo Rigacci wrote: > > Hi, > > > > I'm trying to use libvirt for an armel virtual machine hosted > > into an x86_64 box. > > > > I know the command line to start qemu-system-arm directly, but I > > cannot figure a proper .xml

Hi list, I''m using Dom0 gentoo with xen 3.0.4 and xenman. I have several DomU working and it is really nice :) so all my DomUs are installed with disk images. Now i want to use an ISO to boot and install a linux system (or win). When i try to boot the DomU i dont have nothing, nothing relevant (for me) in logs and i can connect to the console. The state of the DomU is unknow. Any help

Hi: I noticed a bug in the realloc error checking code in the QEMU backend for RealTek8139. However, what''s worse is that there is no cap on the total size of the transmit buffer at all. So a guest can keep extending it until memory runs out. CP_TX_BUFFER_SIZE is already 64K. So it seems to me that we don''t need the while loop to extend the buffer at all since no transmitted

This patch does 3 things to the new device model, qemu-dm: 1) Add `vncviewer'' as an option to `qemu-dm'' to spawn a `vncviewer'' process. 2) Have the `vncviewer'' config parameter translate to the `vncviewer'' flag to `qemu-dm''. 3) Add a new config parameter, `vncconnect'', that spawns a `vncviewer'' process that looks for a

HI, I have a small problem with libvirt / qemu. I have created a guest and when I start it from the command-line the guests starts OK, but when I start the guest through libvirt with "virsh start" I get "Booting from Hard Disk... Boot failed: not a bootable disk No bootable device" This is the command-line I use to start the guest (which works) "cd /var/lib/kvm/Wilmer;

Dear all, I have question regarding GLMs: I have a discrete response variable and a continuous explaining variable. Like this: http://www.myimg.de/?img=example1db0f.jpg I want to use a GLM to investigate. I have to specify the "familiy of the distribution of the response variable" - or, maybe more precise, the "family of the distribution of the residuals of the response

Hi all, I try to understand why the network bandwidth limits are not applied to my ubuntu 16.04.2 VM (qemu-kvm driver) and I would need some insights. I create my VM network with virsh and when I issue a dumpxml on my network, I can see that bandwidth limits are set: virsh # net-dumpxml nat_limit <network> <name>nat_limit</name>

[Moving this thread over to the public mailing list] On Mon, Dec 02, 2013 at 01:17:09AM +0100, Pino Toscano wrote: > On Friday 29 November 2013 18:53:38 you wrote: > > > > I'm marking options with NONE (not used at all), or M (used in > > > > master) and/or RH7 (used in rhel-7.0). > > > > > > > > > * -nographic > > > > >

On 14/11/13 10:53, Christian Gagneraud wrote: > Hi there, > > I have used qemu to install FreeBSD 9.2 release, and i can boot it fine > with: > $ qemu-system-x86_64 -hda images/FreeBSD-9.2-RELEASE-amd64.img > > I then made virsh aware of my brand new VM (see attached XML), but when > i run it via virsh, It hangs after the bootloader whith this message: > Booting... >

Hi, When I'm trying to run qemu-kvm command on RHEL6(linux kernel 2.6.32) then I get following errors which I think related to tap devices in my setup. Any idea why is that? bash$ LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin QEMU_AUDIO_DRV=none /usr/libexec/qemu-kvm -S -M rhel6.2.0 -enable-kvm -m 512 -smp 1,sockets=1,cores=1,threads=1 -name instance-00000027 -uuid

Aha! Thank you. Yes that does prevent the default stdio console . But no output appears on the input pipe, and outputting to input end has no effect: In one terminal, I do: $ cat /tmp/el6x32.out in the main terminal, I run: $ /usr/libexec/qemu-kvm -M rhel6.4.0 -cpu n270 -smp 1 -hda /home/rpmbuild/OEL6/img/OEL6_32.img -kernel /home/rpmbuild/OEL6/boot/vmlinuz-2.6.39-400.215.14.el6uek.i686 -initrd

On Tue, Feb 18, 2014 at 09:33:01AM +0100, Martin Kletzander wrote: > > > > > Wahtever I do in libvirt, I get this paramter added: > > > > > > -device isa-serial > > > > > > > and this is new-style for x86 qemu, however, arm-based qemu haven't > > adopted this option yet. > > > > To be a bit more precise, only *some*

Please can anyone enlighten me as to why linux qemu-kvm always creates the console on my terminal, when I am trying to direct all of its input and output to a pipe ? I have created : $ mkfifo /tmp/el6x32{.in,.out,.monitor} and use the command: $ /usr/libexec/qemu-kvm -M rhel6.4.0 -cpu n270 -smp 1 \ -hda /home/rpmbuild/OEL6/img/OEL6_32.img \ -kernel

Hi! I'm trying to use "Marco Polo Gro?er Reiseplaner 2005/2006" with Wine 0.9.13 on Gentoo Linux. To use it, I ran travel\setup.exe from the DVD and the setup just stops, before the "real thing" starts. Please see http://www.myimg.de/?img=BildschirmfotoWinedesktopSeaa8.png In the terminal window from which I started wine, I get: alexander@blatt ~ $ wine

Hello. Thanks to the tip to use Wine 0.9.12., I now successfully installed "Marco Polo Gro?er Reiseplaner 2005/2006" on Wine 0.9.12. running on Gentoo Linux. After the installation finished, I upgraded to Wine 0.9.13. First off, the names of the streets aren't printed correctly. Please see <http://www.myimg.de/?img=WineMarcoPoloGroerReiseplaner2.png>. As you can see there,

On 02/18/2014 04:03 AM, Niccolo Rigacci wrote: > On Tue, Feb 18, 2014 at 09:33:01AM +0100, Martin Kletzander wrote: >>> >>>> Wahtever I do in libvirt, I get this paramter added: >>>> >>>> -device isa-serial >>>> >>> >>> and this is new-style for x86 qemu, however, arm-based qemu haven't >>> adopted this

Hi all, the patch "qemu-vnc-wmvi.patch" adds support for the WMVi pseudoencoding in qemu vnc server. If the client implements it, it is supposed to be able to change colour depth when receiving a WMVi message. Since I didn''t know any client that supports it and I wanted to test the implementation before submitting any patch I also modified vncviewer to support WMVi. The