search for: slack12

Displaying 4 results from an estimated 4 matches for "slack12".

Did you mean: slack1
2007 Sep 26
1
Install ubuntu/fedora like DomU under Slack12 Dom0.
Hi! I have XEN 3.1 with slack12 dom0. This one work correctly. I would want install ubuntu or fedora like domU possibly from iso or cd. I see some wiki but is not clear. You have some link to advise to me? TNX Best _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lis...
2007 Sep 24
1
XEN....a very big problem :D
Hi! My problem with xen isn''t finished. The terrible situation is next: Under Slack12 work only XEN 3.0.2 version. This one boot....xen 3.1, 3.0.3 and 3.0.4 don''t boot....ever and ever the same error (I try to recompile 3.1 some times....I used others versions prebuilded and however don''t work...): VFS: Cannot open root device "hda5" or unknown-block(...
2008 Mar 05
1
[Lguest] networking in lguest: strange error: lguest: Guest moved used index from 6 to 256
...48 > > /usr/src/linux/arch/i386/boot/bzImage root=/dev/vda rw > > > > The init script files try to do a DHCP. It doesn't work (I do'nt have a > > DHCP server). > > > > If in the host I try to configure the eth0, lguest crashes strangely: > > root at slack12:~# ifconfig eth0 192.168.19.5 > > root at slack12:~# lguest: Guest moved used index from 6 to 256 > > Damn. This is fixed in Linus' tree, but I've reproduced it here for 2.6.24. > > It's non-trivial to repair, unfortunately (2.6.25 has a complete > reset > in...
2008 Mar 05
1
[Lguest] networking in lguest: strange error: lguest: Guest moved used index from 6 to 256
...48 > > /usr/src/linux/arch/i386/boot/bzImage root=/dev/vda rw > > > > The init script files try to do a DHCP. It doesn't work (I do'nt have a > > DHCP server). > > > > If in the host I try to configure the eth0, lguest crashes strangely: > > root at slack12:~# ifconfig eth0 192.168.19.5 > > root at slack12:~# lguest: Guest moved used index from 6 to 256 > > Damn. This is fixed in Linus' tree, but I've reproduced it here for 2.6.24. > > It's non-trivial to repair, unfortunately (2.6.25 has a complete > reset > in...