Updates for Proxmox VE 2.2 - including QEMU 1.3

Re: AW: Updates for Proxmox VE 2.2 - including QEMU 1.3

I have update my PROXMOX & When I try to transfer data from my NAS drive to my VM MY NETWORK of that particular VM stop working - it happens twice I then duplicate this error in my newly built proxmox is this a BUG ?
 
Re: AW: Updates for Proxmox VE 2.2 - including QEMU 1.3

What about giving us some useful details?
What is your vm config file like?
What OS in the guest?
If is M$ one, are you using virtio network type interface AND have you upgraded to the latest drivers available? (http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/bin/virtio-win-0.1-49.iso)
If is M$ one, are you using e1000 network type interface AND have you upgraded to the latest drivers available from Intel site?
 
Re: AW: Updates for Proxmox VE 2.2 - including QEMU 1.3

I am using Windows 2012 Server & Windows 7 when I try to transfer files from NAS drive or over internet like download some file using my VM after some point internet connection breaks and network goes offline..

I am not sure about upgrading drivers as I just upgrade proxmox as that's what we normally do when you release a new version as the instruction didn't state to upgrade drivers nor I have any instructions to do so and since then I am having this problem and I duplicate that in my new Proxmox machine.

Screen Shot 2012-12-28 at 8.54.25 AM.png

pve-manager: 2.2-32 (pve-manager/2.2/3089a616)
running kernel: 2.6.32-17-pve
proxmox-ve-2.6.32: 2.2-83
pve-kernel-2.6.32-16-pve: 2.6.32-82
pve-kernel-2.6.32-17-pve: 2.6.32-83
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.4-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.93-2
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.9-1
pve-cluster: 1.0-34
qemu-server: 2.0-71
pve-firmware: 1.0-21
libpve-common-perl: 1.0-40
libpve-access-control: 1.0-25
libpve-storage-perl: 2.0-36
vncterm: 1.0-3
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1
pve-qemu-kvm: 1.3-10
ksm-control-daemon: 1.1-1
 
Re: AW: Updates for Proxmox VE 2.2 - including QEMU 1.3

/var/log/messages

Dec 28 05:02:41 NOD1 kernel: device tap101i0 entered promiscuous mode
Dec 28 05:02:41 NOD1 kernel: vmbr0: port 9(tap101i0) entering forwarding state
Dec 28 05:04:57 NOD1 kernel: device tap107i0 entered promiscuous mode
Dec 28 05:04:57 NOD1 kernel: vmbr0: port 10(tap107i0) entering forwarding state
Dec 28 05:05:53 NOD1 kernel: device tap108i0 entered promiscuous mode
Dec 28 05:05:53 NOD1 kernel: vmbr0: port 11(tap108i0) entering forwarding state
Dec 28 05:05:53 NOD1 kernel: device tap108i1 entered promiscuous mode
Dec 28 05:05:53 NOD1 kernel: vmbr0: port 12(tap108i1) entering forwarding state
Dec 28 05:46:55 NOD1 kernel: vmbr0: port 11(tap108i0) entering disabled state
Dec 28 05:46:55 NOD1 kernel: vmbr0: port 11(tap108i0) entering disabled state
Dec 28 05:46:55 NOD1 kernel: vmbr0: port 12(tap108i1) entering disabled state
Dec 28 05:46:55 NOD1 kernel: vmbr0: port 12(tap108i1) entering disabled state
Dec 28 05:48:30 NOD1 kernel: device tap108i0 entered promiscuous mode
Dec 28 05:48:30 NOD1 kernel: vmbr0: port 11(tap108i0) entering forwarding state
Dec 28 05:48:30 NOD1 kernel: device tap108i1 entered promiscuous mode
Dec 28 05:48:30 NOD1 kernel: vmbr0: port 12(tap108i1) entering forwarding state
Dec 28 06:14:41 NOD1 kernel: vmbr0: port 9(tap101i0) entering disabled state
Dec 28 06:14:41 NOD1 kernel: vmbr0: port 9(tap101i0) entering disabled state
Dec 28 06:14:59 NOD1 kernel: device tap101i0 entered promiscuous mode
Dec 28 06:14:59 NOD1 kernel: vmbr0: port 9(tap101i0) entering forwarding state
Dec 28 06:25:01 NOD1 rsyslogd: [origin software="rsyslogd" swVersion="4.6.4" x-pid="1413" x-info="http://www.rsyslog.com"] rsyslogd was HUPed,
type 'lightweight'.
Dec 28 06:30:09 NOD1 kernel: vmbr0: port 9(tap101i0) entering disabled state
Dec 28 06:30:09 NOD1 kernel: vmbr0: port 9(tap101i0) entering disabled state
Dec 28 06:30:19 NOD1 kernel: device tap101i0 entered promiscuous mode
Dec 28 06:30:19 NOD1 kernel: vmbr0: port 9(tap101i0) entering forwarding state
Dec 28 06:32:41 NOD1 kernel: vmbr0: port 9(tap101i0) entering disabled state
Dec 28 06:32:41 NOD1 kernel: vmbr0: port 9(tap101i0) entering disabled state
Dec 28 06:33:31 NOD1 kernel: device tap101i0 entered promiscuous mode
Dec 28 06:33:31 NOD1 kernel: vmbr0: port 9(tap101i0) entering forwarding state
Dec 28 06:40:40 NOD1 kernel: vmbr0: port 9(tap101i0) entering disabled state
Dec 28 06:40:40 NOD1 kernel: vmbr0: port 9(tap101i0) entering disabled state
Dec 28 06:40:43 NOD1 kernel: device tap101i0 entered promiscuous mode
Dec 28 06:40:43 NOD1 kernel: vmbr0: port 9(tap101i0) entering forwarding state
Dec 28 06:56:12 NOD1 kernel: vmbr0: port 9(tap101i0) entering disabled state
Dec 28 06:56:12 NOD1 kernel: vmbr0: port 9(tap101i0) entering disabled state
Dec 28 06:56:27 NOD1 kernel: device tap101i0 entered promiscuous mode
Dec 28 06:56:27 NOD1 kernel: vmbr0: port 9(tap101i0) entering forwarding state
Dec 28 07:22:15 NOD1 kernel: vmbr0: port 9(tap101i0) entering disabled state
Dec 28 07:22:15 NOD1 kernel: vmbr0: port 9(tap101i0) entering disabled state
Dec 28 07:22:19 NOD1 kernel: vmbr0: port 8(tap100i0) entering disabled state
Dec 28 07:22:19 NOD1 kernel: vmbr0: port 8(tap100i0) entering disabled state
Dec 28 07:22:30 NOD1 kernel: vmbr0: port 10(tap107i0) entering disabled state
Dec 28 07:22:30 NOD1 kernel: vmbr0: port 10(tap107i0) entering disabled state
Dec 28 07:23:11 NOD1 kernel: vmbr0: port 11(tap108i0) entering disabled state
Dec 28 07:23:11 NOD1 kernel: vmbr0: port 11(tap108i0) entering disabled state
Dec 28 07:23:11 NOD1 kernel: vmbr0: port 12(tap108i1) entering disabled state
Dec 28 07:23:11 NOD1 kernel: vmbr0: port 12(tap108i1) entering disabled state
 
