Hello,
which qemu version supports block copy? qemu-1.5.3 (rhel7) and 1.6.2 (F20)
seems not.
Regards,
Nerijus
Hello,
I cannot suspend Q35 VM because of:
internal error: unable to execute QEMU command 'migrate': State blocked by
non-migratable device ':00:1f.2/ich9_ahci'
I do not have any sata disks or cdroms. The only disk is virtio. I removed
sata controller from the xml file (I use libvirt), but
On Thu, 01 Sep 2016 09:46:30 +0300 Tadas wrote:
> Hello lists,
> I have strange issue while creating VM screenshots.
> virsh screenshot vmname produces ppm image. But when i try to make
> second screenshot, it produces the same image, even is VM screen has
> changed. Running screenshot on third t
On Tue, 03 Jan 2017 12:47:44 + Xi Shen wrote:
> Host: libvirt, qemu, virt-manager
> Guest: Windows 10 64 bit, almost default for all option from creating VM
> there are still 3 devices listed in the "Device Manager" that has an
> exclamation mark. They are:
>
> - HID Button over Interrupt
On Tue, 03 Jan 2017 13:53:20 + Xi Shen wrote:
> Actually, I have not selected any virtio backed devices. My network
> controller is rtlxxx, and my disk controller is SATA. So I wonder if I
> really need those virtio drivers.
No, if network and disk are not virtio, you don't need virtio drive
On Wed, 04 Jan 2017 13:38:52 + Xi Shen wrote:
> I have installed all the drivers shipped with that ISO, plus the qemu
> agent, and spice guest tool. That "HID Button over Interrupt Driver" still
> has a exclamation mark on it. So far the guest system works well. I just
> wonder what could it
On Wed, 4 Jan 2017 17:24:44 +0100 Vincenzo Romano
wrote:
> > > I have installed all the drivers shipped with that ISO, plus the qemu
> > > agent, and spice guest tool. That "HID Button over Interrupt Driver" still
> > > has a exclamation mark on it. So far the guest system works well. I just
> >
On Thu, 26 Jan 2017 10:49:42 +0100 (CET) Mikael wrote:
> The firewall itself utilizes modules which are non-open source. As such
> building your own kernel, even with the same version is not possible as the
> firewall product would cease operating.
You could try to build module for AES accele
On Thu, 26 Jan 2017 12:02:16 +0100 (CET) Mikael wrote:
> > You could try to build module for AES acceleration with the same vermagic
> > (look at the output of modinfo some_module.ko) and try to insmod it
> > without changing the running kernel.
>
> Thanks for the tip. I have considered this. As
On Mon, 6 Feb 2017 16:58:18 +0530 akhilesh rawat
wrote:
> /usr/libexec/qemu-kvm -help
> QEMU emulator version 1.5.3 (qemu-kvm-1.5.3-126.el7_3.3), Copyright (c)
> 2003-2008 Fabrice Bellard
>
> [root@centos qemu]# uname -r
> 3.10.0-514.6.1.el7.x86_64
It is a very old version. I suggest doing
yum
on Technologies
> --
> NON QVIETIS MARIBVS NAVTA PERITVS
>
>
> 2017-02-06 13:02 GMT+01:00 Nerijus Baliunas :
> > On Mon, 6 Feb 2017 16:58:18 +0530 akhilesh rawat
> > wrote:
> >
> >> /usr/libexec/qemu-kvm -help
> >> QEMU emulator version 1.5.3
Hello,
how do I use dumpdtb on ARM? It works on PPC64:
qemu-system-ppc64 -machine dumpdtb=file.dtb
it dumps device tree to a file.
qemu-system-arm -machine virt-2.9 dumpdtb=file.dtb
qemu-system-arm: -machine virt-2.9: Could not open 'dumpdtb=file.dtb': No such
file or directory
Regards,
Nerijus
On Thu, 27 Apr 2017 17:36:34 +0200 Thomas Huth wrote:
> > how do I use dumpdtb on ARM? It works on PPC64:
> > qemu-system-ppc64 -machine dumpdtb=file.dtb
> > it dumps device tree to a file.
> >
> > qemu-system-arm -machine virt-2.9 dumpdtb=file.dtb
>
> Try to use a comma here ---^
>
>
On Thu, 27 Apr 2017 18:49:43 +0300 Nerijus Baliunas
wrote:
> It worked, thanks! But the file size is 65536 and if I try to use the
> generated
> file to boot arm uefi VM (added "devicetree /boot/file.dtb" to grub.cfg), I
> get:
>
> Loading Linux 4.10.11-200.fc25.a
On Thu, 27 Apr 2017 19:22:22 +0300 Nerijus Baliunas
wrote:
> > It worked, thanks! But the file size is 65536 and if I try to use the
> > generated
> > file to boot arm uefi VM (added "devicetree /boot/file.dtb" to grub.cfg), I
> > get:
> >
&g
On Tue, 11 Jul 2017 14:19:35 -0400 Sam Varshavchik
wrote:
> Has anybody successfully installed Windows 10 on qemu 2.9
>
> I upgraded to Fedora 26 (x86_64) going from qemu 2.7 to qemu 2.9, with a
> Windows 10 guest. Booting this guest eventually resulted in a vga resolution-
> sized screen wi
On Mon, 13 Nov 2017 12:12:14 -0500 Sachith Withana wrote:
> I'm having some issues installing qemu in RHEL 7.
> Disclaimer: I'm new to QEMU.
>
> I need to get the qemu-system-x86_64 but yum install does not have the
> qemu-system packages.
> i.e: using yum install qemu-kvm does not install these
On Thu, 21 Dec 2017 17:36:52 +0100 Thomas Schmiedl
wrote:
> I try to emulate this Intel 64-bit app
> https://drive.google.com/open?id=0B-F25LE4in_xYjMwME1BODRpdFU (from
> http://xupnpd.org/) on 32-bit Intel hardware (Ubuntu 16.04.1 LTS) using
> qemu-x86_64 from git, version 2.11.50 (v2.11.0-3
On Wed, 20 Jun 2018 12:55:44 +0200 czezz wrote:
> Questions: 1. Why RHEL 7.4 keeps outdated qemu-kvm-1.5.3 which does not
> allow to do live disk snapshot/active block commit?
I don't know.
> 2. How to update qemu to the version that supports live disk snapshot/active
> block commit ? Bes
Hello,
when running virt-2.9 machine with /usr/bin/qemu-system-arm on Fedora 28,
I get this on F28 arm VM:
# dnf update
Traceback (most recent call last):
File "/usr/bin/dnf", line 57, in
from dnf.cli import main
File "/usr/lib/python3.6/site-packages/dnf/__init__.py", line 23, in
i
On Mon, 2 Jul 2018 13:36:41 +0100 Peter Maydell
wrote:
> > File "/usr/lib/python3.6/datetime.py", line 447, in __new__
> > raise OverflowError("timedelta # of days is too large: %d" % d)
> > OverflowError: timedelta # of days is too large: 10
> >
> > I found in https://github.com/C
On Mon, 2 Jul 2018 13:45:42 +0100 Peter Maydell
wrote:
> >> Could you please try this with a newer version of QEMU?
> >> (ideally, try with current head of git; we fixed some floating
> >> point emulation issues recently.)
> >
> > I have qemu-2.12.0-0.5.rc1.fc28.x86_64 from fedora-virt-preview r
On Fri, 17 Aug 2018 13:00:06 +0200 user 96710 wrote:
> Here's what I want to do: use Qemu on my Windows host while on Wi-Fi.
>
> Currently, I can only use SLIRP with Wi-Fi, but since it's quite slow I
> would like to know what other options do I have.
>
> When the PC uses Ethernet, I can bridge
On Fri, 14 Sep 2018 13:02:07 +0200 Frans de Boer wrote:
> Ever since the release of qemu 3.0, the booting of win10 under qemu 3.0
> freezes in it's initial stage. The Window is showed but there is no
> indication of any progress or error report.
>
> Below is the same qemu command is used as un
Hello,
Up until Fedora 28 I could boot my UEFI ARM VM (machine type virt-3.0) with
these packages:
# rpm -qa|grep grub
grubby-8.40-90.kraxel.fc25.armv7hl
grub2-tools-2.02-0.rc1.kraxel.1.fc25.armv7hl
grub2-efi-2.02-0.rc1.kraxel.1.fc25.armv7hl
Fedora 29 upgraded them, and now I have:
grub2-common-
On Sun, 21 Oct 2018 13:29:52 +0100 Peter Maydell
wrote:
> > Up until Fedora 28 I could boot my UEFI ARM VM (machine type virt-3.0) with
> > these packages:
> > # rpm -qa|grep grub
> > grubby-8.40-90.kraxel.fc25.armv7hl
> > grub2-tools-2.02-0.rc1.kraxel.1.fc25.armv7hl
> > grub2-efi-2.02-0.rc1.kr
On Sat, 5 Jan 2019 14:49:36 +0200 Kevin Wilson wrote:
> HI all,
> I am trying to build qemu-2.3.0 on Fedora 29 machine (X86_64) with
> gcc-8.2.1-5.
> I need this version for an existing legacy setup.
> I am getting the following error:
> /usr/bin/ld: qga/commands-posix.o: in function `dev_major
On Mon, 31 Jan 2022 15:43:56 -0800 ToddAndMargo wrote:
> Fedora 35
> qemu-kvm-6.1.0-10.fc35.x86_64
>
> Will qemu-kvm map a usb/blue tooth transceiver
> through to Windows 11?
Yes, as any other USB device.
Regards,
Nerijus
On Fri, 11 Mar 2022 14:12:24 +0100 Christian wrote:
> Quite a time ago I downloaded an iso-file of FreeDOS (1.2) and the
> installation went well.
>
> In principle FreeDOS works fine with the exception of /networking/.
https://www.freedos.org/
The new FreeDOS 1.3 is now available for download
On Sun, 10 Jul 2022 17:02:09 +0200 (CEST) Stéphane Hoc wrote:
> Is possible to create a static qcow2 image, with a fixed size on disk?
Yes.
Regards,
Nerijus
On Sun, 10 Jul 2022 21:25:32 +0200 (CEST) Stéphane Hoc wrote:
> - Mail original -
> De: "Nerijus Baliunas"
>
> > Yes.
>
> How?
man qemu-img.
Regards,
Nerijus
On Tue, 2 Jan 2024 18:47:18 +0100 Janfi wrote:
> after having reinstalled qemu/kms following a tutorial, I found an empty
> Virtual Machine Manager.
>
> How can I reinstall my VMs in the system please ?
>
> (I have a copy of the old /etc, don't know if usefull in this case)
Copy *.xml files fr
On Mon, 13 Jan 2025 15:15:58 -0800 Sayed Mohammad Badiezadegan
wrote:
> I created a disk file with QCOW2 format and then booted Qemu with
> DragonflyBSD live iso image with no problem and then I went forward to the
> installation of the DragonflyBSD on the created disk file. I also, use
> legacy
On Fri, 10 Jan 2025 00:04:06 -0500 Windows ColorFul Acc
wrote:
> Hello, I have this ISO that is ARM supported. My real machine is AMD Ryzen
> 5 with 16 GB of ram and 2 GPU's. But, I was wondering, can I run ARM VM's
> on a Ryzen 5/x86_64 architecture?
Yes, I am running arm vm using libvirt. Scr
Change Sound device Model in virt-manager.
On Wed, 20 Nov 2019 15:06:13 -0500 Jesse Palser wrote:
> Hi,
>
> Thanks for the response...
>
> How do I use "-soundhw hda" ?
> I use Virtual Machine Manager to launch my QEMU Windows 10 virtual
> machine on my Linux.
>
> Let me know, thanks!
>
> -
On Tue, 31 Dec 2019 16:23:04 +0530 Sameeran Joshi
wrote:
> ./configure
>
> ERROR: glib-2.48 gthread-2.0 is required to compile QEMU
> How do I solve this?
By installing glib devel package.
Regards,
Nerijus
On Mon, 27 Jul 2020 18:28:58 -0400 Jerry Geis wrote:
> I tried to look at the VirtIO stable and new - neither have a Windows 10
> driver under QXL.
> THey stop at windows 7. Lets me to think there is a different way to do
> this - but I dont know what that is .
Driver is in qxldod directory of
On Fri, 27 Nov 2020 09:41:52 +0100 daggs wrote:
> I have an image I've created with a bunch of chost flags which works on my
> machine when it comes to native boot.
> if I take that same image into a vm managed via libvirt, I get kernel panic.
What panic?
> I'd assume that something is missing
On Fri, 27 Nov 2020 23:17:52 + Ken Moffat via
wrote:
> > > Please provide them by text here, the link does not work. Regards, Nerijus
>
> You didn't ask the other question (details of the panic: might be
> missing driver, might be invalid opcode as far as qemu is concerned,
> might be somet
On Sat, 6 Feb 2021 15:12:31 +0200 Hugo Meyer wrote:
> Good day,
>
> The above Linux version supports iBCS (Intel biary compatibility system)
> which is required to execute the SCO binary I have to run to do development
> on a system that's been around since the early nineties. Later version do
>
40 matches
Mail list logo