On Tue, 09/04 08:48, Nikola Ciprich wrote:
> Hi,
>
> I've seen this discussed few times without any real conclusion,
> so I'd like to try asking again..
>
> we're seeing very bad performance on ceph volumes mapped to qemu using
> librbd,
> while block access to krbd is multiple times better (wh
On Wed, 08/22 22:20, David Lee wrote:
> Hi, list
>
> I was trying "drive-backup" for incremental backups, and so far so
> good for individual drives.
> The question is that, when I grouped the drive-backup into a
> transaction, I got errors like:
>
> {"id":"libvirt-377183","error":{"class":"Gener
On Sun, 08/12 17:20, Michael Henriksen wrote:
> Hi All,
>
> I am seeing the following assertion when running qemu-img as part of a test
> in Travis CI:
>
> qemu-img: /builddir/build/BUILD/qemu-2.11.2/util/async.c:481: aio_co_enter:
> Assertion `self != co' failed.
What kind of test is this comma
On Tue, 07/10 08:53, Chris wrote:
> I'm getting a 15 second delay on every VM boot when using the
> ArchLinux kernel and using the virtio-scsi-pci system.
>
> QEMU emulator version 2.12.0 running on Arch Linux (4.17.4 kernel),
> booting the same.
>
> I run qemu like so:
>
> qemu-system-x86_64 \
On Thu, 05/03 10:53, lizhuoyao wrote:
> Aha！ No wonder!
> Thank you,it solved my question..But i meet another question again.
>
> the authorization of /dev/kvm: after I install qemu in making code rather
> then rpm,the authorization of /dev/kvm becomes to 600. i need to chmod 666
> /dev/kvm ever
On Thu, 05/03 08:05, lizhuoyao wrote:
> So,how can I get qemu-kvm binary exe? Actually,there are
> qemu-ga,qemu-io...but no qemu-kvm.
>
> The reason why I need the qemu-kvm is that the result of virsh with showing
> "cannot check QEMU binary /usr/libexec/qemu-kvm:no such fileor directory".And
> I
On Wed, 04/18 15:58, Fam Zheng wrote:
> On Wed, 04/18 15:42, David Lee wrote:
> > On Thu, Apr 12, 2018 at 11:57 PM, David Lee wrote:
> > >>>
> > >>> We tested qemu-kvm-ev-2.9.0-16.el7_4.14.1 - where from the source RPM we
> > >>> verified it
On Wed, 04/18 15:42, David Lee wrote:
> On Thu, Apr 12, 2018 at 11:57 PM, David Lee wrote:
> >>>
> >>> We tested qemu-kvm-ev-2.9.0-16.el7_4.14.1 - where from the source RPM we
> >>> verified it does contain ef6dada8b44e1e7c4bec5c1115903af9af415b50
> >>>
> >>> But the issue still exists. The conve
On Thu, 04/12 21:45, David Lee wrote:
> On Thu, Apr 12, 2018 at 10:16 AM, David Lee wrote:
> >> > My team caught this issue too after switching to CentOS 7.4 with qemu-img
> >> > 2.9.0
> >> > gdb shows exactly the same backtrace when the convert stuck, and we are
> >> > on
> >> > NFS.
> >> >
> >>
On Thu, 04/12 09:51, David Lee wrote:
> On Mon, Apr 9, 2018 at 3:35 AM, Benny Zlotnik wrote:
>
> > $ gdb -p 13024 -batch -ex "thread apply all bt"
> > [Thread debugging using libthread_db enabled]
> > Using host libthread_db library "/lib64/libthread_db.so.1".
> > 0x7f98275cfaff in ppoll () f
On Thu, Jan 18, 2018 at 1:51 AM, Bimal Chollera wrote:
>
>
> On Tue, Jan 9, 2018 at 7:19 PM, Fam Zheng wrote:
>>
>> On Tue, 01/09 23:18, Ala Hino wrote:
>> > qeum version:
>> > qemu-kvm-rhev-2.9.0-16.el7_4.5.x86_64
>> >
>> > On Tue, Ja
On Tue, 01/09 23:18, Ala Hino wrote:
> qeum version:
> qemu-kvm-rhev-2.9.0-16.el7_4.5.x86_64
>
> On Tue, Jan 9, 2018 at 11:10 PM, Ala Hino wrote:
>
> > Hello,
> >
> > A user is hitting the following error when performing `qemu-img commit`:
> >
> > 2018-01-03 09:48:54,168+ ERROR (tasks/5) [ro
On Sun, 12/10 17:20, mahmood n wrote:
> Hi,
> I am trying to run ContikiOS on qemu. The 3GB downloaded file contains some
> vmdk files
>
> mahmood@cluster:InstantContiki3.0$ ls -l
> total 8007536
> drwxrwxr-x 3 mahmood mahmood 4096 Aug 24 2015 caches
> -rw-rw-r-- 1 mahmood mahmood 86
On Tue, 11/21 09:53, Han Han wrote:
> On Mon, Nov 20, 2017 at 4:47 PM, Fam Zheng wrote:
>
> > On Mon, 11/20 10:58, Han Han wrote:
> > > Hello,
> > > On qemu-2.10, I find 'qemu-img info' couldn't get the info of a mirroring
> > > image:
>
On Mon, 11/20 10:58, Han Han wrote:
> Hello,
> On qemu-2.10, I find 'qemu-img info' couldn't get the info of a mirroring
> image:
> # /usr/libexec/qemu-kvm -name A -machine pc,accel=kvm \
> -vnc 0.0.0.0:1 \
> -monitor stdio \
> -qmp tcp:0:,server,nowait \
> -serial unix:/tmp/monitor,server,nowa
- Original Message -
> I create backing file with 'locking=off', but it seems the locking is
> enabled:
> On *qemu-2.10*
> # qemu-img create -b 'json:{"file": {"driver": "file", "filename":
> "/var/lib/libvirt/images/V.qcow2", "*locking*": "*off*"}}'
> /var/lib/libvirt/images/a.qcow2 -f qc
On Wed, 08/30 12:07, Vincenzo Romano wrote:
> 2017-08-30 11:58 GMT+02:00 Fam Zheng :
> > On Wed, 08/30 11:45, Vincenzo Romano wrote:
> >> 2017-08-30 11:40 GMT+02:00 Fam Zheng :
> >> > On Wed, 08/30 11:16, Vincenzo Romano wrote:
> >> >> 2017-08-30 10:53
On Wed, 08/30 11:45, Vincenzo Romano wrote:
> 2017-08-30 11:40 GMT+02:00 Fam Zheng :
> > On Wed, 08/30 11:16, Vincenzo Romano wrote:
> >> 2017-08-30 10:53 GMT+02:00 Fam Zheng :
> >> > On Wed, 08/30 08:17, Vincenzo Romano wrote:
> >> >>
On Wed, 08/30 11:16, Vincenzo Romano wrote:
> 2017-08-30 10:53 GMT+02:00 Fam Zheng :
> > On Wed, 08/30 08:17, Vincenzo Romano wrote:
> >> Il 30 ago 2017 05:19, "Fam Zheng" ha scritto:
> >>
> >> On Tue, 08/29 18:32, Vincenzo Romano wrote:
> >&g
On Wed, 08/30 08:17, Vincenzo Romano wrote:
> Il 30 ago 2017 05:19, "Fam Zheng" ha scritto:
>
> On Tue, 08/29 18:32, Vincenzo Romano wrote:
> > I'd like to move away from "another virtualization solution" to QEmu.
> > I've more or less all the
On Tue, 08/29 18:32, Vincenzo Romano wrote:
> I'd like to move away from "another virtualization solution" to QEmu.
> I've more or less all the needed bits in my hands in order to define,
> run and manage QEmu VMs.
> What I am missing is the knowledge of how to backup a live VM.
> Of course, if I s
On Mon, 08/07 10:10, Pierre Couderc wrote:
> On 08/07/2017 09:50 AM, Fam Zheng wrote:
> > On Mon, 08/07 09:37, nous wrote:
> > > I have tried qemu-img but it converts only the 1rst vmdk vmware disk...
> > > and I have 20 other ones...
> > >
> > >
On Mon, 08/07 09:37, nous wrote:
> I have tried qemu-img but it converts only the 1rst vmdk vmware disk...
> and I have 20 other ones...
>
> And did someone someday success in doing that ?
What are your vmdk files like?
The splitted VMDK images have a description file, you need to pass that to
q
On Fri, 07/21 09:44, Han Han wrote:
> Hi,
> I find a typo on http://wiki.qemu.org/ChangeLog/2.10
> In the sentence 'xres and yes', the 'yes' should be 'yres'. Please fix it.
> BTW, I'd like to know how to register on wiki.qemu.org
Hi,
I will create an account for you, and send you the login info
On Wed, 07/12 17:24, Sam wrote:
> hi all,
>
> I'm running `qemu-system-x86_64 ...` to start a guest vm. Now I want to
> stop and destroy this vm, I found there is no `qemu-stop` related command,
> so I have to `kill -9` this process.
If you have a "monitor", send "quit" command is the right way.
On Thu, 03/02 21:43, behrouz khosravi wrote:
> Hello everyone. Sorry if my question is too easy and thanks for your help.
> I have installed linux on a remote vm. I also have a script that using
> pyqt5 takes screenshots from the desktop. However when I connect to the
> machine using ssh, and try t
On Wed, 01/25 18:37, Narcis Garcia wrote:
> El 25/01/17 a les 12:53, Fam Zheng ha escrit:
> > On Wed, 01/25 12:43, Narcis Garcia wrote:
> >> El 25/01/17 a les 09:49, Alberto Garcia ha escrit:
> >>> On Mon, Jan 23, 2017 at 01:00:26AM +0100, Joe wrote:
> >
On Wed, 01/25 12:43, Narcis Garcia wrote:
> El 25/01/17 a les 09:49, Alberto Garcia ha escrit:
> > On Mon, Jan 23, 2017 at 01:00:26AM +0100, Joe wrote:
> >
> >> I'm trying Qemu (2.8.0) on Slackware GNU Linux 14.2 (64-bit) host.
> >> I've a Windows XP (guest) raw image which was working with Qemu
>
On Wed, 01/25 12:38, Vincenzo Romano wrote:
> I don't see any similarity to the console password "issue".
> While it's wise to avoid a password on a command line (you could read
> with ps), it's rather weird you cannot unplug a network cable from an
> "unstarted" VM.
> Simply, it seems this "featur
On Thu, 01/12 08:21, Kevin Wilson wrote:
> Hi,
> Following your mail I tried using "-device vfio-pci,host=04:02.0" as a
> parameter to qemu-system-x86_64 instead of , and I get:
> ...
> qemu-system-x86_64: -device vfio-pci,host=04:02.0: vfio error:
> :04:02.0: no iommu_group found: No such file
On Wed, 01/11 20:04, Kevin Wilson wrote:
> Hello,
> I have IOMMU in the kernel command line on a server which supports Virt-d:
>
> cat /proc/cmdline | grep -i iommu
> BOOT_IMAGE=...intel_iommu=on iommu=pt
>
> Now when I try to start a KVM VM with qemu-system-x86_64 without any
> PCI device assign
On Thu, 12/22 10:20, Zhenhao Zhang wrote:
> > > > *** Error in `/usr/bin/qemu-system-x86_64': double free or
> > > > corruption (out):
> > > > 0x7f83bc0cc1d0 ***
> > > > 2016-06-28 22:36:16.361+: shutting down
> > > >
> > > >not all vms have crashed and the creashed vms images incloud
On Tue, 12/20 18:29, Zhenhao Zhang wrote:
> hello everyone,
Hi Zhenhao, thanks for the report.
>
> I am sorry to trouble you. but, I meet some trouble when using qemu+kvm
> +libvirt. The qemu-system-x86_64 crash and get some errer info from logs
> :./var/log/libvirt/qemu/instance-06d3.l
On Fri, 11/11 23:11, Berillions wrote:
> Hi,
>
> When i use my Qemu's script to install Debian Sid in a VM, i use the
> NetInstall .iso.
> During the installation, the network works without problem because i
> download all packages need by the installation.
>
> At the end, the VM reboot and after
On Mon, 10/24 14:06, Christian Böhme wrote:
> However, we have also seen regular files, whose data, according to the
> filesystem, was modified weeks before the outage, but that nevertheless had
> garbled contents after the restart. Such a constellation is rather
> unexpected,
> since it is unlik
On Wed, 08/17 17:26, wyang wrote:
> On 2016年08月17日 15:50, Fam Zheng wrote:
> >
> >I am confused about the difference between the guest disk write cache and the
> >host page cache. Aren't these effectively the same (in both cases storing the
> >dirty data in the ho
On Tue, 08/16 12:39, Andrew Martin wrote:
> Hello,
>
> I am running QEMU 2.5 on Ubuntu 16.04. My guests are a mixture of Linux
> (Ubuntu
> 12.04 and newer with ext4) and Windows. The guest qcow2 images are stored in
> a
> ZFS filesystem with sync=standard (on top of a mirrored vdev of SSDs) on
On Sat, 07/30 17:59, Charls D. Chap wrote:
> Hello List,
>
> I have these 3 different call graphs, they are somehow connected in
> the Virtio-blk I/O path. Any help??
Help on what? I don't see a question to answer in your message. Please be
specific.
Fam
>
> "->" means "invokes"
>
> virtio_bl
On Wed, 07/27 15:17, Michael S. Tsirkin wrote:
> On Wed, Jul 27, 2016 at 09:34:25AM +0100, Stefan Hajnoczi wrote:
> > On Tue, Jul 26, 2016 at 06:35:30PM +, Yehuda Yitschak wrote:
> > > Thanks a lot for the detailed answer
> > >
> > > I managed to run virtio-scsi and i am benchmarking the perf
On Wed, 07/27 15:32, Patrick Dumais wrote:
>
> Hi, I'm trying to figure out where is the best place to store qemu disk
> images.
>
> I am using qcow2 format on a raid1 built from 2 7200RPM hdd.
> I am considering moving the images on a ssd (not raid). The move to ssd
> would increase performances
On Mon, 07/18 16:36, Yuxin Ren wrote:
> Thank you for your reply.
>
> the output is
> ls: cannot access /dev/kvm: No such file or directory
>
> How can I solve this problem?
modprobe kvm_intel (or kvm_amd depending on your CPU type).
Fam
On Sun, 07/10 15:39, Yan Fridland wrote:
> Hello All,
>
> Can anyone please explain what is the difference between working with
> /usr/bin/qemu-system-x86_64 and /usr/bin/kvm emulators?
Assuming you're using a modern Linux, they probably are the same thing. do
"--version" outputs of both have any
On Fri, 04/29 16:02, Nguyễn Thùy Linh wrote:
> Hello,
>
> I am working on booting a VM using qemu. My scenario: I have *n* VMs,
> first, I boot the 1st VM completely, then boot the rest VMs at the same
> time.
>
> I found out there are two ways to create a VM disk from image:
>
>1. using *qe
image and
> got the same issue
This indeed makes the application suspicious. Do you see any other errors
beside that application in question?
(A way to valiate the virtual disk is using a storage tester such as HDTune or
iometer.)
Fam
>
> On 02/23/2016 02:28 AM, Fam Zheng wrote:
> &
On Mon, 02/22 16:36, Benoit wrote:
> Thanks Fam
> No error on my guest / host
> Disk usage in Explorer is exactly what it supposed to be this is
> where it is strange...
Does your application work well on other storage types, like virtio-scsi or
ide?
Fam
>
> On 02/17/2016 0
On Tue, 02/16 20:41, Benoit wrote:
> Hi,
>
> -virtio-win-0.1.102.iso
> -host archlinux / qemu 2.4.1 / kvm
> -guest windows 7 pro x64
> -qemu-img create -f raw en_x64_windows_7_ipc2_storage_75 75G
>
> -drive
> file=/srv/qemu/vm/en_x64_windows_7_ipc2_storage_75,if=virtio,cache=none,format=raw,disc
On Mon, 02/01 01:53, Alexandre Schenberg wrote:
> Hello, I tried to convert a .vmdk file to a raw file with this
> command: "qemu-img convert -f vmdk /media/windows/WinXP-disk1.vmdk
> winxp.raw"
>
> The result was: "qemu-img: Could not open '/media/windows/WinXP-disk1.vmdk"
>
> I am sure that the
On Thu, 11/05 04:59, Ivan Volosyuk wrote:
> I cannot confirm that. There is a possibility that VM was still running
> when I created new snapshot.
That is definitely very dangerous and may be the reason why it's corrupted...
Fam
>
> On Thu, Nov 5, 2015 at 2:46 PM Fam Zheng
0
> *
> 001 0200 0380
> 0010010 0100 1c00 0100 1e80
> 0010020 0200 0a00 0200 0d80 0000
> 0010030 0300 1a00 0300 0380
>
>
> On Thu, Nov 5, 2015 at 2:08 PM Fam Zheng
.qcow2.broken",
> fix=, fmt=) at qemu-img.c:444
> #7 0x5556a53e in img_check (argc=, argv= out>) at qemu-img.c:570
> #8 0x5556559c in main (argc=3, argv=0x7fffd938) at
> qemu-img.c:3087
> --
> Regards,
> Ivan
>
> On Thu, Nov 5, 2015 at 12:29
On Thu, 11/05 01:09, Ivan Volosyuk wrote:
> Yesterday, I did a few tweaks for my system which uses VGA passthrough.
> - I moved virtual CPUs to dedicated CPUs (isolcpus=4-7 kernel boot argument)
> - I instructed my windows guest to use MSI IRQ
>
> Sound crackles disappeared, but after a few minute
01 2C
> 0E13: 62 0F
> 0E30: 2B B0
> 0E31: DF C8
> 00000E32: 45 D2
> 0E33: AD BE
> 0E34: 5B 2A
> 0E35: D7 C3
> 0E36: 92 51
> 0E37: 4B 49
> 0E38: 9F A5
> 0E39: E4 DA
> 0E3A: 89 40
> 0E3B: 1A B8
> 0E3C: 22 31
On Wed, 10/21 08:02, Flavio Borup wrote:
> ESX 4.1 does not recognize the converted VMDK file
>
>
>
> I´ve converted a VHDX file to .VMDK file with the following command:
>
>
>
>
>
> qemu-img convert -f vhdx "source.vhdx" -o subformat=monolithicFlat -O vmdk
> "destination.vmdk"
>
>
>
>
On Thu, 09/10 19:22, LiChuanyun wrote:
> Hi, all We have a openstack cluster newly installed. Every vm in the cluster
> randomly freezes(about 2~3 seconds) every few minutes. When a vm freeze,
> ping from outside (a physical machine or another vm) will have latency of a
> few seconds or timeout (
On Sun, 06/21 01:32, Васил Рангелов wrote:
> Hi.
>
> As part of testing an application, I need to set up a network between the
> host and the VM so that they can both be accessed from the host on the same
> ports via different IPs. This can be done easily with VirtualBox (and I've
> already done i
On Thu, 04/02 23:40, Ming Lin wrote:
> Hi,
>
> For nvme, it uses "drive=" property to connect to backend.
> -drive file=/path/to/image,if=none,id=foo -device nvme,drive=foo,serial=1234
>
> But megasas doesn't have "drive" property.
> Could you share qemu commands to connect megasas device to its
On Sat, 01/10 01:53, nitinjava...@gmail.com wrote:
> Hi,
>
> I am trying to use a base image.qcow2 file and create many VMs out of it
> using following command.
>
> qemu-img -f qcow2 -b image.qcow2 vm1.qcow2
>
> Now image.qcow2 is a 40G disk with 23G worth of data. So its virtual size
> is 40G a
On Thu, 09/18 07:17, Priyanka Ranjan wrote:
> Sorry I sent this mail without subject earlier. Resending it with subject.
>
> Hello Experts,
> I am using CentOS 6.5. I am getting an issue with libguestfs (qemu-kvm)
>
> # /usr/libexec/qemu-kvm -nographic -machine accel=kvm:tcg -device \?
>
> op
On Mon, 04/07 15:23, Robin Bussell wrote:
>
>
>
>
> Hi Folks,
> I'm new to qemu so forgive me if I use the wrong terminology here:
>
> I have a base linux qcows2 image (base.bak) and two development images which
> use that file as a backing file (dev1.img and dev2.img).
>
> I now wis
Thank you,
>
> Best regards,
>
> Alexandre
>
> 2014-04-03 11:20 GMT+02:00 Fam Zheng :
>
> > On Thu, 04/03 11:06, Alexandre LAURENT wrote:
> > > Hi,
> > >
> > > I am using QEMU 1.7.1 and I would like to know how to use the 'drive'
> &
On Thu, 04/03 11:06, Alexandre LAURENT wrote:
> Hi,
>
> I am using QEMU 1.7.1 and I would like to know how to use the 'drive'
> options :
> - bps_wr
> - bps_wr_max
> - bps_rd
> - bps_rd_max
>
> Can you explain me how to limit IO access between two VMs, where one would
> be limited and the second
On 2013年12月12日 20:13, Marko Weber | 8000 wrote:>
>>
>> Another question, what is the physical block size of the device for
>> your xfs partition?
>
>>
>> # lsblk -o NAME,PHY-SeC
>
> atabunka virtual # lsblk -o NAME,PHY-SeC
> NAME PHY-SEC
> sda 512
> ├─sda1512
> ├─sda2
On 2013年12月12日 17:59, Marko Weber | 8000 wrote:
open("/raid6/virtual/foo.tmp", O_WRONLY|O_CREAT|O_TRUNC|O_DIRECT, 0666) = 3
OK, O_DIRECT actually works with /raid6/virtual/foo.tmp, my guess was
wrong. Let's just check qemu with strace then. Could you try this:
strace /YOUR/PATH/TO/qemu-syste
On 2013年12月12日 16:01, Marko Weber | 8000 wrote:
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 100, in
cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 122, in
tmpcb
callbac
On 2013年12月11日 22:44, Marko Weber | 8000 wrote:
hello list,
on gentoo with the subject listed components, i cant start my virtual
machines
when cache=none is set on disk settings
when i set cache=default, the machine starts.
the partition where the disk-images lies is mounted with xfs with t
On 11/04/2013 09:16 PM, Dmitry wrote:
Hello,
After upgrade to QEMU emulator version 1.6.1 (Debian 1.6.0+dfsg-2) it
is not possible to connect ISO via HTTP anymore:
--8<--
QEMU 1.6.1 monitor - type 'help' for more information
(qemu) info version
info version
1.6.1 (Debian 1.6.0+dfsg-2)
(qemu)
On Fri, 10/25 13:41, dE wrote:
> On 10/10/13 07:18, Fam Zheng wrote:
> >On Wed, 10/02 20:15, dE wrote:
> >>On execution of this command --
> >>
> >> block_set_io_throttle cdrom 314572800 1048576 0
> >>
> >It expects 6 numbers.
> >
> >
On Wed, 10/02 20:15, dE wrote:
> On execution of this command --
>
> block_set_io_throttle cdrom 314572800 1048576 0
>
It expects 6 numbers.
Fam
> I get "unexpected end of expression". What might be wrong?
>
> Thanks for the response.
>
On Mon, 09/02 07:38, dE wrote:
> Hello everyone! I just started working on Qemu, however qemu does
> not start. In the following command --
>
> qemu-system-x86_64 -boot order=d -cdrom ~/large/FOSS/iso\
> images/systemrescuecd-x86-3.4.0-beta007.iso
>
> The process runs, it grabs the terminal, but
Hi Maryyam,
What Linux distribution are you using? If Debing/Ubuntu, you can try to
install libglib2.0-dev. (*-dev package is used for compiling software
from source).
On Thu, 08/01 12:04, Maryyam Muhammad Din wrote:
> Host Architecture: MIPS
> Host OS: Linux
>
> I want to use QEMU on MIPS as ho
On Mon, 07/22 13:51, Yaodong Yang wrote:
> Hi everyone,
>
> Previously, I used the qemu-kvm-1.2.0 from
> (http://www.linux-kvm.org/page/Downloads), and it worked well in my ubuntu
> server. Later, I found that some of the implementation(qemu-kvm-1.2.0) is out
> of date, so that I changed to qem
On Fri, 06/14 08:53, Bruno Diraison wrote:
> Hi,
>
> Still now I was used to use Qemu to simulate Linux kernel image that I
> built by myself.
> Today, I want to run a Kernel image, built for ARM926EJ-S, with
> qemu-system-arm.
> The issue I'm facing is that the kernel doesn't start and I don't ha
On Fri, 06/14 10:16, Hendré Louw wrote:
> Morning
>
> I installed qemu using sudo apt-get install qemu on Ubuntu 12.04.
> However, I cannot find the qemu command. I only have commands like
> qemu-img and qemo-io.
>
> Please assist.
> Hendre
>
Hendre,
You need to use qemu-system-x86_64 or qemu-
On Sat, 04/27 17:07, Mike Zhang wrote:
>I installed the SDL1.2, but it always told that "ERROR: QEMU requires
>SDL or Cocoa for graphical output" which makes me cannot go on to
>install it.
>Is there any one knew how to solve this problem?
>I'll be apprecaited your helps, thanks
Could you try to upgrade your glibc and maybe use gcc4 to compile.
Latest release of qemu is worth a try?
Thanks.
On Sun, 04/28 16:55, Mike Zhang wrote:
>when I install the qemu0.9.1 on my ubuntu13, it gives me this error.
>I also tried to edit the block-raw-posix.c #include
>to linu
75 matches
Mail list logo
