It's been a very very long time since I've last ran a Windows virtual
machine on Ubuntu, so I can't really tell. I do remember I never got it
"fixed", but did find a fix for it by disabling the Windows power plan
option "Allow Windows to put this device to sleep". Over the years I did
get some than
never use google docs
On Mon, Apr 06, 2020 at 11:57:11AM +0100, Peter Maydell wrote:
> On Mon, 6 Apr 2020 at 11:35, Paolo Bonzini wrote:
> > On 04/04/20 03:37, John Snow wrote:
> > > I have a lot of opinions and thoughts on python and how docs should be
> > > laid out, but I'm afraid I'm not so
Its ingoogle... We don't do google.
On April 3, 2020 9:37:09 PM EDT, John Snow wrote:
>
>
>On 4/1/20 12:37 PM, Philippe Mathieu-Daudé wrote:
>> Hi,
>>
>> Google recently announced their 'Season of Docs' project:
>> https://developers.google.com/season-of-docs
>>
>> QEMU project seems to fit a
Public bug reported:
QEMU emulator version 4.1.94
Documentation states that qemu will create a default nic as long as not
explicitly forbidden (-nic none) or defined ( e.g. -nic ).
Observation:
Even though qemu-system-ppc is started with "-readconfig" (which defines a
nic), another nic gets cre
Glad to hear you solved they issue by reading this bug report, Maarten!
As you can see the bug has been updated with the confirmed-status on
October 21st of 2015 and I hope they can fix this a.s.a.p. I don't have
a Windows-guest anymore, but even for all the other Qemu-users out there
that do, I'd
Ok, thanks for the info! By Rubin, do you mean Ruben (a.k.a. me)? :D
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1323758
Title:
Mouse stops working when connected usb-storage-device
Status in
Any news on this?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1323758
Title:
Mouse stops working when connected usb-storage-device
Status in QEMU:
New
Status in “qemu” package in Ubuntu:
New
On Mon, Aug 20, 2012 at 10:23 AM, Paolo Bonzini wrote:
> Il 19/08/2012 10:13, Ruben Kerkhof ha scritto:
>>> > That's correct. Live block migration will use two ports, both served by
>>> > the destination, one using NBD and one for RAM/device migration data
at libvirt cannot orchestrate.
Will I still be able to cap the migration bandwidth?
And how about security? Libvirt can tunnel the data, I believe by
passing an fd to qemu, and encrypting the connection with TLS.
Thanks,
Ruben
est one to get started. (Libvirt
> could orchestrate an NBD connection behind the scenes, for example.)
I really don't care which protocol is used, as long as libvirt handles
it for me.
Kind regards,
Ruben
xist, I think it should be:
> http://wiki.qemu.org/Features/LiveBlockMigration
Can the new live block copy method still use tcp just like the current
block migration? The wiki page only mentions iscsi.
I make extensive use of block migration over tcp, which works fine and
is handled by libvirt. I'd rather not introduce iscsi in my
environment.
Kind regards,
Ruben
11 matches
Mail list logo
