[PVE-User] Fails to start KVM with error code 1 - what does that mean?

[Bruce B]

Hi everyone,

After changing the motherboard everything boots fine except for the KVM does
not pick IP from DHCP. VMs are fine. I tried to lunch another KVM fresh but
I get this:

May 21 13:59:41 pvedaemon 18895 starting VM 14 on node 0 (localhost)
May 21 13:59:41 qm 18896 VM 14 start
May 21 13:59:41 qm 18896 VM 14 start failed: command '/usr/bin/kvm -monitor
unix:/var/run/qemu-server/14.mon,server,nowait -vnc
unix:/var/run/qemu-server/14.vnc,password -pidfile
/var/run/qemu-server/14.pid -daemonize -usbdevice tablet -name
Centos_KVM_New -smp sockets=4,cores=1 -nodefaults -boot menu=on -vga cirrus
-tdf -k en-us -drive
file=/var/lib/vz/images/14/vm-14-disk-1.raw,if=ide,index=0,boot=on -drive
file=/var/lib/vz/template/iso/CustomCentOS-17551_32bit.iso,if=ide,index=2,media=cdrom
-m 2024 -netdev
type=tap,id=vlan0d0,ifname=vmtab14i0d0,script=/var/lib/qemu-server/bridge-vlan
-device rtl8139,mac=06:79:F9:3B:B2:D3,netdev=vlan0d0 -id 14 -cpuunits 1000'
failed with exit code 1
May 21 13:59:41 pvedaemon 18895 VM 14 start failed -



What could be going wrong? *"exit code 1"*
*
*
I am also very interested to know why my KVM doesn't pick IP. vmbr0 is still
check marked and good. I see an eth5 added that doesn't show up on list when
I add a NIC. My vmbr1 has always been off anyhow just like eth5 is now.

Thanks

[Giovanni Toraldo]

What could be going wrong? "exit code 1"
I am also very interested to know why my KVM doesn't pick IP. vmbr0 is still
check marked and good. I see an eth5 added that doesn't show up on list when
I add a NIC. My vmbr1 has always been off anyhow just like eth5 is now.

Something is probably wrong with your bridge.

Can you paste the output of:
ifconfig -a
cat /etc/network/interfaces
brctl show vmbr0

[Bruce B]

Hi Giovanni,

Thanks for the input. Here is what you asked. ****KVM number is 106.*

prox:/var/lib/vz/template/iso# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:25:90:1a:a7:74
inet6 addr: fe80::225:90ff:fe1a:a774/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:235174 errors:0 dropped:0 overruns:0 frame:0
TX packets:202323 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:27697335 (26.4 MiB) TX bytes:48171663 (45.9 MiB)
Memory:faee0000-faf00000

eth5 Link encap:Ethernet HWaddr 00:25:90:1a:a7:75
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Memory:fafe0000-fb000000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:28217 errors:0 dropped:0 overruns:0 frame:0
TX packets:28217 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:19622595 (18.7 MiB) TX bytes:19622595 (18.7 MiB)

venet0 Link encap:UNSPEC HWaddr
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

veth101.0 Link encap:Ethernet HWaddr 00:18:51:cf:df:ef
inet6 addr: fe80::218:51ff:fecf:dfef/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:40324 errors:0 dropped:0 overruns:0 frame:0
TX packets:75542 errors:0 dropped:14 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1682267 (1.6 MiB) TX bytes:4127135 (3.9 MiB)

veth102.0 Link encap:Ethernet HWaddr 00:18:51:cd:ed:11
inet6 addr: fe80::218:51ff:fecd:ed11/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:350 errors:0 dropped:0 overruns:0 frame:0
TX packets:35540 errors:0 dropped:29 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:26000 (25.3 KiB) TX bytes:1754898 (1.6 MiB)

veth150.0 Link encap:Ethernet HWaddr 00:18:51:55:bd:8b
inet6 addr: fe80::218:51ff:fe55:bd8b/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:73 errors:0 dropped:0 overruns:0 frame:0
TX packets:35302 errors:0 dropped:30 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4120 (4.0 KiB) TX bytes:1807251 (1.7 MiB)

veth151.0 Link encap:Ethernet HWaddr 00:18:51:40:46:56
inet6 addr: fe80::218:51ff:fe40:4656/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:298 errors:0 dropped:0 overruns:0 frame:0
TX packets:35390 errors:0 dropped:37 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:17924 (17.5 KiB) TX bytes:1736070 (1.6 MiB)

