headers
Dale Bewley | 1 Apr 08:48
Picon
Favicon

f11 virt release notes freezing

I've been busy at my day job and not paying close enough attention to
Fedora 11 docs deadlines. Apparently the window for changes essentially
closes Wednesday (today).[1]

The notes are essentially in place. I don't think there are any gaping
holes, but I should have prompted for feedback much sooner. If you could
apply any love to the release notes[2] it would be appreciated. 

= QEMU / KVM =
It is noted that QEMU and KVM are merging as a package, but I've also
separately listed the fact that QEMU is now 0.10.0 and KVM is now 84. 

With the merge, might it be confusing or inaccurate to mention a
distinct new version of KVM? I'll admit to being somewhat fuzzy on
where/how that line is drawn.

I see[3] QEMU 0.10.0 in rawhide, but not 0.10.1, so I adjusted the
version in the relnotes. I copied the feature list from the 0.10.0
release announcement. If you'd care to suggest deletes or enhancements
of the list please do.

The KVM changelog since 74 (version at initial F10 release) is quite
long and not easily digestible by me at this late hour. Would anyone
care to offer some highlights or fill them into the wiki? Or, again,
should those be folded into QEMU?

= Libvirt =
I previously copied the list of changes from the releases, but did not
try to prune them down. It may be fine.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Daniel P. Berrange | 1 Apr 11:21
Picon
Favicon

Re: virtinst ... proper API way to add a floppy drive?

On Tue, Mar 31, 2009 at 04:15:44PM -0400, Michael DeHaan wrote:
> I'm working on adding scripted Windows install support (ISO + answer 
> file on floppy) support to koan.
> 
> I'm getting the following when trying to attach a floppy image.  
> 
> 
> =======================
> 
> Here's the error:
> 
> libvir: QEMU error : Domain not found
> libvir: QEMU error : Domain not found
> libvir: Domain Config error : internal error Invalid floppy device name: hda
> <class 'libvirt.libvirtError'>

This is the core issue - you're giving the floppy a harddisk name

> internal error Invalid floppy device name: hda
>    <disk type='file' device='floppy'>
>      <source file='/tmp/tmpkmVdz3.floppy'/>
>      <target dev='hda' bus='ide'/>
>    </disk>

This should be 
    <disk type='file' device='floppy'>
      <source file='/tmp/tmpkmVdz3.floppy'/>
      <target dev='fda' bus='fdc'/>
    </disk>
(Continue reading)

Permalink | Reply | 8 comments |
headers
Michael DeHaan | 1 Apr 18:14
Picon
Favicon

Re: virtinst ... proper API way to add a floppy drive?


> This is the core issue - you're giving the floppy a harddisk name
>   

Yeah, I caught that :)

>>  
>> guest.disks.append(virtinst.VirtualDisk(device=virtinst.VirtualDisk.DEVICE_FLOPPY, 
>> path=floppy_path))
>>     
>
> I think you'll need to at least give a device name.
>
> libvirt fills in the bus, based on device name if you leave it out
>   

The constructor signature for VirtualDisk is...

__init__(self, path=None, size=None, transient=False, type=None, device='dis
k', driverName=None, driverType=None, readOnly=False, sparse=True, 
conn=None, vo
lObject=None, volInstall=None, volName=None, bus=None)

Which field would I use for specifying the device name?

Thanks!

--Michael
Permalink | Reply | 7 comments |
headers
Daniel P. Berrange | 1 Apr 18:25
Picon
Favicon

Re: virtinst ... proper API way to add a floppy drive?

On Wed, Apr 01, 2009 at 12:14:49PM -0400, Michael DeHaan wrote:
> 
> >This is the core issue - you're giving the floppy a harddisk name
> >  
> 
> Yeah, I caught that :)
> 
> >> 
> >>guest.disks.append(virtinst.VirtualDisk(device=virtinst.VirtualDisk.DEVICE_FLOPPY, 
> >>path=floppy_path))
> >>    
> >
> >I think you'll need to at least give a device name.
> >
> >libvirt fills in the bus, based on device name if you leave it out
> >  
> 
> The constructor signature for VirtualDisk is...
> 
> __init__(self, path=None, size=None, transient=False, type=None, device='dis
> k', driverName=None, driverType=None, readOnly=False, sparse=True, 
> conn=None, vo
> lObject=None, volInstall=None, volName=None, bus=None)
> 
> Which field would I use for specifying the device name?

