similar to: qemu-attach fails

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),

Hi all, I have a qemu-system-arm machine that I am currently starting using: qemu-system-arm -M versatilepb -nographic \ -hda img.qcow2 \ -net vde,vlan=0,sock=/var/run/qemu-vde.ctl \ -net nic,vlan=0,macaddr=52:54:00:12:34:22 \ -kernel vmlinuz-2.6.18-6-versatile \ -initrd initrd.img-2.6.18-6-versatile \ -append "root=/dev/sda1

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

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

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

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 Sat, Jun 03, 2017 at 09:22:58AM -0400, Michael C Cambria wrote: > > >On 06/02/2017 09:53 AM, Michael C. Cambria wrote: >> >> >> On 06/02/2017 09:43 AM, Martin Kletzander wrote: >>> [adding back the ML, you probably hit reply instead of reply-all, this >>> way other people might help if they know more] >>> >>> On Fri, Jun 02, 2017 at

Hi, i want to port an open-source project to sparc. I just downloaded OpenSolaris (sol-nv-b75-sparc-...iso), created an empty image for the hard disk, and tried to start qemu in a linux x64bit-host: qemu-system-sparc -hda test.img -cdrom sol-nv-b75-sparc-v1.iso -boot d -nographic The output says: Nvram id QEMU_BIOS, version 1 CPUs: 1 nvram error detected, zapping pram Welcome to OpenBIOS

On Sun, Jun 04, 2017 at 06:42:39PM -0400, Michael C Cambria wrote: >I've upgraded from Fedora 20; probably missed a merge of rpmnew with >existing .conf; permission problem, some other mistake along the way to >Fedora 25. > Yeah, probably some 'rpm -qV' (or whatever the command to verify all packages is) could help as well. >Is there a "how to" similar to [1]

On Sat, Jun 03, 2017 at 08:27:08PM -0400, Michael C Cambria wrote: > > >On 06/03/2017 05:47 PM, Martin Kletzander wrote: >> On Sat, Jun 03, 2017 at 05:20:47PM -0400, Michael C Cambria wrote: >>> I also tried stopping libvirtd, renaming both qemu-system-i386 and >>> qemu-system-x86_64, start libvirtd. Things get further along; dnsmasq >>> log messages show

On Mon, Jun 05, 2017 at 07:52:58PM -0400, Michael C Cambria wrote: > > >On 06/05/2017 10:46 AM, Martin Kletzander wrote: >> On Sun, Jun 04, 2017 at 06:42:39PM -0400, Michael C Cambria wrote: >>> I've upgraded from Fedora 20; probably missed a merge of rpmnew with >>> existing .conf; permission problem, some other mistake along the way to >>> Fedora 25.

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*

On Sat, Jun 03, 2017 at 05:20:47PM -0400, Michael C Cambria wrote: >I also tried stopping libvirtd, renaming both qemu-system-i386 and >qemu-system-x86_64, start libvirtd. Things get further along; dnsmasq >log messages show up. > >$ sudo systemctl status libvirtd.service >● libvirtd.service - Virtualization daemon > Loaded: loaded

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

Hello everyone I come back to ask for a hand to solve a problem that has affected me since October 2016 and I have not yet solved using libvirt. I thought I would solve it by going to a 4.9.x kernel with qemu 2.8.1.1 and with libvirt 3.2.0. Compile it all in a stable LFS environment version 7.9 and that all checks pass without errors. The strange thing is that the libvirtd process starts without

Hi, a small update on this. We have migrated the virtualized host to use the virtio drivers and now the drive performance is improved so that we can see a constant transfer rate. Before it used to be the same rate but regularly dropped to a few bytes/sec for a few seconds and then was fast again. However we still observe that the following fails regularily: $ virsh snapshot-create-as --domain

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 Guys, Now I am using Xen-4.0.0. I need to attach CDROM from ISO files to vitual machines when they are running. The VMs contain RHEL4.6, Windows Server 2003 32bit and Windows Server 2006 64bit. The disk configuration of the VMs is: disk = [ ''tap:vhd:/guest/SS_test/vhd/hmi-100130.vhd,hda,w''] (1) When I attach a CDROM to RHEL4.6 VM with the command: virsh

Hi Guys, Now I am using Xen-4.0.0. I need to attach CDROM from ISO files to vitual machines when they are running. The VMs contain RHEL4.6, Windows Server 2003 32bit and Windows Server 2006 64bit. The disk configuration of the VMs is: disk = [ ''tap:vhd:/guest/SS_test/vhd/hmi-100130.vhd,hda,w''] (1) When I attach a CDROM to RHEL4.6 VM with the command: virsh