On Fri, Aug 02, 2013 at 10:31:11AM +0200, Paolo Bonzini wrote:
> On 08/02/2013 12:42 AM, Eric Blake wrote:
> >On 08/01/2013 04:23 PM, Paolo Bonzini wrote:
> >>>Automatic devices with no command line argument have proven to be a
> >>>nightmare for libvirt as well. Although the just-released libvirt
On 08/02/2013 12:42 AM, Eric Blake wrote:
On 08/01/2013 04:23 PM, Paolo Bonzini wrote:
Automatic devices with no command line argument have proven to be a
nightmare for libvirt as well. Although the just-released libvirt 1.1.1
now supports the element for controlling the command line
parameter
On Thu, 2013-08-01 at 16:32 +0300, Michael S. Tsirkin wrote:
> On Thu, Aug 01, 2013 at 04:08:57PM +0300, Marcel Apfelbaum wrote:
> > Hi,
> >
> > The problem with pvpanic being an internal device is that VMs running
> > operating systems without a driver for this device will have problems
> > when
On Thu, Aug 01, 2013 at 04:08:57PM +0300, Marcel Apfelbaum wrote:
> Hi,
>
> The problem with pvpanic being an internal device is that VMs running
> operating systems without a driver for this device will have problems
> when qemu will be upgraded (from qemu without this pvpanic).
>
> The outcome
On 08/01/2013 04:23 PM, Paolo Bonzini wrote:
>> Automatic devices with no command line argument have proven to be a
>> nightmare for libvirt as well. Although the just-released libvirt 1.1.1
>> now supports the element for controlling the command line
>> parameters of qemu related to how qemu wil
On 08/01/2013 06:26 PM, Eric Blake wrote:
On 08/01/2013 08:18 AM, Gerd Hoffmann wrote:
On 08/01/13 15:08, Marcel Apfelbaum wrote:
Hi,
The problem with pvpanic being an internal device is that VMs running
operating systems without a driver for this device will have problems
when qemu will be up
On Thu, Aug 01, 2013 at 10:26:53AM -0600, Eric Blake wrote:
> On 08/01/2013 08:18 AM, Gerd Hoffmann wrote:
> > On 08/01/13 15:08, Marcel Apfelbaum wrote:
> >> Hi,
> >>
> >> The problem with pvpanic being an internal device is that VMs running
> >> operating systems without a driver for this device
On Thu, 2013-08-01 at 19:31 +0300, Michael S. Tsirkin wrote:
> On Thu, Aug 01, 2013 at 10:26:53AM -0600, Eric Blake wrote:
> > On 08/01/2013 08:18 AM, Gerd Hoffmann wrote:
> > > On 08/01/13 15:08, Marcel Apfelbaum wrote:
> > >> Hi,
> > >>
> > >> The problem with pvpanic being an internal device is
On 08/01/2013 08:18 AM, Gerd Hoffmann wrote:
> On 08/01/13 15:08, Marcel Apfelbaum wrote:
>> Hi,
>>
>> The problem with pvpanic being an internal device is that VMs running
>> operating systems without a driver for this device will have problems
>> when qemu will be upgraded (from qemu without this
On 08/01/13 15:08, Marcel Apfelbaum wrote:
> Hi,
>
> The problem with pvpanic being an internal device is that VMs running
> operating systems without a driver for this device will have problems
> when qemu will be upgraded (from qemu without this pvpanic).
>
> The outcome may be, for example: in
Hi,
The problem with pvpanic being an internal device is that VMs running
operating systems without a driver for this device will have problems
when qemu will be upgraded (from qemu without this pvpanic).
The outcome may be, for example: in Windows(let's say XP) the Device manager
will open a "ne
11 matches
Mail list logo