Just set

   device=VirtualDisk.DEVICE_FLOPPY
(Continue reading)

Permalink | Reply | 6 comments |
headers
Michael DeHaan | 1 Apr 18:25
Picon
Favicon

Re: virtinst ... proper API way to add a floppy drive?

Daniel P. Berrange wrote:
> On Wed, Apr 01, 2009 at 12:14:49PM -0400, Michael DeHaan wrote:
>   
>>> This is the core issue - you're giving the floppy a harddisk name
>>>  
>>>       
>> Yeah, I caught that :)
>>
>>     
>>>> guest.disks.append(virtinst.VirtualDisk(device=virtinst.VirtualDisk.DEVICE_FLOPPY, 
>>>> path=floppy_path))
>>>>    
>>>>         
>>> I think you'll need to at least give a device name.
>>>
>>> libvirt fills in the bus, based on device name if you leave it out
>>>  
>>>       
>> The constructor signature for VirtualDisk is...
>>
>> __init__(self, path=None, size=None, transient=False, type=None, device='dis
>> k', driverName=None, driverType=None, readOnly=False, sparse=True, 
>> conn=None, vo
>> lObject=None, volInstall=None, volName=None, bus=None)
>>
>> Which field would I use for specifying the device name?
>>     
>
> Just set
>
(Continue reading)

Permalink | Reply | 5 comments |
headers
Cole Robinson | 1 Apr 21:22
Picon
Favicon

Re: virtinst ... proper API way to add a floppy drive?

Michael DeHaan wrote:
> Daniel P. Berrange wrote:
>> On Wed, Apr 01, 2009 at 12:14:49PM -0400, Michael DeHaan wrote:
>>   
>>>> This is the core issue - you're giving the floppy a harddisk name
>>>>  
>>>>       
>>> Yeah, I caught that :)
>>>
>>>     
>>>>> guest.disks.append(virtinst.VirtualDisk(device=virtinst.VirtualDisk.DEVICE_FLOPPY, 
>>>>> path=floppy_path))
>>>>>    
>>>>>         
>>>> I think you'll need to at least give a device name.
>>>>
>>>> libvirt fills in the bus, based on device name if you leave it out
>>>>  
>>>>       
>>> The constructor signature for VirtualDisk is...
>>>
>>> __init__(self, path=None, size=None, transient=False, type=None, device='dis
>>> k', driverName=None, driverType=None, readOnly=False, sparse=True, 
>>> conn=None, vo
>>> lObject=None, volInstall=None, volName=None, bus=None)
>>>
>>> Which field would I use for specifying the device name?
>>>     
>> Just set
>>
(Continue reading)

Permalink | Reply | 4 comments |
headers
Michael DeHaan | 1 Apr 21:28
Picon
Favicon

Re: virtinst ... proper API way to add a floppy drive?

