This doesn't really make sense, but the patch adding the pc-1.0-qemu-kvm machine
type seems to be also adding pc-1.0-qemu-kvm as an alias for pc-1.0, all the way
back to the original version where we introduced the patch. Which doesn't
really make sense as the package did pass SRU testing.
When
That seems like an unrelated bug. Please open a new bug, giving as much
information as possible about the two hosts and the vms.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1291321
Having trouble with this still. I've installed the packages and made
the changes to machine type and qemu as stated above. These are the
errors I'm getting.
2015-10-23 19:25:57.491+: 7277: warning :
qemuDomainObjEnterMonitorInternal:1274 : This thread seems to be the async job
owner;
** Changed in: libvirt (Ubuntu)
Status: Triaged = Fix Released
** Changed in: qemu (Ubuntu)
Status: Triaged = Fix Released
** Changed in: libvirt (Ubuntu Trusty)
Status: Confirmed = Fix Released
** Changed in: qemu (Ubuntu Trusty)
Status: Confirmed = Fix Released
--
@Serge
Thank you very much. This was exactly the missing piece in my puzzle!
The live-migration between 12.04 and 14.04 is now working as expected.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
@Raphael,
if you're having trouble with the virtio network type, then it sounds
like either you are not passing the romfile option to qemu in the trusty
host (-global virtio-net-pci.romfile=pxe-virtio.rom.12.04), or you do
not have the pxe-virtio.rom.12.04 file installed (in /usr/share/qemu/ as
a
@Serge:
Thanks for the response. Unfortunately the problem persists even with the
-machine pc-1.0-qemu-kvm argument. The qemu process is just dying on the target
node without any message. Do you have any tips for us how to get further
information about the cause? The source node doesn't report
In the meantime I could find out that the problem only pops up when
virtio (or virtio-net) is being used for network devices. With the
e1000 nic_type everything is working as expected. Can this be seen as
related to this bug?
--
You received this bug notification because you are a member of
Quoting Raphael Thoma (raphit...@gmx.ch):
In the meantime I could find out that the problem only pops up when
virtio (or virtio-net) is being used for network devices. With the
e1000 nic_type everything is working as expected. Can this be seen as
related to this bug?
Perhaps, but if so then
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libvirt (Ubuntu Trusty)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: qemu (Ubuntu Trusty)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
I installed the patched package from the ppa on our upgraded
(12.04-14.04) system - however the live-migration is still not working
as expected.
The kvm process is just dying without any message/logs as soon as the
migrate command is started on the source node. We're using googles
ganeti to
@Raphi,
You say you started the instance with -machine pc-1.0. To accept incoming
migration from precise you must use -machine pc-1.0-qemu-kvm
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
Quoting Matt Mullins (mokom...@gmail.com):
That's awesome. I just got a chance to test it out, and with a couple
hiccups (below), I seem to have successfully migrated a guest from a
precise host to a new trusty one.
It looks like qemu failed to build in Serge's PPA due to the spice that
(Note, the patches being tested are the ones from this thread:
https://lists.nongnu.org/archive/html/qemu-devel/2014-07/msg03160.html )
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
That's awesome. I just got a chance to test it out, and with a couple
hiccups (below), I seem to have successfully migrated a guest from a
precise host to a new trusty one.
It looks like qemu failed to build in Serge's PPA due to the spice that
also lives in that PPA. I built the qemu from the
Thanks very much to Alex Bligh for posting a working patchset for qemu!
Test packages for both qemu and libvirt are in ppa:serge-hallyn/virt.
The source of these allowd me to successfuly migrate a cirros VM from
precise to utopic. To trigger this, /etc/libvirt/qemu.conf must contain
This is pretty annoying. In a situation where you have many customer VMs
running on 12.04, and want to migrate them to a host running 14.04 (so
you can do a rolling OS upgrade), I'm afraid shut down all your
customer VMs and restart isn't really an option for obvious reasons.
Equally, installing
Looks like there is a patch here:
http://pkgs.fedoraproject.org/cgit/qemu.git/tree/0001-Fix-migration-from-qemu-kvm.patch?h=f20
but it's either take it (and break inbound migrates from quantal etc.)
or don't (and break inbound migrates from precise). Another possibility
(unhelpful for libvirt
Hi Matt,
some feeble attempts at that were made, but the result was deemed too
fragile. The safest option is to shut down the VMs, change the machine
type in the xml definition, migrate the shut-down images, and re-start
them in trusty.
--
You received this bug notification because you are a
** Changed in: qemu (Ubuntu)
Status: Confirmed = Won't Fix
** Changed in: libvirt (Ubuntu)
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
This is also blocking a precise - trusty migration for me.
Would it be possible / feasible to provide a pc-1.0-precise machine
type in qemu for trusty and an updated libvirt for precise that allows
you to change the machine attribute on the type element for migration,
so I could specify a
My comment may not apply to this, but I'll make it anyhow:
I upgraded my host server from ubuntu 12.04 to 14.04. Afterwards, none
of my desktop VM's worked (I haven't even tried the server VM's yet). I
made a new guest VM using the exact same virst-install command I had
used for the original VM
@Doug I saw the same in a 12.04 to 14.04 upgrade, also had to edit the
machine type. Other than that one edit, all of my VMs worked after the
Trusty upgrade. Take note that this triggers Windows VMs to have to re-
activate due to the changed 'hardware.'
But I think this bug is more about a live
Indeed, as Ryan suggests this is different. Doug, would you mind filing
a new bug for what you are seeing? pc-1.0 should certainly still work,
although it's meaning has changed a bit since 12.04. My understanding
(which may be inaccurate) was that while the change in meaning will
prevent live
Unfortunately, no, that doesn't seem to work either. I managed to
compile qemu-kvm-1.0+noroms (required a few minor changes, linking with
librt and a documentation difference) and the supporting bios and pxe
files on Trusty. Migration now seems to work (Completed 100 %), but then
the target
After trying a few more things and discussing with upstream, I'm afraid
the answer will be to mark this as unsupported in the release notes.
Because users could be using -m pc-1.0 in raring+, we cannot simply use
the old qemu-kvm values for pc-1.0 and lower machines, as that would fix
users from
Ok, I understand. Please note that this was also an issue for 10.04 - 12.04,
so it's definitely a good idea to have it fixed for future upgrades (aka
trusty specific machine type).
I'm not sure about the extra qemu. The next action after migration would be to
install the real qemu, right? After
I'm not sure about the extra qemu. The next action after migration
would be to install the real qemu, right? After which I should
stop-start (as opposed to re-start!) all VM's to make sure they're
under a trusty-compatible qemu? Or an I missing something here?
Right, it would be a very
Otoh, now we're facing a non-migrateable 12.04 in general, because you cannot
move your VMs out of the way :-(
Anyway, proper documentation is helpful in any case. Finally: there is no real
workaround now, or is there? What would you do, having several 12.04 host
machines? Just migrate
Now I suppose one simple workaround would be to build the qemu-kvm package
from precise on trusty...
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1291321
Title:
migration fails
Hi,
Adding qemu:commandline tags needs a namespace. What you do is:
12.04~# virsh edit machine
Now add the namespace. The resulting first line of the domain xml-file should
read:
domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'
After that, adding qemu:commandline tags
So 12.04 doesn't have the option. I even tried to trick the system
into
Right, that was the conclusion I unfortunately came to yesterday. So I
will look at the qemu source and see if there is a reasonable way to
resize the vram when the mismatch is found at migration time.
--
You received
Please note my comment #5: removing the vga adapter showed up a new
mismatch, this time for the virtio network adapter. I did not look into
that but you might want to check if there's more memory mismatches that
should be addressed before you start adding code.
--
You received this bug
Yes, I did run into that yesterday as well. However, we have to
start somewhere :)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1291321
Title:
migration fails between 12.04 Precise
Hi, is there anything I can do to help this bug's status?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1291321
Title:
migration fails between 12.04 Precise and 14.04 Trusty
To
Sorry, that was meant to be reset to New. I'm intending to set up
reproducers today and get to the bottom of it. This definately should
be fixed somehow before release. Thanks for reporting this.
** Changed in: libvirt (Ubuntu)
Status: Incomplete = New
** Changed in: qemu (Ubuntu)
** Changed in: qemu (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1291321
Title:
migration fails between 12.04 Precise and 14.04 Trusty
To
Adding
-global cirrus-vga.vgamem_mb=10
to the receiving end's qemu command line options brings us past that
error. You may end up with other incompatibilities (I did) but perhaps
libvirt will ensure the rest of the devices match up. Please let us
know how it fares with that option.
--
You
Sorry, I guess that doesn't help much with your use of libvirt.
Can you please show the xml for the original VM you are migrating? It
can and should be specifying a vga ram size.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu
When you add a machine with virt-manager, the display setting is model
type='cirrus' vram='9216' heads='1'/. I tried to set it to 10240 (which
is 10mb) but that didn't help - the error is the same.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
BTW, that last test was with the regular qemu-kvm in trusty, which is
1.7.0+dfsg-3ubuntu6. I upgraded to the ppa-version again and ... it
seems to do something. BRB.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
error: Unable to read from monitor: Connection reset by peer and the machine
crashed :-(
Next try, same as always: Length mismatch: vga.vram: 100 in != 80
That's a weird side effect, sometimes not only migration fails, but the machine
on the source host crashes, too. Did you reproduce
Quoting Valentijn Sessink (valent...@sessink.nl):
When you add a machine with virt-manager, the display setting is model
type='cirrus' vram='9216' heads='1'/. I tried to set it to 10240 (which
is 10mb) but that didn't help - the error is the same.
Yes, oddly the way to specify this is to add
Hi,
Installed qemu-common qemu-keymaps qemu-kvm qemu-system-common
qemu-system-x86 qemu-utils from the ppa, same error:
source (12.04): # error: operation failed: migration job: unexpectedly
failed
Log file on target (14.04, log_level = 1) says:
2014-03-13 07:03:56.550+: starting up
The 100 comes from vga.h in the source for qemu-kvm-1.0+noroms: #define
VGA_RAM_SIZE (16 * 1024 * 1024)
I could not find the 80 value - as far as I can see, vga ram size is not
fixed anymore in the qemu-1.7.0+dfsg source - but I did not fully understand
the code.
Anyway, I tried
Thanks for submitting this bug. Would it be possible for you to test
with the qemu package in ppa:ubuntu-virt/candidate to see whether that
works any better?
** Changed in: libvirt (Ubuntu)
Importance: Undecided = High
** Also affects: qemu (Ubuntu)
Importance: Undecided
Status:
Yes, that's possible. Should I install the ppa on source, target or
both?
V.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1291321
Title:
migration fails between 12.04 Precise and
Only on the target, as it only has a package for trusty.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1291321
Title:
migration fails between 12.04 Precise and 14.04 Trusty
To
49 matches
Mail list logo
