xen-bugs
[Xen-bugs] [Bug 1773] new 3.0.0 kernel cannot connect to network, Device
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1773
------- Comment #4 from johneed@xxxxxxxxxxx 2011-07-29 08:28 -------
Konrad. tell me is tun/tap one module or two? I believe it is just tun.
idella@gentoo64 ~/bin $ Error: Device 0 (vif) could not be connected. Hotplug
scripts not working.
idella@gentoo64 ~/bin $ uname -r
3.0.0-gentoo-amd64
idella@gentoo64 ~/bin $ lsmod
Module Size Used by
tun 21662 0
btrfs 847756 3
crc32c 3283 1
libcrc32c 1518 1 btrfs
ext3 199358 3
jbd 86140 1 ext3
reiserfs 346240 2
snd_hda_codec_realtek 334560 1
snd_hda_intel 31730 5
snd_hda_codec 102232 2 snd_hda_codec_realtek,snd_hda_intel
nouveau 916341 2
snd_hwdep 9769 1 snd_hda_codec
snd_pcm 122648 3 snd_hda_intel,snd_hda_codec
snd_timer 33458 2 snd_pcm
snd 99724 14
snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
ath5k 204327 0
ath 23697 1 ath5k
r8169 62385 0
ttm 96345 1 nouveau
drm_kms_helper 41722 1 nouveau
mxm_wmi 2336 1 nouveau
wmi 13045 1 mxm_wmi
sp5100_tco 7741 0
snd_page_alloc 12351 2 snd_hda_intel,snd_pcm
ohci_hcd 50991 0
xen_evtchn 8228 1
I have guests by the dozens. Only try it on a couple of them, try using two -
three methods.
1. import via virtinst in virt-manager some established vms.
Using the gentoo xenkernel, all works well.
Start the vm. The time-out period is a bout a minute or so. That might be set
in /etc/xen/xen-config.sxp; not sure.
2. Conventional idella@gentoo64 ~/bin $ sudo xm create Lenny.com.cfg
It is listed in virt-manager, I unpause it. It gets lost and doesn't find
grub.
3. idella@gentoo64 ~/bin $ sudo xm create -c Lenny.com.cfg
Using config file "/etc/xen/Lenny.com.cfg".
xenconsole: Could not read tty from store: No such file or directory
These last two are consistent. They are missing finding a console
Back to the first. Here is the standard err msg in the little window;
Error starting domain: POST operation failed: xend_post: error from xen daemon:
(xend.err 'Device 0 (vif) could not be connected. Hotplug scripts not
working.')
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 45, in
cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/engine.py", line 959, in asyncfunc
vm.startup()
File "/usr/share/virt-manager/virtManager/domain.py", line 1118, in startup
self._backend.create()
File "/usr/lib64/python2.7/site-packages/libvirt.py", line 457, in create
if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: POST operation failed: xend_post: error from xen daemon:
(xend.err 'Device 0 (vif) could not be connected. Hotplug scripts not
working.')
Commenting out vif in Leny.com.cfg
idella@gentoo64 ~/Documents $ sudo xm create Lenny.com.cfg
Using config file "/etc/xen/Lenny.com.cfg".
Error: Device 51713 (vbd) could not be connected. Path closed or removed during
hotplug add: backend/vbd/17/51713 state: 1
Let's do a dump via virsh. I shall put it in an attachment.
Also the Lenny.com.cfg.
It appears there are two current deficits;
console and vif device.
Thanks for replying. Please keep it up.
--
Configure bugmail:
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Xen-bugs] [Bug 1773] New: new 3.0.0 kernel cannot connect to network, bugzilla-daemon
- [Xen-bugs] [Bug 1773] new 3.0.0 kernel cannot connect to network, Device 0 (vif), bugzilla-daemon
- [Xen-bugs] [Bug 1773] new 3.0.0 kernel cannot connect to network, Device 0 (vif), bugzilla-daemon
- [Xen-bugs] [Bug 1773] new 3.0.0 kernel cannot connect to network, Device 0 (vif), bugzilla-daemon
- [Xen-bugs] [Bug 1773] new 3.0.0 kernel cannot connect to network, Device 0 (vif), bugzilla-daemon
- [Xen-bugs] [Bug 1773] new 3.0.0 kernel cannot connect to network, Device 0 (vif), bugzilla-daemon
- [Xen-bugs] [Bug 1773] new 3.0.0 kernel cannot connect to network, Device 0 (vif),
bugzilla-daemon <=
- [Xen-bugs] [Bug 1773] new 3.0.0 kernel cannot connect to network, Device 0 (vif), bugzilla-daemon
- [Xen-bugs] [Bug 1773] new 3.0.0 kernel cannot connect to network, Device 0 (vif), bugzilla-daemon
- [Xen-bugs] [Bug 1773] new 3.0.0 kernel cannot connect to network, Device 0 (vif), bugzilla-daemon
- [Xen-bugs] [Bug 1773] new 3.0.0 kernel cannot connect to network, Device 0 (vif), bugzilla-daemon
- [Xen-bugs] [Bug 1773] new 3.0.0 kernel cannot connect to network, Device 0 (vif), bugzilla-daemon
- [Xen-bugs] [Bug 1773] new 3.0.0 kernel cannot connect to network, Device 0 (vif), bugzilla-daemon
- [Xen-bugs] [Bug 1773] new 3.0.0 kernel cannot connect to network, Device 0 (vif), bugzilla-daemon
- [Xen-bugs] [Bug 1773] new 3.0.0 kernel cannot connect to network, Device 0 (vif), bugzilla-daemon
- [Xen-bugs] [Bug 1773] new 3.0.0 kernel cannot connect to network, Device 0 (vif), bugzilla-daemon
- [Xen-bugs] [Bug 1773] new 3.0.0 kernel cannot connect to network, Device 0 (vif), bugzilla-daemon
|
|
|