veth16.0 Link encap:Ethernet HWaddr 00:18:51:cf:ec:89
inet6 addr: fe80::218:51ff:fecf:ec89/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:10 errors:0 dropped:0 overruns:0 frame:0
TX packets:35282 errors:0 dropped:15 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:496 (496.0 B) TX bytes:1710404 (1.6 MiB)

veth160.0 Link encap:Ethernet HWaddr 00:18:51:61:2b:80
inet6 addr: fe80::218:51ff:fe61:2b80/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:12 errors:0 dropped:0 overruns:0 frame:0
TX packets:35170 errors:0 dropped:39 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:552 (552.0 B) TX bytes:1705076 (1.6 MiB)

veth17.0 Link encap:Ethernet HWaddr 00:18:51:08:22:ac
inet6 addr: fe80::218:51ff:fe08:22ac/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:12 errors:0 dropped:0 overruns:0 frame:0
TX packets:35272 errors:0 dropped:19 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:552 (552.0 B) TX bytes:1709958 (1.6 MiB)

veth180.0 Link encap:Ethernet HWaddr 00:18:51:fc:04:5e
inet6 addr: fe80::218:51ff:fefc:45e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:10 errors:0 dropped:0 overruns:0 frame:0
TX packets:35129 errors:0 dropped:52 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:496 (496.0 B) TX bytes:1703144 (1.6 MiB)

veth181.0 Link encap:Ethernet HWaddr 00:18:51:5d:86:5f
inet6 addr: fe80::218:51ff:fe5d:865f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:24 errors:0 dropped:0 overruns:0 frame:0
TX packets:35104 errors:0 dropped:18 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1436 (1.4 KiB) TX bytes:1702915 (1.6 MiB)

veth182.0 Link encap:Ethernet HWaddr 00:18:51:9f:98:37
inet6 addr: fe80::218:51ff:fe9f:9837/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:41 errors:0 dropped:0 overruns:0 frame:0
TX packets:35104 errors:0 dropped:27 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:10721 (10.4 KiB) TX bytes:1704136 (1.6 MiB)

veth191.0 Link encap:Ethernet HWaddr 00:18:51:68:11:bc
inet6 addr: fe80::218:51ff:fe68:11bc/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:122425 errors:0 dropped:0 overruns:0 frame:0
TX packets:157407 errors:0 dropped:49 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:31088553 (29.6 MiB) TX bytes:16278945 (15.5 MiB)

veth200.0 Link encap:Ethernet HWaddr 00:18:51:98:4d:84
inet6 addr: fe80::218:51ff:fe98:4d84/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:10 errors:0 dropped:0 overruns:0 frame:0
TX packets:34991 errors:0 dropped:12 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:496 (496.0 B) TX bytes:1696716 (1.6 MiB)

vmbr0 Link encap:Ethernet HWaddr 00:25:90:1a:a7:74
inet addr:192.168.20.20 Bcast:192.168.20.255 Mask:255.255.255.0
inet6 addr: fe80::225:90ff:fe1a:a774/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:70350 errors:0 dropped:0 overruns:0 frame:0
TX packets:36913 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:6219822 (5.9 MiB) TX bytes:12589705 (12.0 MiB)

vmtab100i0d0 Link encap:Ethernet HWaddr 7e:f6:32:bb:94:76
inet6 addr: fe80::7cf6:32ff:febb:9476/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:1708 errors:0 dropped:0 overruns:0 frame:0
TX packets:36779 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:434505 (424.3 KiB) TX bytes:2722583 (2.5 MiB)

vmtab106i0d0 Link encap:Ethernet HWaddr 1e:17:3f:a9:f8:7d
inet6 addr: fe80::1c17:3fff:fea9:f87d/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:12 errors:0 dropped:0 overruns:0 frame:0
TX packets:2679 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:2520 (2.4 KiB) TX bytes:166830 (162.9 KiB)

vmtab106i0d1 Link encap:Ethernet HWaddr c2:70:c7:0a:7a:3d
inet6 addr: fe80::c070:c7ff:fe0a:7a3d/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:10 errors:0 dropped:0 overruns:0 frame:0
TX packets:2681 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:1836 (1.7 KiB) TX bytes:167514 (163.5 KiB)

vmtab190i0d0 Link encap:Ethernet HWaddr 36:8a:45:b3:0a:34
inet6 addr: fe80::348a:45ff:feb3:a34/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:12 errors:0 dropped:0 overruns:0 frame:0
TX packets:34989 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:2520 (2.4 KiB) TX bytes:2184788 (2.0 MiB)

