On Wed, Feb 20, 2013 at 2:54 AM, Zeeshan Ali (Khattak)
wrote:
>
> For further information about libosinfo please consult the project homepage
>
>https://fedorahosted.org/libosinfo/
Yikes, forgot to update the URL in release announcement: http://libosinfo.org/
--
Regards,
Zeeshan Ali (Khat
Libosinfo 0.2.4 is out!
Changes since 0.2.3:
- Fix crash in osinfo-detect against non-bootable media.
- osinfo-install-script now displays names of generated files.
- Add an all-in-one virtio and QXL device driver setup binary to Windows XP
and 7. Same binary also installs spice-vdagent for us.
On Mon, Feb 18, 2013 at 1:16 PM, Cole Robinson wrote:
> On 02/18/2013 02:12 PM, Doug Goldstein wrote:
>> On Mon, Feb 18, 2013 at 9:11 AM, Guido Günther wrote:
>>> Hi,
>>>
>>> On Sat, Feb 16, 2013 at 02:32:36PM -0500, Cole Robinson wrote:
>>> [..snip..]
merge virtinst:
- no big clean up,
I just want to bring everyone's attention this important bug in
Fedora 18. It looks like people are now starting to upgrade to F18
and are hitting this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=912499
In brief, when virt-manager runs, it starts some libguestfs instances
in the backgroun
'Allocate entire disk now' is working correctly.
But if I need to add another volume to VM I use -> Connection Details -> Storage
-> New Volume
So what's the reason if I fill up
Max Capacity: 10240 MB
Allocation: 10240 MB ---> description (Allocation: Actual size allocated to
volume at this t
On 19.02.2013 13:19, Peter Velas wrote:
> Hello guys,
>
>
> My environment
> Fedora 18 with kernel 3.7.8-202.fc18.x86_64
> Virtual Machine Manager 0.9.4
>
> when creating New Storage Volume in virt-manager
> newVM.img with qcow2 format for example with following settings:
>
>
> Max Capacity
Hello guys,
My environment
Fedora 18 with kernel 3.7.8-202.fc18.x86_64
Virtual Machine Manager 0.9.4
when creating New Storage Volume in virt-manager
newVM.img with qcow2 format for example with following settings:
Max Capacity: 10240 MB
Allocation: 10240 MB
But then if I check the file
On Mon, Feb 18, 2013 at 01:33:42PM -0800, Eric wrote:
> Unfortunately, gcc is also absent from the OVS public repository
> (http://public-yum.oracle.com/repo/OracleVM/OVM3/latest/x86_64/).
>
> Have you got any other suggestions (besides to give up on extending
> Oracle VM Server 3)?
Maybe you can