From: Serge Hallyn <1062201@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 1062201] Re: qemu core dumped by kvm-spice
Date: Mon, 08 Oct 2012 14:22:26 -0000 [thread overview]
Message-ID: <20121008142226.GA27031@sergelap> (raw)
In-Reply-To: 20121008140523.25745.16952.malone@gac.canonical.com
Quoting Tom Wijmenga (tomwijmenga@gmail.com):
> @ Serge,
>
> Ah oke, I was not aware of the big version issues. But as Quantal is not officially released yet and only RC's are out, won't that cause issues?
I'm not sure what you mean by issues - bugs reported against Q will
definately be addressed. The qemu versions in Q are basically set
in stone. If you need features added, then indeed that won't happen
in Q at this point.
> All I am trying to do is get a working demo of the capabilities of the
Spice protocol but many of the how-to's and PPA's are heavely out of
date / support. Would you have any advice, as manyally building the
protocol isn't working for me
What do you mean by manually building the protocol?
In Q, I've been doing:
sudo apt-get install qemu-kvm-spice
qemu-img create spice.img 10G
kvm-spice -cpu host -enable-kvm -m 1024 -M pc-1.2 -drive file=spice.img,if=virtio,cache=none -vga qxl -spice port=5900,disable-ticketing
(except also using tap bridged to eth0)
It's worked great for ubuntu quantal and fedora 18 guests.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1062201
Title:
qemu core dumped by kvm-spice
Status in QEMU:
New
Status in “qemu-kvm-spice” package in Ubuntu:
Invalid
Bug description:
Hi there,
I am trying to use kvm-spice to start the qemu virtual machines. They
start fine with the /usr/ bin/kvm command, but when I use the kvm-
spice command the VM will not start and the core is dumped.
Command I used:
kvm-spice -cpu host -enable-kvm -name win-7 -m 3000 -drive file=/var/vmmachines/win-7.img -net nic,model=rtl8139 -net user -localtime -usb -vga qxl -global qxl-vga.vram_size=67108864 -spice port=5901,disable-ticketing -boot d
Response:
do_spice_init: starting 0.10.1
spice_server_add_interface: SPICE_INTERFACE_MIGRATION
spice_server_add_interface: SPICE_INTERFACE_KEYBOARD
spice_server_add_interface: SPICE_INTERFACE_MOUSE
spice_server_add_interface: SPICE_INTERFACE_QXL
red_worker_main: begin
display_channel_create: create display channel
cursor_channel_create: create cursor channel
kvm-spice: /build/buildd/qemu-linaro-1.0.50-2012.03/exec.c:2641: register_subpage: Assertion `existing.mr->subpage || existing.mr == &io_mem_unassigned' failed.
Aborted (core dumped)
I am running Ubuntu 12.04 sserver for this. Any information about this issue would be appreciated, i'm stuck on this one.
Kind regards,
Tom
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1062201/+subscriptions
next prev parent reply other threads:[~2012-10-08 14:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-05 11:11 [Qemu-devel] [Bug 1062201] [NEW] qemu core dumped by kvm-spice Tom Wijmenga
2012-10-05 14:15 ` [Qemu-devel] [Bug 1062201] " Serge Hallyn
2012-10-05 14:16 ` Serge Hallyn
2012-10-08 7:29 ` Tom Wijmenga
2012-10-08 13:36 ` Serge Hallyn
2012-10-08 14:05 ` Tom Wijmenga
2012-10-08 14:22 ` Serge Hallyn [this message]
2012-10-09 8:54 ` Tom Wijmenga
2016-08-17 10:09 ` T. Huth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20121008142226.GA27031@sergelap \
--to=1062201@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).