vmtab202i0d0 Link encap:Ethernet HWaddr c6:fb:a9:bf:24:3b
inet6 addr: fe80::c4fb:a9ff:febf:243b/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:7 errors:0 dropped:0 overruns:0 frame:0
TX packets:34992 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:2394 (2.3 KiB) TX bytes:2184812 (2.0 MiB)
*
*
*prox:/var/lib/vz/template/iso# cat /etc/network/interfaces*
# network interface settings
auto lo
iface lo inet loopback

iface eth0 inet manual

iface eth1 inet manual

auto vmbr0
iface vmbr0 inet static
address 192.168.20.20
netmask 255.255.255.0
gateway 192.168.20.1
bridge_ports eth0
bridge_stp off
bridge_fd 0

iface vmbr1 inet manual
bridge_ports eth1
bridge_stp off
bridge_fd 0


*prox:/var/lib/vz/template/iso# brctl show vmbr0*
bridge name bridge id STP enabled interfaces
vmbr0 8000.0025901aa774 no eth0
veth101.0
veth102.0
veth150.0
veth151.0
veth16.0
veth160.0
veth17.0
veth180.0
veth181.0
veth182.0
veth191.0
veth200.0
vmtab100i0d0
vmtab106i0d0
vmtab106i0d1
vmtab190i0d0
vmtab202i0d0


Your input is much appreciated.


Regards,

Post by Giovanni Toraldo

What could be going wrong? "exit code 1"
I am also very interested to know why my KVM doesn't pick IP. vmbr0 is

still

check marked and good. I see an eth5 added that doesn't show up on list

when

I add a NIC. My vmbr1 has always been off anyhow just like eth5 is now.

Something is probably wrong with your bridge.
ifconfig -a
cat /etc/network/interfaces
brctl show vmbr0
--
Giovanni Toraldo
http://gionn.net/

[Giovanni Toraldo]

eth5      Link encap:Ethernet  HWaddr 00:25:90:1a:a7:75
          BROADCAST MULTICAST  MTU:1500  Metric:1

A good start would be to fix up your network configuration, even if
you don't use that secondary network card.

You can edit:
/etc/udev/rules.d/70-persistent-net.rules

you should have a line like this:
# PCI device 0x1969:0x1048 (atl1)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:12:34:56:78:90", ATTR{dev_id}=="0x0",
ATTR{type}=="1", KERNEL=="eth*", NAME="eth5"

Change eth5 to eth1, delete any other definition than eth0.

vmtab106i0d0 Link encap:Ethernet  HWaddr 1e:17:3f:a9:f8:7d
vmtab106i0d1 Link encap:Ethernet  HWaddr c2:70:c7:0a:7a:3d

Why 2 network cards on the same bridge for VM 106?

