Hi,
FYI, I upgraded to Ubuntu 14.04 and the bug vanished!
Thanks
On 13 August 2014 06:17, Launchpad Bug Tracker <1320...@bugs.launchpad.net>
wrote:
> [Expired for qemu-kvm (Ubuntu) because there has been no activity for 60
> days.]
>
> ** Changed in: qemu-kvm (Ubuntu)
>Status: Incomple
Hi Serge,
I have only one VM on my PC.
I have found that these actions can reliably trigger the crash:
- starting the vm via virsh start
- connecting to it with remmina via RDP
- exiting remmina
- starting virt-manager
- connecting to the console
- CRASH
On 22 May 2014 16:28, Serge Hallyn <13
** Description changed:
My Win7 VM running on KVM keeps crashing lately.
I cannot say when it started to do so but I can say that this was not
happening at all some weeks ago.
From the qemu-kvm log file related to this VM just after the crash I
have found what follows:
2014-05
Hi Serge,
I have opened this new bug:
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1320144
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1303926
Title:
qemu-system-x86_64
Public bug reported:
My Win7 VM running on KVM keeps crashing lately.
I cannot say when it started to do so but I can say that this was not
happening at all some weeks ago.
>From the qemu-kvm log file related to this VM just after the crash I
have found what follows:
2014-05-16 08:37:14.597+000
Hi Serge,
I think I have already reported the required information a number of times with
the Ubuntu built-in bug reporting facility (apport?), which asked me to report
the crash information to developers.
Are you able to find it out or do I need to manually open a new bug?
Thanks you.
--
Hi Serge,
I keep getting the crash notification due to kvm crashes with the same
bug title as this one. I see that the status is Fix Released, I'm on
precise and fully up-to-date.
My package is:
ii qemu-kvm 1.0+noroms-0ubuntu14.14
Full virtualization on i386 and a
Hi,
I've double checked my conf, I can confirm I'm not using virtio but
standard Win 7 drivers. (please see my VM conf that I posted some time ago).
So it's not definitely a virtio-specific issue.
On 3 October 2013 16:31, Serge Hallyn <1180...@bugs.launchpad.net> wrote:
> Quoting Vasile Dumitr
Thanks for the tip Dumitrescu,
I'll rive it a try AMD report here che result.
Regards
Il 29/set/2013 14:50 "Vasile Dumitrescu" ha
scritto:
> I added a rtl8139c netcard to the VM and connected through it by RDP -
> no more freezes.
>
> It looks like kvm does not play well with virtio network ca
VM and after a while it seems to
>> freeze, then, I connect via VNC an without doing anything the
>> communications are restored between the VM and the outside world. So i
>> can connect again with RDP.
>>
>> Even more, if i leave an open connection with VNC (minimize
an open connection with VNC (minimized because is
> more slow than RDP), connecting via RDP has no trouble and no problem of
> freeze (lost of communications) occurs.
>
> f3a97, Could you do this test and tell if you have the same experience
> than i?, If so, my bug is the same o
Hi Serge,
In order to reconnect, I have simply restarted another RDP client without
any further step required (no need to use VNC and ping, it was just a test
to check network connectivity).
On 24 July 2013 15:16, Serge Hallyn <1180...@bugs.launchpad.net> wrote:
> Quoting f3
** Description changed:
Hi,
- I recently started using KVM over VirtualBox for my Office needs. I
- setup a Windows 7 VM on KVM and started using it through remote desktop.
+ I have recently setup a Windows 7 VM on KVM and started using it through
+ remote desktop.
What happens is that,
Hi Serge,
I performed the experiment you suggested:
1) Connected with RDP client
2) Worked until it hanged
3) Successfully connected to the VM via virt-manager (RDP client still
freezed)
4) Verified that Windows is still connected to the network
5) Successfully pinged my host IP from within the V
Hi Serge,
Thanks for that.
Please find attached my VM complete xml configuration file (virsh
dumpxml).
On 12 June 2013 21:21, Serge Hallyn <1180...@bugs.launchpad.net> wrote:
> In fact that did not suffice (this is raring, not precise) - windows
> needed to reboot to reset the model=rtl8139 ni
, so it probably has nothing to do with remmina itself.
>
> Thank you!
>
>
> On 5 June 2013 14:30, Serge Hallyn <1180...@bugs.launchpad.net> wrote:
>
>> Quoting f3a97 (1180...@bugs.launchpad.net):
>> > Hi Serge,
>> >
>> > I'm invoking r
probably has nothing to do with remmina itself.
Thank you!
On 5 June 2013 14:30, Serge Hallyn <1180...@bugs.launchpad.net> wrote:
> Quoting f3a97 (1180...@bugs.launchpad.net):
> > Hi Serge,
> >
> > I'm invoking remmina from the Unity shell, not from the termin
Hi Serge,
I'm invoking remmina from the Unity shell, not from the terminal.
As regard your question: I'm connecting to the VM via RDP, not VNC (it is
much faster).
On 5 June 2013 00:07, Serge Hallyn <1180...@bugs.launchpad.net> wrote:
> Could you show the exact remmina command you were using t
Hi Serge,
Thanks for the reply.
What I meant is that I started using KVM for my virtualization needs, while I
was previously using VirtualBox. Sorry for not being clear on this point.
Yes the VM continues to run, however it is pretty annoying and can potentially
imply that for me Win 7 on KV
Public bug reported:
Hi,
I recently started using KVM over VirtualBox for my Office needs. I
setup a Windows 7 VM on KVM and started using it through remote desktop.
What happens is that, after some hours of usage, the remote desktop
connection freezes. I thought it was a remmina bug, as the it
20 matches
Mail list logo