Re: [qubes-users] Cannot boot new HVM from cdrom. What is the new command?
Thanks, Unman and Ivan.. I ended up trying: qvm-start --cdrom=dom0:/dev/sr0 win7 ..and it worked, since that's where my CD drive was mounted as. I'll give the suggested syntax a try as well, and imagine it will succeed also. The transition from Qubes 3.2 to 4.0 has been full of hiccups both large and small due to various scattered system changes like this one, and I appreciate the assistance here. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/e1904a55-e27d-4703-b79c-e890a72c59ac%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Cannot boot new HVM from cdrom. What is the new command?
On 11/4/18 9:25 PM, Otto Kratik wrote: Previously when creating a new Windows HVM on Qubes 3.2, to boot from a physical CD in the physical CD drive I would do: qvm-start --cdrom=/dev/cdrom win7 When I try that in Qubes 4.0, I get an error that starts with "Traceback" and ends with "Not enough values to unpack (expected 2, got 1)." What am I doing wrong? What is the new command to make this work in Qubes 4? The following command should work: qvm-start --cdrom=dom0:/dev/cdrom win7 (and yes, the error message is cryptic). -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/0ba43017-5be6-0695-83f6-4617bc5d29bb%40maa.bz. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Cannot boot new HVM from cdrom. What is the new command?
On Sun, Nov 04, 2018 at 11:25:49AM -0800, Otto Kratik wrote: > Previously when creating a new Windows HVM on Qubes 3.2, to boot from a > physical CD in the physical CD drive I would do: > > qvm-start --cdrom=/dev/cdrom win7 > > When I try that in Qubes 4.0, I get an error that starts with "Traceback" and > ends with "Not enough values to unpack (expected 2, got 1)." > > What am I doing wrong? What is the new command to make this work in Qubes 4? > This works for me, specifying the attached domain: qvm-start win7 --cdrom=dom0:/dev/cdrom unman -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20181105140052.7lso5fbdkqg42ouq%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Cannot boot new HVM from cdrom. What is the new command?
Previously when creating a new Windows HVM on Qubes 3.2, to boot from a physical CD in the physical CD drive I would do: qvm-start --cdrom=/dev/cdrom win7 When I try that in Qubes 4.0, I get an error that starts with "Traceback" and ends with "Not enough values to unpack (expected 2, got 1)." What am I doing wrong? What is the new command to make this work in Qubes 4? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/f991bcb7-633d-4251-837c-bfd795dc4402%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.