Cole Robinson wrote:
> Michael DeHaan wrote:
>   
>> Daniel P. Berrange wrote:
>>     
>>> On Wed, Apr 01, 2009 at 12:14:49PM -0400, Michael DeHaan wrote:
>>>   
>>>       
>>>>> This is the core issue - you're giving the floppy a harddisk name
>>>>>  
>>>>>       
>>>>>           
>>>> Yeah, I caught that :)
>>>>
>>>>     
>>>>         
>>>>>> guest.disks.append(virtinst.VirtualDisk(device=virtinst.VirtualDisk.DEVICE_FLOPPY, 
>>>>>> path=floppy_path))
>>>>>>    
>>>>>>         
>>>>>>             
>>>>> I think you'll need to at least give a device name.
>>>>>
>>>>> libvirt fills in the bus, based on device name if you leave it out
>>>>>  
>>>>>       
>>>>>           
>>>> The constructor signature for VirtualDisk is...
>>>>
>>>> __init__(self, path=None, size=None, transient=False, type=None, device='dis
(Continue reading)

Permalink | Reply | 3 comments |
headers
Cole Robinson | 1 Apr 21:36
Picon
Favicon

Re: virtinst ... proper API way to add a floppy drive?

Michael DeHaan wrote:
> Cole Robinson wrote:
>> Michael DeHaan wrote:
>>   
>>> Daniel P. Berrange wrote:
>>>     
>>>> On Wed, Apr 01, 2009 at 12:14:49PM -0400, Michael DeHaan wrote:
>>>>   
>>>>       
>>>>>> This is the core issue - you're giving the floppy a harddisk name
>>>>>>  
>>>>>>       
>>>>>>           
>>>>> Yeah, I caught that :)
>>>>>
>>>>>     
>>>>>         
>>>>>>> guest.disks.append(virtinst.VirtualDisk(device=virtinst.VirtualDisk.DEVICE_FLOPPY, 
>>>>>>> path=floppy_path))
>>>>>>>    
>>>>>>>         
>>>>>>>             
>>>>>> I think you'll need to at least give a device name.
>>>>>>
>>>>>> libvirt fills in the bus, based on device name if you leave it out
>>>>>>  
>>>>>>       
>>>>>>           
>>>>> The constructor signature for VirtualDisk is...
>>>>>
(Continue reading)

Permalink | Reply | 2 comments |
headers
Michael DeHaan | 1 Apr 21:44
Picon
Favicon

Re: virtinst ... proper API way to add a floppy drive?

Cole Robinson wrote:
> Michael DeHaan wrote:
>   
>> Cole Robinson wrote:
>>     
>>> Michael DeHaan wrote:
>>>   
>>>       
>>>> Daniel P. Berrange wrote:
>>>>     
>>>>         
>>>>> On Wed, Apr 01, 2009 at 12:14:49PM -0400, Michael DeHaan wrote:
>>>>>   
>>>>>       
>>>>>           
>>>>>>> This is the core issue - you're giving the floppy a harddisk name
>>>>>>>  
>>>>>>>       
>>>>>>>           
>>>>>>>               
>>>>>> Yeah, I caught that :)
>>>>>>
>>>>>>     
>>>>>>         
>>>>>>             
>>>>>>>> guest.disks.append(virtinst.VirtualDisk(device=virtinst.VirtualDisk.DEVICE_FLOPPY, 
>>>>>>>> path=floppy_path))
>>>>>>>>    
>>>>>>>>         
>>>>>>>>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Gerrit Slomma | 2 Apr 00:59
Picon

fix for presenting memory allocation of host and/or vm

Hello

I found the presentation of the memory allocation of host and/or vm
annoying, e.g. hosts/vms with more then one GB showed up in
virtual-manager with x.yy GBwhereas hosts/vms with less or equal to on
GB showed up as xxxx.yy MB. In details of hosts this also showed up.
I changed this behavior to showing GB if memory is >10 GB and set
MB-presentation to 2.0f.
I find it clearer, what is your opinion?

--- a/src/virtManager/domain.py       2009-04-01 23:19:28.000000000 +0200
+++ b/src/virtManager/domain.py       2009-04-02 00:28:44.000000000 +0200
@@ -379,7 +379,7 @@

     def current_memory_pretty(self):
         if self.get_id() == -1:
-            return "0.00 MB"
+            return "0 MB"
         return self.get_memory_pretty()

@@ -400,10 +400,10 @@

     def get_memory_pretty(self):
         mem = self.get_memory()
-        if mem > (1024*1024):
+        if mem > (10*1024*1024):
             return "%2.2f GB" % (mem/(1024.0*1024.0))
         else:
-            return "%2.2f MB" % (mem/1024.0)
+            return "%2.0f MB" % (mem/1024.0)
(Continue reading)

Permalink | Reply | 1 comment |

Gmane