Re: AW: Updates for Proxmox VE 2.2 - including QEMU 1.3

Ok, (btw, I'm just an user, not from Proxmox team), I asked because I had a lot of networking issues time ago with M$ guests and virtio networking, and the "upgrade the driver" stuff is because new proxmox have new KVM so is wisdom to update guest KVM drivers as well (in fact a lot of problems / compatibilities have been fixed so far).
I see you use rtl8139 instead, that I never used due to poor performances (at least is what I've been told), so I've no idea about those.
At this point could be a kenerl bug, or a kernel problem with your hardware, or a kvm 1.3 problem with rtl8139.
I can suggest you to test in your new proxmox a different VM network driver, like virtio or intel e1000 if the problem persists, and please report back, this can help other users as well.
 
Re: AW: Updates for Proxmox VE 2.2 - including QEMU 1.3

tom said:
I just installed a fresh freebsd9 with success, just following this howto:
http://pve.proxmox.com/wiki/FreeBSD_Guest_Notes

(without the fix, it just hang)
Click to expand...

I have a new server and installed Proxmox 2.2

i tried to installed a fresh freebsd 9.1 amd64 on VM with no success
i used raw disk not scsi disk (it was booted but won't start)

and I have restore my backup from proxmox 2.1 to another proxmox 2.2 with success
but when I started the VM on proxmox 2.2 it won't start

note : all my VM were FreeBSD, it ran well on 2.1 but it won't run on 2.2

isit bug or what ?
 
Re: AW: Updates for Proxmox VE 2.2 - including QEMU 1.3

Hi,

I'd like to ask if bug with slow virtio with vhost=on and multiple cores on 2.6.32 guest kernel (like ubuntu 10.04.4) is fixed with qemu 1.3 ???
If anyone know, please answer.

Regards,
michu
 
Re: AW: Updates for Proxmox VE 2.2 - including QEMU 1.3

michu said:
Thank you for answer. So the only way for me is to try using backported kernel in lucid - can't upgrade distro because I still rely on squid 2.x.
Do you know if backported oneiric kernel (linux 3.0) has this bug fixed ???

Regards,
michu
Click to expand...

I am sorry, I didn´t tried this. but it should be easy to test.
 
Re: AW: Updates for Proxmox VE 2.2 - including QEMU 1.3

Is it necessary to stop all VMs and containers, install the update and reboot? Or is just running the package manager commands enough?

Thanks...
 
You must log in or register to reply here.
Top Bottom