2011/4/21 Ian Forde ianfo...@gmail.com:
Turns out that wasn't the only problem I faced in my migration. With 2
KVM servers, both sharing a volume mounted via NFS for VMs, I migrated
all VMs to the second node, upgraded the first, them moved them all back
to KVM1. Instant disk corruption on
On 04/21/2011 01:16 PM, Kenni Lund wrote:
2011/4/21 Ian Forde ianfo...@gmail.com:
Turns out that wasn't the only problem I faced in my migration. With 2
KVM servers, both sharing a volume mounted via NFS for VMs, I migrated
all VMs to the second node, upgraded the first, them moved them all
On Thu, 2011-04-21 at 20:16 +0200, Kenni Lund wrote:
2011/4/21 Ian Forde ianfo...@gmail.com:
Turns out that wasn't the only problem I faced in my migration. With 2
KVM servers, both sharing a volume mounted via NFS for VMs, I migrated
all VMs to the second node, upgraded the first, them
On Sun, 2011-04-10 at 03:47 -0500, Johnny Hughes wrote:
On 04/09/2011 12:04 PM, compdoc wrote:
A similar incident was reported during the QA. Look at the .xml file.
If it says type='raw', change it to type='qcow2' and restart libvirtd.
Would that fix the problem ?
Akemi
Thank you.
On 04/09/2011 12:04 PM, compdoc wrote:
A similar incident was reported during the QA. Look at the .xml file.
If it says type='raw', change it to type='qcow2' and restart libvirtd.
Would that fix the problem ?
Akemi
Thank you. After reading your message, I googled the error and found a
On Sat, Apr 9, 2011 at 9:21 AM, compdoc comp...@hotrodpc.com wrote:
After updating to 5.6 on a server this morning, I can no longer boot two
virtual machines. One is trixbox which I believe is a 32bit centos based
distro, and the other vm is a 64bit Windows 2008 installation.
The error I get
A similar incident was reported during the QA. Look at the .xml file.
If it says type='raw', change it to type='qcow2' and restart libvirtd.
Would that fix the problem ?
Akemi
Thank you. After reading your message, I googled the error and found a
webpage that describes a slightly different
7 matches
Mail list logo