On Wed, Jul 27, 2011 at 08:42:59AM -0400, Whit Blauvelt wrote:
[..]
> be accepted. Clearly having libvirt recognize that the kvm hypervisor is
> available, and automatically using it when the xml file specifies it, does
> not take some extraordinary level of clever programming. "The xml specifies
>
> Are you sure that libvirt 0.9.3 and before had VirtualBox support
> compiled in? If not then VirtualBox can not supersede QEMU in the
> autodetection. That might explain it, but I don't see how that can
> happen apart from you explicitly disabling VirtualBox support at
> configure time.
libvirt
2011/7/27 Cole Robinson :
> On 07/27/2011 03:21 AM, Matthias Bolte wrote:
>> 2011/7/27 Whit Blauvelt :
What's the output of "# virsh -V" on your second ubuntu box? I guess
your libvirt on that box might not be compiled with qemu driver.
>>>
>>> # virsh -V
>>> Virsh command line tool of li
2011/7/27 Whit Blauvelt :
>> That's not how libvirt works. The architecture is different than you
>> seem to expect it.
>
> Matthias,
>
> Even with all you say - and I thank you for your patient explanation - there
> remains a question: Why should 0.9.3+ git suddenly decide that the default
> drive
> That's not how libvirt works. The architecture is different than you
> seem to expect it.
Matthias,
Even with all you say - and I thank you for your patient explanation - there
remains a question: Why should 0.9.3+ git suddenly decide that the default
driver should be vbox, when 0.8.3 and 0.9.2
On 07/27/2011 03:21 AM, Matthias Bolte wrote:
> 2011/7/27 Whit Blauvelt :
>>> What's the output of "# virsh -V" on your second ubuntu box? I guess
>>> your libvirt on that box might not be compiled with qemu driver.
>>
>> # virsh -V
>> Virsh command line tool of libvirt 0.9.3 ...
>>
>> Compiled wit
2011/7/27 Whit Blauvelt :
> On Wed, Jul 27, 2011 at 09:21:08AM +0200, Matthias Bolte wrote:
>
>> The point is that libvirt autodetects the available hypervisors at
>> runtime when you don't specify a connection URI. For example, just
>> running virsh results in autodetecting VirtualBox because you
I have the same problem. I've already tried to start vbox vm without GUI but
I couldn't do it.
Christian, as it seems that you've managed to do it successfully, could you
help us out in this task?
If not, does anyone here have a way to do it? Or is it impossible with
current libvirt code?
thanks
On Wed, Jul 27, 2011 at 09:21:08AM +0200, Matthias Bolte wrote:
> The point is that libvirt autodetects the available hypervisors at
> runtime when you don't specify a connection URI. For example, just
> running virsh results in autodetecting VirtualBox because you have it
> installed in a way tha
On Tue, Jul 26, 2011 at 04:15:45PM -0400, Whit Blauvelt wrote:
> On Mon, Jul 25, 2011 at 03:32:32PM -0600, Eric Blake wrote:
>
> > Yes, both useful lock managers (sanlock and fcntl) work best with
> > the use of a shared lock directory, at which point they correctly
> > handle live migration betwe
2011/7/27 Whit Blauvelt :
>> What's the output of "# virsh -V" on your second ubuntu box? I guess
>> your libvirt on that box might not be compiled with qemu driver.
>
> # virsh -V
> Virsh command line tool of libvirt 0.9.3 ...
>
> Compiled with support for:
> Hypervisors: QEmu/KVM UML OpenVZ Virt
11 matches
Mail list logo