Another hint (but maybe I'm wrong): why you have both vmtab* and veth*
interfaces? Should'nt the first be renamed to the second after a
recent proxmox update? Have you ever rebooted the host?

Everything else looks fine to me, maybe you can try to configure
manually an IP inside the VM and try to ping the host or your default
gateway?

Regards,

[Bruce B]

Thanks Giovanni.

Forcing IP down the kvm throat worked and I don't want to touch the rest as
it's long weekend and really don't like to drive to data-center if things
mess up.

At one point I added a second NIC to the KVM to test and I also restarted,
and shutdown multiple time during the process but that was no help.

I am afraid to touch the eth0 now as I said I changed the motherboard so
maybe that's why that came but I can't risk to loose GUI access at this
time.

I shall check this another day.

Thanks again for the great help.

Post by Giovanni Toraldo

Post by Bruce B
eth5 Link encap:Ethernet HWaddr 00:25:90:1a:a7:75
BROADCAST MULTICAST MTU:1500 Metric:1

A good start would be to fix up your network configuration, even if
you don't use that secondary network card.
/etc/udev/rules.d/70-persistent-net.rules
# PCI device 0x1969:0x1048 (atl1)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:12:34:56:78:90", ATTR{dev_id}=="0x0",
ATTR{type}=="1", KERNEL=="eth*", NAME="eth5"
Change eth5 to eth1, delete any other definition than eth0.

Post by Bruce B
vmtab106i0d0 Link encap:Ethernet HWaddr 1e:17:3f:a9:f8:7d
vmtab106i0d1 Link encap:Ethernet HWaddr c2:70:c7:0a:7a:3d

Why 2 network cards on the same bridge for VM 106?
Another hint (but maybe I'm wrong): why you have both vmtab* and veth*
interfaces? Should'nt the first be renamed to the second after a
recent proxmox update? Have you ever rebooted the host?
Everything else looks fine to me, maybe you can try to configure
manually an IP inside the VM and try to ping the host or your default
gateway?
Regards,
--
Giovanni Toraldo
http://gionn.net/

[Bruce B]

So, I did a fresh install of the latest Proxmox and everything is just fine.
But yet again an .iso of PBXinaFlash does not start and it gives me the same
exact error. Someone should be able to decipher this. Here it is:

s1:/var/lib/vz/template/cache# qm start 19
Invalid ID
start failed: command '/usr/bin/kvm -monitor
unix:/var/run/qemu-server/19.mon,server,nowait -vnc
unix:/var/run/qemu-server/19.vnc,password -pidfile
/var/run/qemu-server/19.pid -daemonize -usbdevice tablet -name
PBX_AptsInternational -smp sockets=1,cores=1 -nodefaults -boot
menu=on,order=cad -vga cirrus -tdf -k en-us -drive
file=/var/lib/vz/images/19/vm-19-disk-1.raw,if=ide,index=0,cache=none,boot=on
-drive
file=/var/lib/vz/template/iso/pbxinaflash-17554.iso,if=ide,index=2,media=cdrom
-m 2048 -netdev
type=tap,id=vlan0d0,ifname=tap19i0d0,script=/var/lib/qemu-server/bridge-vlan
-device e1000,mac=FE:FE:E0:88:CD:D8,netdev=vlan0d0 -id 19 -cpuunits 1000'
failed with exit code 1

The .iso is hosted here if you can test it:
http://pbxinaflash.vitel.net/1.7.5.5/pbxinaflash-17554.iso

This actually worked with an older version of Proxmox but after I upgraded
or something has changed with the .iso and it's not starting anymore.

Please try this and give me your feedback. I also tried the CentOS 5.5
version and the same issue. The .iso developers are telling me that they can
run this fine on their Proxmox.

Regards,
Bruce

Post by Bruce B
Thanks Giovanni.
Forcing IP down the kvm throat worked and I don't want to touch the rest as
it's long weekend and really don't like to drive to data-center if things
mess up.
At one point I added a second NIC to the KVM to test and I also restarted,
and shutdown multiple time during the process but that was no help.
I am afraid to touch the eth0 now as I said I changed the motherboard so
maybe that's why that came but I can't risk to loose GUI access at this
time.
I shall check this another day.
Thanks again for the great help.

Post by Giovanni Toraldo

Post by Bruce B
eth5 Link encap:Ethernet HWaddr 00:25:90:1a:a7:75
BROADCAST MULTICAST MTU:1500 Metric:1

A good start would be to fix up your network configuration, even if
you don't use that secondary network card.
/etc/udev/rules.d/70-persistent-net.rules
# PCI device 0x1969:0x1048 (atl1)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:12:34:56:78:90", ATTR{dev_id}=="0x0",
ATTR{type}=="1", KERNEL=="eth*", NAME="eth5"
Change eth5 to eth1, delete any other definition than eth0.

Post by Bruce B
vmtab106i0d0 Link encap:Ethernet HWaddr 1e:17:3f:a9:f8:7d
vmtab106i0d1 Link encap:Ethernet HWaddr c2:70:c7:0a:7a:3d

Why 2 network cards on the same bridge for VM 106?
Another hint (but maybe I'm wrong): why you have both vmtab* and veth*
interfaces? Should'nt the first be renamed to the second after a
recent proxmox update? Have you ever rebooted the host?
Everything else looks fine to me, maybe you can try to configure
manually an IP inside the VM and try to ping the host or your default
gateway?
Regards,
--
Giovanni Toraldo
http://gionn.net/

[Bruce B]

***Bingo. This sounds like a Bug to me.

I just got this working by no manipulating the KVM ID. Previously at the
create time I used to input 19 for the KVM ID and now I entered 119 and it
works just fine. Is there a limitation to KVM ID number under 100?

Can someone try this and confirm the bug?

Thanks

Post by Bruce B
So, I did a fresh install of the latest Proxmox and everything is just
fine. But yet again an .iso of PBXinaFlash does not start and it gives me
s1:/var/lib/vz/template/cache# qm start 19
Invalid ID
start failed: command '/usr/bin/kvm -monitor
unix:/var/run/qemu-server/19.mon,server,nowait -vnc
unix:/var/run/qemu-server/19.vnc,password -pidfile
/var/run/qemu-server/19.pid -daemonize -usbdevice tablet -name
PBX_AptsInternational -smp sockets=1,cores=1 -nodefaults -boot
menu=on,order=cad -vga cirrus -tdf -k en-us -drive
file=/var/lib/vz/images/19/vm-19-disk-1.raw,if=ide,index=0,cache=none,boot=on
-drive
file=/var/lib/vz/template/iso/pbxinaflash-17554.iso,if=ide,index=2,media=cdrom
-m 2048 -netdev
type=tap,id=vlan0d0,ifname=tap19i0d0,script=/var/lib/qemu-server/bridge-vlan
-device e1000,mac=FE:FE:E0:88:CD:D8,netdev=vlan0d0 -id 19 -cpuunits 1000'
failed with exit code 1
http://pbxinaflash.vitel.net/1.7.5.5/pbxinaflash-17554.iso
This actually worked with an older version of Proxmox but after I upgraded
or something has changed with the .iso and it's not starting anymore.
Please try this and give me your feedback. I also tried the CentOS 5.5
version and the same issue. The .iso developers are telling me that they can
run this fine on their Proxmox.
Regards,
Bruce

Post by Bruce B
Thanks Giovanni.
Forcing IP down the kvm throat worked and I don't want to touch the rest
as it's long weekend and really don't like to drive to data-center if things
mess up.
At one point I added a second NIC to the KVM to test and I also restarted,
and shutdown multiple time during the process but that was no help.
I am afraid to touch the eth0 now as I said I changed the motherboard so
maybe that's why that came but I can't risk to loose GUI access at this
time.
I shall check this another day.
Thanks again for the great help.

Post by Giovanni Toraldo

Post by Bruce B
eth5 Link encap:Ethernet HWaddr 00:25:90:1a:a7:75
BROADCAST MULTICAST MTU:1500 Metric:1

A good start would be to fix up your network configuration, even if
you don't use that secondary network card.
/etc/udev/rules.d/70-persistent-net.rules
# PCI device 0x1969:0x1048 (atl1)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:12:34:56:78:90", ATTR{dev_id}=="0x0",
ATTR{type}=="1", KERNEL=="eth*", NAME="eth5"
Change eth5 to eth1, delete any other definition than eth0.

Post by Bruce B
vmtab106i0d0 Link encap:Ethernet HWaddr 1e:17:3f:a9:f8:7d
vmtab106i0d1 Link encap:Ethernet HWaddr c2:70:c7:0a:7a:3d

Why 2 network cards on the same bridge for VM 106?
Another hint (but maybe I'm wrong): why you have both vmtab* and veth*
interfaces? Should'nt the first be renamed to the second after a
recent proxmox update? Have you ever rebooted the host?
Everything else looks fine to me, maybe you can try to configure
manually an IP inside the VM and try to ping the host or your default
gateway?
Regards,
--
Giovanni Toraldo
http://gionn.net/

[Dietmar Maurer]

ID 0-100 are reserved for the system - you cant use them.

From: pve-user-***@pve.proxmox.com [mailto:pve-user-***@pve.proxmox.com] On Behalf Of Bruce B
Sent: Freitag, 27. Mai 2011 23:15
To: Giovanni Toraldo; proxmoxve (pve-***@pve.proxmox.com)
Subject: Re: [PVE-User] Fwd: Fails to start KVM with error code 1 - what does that mean?

***Bingo. This sounds like a Bug to me.

I just got this working by no manipulating the KVM ID. Previously at the create time I used to input 19 for the KVM ID and now I entered 119 and it works just fine. Is there a limitation to KVM ID number under 100?

Can someone try this and confirm the bug?

[Bruce B]

Well, the previous versions allowed me to create them. In fact I had a bunch
them under 20. Petty there are no warnings for this and one has to find the
hard way. The GUI shouldn't even allow them.

Thanks for the clarification.

ID 0-100 are reserved for the system – you cant use them.
*Sent:* Freitag, 27. Mai 2011 23:15
*Subject:* Re: [PVE-User] Fwd: Fails to start KVM with error code 1 - what
does that mean?
***Bingo. This sounds like a Bug to me.
I just got this working by no manipulating the KVM ID. Previously at the
create time I used to input 19 for the KVM ID and now I entered 119 and it
works just fine. Is there a limitation to KVM ID number under 100?
Can someone try this and confirm the bug?