Timeout of network interface
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all! Until today I was using OpenBSD 4.5 like KVM virtual machine on Ubuntu Hardy Heron server amd64 with KVM-64. But due to a bug that could affect to hosts with a high rate of I/O [1], I decided to update to backport of KVM-84 for Hardy heron server amd64 that solved this bug. Although with the other virtual machines that it had in the host I did not have problems, I had some problems with the installation of OpenBSD. Next I paste the output when connecting to the VM by means of serial console from the host machine. After 'mtrr: Pentium Pro MTRR support', I see a 'u' followed sometimes by a 'k', and the operating system is rebooted repetitively when arriving at this instance. - --- r...@ubuntu:/etc/modprobe.d# telnet localhost 4001 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. OpenBSD/i386 BOOT 3.02 boot booting hd0a:/bsd: 6039964+1059784 [52+336688+318896]=0x7657ec entry point at 0x200120 [ using 656008 bytes of bsd ELF symbol table ] Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2009 OpenBSD. All rights reserved. http://www.OpenBSD.org OpenBSD 4.5 (GENERIC) #1749: Sat Feb 28 14:51:18 MST 2009 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC cpu0: QEMU Virtual CPU version 0.9.1 (AuthenticAMD 686-class, 512KB L2 cache) 1.71 GHz cpu0: FPU,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3 real mem = 536375296 (511MB) avail mem = 510361600 (486MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 07/08/09, BIOS32 rev. 0 @ 0xfb4d0, SMBIOS rev. 2.4 @ 0xfbd3f (10 entries) bios0: vendor QEMU version QEMU date 01/01/2007 acpi0 at bios0: rev 0 acpi0: tables DSDT FACP APIC acpi0: wakeup devices acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat acpiprt0 at acpi0: bus 0 (PCI0) acpicpu0 at acpi0 mpbios0 at bios0: Intel MP Specification 1.4 cpu0 at mainbus0: apid 0 (boot processor) cpu0: apic clock running at 1000MHz mpbios0: bus 0 is type ISA ioapic0 at mainbus0: apid 1 pa 0xfec0, version 11, 24 pins ioapic0: misconfigured as apic 0, remapped to apid 1 bios0: ROM list: 0xc/0x8c00 pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 Intel 82441FX rev 0x02 pcib0 at pci0 dev 1 function 0 Intel 82371SB ISA rev 0x00 pciide0 at pci0 dev 1 function 1 Intel 82371SB IDE rev 0x00: DMA, channel 0 wired to compatibility, channel 1 wired to compatibility wd0 at pciide0 channel 0 drive 0: QEMU HARDDISK wd0: 16-sector PIO, LBA48, 38912MB, 79691776 sectors wd0(pciide0:0:0): using PIO mode 0, DMA mode 2 atapiscsi0 at pciide0 channel 1 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: QEMU, QEMU DVD-ROM, 0.9. ATAPI 5/cdrom removable cd0(pciide0:1:0): using PIO mode 0 piixpm0 at pci0 dev 1 function 3 Intel 82371AB Power rev 0x03: apic 1 int 4 (irq 10) iic0 at piixpm0 iic0: addr 0x18 00=d0 01=d0 02=d0 03=d0 04=d0 05=d0 06=d0 07=d0 08=d0 words 00= 01= 02= 03= 04= 05= 06= 07= iic0: addr 0x1a 00=d0 01=d0 02=d0 03=d0 04=d0 05=d0 06=d0 07=d0 08=d0 words 00= 01= 02= 03= 04= 05= 06= 07= iic0: addr 0x4c 00=d0 01=d0 02=d0 03=d0 04=d0 05=d0 06=d0 07=d0 08=d0 words 00= 01= 02= 03= 04= 05= 06= 07= iic0: addr 0x4e 00=d0 01=d0 02=d0 03=d0 04=d0 05=d0 06=d0 07=d0 08=d0 words 00= 01= 02= 03= 04= 05= 06= 07= vga1 at pci0 dev 2 function 0 Cirrus Logic CL-GD5446 rev 0x00 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) ne3 at pci0 dev 3 function 0 Realtek 8029 rev 0x00: apic 1 int 12 (irq 11), address 00:16:3e:00:00:35 unknown vendor 0x1af4 product 0x1002 (class memory subclass RAM, rev 0x00) at pci0 dev 4 function 0 not configured unknown vendor 0x1af4 product 0x1003 (class prehistoric unknown subclass 0xff, rev 0x00) at pci0 dev 5 function 0 not configured isa0 at pcib0 isadma0 at isa0 com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo com0: console pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard, using wsdisplay0 pmsi0 at pckbc0 (aux slot) pckbc0: unable to establish interrupt for aux slot wsmouse0 at pmsi0 mux 0 pcppi0 at isa0 port 0x61 midi0 at pcppi0: PC speaker spkr0 at pcppi0 lpt0 at isa0 port 0x378/4 irq 7 npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16 fdc0 at isa0 port 0x3f0/6 irq 6 drq 2 fd0 at fdc0 drive 0: density unknown fd1 at fdc0 drive 1: density unknown mtrr: Pentium Pro MTRR support u OpenBSD/i386 BOOT 3.02 boot booting hd0a:/bsd: 6039964+1059784 [52+336688+318896]=0x7657ec entry point at 0x200120 -
Re: Timeout on network interface
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2008-10-13, Stuart Henderson [EMAIL PROTECTED] wrote: There are not issues with re(4) which are being worked on which pertain to this issue. The problem mentioned by the original poster is an issue with the (emulated) RTL8139 driver provided by QEMU which KVM is derived from. The driver does not fully emulate the hw by default unless compiled with a particular define, in this case it is the timer interrupt. This needs to be fixed upstream with QEMU and then also bug the KVM developers to copy the change over to their source tree. I was looking for the bug report in Qemu but I could not find it. You have some link to be able to have a reference and track its state? No, but there's a nice post about it here. http://forums.citrix.com/thread.jspa?messageID=1343896tstart=0 OpenBSD and FreeBSD both have this defined in their respective ports trees. http://www.openbsd.org/cgi-bin/cvsweb/ports/emulators/qemu/patches/patch-hw_rtl8139_c?rev=1.4 http://www.freebsd.org/cgi/cvsweb.cgi/ports/emulators/qemu/files/rtl8139-re-patch?rev=1.1 It's peculiar that testing both Linux distributions and Windows XP, I did not have this problem using the same network card. Not really. Not all drivers for the same hardware work the same way. Thanks for the reply and the links, Stuart. I found temporarily a workaround using model=ne2k_pci with kvm. Regards, Daniel iEYEARECAAYFAkj3ChIACgkQZpa/GxTmHTd84ACeLnASR8uKIGzlDoxq/0OBx7W9 kb4AnA2SB4wtuaHcqDv9uUscL+aiJ9A2 =+n1O -END PGP SIGNATURE-
Re: Timeout on network interface
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Brad. There are issues with re(4) which are being worked on, use a snapshot instead. There are not issues with re(4) which are being worked on which pertain to this issue. The problem mentioned by the original poster is an issue with the (emulated) RTL8139 driver provided by QEMU which KVM is derived from. The driver does not fully emulate the hw by default unless compiled with a particular define, in this case it is the timer interrupt. This needs to be fixed upstream with QEMU and then also bug the KVM developers to copy the change over to their source tree. I was looking for the bug report in Qemu but I could not find it. You have some link to be able to have a reference and track its state? It's peculiar that testing both Linux distributions and Windows XP, I did not have this problem using the same network card. Thanks for your reply. Regards, Daniel iEYEARECAAYFAkjzaGYACgkQZpa/GxTmHTeyJACfTkELjl5tEyCDeS8snIuLCVXi /5UAnjiqFVE8Dbm7i/9GJswNitmZNJLP =bYNy -END PGP SIGNATURE-
Re: Timeout on network interface
On 2008-10-13, Daniel Bareiro [EMAIL PROTECTED] wrote: Hi Brad. There are issues with re(4) which are being worked on, use a snapshot instead. There are not issues with re(4) which are being worked on which pertain to this issue. The problem mentioned by the original poster is an issue with the (emulated) RTL8139 driver provided by QEMU which KVM is derived from. The driver does not fully emulate the hw by default unless compiled with a particular define, in this case it is the timer interrupt. This needs to be fixed upstream with QEMU and then also bug the KVM developers to copy the change over to their source tree. I was looking for the bug report in Qemu but I could not find it. You have some link to be able to have a reference and track its state? No, but there's a nice post about it here. http://forums.citrix.com/thread.jspa?messageID=1343896tstart=0 OpenBSD and FreeBSD both have this defined in their respective ports trees. http://www.openbsd.org/cgi-bin/cvsweb/ports/emulators/qemu/patches/patch-hw_rtl8139_c?rev=1.4 http://www.freebsd.org/cgi/cvsweb.cgi/ports/emulators/qemu/files/rtl8139-re-patch?rev=1.1 It's peculiar that testing both Linux distributions and Windows XP, I did not have this problem using the same network card. Not really. Not all drivers for the same hardware work the same way.
Re: Timeout on network interface
There are issues with re(4) which are being worked on, use a snapshot instead. There are not issues with re(4) which are being worked on which pertain to this issue. The problem mentioned by the original poster is an issue with the (emulated) RTL8139 driver provided by QEMU which KVM is derived from. The driver does not fully emulate the hw by default unless compiled with a particular define, in this case it is the timer interrupt. This needs to be fixed upstream with QEMU and then also bug the KVM developers to copy the change over to their source tree. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
Timeout on network interface
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all! Today I was testing the installation of a VM OpenBSD 4.3 on KVM in a host Hardy Heron and although I could finish to the installation and the virtual machine taking IP via DHCP and I can be connected via ssh, I obtain in the console a continuous message saying: re0: watchdog timeout I suppose that for that reason it is that the connection ssh eventually are freeze by a small time interval. I tried passing to kvm command the option model=rtl8139 and without it, and also with the option --no-acpi to disable ACPI from host, but I continue obtaining this message. Downloading a daily image of OpenBSD 4.4 I obtain the same behavior. The card is a Gigabit Ethernet RTL-8169. Can it have some problem of compatibility with OpenBSD? Somebody had the same problem and could solve? Thanks in advance. Regards, Daniel iEYEARECAAYFAkjtZYoACgkQZpa/GxTmHTftVwCfclcbfcekAb4KfaKHsBFQ7Ut2 HOEAoIwauZ+ffRma8wec2ni7np83UqxP =oOg4 -END PGP SIGNATURE-
Re: Timeout on network interface
The card is a Gigabit Ethernet RTL-8169. Can it have some problem of compatibility with OpenBSD? Somebody had the same problem and could solve? There are issues with re(4) which are being worked on, use a snapshot instead. http://clk.atdmt.com/UKM/go/111354029/direct/01/
